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
d97b8eeff91e0d549f25c4697570f9db688b22bfc998002a2c736ba7a9aae10c
59fecc93d83ac4b7fc1bd91d826a18d643c04fc67b5854f4602e7a4bd119c130
e8beb2ca7255267b01d7caec30b9f9de3dedb7544964df2bac48e162aa62d873
3affe93d1edaefbb06d429444bcaa5a163de4dca41fe198a0348758366eab535
df7454129a9b6d4147368ee402c9f40804dddf9b13a66169ca42b92ccf83a886
626eec410d5b86f5e7c1921bc4476397d10fbbfc311419e1d5897a5f39297566
3dd6d5a8b5768aea20bcd070991acc6bf56b30d4383e0ae7a972ae0de071e527
8854830c4f8e25ffa04792e9a4dda4f332602ce723d6fc6268bb26f22595adb0
efcd52b09e30b7e59dfab0c1db7f0a284b5ad78a62cfbeccfa170f4d1a259e5f
27920dcfd7cba53bbc8acd67245988a4cc47667c546d4911a0dbbd77820cdf08
d0f8ab88170a2795798b45e2af57665bc4ac400481f545c86b67e9a660f0c7b6
1ffbe888a8f4be1119911f1e7af72f7638d782b52fc71313bed459b4f1392abf
b924549b58a133c9d2fa206306146be612548b15fa9b16cf81340f8c131793b7
818b84aa64d8de6e3981dd2bdc4bcb80142a0663dfc6e946b71a80f87ed96266
a44f0e91e341e956c2866e2307a645ab0ec66a3f5fa11930b7da5aabf96c2e6c
0f9d6debbd5b4408f8764ef0560f0bdcf002000731ddad37287c62e95607668f
3a446b9129dc63d89146e78d884d34f4be7a472448bdc4282beead8b9a20fa4c
72df84db0f98004d48b2362bfccdfdc92dd8fa5206a1c7ee838656d00a39fb6e
411f750d3757fb2da5bd8d50a62141c99d3c00d64899ddbd1fdb7dd4c3f55edeTrust 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 965016 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 997087be5051e6055e57255ce397c56a86eafc47a2cc85f61141285a6bdfd4c1; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 997087be5051e6055e57255ce397c56a86eafc47a2cc85f61141285a6bdfd4c1, and the block's
timestamp proves the page looked this way at or before that time.