Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — 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
5203779d46da9e588dacf15411514dcbf0e19aeebc2c46bf74a80e275b5d6c79
844eb05cd65824f6d716f05a66e16d765b4f0f32fc072605ba5bd79b1a5a1529
f76f38ab740e61074a1658f3d5dbf706a5160b468f7f53977ff475dad7982e4a
d990b2c7507d1206b9dd1142b96713e7b87c6b85935e47c9fc67d2b49eb7ed94
2fe2d8f11871b08d30c0ed430c7e7f5faf346f97b7afaaade3dfec0f526b63ae
2ce60d379a9e785fd8e097d3bff9294b525d533991c194afeb823b151df6f133
745a33cd29ea60f310cca7a123e5b192eaa2447320e8040d37f79b83c2aea5a3
a82cdd9bedf6b80db0e1fe07d71f9f801d1877fe3b56bbf278754285e8c6ed25
9aee4f9cc1d1ee556780fdcb20b47a7e9d55998ef3d88561d7e276800c9b9b50
bb33bb1461cc570cb61ef2cd8d0c4cc8cd3416705d402d75654e0b354cc23110
a648acb30a368d1a555ce24159600e97f1ba01f48de1d6b0e83593599d91e036
4509b4561a40f32597eca1e9cd2a2cff7976dda77a1d6ff3d6048c6f0b791094
e13cf1d88692283394b83e93826f65be1011e1c41056852d49fcfd356939178c
c7e191e65dc579fd567dc9761eab34251f9b6691a598a718a92d3939a1b2abc7Trust 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 972146 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 7fc15af852654f8adb39d9d84b7d092ba517cbb4ed36afa57ecdb47172525e73; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 7fc15af852654f8adb39d9d84b7d092ba517cbb4ed36afa57ecdb47172525e73, and the block's
timestamp proves the page looked this way at or before that time.