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
b002db9e2426d45b32681acc169977b39865a8af4ea49f06a8bd6e57ce0f4b44
a3f9cbdac52ba809da7ccaf3131e9f30d4a5e77bc7525a2ce234325c3df4511a
61fdaca760988e2ad0918ed2b544fda2eb949c58593b8dfe34c1df2def1d8431
62ecb3da38ddf6a61980d4f3e086fd8b415beb010aa86ae07b8676223be44048
1100044ac201ec94fb8ee1c55525caee0dcd7eaccde2714f50c3504cec7641ed
a3e9308d9db2628ab4036863fadd5f0e8fcda6dce6ce44259f88064d5f3bb4b5
a16e44d9d24dde8e15a96b1447a68546053b7dbc256a43f40a1b188688cd9cef
64098762eb4e0251f7ed9ae96e956c8efd7d628891e9bdc01fe1d161bf9301ba
31b495298351fb637386e95f7c07401e52eea8d2774a576a60d294f8f6aa3005
b8cc242ce9ae745f549059f23cd6b7354045c2d583801e3a6839fc1aa55fbb06
f45bfe4a0239b149d44e1bab64c3ec76dcca56bb18e6d2043711af79b62d44f7
045709c546082bd92279efe77895e819213fecab881b12401ca7a2a98136d291
a6cf80569588162950d54cb59b9867a9e7d0fe51246865965324c810e6ff13c5
1290a81e31aa191da0341459304ab9cfd3ab1dd7ab13ebdb525ef39711f80fd4
97599afe97ff1d78896cb9b5bb35912b532d5d243d3e60466b8b47b2dd3b19af
375497d2074922c448126fbec8624438f7407ccd2ccbf490c87027cde5279240
c7cf7978cc56a043ace0bad5bb9689a3cc0945c616007fcabcb6dc33b3a115feTrust 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 965202 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 ff8d7db7d36f9c2ab69bd42b30a0580db9e2e7031824e1664b3d0e4cd5681c1c; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ff8d7db7d36f9c2ab69bd42b30a0580db9e2e7031824e1664b3d0e4cd5681c1c, and the block's
timestamp proves the page looked this way at or before that time.