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
f8a481ec542da54f743fa2928b7d1e9f15e76b5eebd800f22636d13e8773eb0e
78976950ce106cbb794959cfba308bb938c41009bb9d37a142ba77ad94774fd4
8ed581de779c032b55d55450282726289d9a2ab3c9f8fbd1fc6e06c0baf06729
57dbfe0758dc1fe253d9b67f2647d977898b08d1864958af00b53612332ebe34
0ed7b1a2991ed93c9e19f23f4dc0ec20e430c5b60411cc50f9db83f2a0dfddae
f87418456020d77246887bb41edee7e9fcbe30daaef8c4ac45beb8074c8b4b95
720551fb3ae898fa1dacf266427ac6a20e0c5686e5d8e8e4dd67eac62c5c1482
57352cf2ed2b0fb303227bf2e50e12d5efe7a38f09251a96f8ce91cf8ad11f1b
9fb4ef8ec0979b6c13eccc1ec896ed866309fccfa9b34d3f9db3ab23f1276117
d6efa0349e99871e3ed22572acbb203c4bdbd2126952b777dbfb9f22ae3a6083
186bf3849d627ac64706e5edb25eb6e92d5aa98679b2e066f8679c2b466f4bc0
1400cfae02d2afb9c15e89d2aac39635c7bb06fa32b9b1f601f54ebb769a69b2
e5645773afa231dc6d248a9c517fac674eb619be09c111fc792266c48c50736bTrust 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 967775 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 3dabc79a11ae124407268e02a0e6281a352a3e5cca35193bc43311b920d9de24; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3dabc79a11ae124407268e02a0e6281a352a3e5cca35193bc43311b920d9de24, and the block's
timestamp proves the page looked this way at or before that time.