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
6afc91e4f3eaf06335fa4251f6d3f12021e6e59a223f7e251cca8471396df0be
350d5146d84b550b4c425a5adfe98bf927719106ff9334227f7f888ac222cb96
8e0b040f92d603c035e14a4d4f87b549785243016d844f9ff2fe1c69a9b9daa1
b0590372c21a08249e0169f297224e67c81cb0fdc7705d38ff959ebb0218d586
c2b02bb1e521db48fa30de8e04ff67317b0bb630458e4696ed812ac58420954c
5be00c57a444f8e96c00782f598dca89bbc6ee55791dec945fee9070ee848fa7
6ca983933997aa751de5ca73eabd9ae65c25402e17a99f14c391bb93c3f3c7de
29821363f4f25db9eaa5b424e77e387b6bb44a41613b4184639159e2df76beb8
582ca594bf5dc38daca63522ef0bccd5464784be5db352e93f383bdc7bca6217
d5e52a9e748819b4a50790f0cc68f286e5e40ac85661ae41f60907de54fda52f
2be407b0a357214b3a7273dbedfa51fc595725f85271e16076d3c7ad12f1d65a
50fa883ec4094f34314d1f8bdabfd44b34e163ac17bb8665cae47069c1762ba2
8e44e8e17f4f43164e942cf1fd6507268afd5ef507dbdab76be5348d8599011c
bd14559d255cda58c3ef3421f07ee37ce509b5ad3620494393ee3b63e50f5fe5
9a56d277a7541bbab0ce4d1f62f22310f8e5192595a595c063548354d3bfd2c8Trust 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 963401 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 79ae60d8363f2c0595b2e4c067e802bd56e1418367a362a9289febb3a1d647e7; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 79ae60d8363f2c0595b2e4c067e802bd56e1418367a362a9289febb3a1d647e7, and the block's
timestamp proves the page looked this way at or before that time.