Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — bsv.cx
Rendered page — archived HTML, sandboxed · click to collapse
Html-only render: no scripts or original assets, so it may look unstyled. Not the live page; not endorsed by bsv.cx. ⤢ full screen
WhatsOnChain · Banana Blocks
SPV proof & how to re-verify it yourself
b437a2c8d34e13e631b4bfe7ec6900b82db33587d0ad0ddfce75f32d5539bf79
0244ad4e822ccb4dd03c22fcd70295f3aaea04515aa044820a396a781d63abc1
4e48de3fa571765a6d79c02055fddaa12b3cecf46eb64413ccb525a3092b814d
40063fb1cf5ab0150245e0f403cca1b5aa2c68425f15dc18ee22a7e6823f7818
528c59b1257e46d8d4dc37932e872e128f5f8d8a2d8a86eae2dc7281dd2a715c
16fb6a7b93e05ff58b9bef94e8b077a058d47f24becc514ee4931f54211d59f0
939a2ef66f377007c56895a53051dcdac41f053559096212283b021a8b4c0f5d
74c2766dd28cc4ddcb3bbd609d136c3533c11e495e46768edcac1b361e2dcadb
603ed183ab8e70c0f011c716e4bd7e818e4aefe7a3734951fe0874f95dad08ea
ecb7f022938e1657652777bf138b8cb7aec2a98a6c16a048556efd2239843a8eTrust no one: double-SHA256 the txid up this branch — at each level your hash goes
left when index is even, right when odd, halving the index each step —
to get the block Merkle root, then confirm that root is the header at height 965808 on
any block-header source you trust. We verified it against headers we run ourselves; you
verify against yours — no explorer, and no bsv.cx, in the trust path.
Prefer to check it against a second independent source? Paste these fields into
our public verifier (POST /spv/verify) — it folds the root itself and
checks it against headers we sync, so it can only ever make a bad proof fail.
Or take it to your own tools in the ecosystem standard format:
BEEF (BRC-62, tx + proof) ·
BUMP (BRC-74, path only). Any @bsv/sdk client verifies
these with no bsv.cx-specific code — Transaction.fromHexBEEF(hex).
Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — so from your saved files you can recompute every hash and match the transaction's OP_RETURN yourself, with no dependence on bsv.cx ever being online.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 1cc3c859a399dd68ee128b3816dfa5fceb7a7343c8683ca69b2ba29ef6f8224d; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1cc3c859a399dd68ee128b3816dfa5fceb7a7343c8683ca69b2ba29ef6f8224d, and the block's
timestamp proves the page looked this way at or before that time.