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
c7e60b2a8dbff03012150b38e68f7847ccec0b219ccef5ef63f29c1242869210
d3e43fc310944bbfe4f3dfd2b69262cc2e3dd7c406cf60e559f68616ed7c4d54
0681b153a0acce8a27796f6e5c9798628160de33644ac29e015ac9ed49a5f4e6
f276780c3aed18f93104e5eaedb77075e89a36aa3da527f6c665f2909401a243
333a2729bc913809b85b11bb41d7322d8e1bff6d035ac72f1bce23c4827cb825
dc5f2bb2bb6572618190ee5e78ed85c4d7115ec2709aa1d39fff8bb0679e16bc
5dfcd12c0d6a8c84394b7b3fbe21dc2b0e2438a4e368c265b4f55d257b09545a
bf7a6ddb249a5a8251ed534ef71ce296e4f1f38828f78b6017475ac19f1cf200
2ca879e1d06aedb8b4855cfe8879b5fbb490faaeb4a0be9f76b358a94ca8ec7d
9a6cdef765455f9a0dc2b6f79e2a99367e70530900b4aaaeafd4a679b9f2eb4a
9048953b59167624ab44a1101b57d604af4a6fa6d13e4fbf73abedfd28d1001aTrust 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 970216 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 bef4440ef3224438edfda6632d2ba5e8cc17aebd81a5f588b84f21c5d80ea0f2; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / bef4440ef3224438edfda6632d2ba5e8cc17aebd81a5f588b84f21c5d80ea0f2, and the block's
timestamp proves the page looked this way at or before that time.