Appendix D
Annotated whitepaper
A guide to the critical reading of the Bitcoin Hyper whitepaper (v. 04/01/2026). Based on Appendix D of Michele Stefanelli's book.
How to read the whitepaper: A whitepaper is a technical marketing document, not a formal specification. It should be read with critical attention: distinguishing independently verifiable claims from promises, identifying the gaps, and comparing it against the team's subsequent updates.
An active-reading framework
Read the structure
Before going into the detail, map out the structure of the document: what are its central theses? Which sections are missing? A whitepaper that says nothing about data availability or the decentralisation of the sequencer is avoiding awkward subjects.
Identify the claims
Distinguish between: (a) independently verifiable technical claims (“the SVM supports parallel execution”), (b) contestable claims (“Bitcoin-level security”), and (c) future promises (“we will decentralise the sequencer”).
Compare against the updates
The whitepaper is a static snapshot. The team's updates (blog, Twitter, forums) contain more recent information. If an update contradicts the whitepaper, which is the current version?
Gap analysis
What is left unsaid? Silence on DA, on forced inclusion, on the proving system, and on a specific timeline for decentralisation — these are just as relevant as the information that is present.
Key claims — a critical analysis
“Bitcoin-level security for assets on Hyper”
Partially accurate. Finality is anchored to Bitcoin. The custody of the BTC within the bridge, however, is federated/centralised at launch. If the bridge is compromised, the assets are at risk regardless of the security of Bitcoin itself.
⚡ Partially accurate“Drop-in compatibility with Solana: same code, same tooling”
Broadly accurate for the core functionality. The SVM runtime is the same. Anchor and the Solana CLI work. Differences: fees are paid in $HYPER rather than SOL, and some Solana system programs may not be available in identical form.
✓ Broadly accurate“Higher throughput thanks to the SVM/Sealevel”
The architecture is sound: Sealevel allows parallel execution. No benchmarks have been published for Bitcoin Hyper specifically. Actual throughput will also depend on the DA layer and on the sequencer.
◎ Architecture is sound“Mainnet expected in Q4 2025”
Not met. As at 28 April 2026 the mainnet was not yet live. The delay is attributable mainly to the completion of the audits and to the stabilisation of the bridge — as any prudent analyst would expect.
✗ Not met“Security audit before the TGE”
A public commitment not yet honoured as at 28 April 2026. No public audit report has been identified. To be monitored as a critical signal.
○ To be verified📖 For the full reading
Appendix D of Michele Stefanelli's book «Due Diligence of a Layer 2 – The Bitcoin Hyper Case» contains the full guide to reading the whitepaper: structure, claims analysed chapter by chapter, gap identification and synthesis. Go to the book →