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
d319847211c977144a9504029030454e267cf1d8fecfee4beaa01954c391ac76
4380b469177472fffd6d6553e3034151de8df2b9fcb9455da5ae578eb38cf7ac
725963396633a04845ccc975f5f713de697a7791cb7229d8ef0d9eec0801acb5
e7469e0f3c91144cc3906409862b8a988b5a514396f069c94fbda2fd429d784a
2d88e2de5366cd2f333f260bf22fca3cd2f622a2dbd72a1102c5c122a885a88b
5e176b839f04584688d7fb50ffc02573ccc40727265b580375f55b7bbe13d22f
2967d042dc2295a2cbff42192cc1729d41fbdf12ac2c42886ef4f235cfb2bb56
1616bf8e31018f32ad8f5c25080d778b7bdaa01560996995dec5d995426884ae
3e0332be1c5056f4522fd3d0d3fa1e0504271af88d93afed118fe124ff90c542
0676c3f30ccf3ea158ecd117c6bed0920f7644f20080169a2cf12cfb9e2d44d0
0282418d1d8206595c5b07d94c5a414ee21774c71602d752f54bed6a117869bb
4c04354f3b8ef19b06fcabc4128a91ef53f7bdeef7a6fd6d2865b37eea6ca89d
b9b1381bec0db9b80dcd1033d77289a5c84e0e2450feb98939bb1cadea901724
6627ffe4409492ff3db21a09c8afdcf74f2cdf31e8bfce867cdf56fbdfd72b22Trust 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 974631 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 ee291bab0e2b1dfef28e37bae34f58c1d3ab722f8f54e0979d5961176e9b4b58; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ee291bab0e2b1dfef28e37bae34f58c1d3ab722f8f54e0979d5961176e9b4b58, and the block's
timestamp proves the page looked this way at or before that time.