Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — 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
7c57fec7553fe0ba923894d242271196a4d6b829e3cad8a862f237effd411989
8186234e5759d01e0a0ae638ed231eed3c5f1c8ee2017ce096373286587688f4
eb83f2a36d82e36831285f5644e3a9b3adb042c874e5a333713a6faa0de9cdb8
717eca220e786ed7f238e51f3ab119cd44f19b448c7562469ea86367b5c343f6
0a83cb6f56099350a7904a93a73b43161c2d44a0deb911fecf697ba9f1548a9d
f6294ee672897ecdd9b6be685f474ba1e393619bf5a5b8db88a4bb674e351f72
af05d5057dd440413195c4ee7d7c93225038c8ccf103e0d9ab2c0e55fe279ca3
07ba563b671d43e58f3faf147d0ce069f7f85285eddfe74ad8aa2e148b138818
04cd92dc45130266f315cc32f9335cdabb75293a99b2f8460256f6094e82e02f
d1d66d47837cee0e59c86af15567832a595f9fc7df22fcc8f9b501722b503173
a6084c86b0e886744e0376ab25b5c3de3733af9fc978b65cc24332ba43af0dc0
c2482e49e290beff7c8853a511bf3c0053e51af07d2671bf56a74e59e88f6471
847df203022830fecd50b289ed75b9e103b67267c9e422557e38a03e9776e84c
7bd751b7b9eccd5a655bf46d6a3cf118b6be8da368e6f1497c9a1b21303641b3
8518a222ae6dd42a35350739684b0d93633fd0e26540a34c9cac307e9bbd999bTrust 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 965083 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 1481ab74567db8b0b86f755b75ebd883fbb5e45da629677375c736d4e9eab84b; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1481ab74567db8b0b86f755b75ebd883fbb5e45da629677375c736d4e9eab84b, and the block's
timestamp proves the page looked this way at or before that time.