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
2713c1e1d37409b9fef72bbd51fffb5aae1b48d3630c19d4112d0a05335dd2aa
9140f8f804e6560bceda06f683ef954af57651e3e26c9ac7475a93b0d8f83c30
bb8ae787e0d64e71c076fb71503b7b1540a8e9886bc3cf521b849067ce041be2
a81b3cce85cd3f0e96ee15ba564cd047dd74009bbb41f409dd7cc24932a97d1c
663b1cc67fd22ab17215ab14f1c8729be4d2527234b180d41ef93ba23e42e9f1
b4e5a34ef82bdf1158d995b276bd26fccbb4006ba62912b3c33f8858c473d549
10dffddf4983f3c9ba152a2e560236395f16d942d4cabe2fd6afd932b293d89b
182886e6978f1a72da54190ba13bf45f0d7d4627f18b694fc69e3e69516dcf47
0a8e8c30dc2c519a7345c92c2635120cd67e2919df44bb80c7569e43b9098531
4461fa0493b66268fb890e4e2f1516fa81e9dc5d52273a9b7b6dd2676842522e
0af8c6a980c4b1c527bc2322cb2ea1c0e1763596a42a34970abd61c39156fdbcTrust 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 969189 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 0d8e670fac5f37cb435b4699092a086b8eef57b7595a8240cee8c0ccfd0c0202; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0d8e670fac5f37cb435b4699092a086b8eef57b7595a8240cee8c0ccfd0c0202, and the block's
timestamp proves the page looked this way at or before that time.