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
0c196a949ccbb152755c72712f4553b3e25cbecfff1613499d0a18dd157a88df
c13162f9f96b7790707d41837d1e96ec19ebb6f1e55c0a006b7358296f5da25c
5297d98300ba55e5c4415eee3e3a72ca13f17edfd2288788d78de04fa0685964
aff0201310254debf6b8fc30d13a5090cfceb8792e8c56179aa1cf06c16a009b
81dd99f841179205083d779646511fe31af880cdde2ade0c7074ac8e1ee96291
03a80acbedbc947903735a6ee201b0ae6e64e7ae3c29e34ae7e5db42af9120c3
7a07ccda72b5f8fba10bd5f2a278769b8dd8db7d8fe7a49b84d97f8aa37619cf
446aa607ee379de0372260805afcad0e8d4acae44ca2355dbb9e59cda74e7400
97cc6d1f5e6469208dacdf53ad4fee2696834730a2d00af35b49afed135d12ad
c0442fade30780c06936140b5df9489d16362aaa8dc54ee5556edf09ef80210e
85bba0f75c620ea97845219975089374010341f941c7b3148b1777e977f1cb63
779492a84a01b2f4d3e9570743aa83e2f2f414450a533c38bb3a1a2d3f022303
a9b611685effd8dd3fcf14982cf111d0ddd37afaba53a8bba97a444b00e487be
d7c4281674da4e3742f7b3e615be7a3ae3693684f0dbb668077df5d4cf7d8d4f
7b9f6eaf352e9105e5e5d4e5187fc37924523c5e66034cc119b5fe8afd0ff9d6
dd0f966842b9da76245d095249a19ce60c3b69844947f9b6f37b5705db7fd38d
772af6dad1a3a0d5d9dfa795c9b07ac0e06a94124d0d9fced3053b55a5290628
8f86898f67c0038d9d215c6790b90a3c672858b5978f220932cf2e5c2ccbc8ba
23f73605be544fce6bfd4ee1b6ef1d882f491d9d77d6677349eeab6085af416bTrust 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 973567 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 72d29346124f358ec92d710c766fed8cccd8ef88893271b1c5df93d3e0385e51; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 72d29346124f358ec92d710c766fed8cccd8ef88893271b1c5df93d3e0385e51, and the block's
timestamp proves the page looked this way at or before that time.