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
92b00137a77785321539fbe04d6ded7732f1d6b120c81de2275399972c5ff22f
fd144fb7d318f4dc598284d05ece7874a765d68c1d89a2076af52787d4202078
bc846389f1019e82785a57a7e2cff6e3bc51a8c98b256dc3e6ca48d19a4da018
864c3428f96bea25cd01bda50ddd340c0a48f2211b7225e7dd27883c92ef2180
d59b9eaf258e2e43f44266da7d9ca8450da404978e6676616459d409f40ccce9
3fa0547ea27010109c9f7682d290269385de200f5eef3089996024859ecf78a3
fc403c36ebebca95c46a98a623917fdcf9e07985d965a2f2d7d3113ef8c6f73b
5f06fb19abf136be272c9e9b8114e5bab1392c6af2ce58cf42638b0a327a5119
5069afa93c06647f265ecb951ebb93fc413bf65e6aeaf7a1fcb8e5e5ae57cb6b
7d5f02a45b90805da247c43a4176afb1015f2e721b957844f748047cc1554e55
2afdc742448ec01684366afad3a45ad626ca7a9b68af1c80a42ebcfc8a6428e9
fc9bd793ba3cdfcc04770d62a69fdc95db3c656c610a97c24c9bb1d66e01e3a3
80131be4512d9a66b406b4e4f4ea90b8e01a26dd38452e82cedbcf8d91c0e246
4bf22438da8c28b2c15a55c15a881633bbf870d41bd5fbc3d64579ae8b77a537
2ae08cb08f20e44b5300e3b1bf394ed16cd16ce708bea87e6ff63f6f87b1aa89
148af03a942122725cba68c4330b21137350ab646eacf0b164654305bac36b29
394854f5f885487852d1c6fdfffd5cac0140e8f7a2456896fb0db62b2450e45aTrust 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 972110 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 620c2089d3d4aabd9e839371dcb34faa4233716dc33904a395692456f837e2fa; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 620c2089d3d4aabd9e839371dcb34faa4233716dc33904a395692456f837e2fa, and the block's
timestamp proves the page looked this way at or before that time.