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
e3d998cb858bd473cb98b8c9f9a550d3b3dfb324b6e4c02e4b7a3119ef6f0ba3
dd7769f64c81f33f9a8d194f940dff2a857e1d701c8e37190bb90a65140938c5
e9f19e26dbba53565719b98b2745ac6aa3c95a4d4cc3ec2651007a524857eb2b
53d38500d341aaf227855139257bc52bcd59a111086c3041df37aa5ae3b32fc4
7d1a7c821554f9850b06949a3e9afe7f410e2a55d1a7d197f1cdc23c2ed84d9f
56466837e6b66acd90d642251ae525f8b26057778b684bab6ea9641f752180b8
6b635583794b7fab66b15fcc5eda68a1d1362f5c935869d56293a681f1725e25
b5a40d198e3790cb46e8e79b96c50d09d6af53212b7b5137333029584cc0484f
5ef0cdbc8c845d7aea22b2795c8413d6035c013e6b066dd0a7deb3dbcae0d54b
2fa699f7fe1e81c267c1b0c77fdbe01c2b4564bcfa9292162cbcfd5247cd5926
b050293bc84440387f35e286594dea38a33e9069ce638c9b4130383ebbe42b25Trust 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 968377 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 adf934709ef17884b1c10ea84b4dbcde953c6d28a4fc93bad72bf300a98e9219; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / adf934709ef17884b1c10ea84b4dbcde953c6d28a4fc93bad72bf300a98e9219, and the block's
timestamp proves the page looked this way at or before that time.