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
e8782cb1aa7eeabe727e41077d3e3294493888aacb32b91fa7a403be1031b7d9
c1d712e75178ef37d6a274d3ceaf7708d20c125b768ac10f0e8f30602e9f9a90
79260b1c8ec1575425fe98b45c39a39ef7f588d159fb3ab91fd00e5bfa678432
3615372da341f0da11a0bd36a2e04da3e905b85459ac6538a6f076579b7fed3a
c8ad87fd52a42ea69b82e11a9cadfc4b933e3de24ec9bab8e80ff652c9ed9ce2
14bbb326657a0b080b35e1b013995b5fbd4b68a4b8818a150ae0e76da7403f0c
2ce9b557a2e05d361823f235c047fcf4bd353c58dc777f4cab55398b6952545c
97e0b7df6f952f77a55ee4d70adf76eb49d7483fc01050a9b5e007a6f81ec378
3666f50bba35b9bb98fcf0b3cbdb4d9a12f495a91e08ed303bc7a51f5aa789c2
76e32e771362aac48ba38ab1d523a1aebfb11b806157d5720f42b89dbff7fbf1
a250722d63f6bc4188a3378911aec21e7d4a0f376d1aca9d2e64ba8e611ea5f3
41a0a2fbc89957c3e502e476cca7dd10512c993e47c71aa071dc8c07e7797e86
4aaaadf715c9e6983eb362f1a1a7faddd3e9c853839980a72b621c4c41201e5a
6565e9d0c67a742dc4d50db8cfdec73ccea4889d56ebc1a61d9adaf2ac5028d3
9fa6e87912d34f2b5c3e6dfafc6022f2f2bcac93374d321c8dd330df70bee3da
e0466dce5c46714c5b0d4896512dfe747279f51fda3d44d88f8834df523b35e5Trust 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 965924 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 e14bd201a534eec0ed1b555b55c3fd8539a100a07c6511701362784d29b362b7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / e14bd201a534eec0ed1b555b55c3fd8539a100a07c6511701362784d29b362b7, and the block's
timestamp proves the page looked this way at or before that time.