SERVED FROM BLOCKCHAIN STATE
jOhNCHAIN
This website has no server. The page you are reading is stored as bytes in a blockchain.
Connected to the chain…
Every website you've ever visited lived on a server. A computer, somewhere,
with a file on its disk. Someone can edit that file. Someone can delete it.
Someone can change what it says without anyone knowing.
This page is different. The HTML you are reading right now — these
exact words, this exact styling — is stored as bytes inside a
cryptographic Merkle trie. It was committed to the
chain by a signed transaction, verified by BFT consensus, and frozen into a
block. There is no file. There is no disk. There is only the chain.
The block this page lives in
loading…
The state root that commits this page's bytes
loading…
How is this even possible?
- The page's HTML is split into chunks and written to a smart contract's
storage on the jOhNCHAIN blockchain.
- Each chunk is a key-value pair in a sparse Merkle trie — the
same data structure that commits account balances and nonces.
- The trie produces a single state_root —
a hash that cryptographically commits to every byte of this page.
- When your browser requests this page, the node reads the bytes from
the trie and serves them. The node is a relay, not the source of
truth. The chain is the source of truth.
- To change this page, you submit a new signed transaction. The old
version is permanently frozen in the chain's history. You can never
silently edit it.
What this could be used for
- Hosting that can't be seized. No single server to raid, no
domain to seize, no hosting provider to pressure. Content persists as
long as one node runs the chain. Relevant for media hosting under
hostile regimes or operators who face infrastructure seizures.
- Whistleblower evidence publishing. A document committed to a
state root cannot be deleted, altered, or backdated by anyone. Combined
with a Tor layer, you could host an entirely anonymous, serverless
site — no server to raid, no domain to seize, no identity to
trace, and the content is permanent.
- Terms of service that can't be silently rewritten. Publish
the ToS on-chain. The version a user agreed to at block 47 is frozen
forever. No retroactive edits.
- Scientific priority claims. Hash a preprint or dataset and
commit it before publication. Proves you had the result first,
cryptographically, without relying on a trusted timestamp server.
- Verifiable software supply chains. Publish dependency hashes
on-chain at build time. If a dependency is later compromised, the
on-chain record proves what the original was.
This page is a demonstration. The above are directions the concept
could extend toward, not claims about the current implementation.
This is the same chain that evolves
cryptographic S-boxes by natural selection and that you can
explore block by block. It's one blockchain
doing three things that each seem impossible in different ways.