Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
c6312a6f31535792587bad298cc0a299356699fd89f8291bf2f953fb69b54f7a
e5c94ea58a032d0fde6ce3edf27bbad22aa11651564d5922df33ca59b7ed996f
8a5b58034a3d6afe5d535685c1e0c074f545bc1a5beb2318358e15454a4cd9bd
de68e3c9f4bdeaff0e91cc71b1c46b9b717b329b035689f6d9326c42f1588fb0
f16b4c8f7afdcab57f89537d6a0c0af0623f39bc87adf7f0aa0788ec12446e52
161c9c834d9551439e5eb95aeda197a3c28141c42bb9a481baa1d0ff663fa3b5
4801ea3b8cd2bcd8b6e6667eb6f0f5934fc64f4c135117c503345cc59fc1f2b5
d0935dce9b6425872db415321343a47d3bcddc2d74ef6c667e8bdf12ee124e00
2b6f355f4e14958e5c51dd7b216c2006a21604d39afaab4f57272f46c8c2ce6e
0d4983cdbeb47386b51deac0b9208636af0de5e328d4cd50b8d006b0b07254f5
692ef12b29017ea688c3bb91ebfb1205fb92ae4b6e4ac7a04b8a98e4d98788f2
2791d33bf11c86865fd7042c03ef71137180c79c8d56d14f29abe9cd08a9f0a3Trust 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 963680 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 4487d302c82fc47a1b1564e15c9c487987b187b092143c478bc9851e00bf1009; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4487d302c82fc47a1b1564e15c9c487987b187b092143c478bc9851e00bf1009, and the block's
timestamp proves the page looked this way at or before that time.