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
3989e773652ee6fdf82e9cf19ec760640825a295ff65e29d6524516ea02362c4
e9b110b912cc603346012bbb0947ad5112cedb564d65b397222b3b8ec717b3c9
21af82754faa039fe7aec43751600fb0d6bbc664d00ddeeb73cf801bb692cb5f
3b253bf7e0191da9394912925812d55c7bd51e103db82336fed143ab23722632
fdf5b95a7fba64d6c444fa8184270d8f0724edcf667aacb0fc737e622ce93b88
dce1ef2d47aa258c1fb71130b5786e54fbc9f33236d33664eb8558a11a5419c5
a60915c115352673e5b603de438d19ca888140b3d42434696f20c063b2e0ccff
d4947d4ea2f6375854d4bdeda807f6e733e0aca649e054fd6fd94eaa227960f1
063f16c4633d31cfb9f0ff52150672ea2d9ad479a49710cc00ed95e9046b27ce
76413d8eadacbaf1aa9831ff1992443eff7900cf6fcd660ccbb979614b221ea7
d47e5df3f1213974e93d692681e0ca8073797bffdd9ff406f77dfe6e5d05733c
7dd4173450c70a9e41f200de305dfeea646f185a2d321da7d58520c087aabc0a
5324f20ab9273968691218957fca3a595ab5438d7bda264e73bbb23e5870995c
e0c5df05f368a69e7fccbb884df3fc8c7039c721a9a6db0af945619decb425d3
cdd15691de809d02d75a3af319c3efa5c107aab40ef40f3b8db480dfd99d8435
f7a481dbcdd3d8216d10d1185f6c435a9c3f3bded08ec87aad40a9f2c076af53
8e58f2c2df93c2fe7b4128fe52b3b4aaa288487b12e990b9ecd1c31b2ff69c41
854a8c638afb33c391fe179e657d84d6c736e9d67f0f7c4ecce7e667f4c26f15Trust 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 964647 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 58cc95c7eca19b10b60ae5719ea165218ee72f971de862ca4a3244894f228a32; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 58cc95c7eca19b10b60ae5719ea165218ee72f971de862ca4a3244894f228a32, and the block's
timestamp proves the page looked this way at or before that time.