Skip to content

docs: add developer-facing litepaper (EN)#13

Merged
satyakwok merged 1 commit into
mainfrom
feat/dev-litepaper
Jun 3, 2026
Merged

docs: add developer-facing litepaper (EN)#13
satyakwok merged 1 commit into
mainfrom
feat/dev-litepaper

Conversation

@satyakwok

Copy link
Copy Markdown
Member

What

Adds a litepaper — a short, human-readable developer on-ramp, distinct from the whitepaper.

  • Whitepaper = engineer-auditable spec (BFT proofs, performance model, adversarial bounds, failure handling). For people who verify.
  • Litepaper = the 5-minute read that tells a developer whether Sentrix is worth their time. For people deciding.

Approach

Dev-focused, ~5 pages. Opens on the strongest honest hook — "You already know how to build on Sentrix": Solidity compiles unchanged, and viem already ships Sentrix as a built-in chain (import { sentrix } from "viem/chains"). Then:

  • Why another L1? — framed as three properties a builder can check in an afternoon, not an unverifiable TPS number.
  • What you can build today — tooling table (MetaMask / Hardhat / Foundry / explorer / faucet / npm).
  • How it works without the proofs — Voyager BFT in plain language ("final the moment it commits").
  • SRX in 60 seconds — tokenomics table.
  • Run it yourself — 3-line clone + build.
  • Where things stand — honest live / testnet / shipped-not-activated status.

Accuracy

Every specific cross-checked against the internal chain reference + the whitepaper: chain IDs 7119/7120, SRX 8-decimal, 315M cap, 63M premine, reward-to-precommitters, 50% fee burn. No fabricated numbers; positioning stays dev-focused factual (no RWA framing).

Files

  • sentrix-litepaper-en.md — source
  • sentrix-litepaper-en.html / .pdf — pandoc-rendered
  • README.md — manifest updated
  • .gitattributes — pins *.pdf binary

ID translation can follow once the EN voice is approved.

A short, human-readable on-ramp distinct from the whitepaper. The whitepaper
is the engineer-auditable spec (BFT proofs, performance model, failure
handling); the litepaper is the 5-minute read that tells a developer whether
Sentrix is worth their time.

Dev-focused, ~5 pages: opens on the strongest honest hook (Solidity compiles
unchanged, viem already ships Sentrix as a built-in chain), then why-another-L1
framed as three checkable properties (real EVM via revm, open-source single-Rust
node, economics fixed in code), what you can build today, consensus without the
proofs, SRX in 60 seconds, run-it-yourself, and an honest live/testnet/pending
status section.

All specifics cross-checked against CHAIN_INFO_REFERENCE + the whitepaper:
chain IDs 7119/7120, SRX 8-decimal, 315M cap, 63M premine, reward-to-precommitters,
50% fee burn. Positioning stays dev-focused factual — no fabricated numbers,
no RWA framing. md source + pandoc-rendered html + pdf. Adds .gitattributes
(*.pdf binary) to pin binary handling for the committed PDFs.
@coderabbitai

coderabbitai Bot commented Jun 3, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 613dbcfa-b986-4256-990d-80d154d78279

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/dev-litepaper

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@satyakwok satyakwok merged commit 5f87335 into main Jun 3, 2026
8 checks passed
@satyakwok satyakwok self-assigned this Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant