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
b8340c5ee913768b08a896d637466cfe75d98a622bcc14d8840708776c1d5bf9
7f95389f48664f6b06ac3fe93a14564fd17951d5957dfbdc92abd3c2eeabba85
8a3d04edab716331838019b3f02abccf0f24d6bb78cd6814e84e6697fbe25954
caad838ad80d47f88b01d765320f1b0a75ac6c9036b549b295ab1254750aad4e
ce7e8325ce6024e3fa58cf139d6f2123e4b989db266175aecaa1f1953eef04a1
4c43e9d83a231bd82dc597a6194a9544a9d973e479d45c7975e803e451347a95
c58c6a625618e5ce81ffa1f234f2a0345f77785ee0395d71a011a8437d96e82e
fd02344a96070669dc453ee2b85a319c07494c3a09100cefbae9e0ce3f3b4001
01bb84717114a8c77636293067378934f15c4a1ca3724f08f2fe499080e13cfc
f0fbefacdc2004d2f55bb3d1e2ca7049e1579a2787b0540945a5d373650a656d
f9d2d4ce1901bc20a4c937ec7367fe0381a3083a0faaa9b7c2096b210e3b092f
719f64d11db75343d83779568b71255351b0bdbb436fed6435f49c6d26e8ac17Trust 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 963633 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 a5960b96bd4ff80785aee61e6f480ee604b973edd6585188ee8ab53c1280afea; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a5960b96bd4ff80785aee61e6f480ee604b973edd6585188ee8ab53c1280afea, and the block's
timestamp proves the page looked this way at or before that time.