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
d7f3d1096b1b4c64e7d0564911cb0a3b9710782cf2129660dbe2b4b0223ff820
9e9ef7d963fe58282804f2efccd559b4bee2304ccfca490b4e694a5c07f65708
b81e4d5430ab12a2d2932b0044dc23506f5f5aacde9a99b061cdbe60f9e8c777
c0a0cec2e8ba96f8e58eb5ee5528b317a6dc0be73b26c0b0895abc6e84a284a3
842bbaaa96da7aba2c52638202f53d3dcdf50845cc582c1426920b074988a2a6
1bed24f96f4c335d892ea12a169d6fc04258dd3dcf27dbffcd8dfc23fda14680
a1fbcea41d2c0a0064d7cb16adb00032ad577bd04eaefee9f32352ee4553628b
406ac6d7b21b91ac9852fbf213a6cd76c9bd92f9d2c5b3b54c06d110a42d422f
ca26edd81e08959ab234beecb1a63818d2b41e7049a744b5161416dc446477a5
fd0b9b5747103825ea2edac3312ad787b5cc544ee7597c7fd3975a825c21e0a1
beb8b5dfd5cc72239616db4600b7d328f415e1cfe95f20e56a0f17b83d314128
68d528440c333bd3abb9dcc74b45e06927ad34606cc448725d63d8acb1ee81cf
fefca4e5f95da59bdb7eb3a3899f288cea438a977272d862d78ca62bab441160
76665691ad98cda574d49f3d9aa476e1dd7af03e0cf2dcd2a4f4c22936b76557
8e3efe6ebbcda1ce8380d9a980b749a86d0084d03c3c15e4aadeb8a513b487e5
e897300bc436d40f2d6988561fc7a4b6cfc096e0744ed03abf3bc55f260cdec0
b0af53f3e033e99c74da609d264833e93820da6ec70238b3416b0a580ed1dbfa
f8e08066d57dac7f430a54f1ea317b6e79ef308b343b3a765974d36afbd45d5cTrust 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 964845 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 b0c2b1b6c1eccc3d82b328e14c737e8dc40f7cb6a3ea86fbb54a26aa726b5b09; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b0c2b1b6c1eccc3d82b328e14c737e8dc40f7cb6a3ea86fbb54a26aa726b5b09, and the block's
timestamp proves the page looked this way at or before that time.