A library that cannot burn
This site hosts nothing. Every document below lives inside the Cardano blockchain. Your browser queries the public ledger, rebuilds the bytes, and verifies every hash before showing you a single word — and shows you each request it makes while doing it.
Not a walled garden — anyone’s scrolls, channels, and registries resolve here.
- 🔍Verify, don’t trustSHA-256 recomputed locally against an on-chain commitment.
- 🌐Hosts nothingThe page is a lens. Your browser does the querying.
- ⚡Zero dependenciesOne self-contained file. No build, no CDN, no servers of record.
The Stacks
The on-chain catalog, merged with a built-in shelf of known scrolls.
- Pointlocate on chain
- Fetchpull raw data
- Rebuildassemble bytes
- VerifySHA-256 seal
- Renderonly if proven
Trust log — every request this page makes
How this room works
The trust model is part of the interface — nothing here asks you to take its word for it.
Verify, don’t trust
Each scroll carries an on-chain SHA-256 commitment. This page recomputes it from the reconstructed bytes, locally, every time. A mismatch renders nothing. HTML scrolls open in a fully sandboxed frame: hash-verified is not the same as safe-to-execute, so scripts never run.
Three forms of stone
- Lock — the whole file in one unspendable UTxO datum; in the live ledger state forever.
- Chain — any size, as bare metadata transactions listed by a locked manifest. spec
- Pages — the original CIP-25 page NFTs (the Bible, the Constitutions); read forever, superseded for writing.
Write your own
The protocol is open, tested, and implementable by strangers: the repository — minting tools, spec, conformance vectors. Start with the per-media-type guide, read the tutorial scroll above (it lives on-chain), or launch a publisher channel like BEACN Leaks — a byline nobody can forge.
Your trust anchors
Data source (Koios-compatible base URL; first that answers wins)
Registry head (the on-chain catalog this library reads)