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
18e397c037f6b0d39368a73ebee881c5e764bde2194999511a97fd210d6273e3
921a55db55768f2d8d21eaa5593bb05b21c1bdc1d4c97fa44926c101b42bd065
f26f883d42e636709e89abe96ebfd75d3d22552d173175756da88a8c70f81d1f
1ba53849b218d42dbeda189ac40ede9cbebc12afb30d29fb9f2f8f8012a339a9
c954b3d270f4eb34a319dc79f2bf592c13c36edbfc4df935490ac4ffcfbb9751
0e6669596bfe1477bbdbfed10670e9b5258298753226f72a83bda32ac2386c3f
162df5b075515da622094b59ffdf84d85429c5999998e403aea5cdf1a81bd9ff
d8303538689a9bd0c662f0a38f45669495c2e36e7c9d47a204eadc5451896ebb
d916cf7ff02aa37f403de6ededc24e707697bc548ccfd6603b3f3f5e14e7e679
40c9ae502078f7179b467348580efa6746dfe14c75cee5578ca3c8eb31b053c7
566ee786cb0d4d1dfec34eeb4df3766788efa8803f32970e386de3f24446735b
86d4e1c3c048996245a9fda5fe80d8647e06893abf2b26e6d4d7047cd5ec2d6eTrust 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 963658 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 e1295f5373998665dcb74fe7a137f5bf63d54bf62894dc19fbf880588455d973; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / e1295f5373998665dcb74fe7a137f5bf63d54bf62894dc19fbf880588455d973, and the block's
timestamp proves the page looked this way at or before that time.