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
9fb57258168c49557dd1a3f9fcbd492a44b22c083bc0455a0888a8c13e6db4c0
0aaa19bc63ed8d79ea24e22c91cc94397eaeef10fd04aed7e183d7e44a926485
cde37219df9e4b567f6ab2748be8f24d815ac4591571473efd6b5c06c0a6115a
7ea666922c046fc7ec922176b03bfdc6b97cd4cb70b83a44d81826bc74958e83
e79083ba3d2001185568067673b06f274b448e08a60e481af0e8da7127653324
f743bbd6dea2eec7a4b948463a9b0d15927f1ad6fa9c3e3131006165f34a24ba
31c0f40486168ea7a3383ce6d148212a4f713af3bf281f65106dece592de67e8
5f415db9df8efc2327d52d99108d1410c2e4ba40a85484b5478cf6b714fb242c
90bee833363b81bdb85a4d96be0c6fa1ec6a4c905bf3067e845a9ae09b0a8920
b36215618cecd53bb1bdf67af91ed26cb1828c5ed10509b271e83233fd58300d
87dae176bab870f252cb61d583bb6dda3a6b5be9884243497d283549ec419d5aTrust 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 965859 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 60c1893cbb3dec038e52f779a529022879abbbc94b1074417e6ef33e52569b40; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 60c1893cbb3dec038e52f779a529022879abbbc94b1074417e6ef33e52569b40, and the block's
timestamp proves the page looked this way at or before that time.