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
99698055bc48624dd26bc789419957fb7e910ae096e8436ebee4239649c1fcfb
f614a73b2b961ebb3cccdebe2fe56a2f20747ad84a12ee6a56172eea854fbdb8
edc8c8774b347715bbdd74c6129066fcbd80ef26a2692f088484f9855bbb57f8
942467b3d6caa755bdd10cd753ce31499101ba0b9fccd91e23c2bcdc70067d74
b5255a8cd660bde13ecf28de7bd0c5b5748d992d8ee156b049b63f7c7772df57
38413c310f47fb4ad0d56082c79f86709cbba34156873f019be5b6dcaef90569
95b8d419bff31adf8c4ec967348a90f0f9dbc23dab20e99985d769fe6b546800
cec505e45328326518dd3ff98984e8b4c0b48921f7aecc41286a8e7b984fef2a
4f6489f9bffef4db94a23ed7fd44859cadf4bfe0ddb57ac74ef3fc9d531e36d7
d89b0594b80f6afa4f75a91b97e65f641648c23a24b7a27c042d1595d98be5bc
2b5c23c637f6d86b181f6d4c45e87bd0d5e960ca5dd53a5d6d1b96128d93eb92
1a59466380e43f66bb54a9b983ceb4d4593776b6943f9783d8ab0aded2009c75
0cf1179b23536ecef964d3d3650cf10a976b12500a9c9d02769ff7a3527a92fc
db7dc0a3419cfd8a303d980510e1ea487eb802db40290cdd32f977df376203b4
1ff1d96d6771a48099daa14823d4b59fb52dcfbc35813cb6bec7c99f3422c7c3
234d1f16a3efff73c7397f7cbf911ab7c856db0528ce96cd39da8a1b7a5c6812Trust 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 973305 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 50f361f314ec07fc9cda3973795c3432eacef4a00c1e66e2d2e7a530b2ab6cd1; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 50f361f314ec07fc9cda3973795c3432eacef4a00c1e66e2d2e7a530b2ab6cd1, and the block's
timestamp proves the page looked this way at or before that time.