Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
15ff65a496836c0e458fdedbbfc9385b2fce4afe97b8b277a41d76026f7784fe
cf59f4aeab3233238e340f075945adb2c381e321049b9166e1aeb76e5c289eaa
4871adf04d7c2ff4aae717dc9eb071014c2de6357e4f438565e665c419df6092
7749a786a2808dfe54423f8391c1ee6559295ea45904497a25c39b6c73f6fe99
da0cb4ca689c9e9c1e835557b90931175a5f54d77edb812e3ee500a311080f8d
df5ed44d57e47a758f1ffc5b6df717a8c704780f69306a2430d13eed84906770
aff198edc2bc10b12867d5187c01d482fd725d9f213834b62c0911fe365bc11c
9188c6131eb80b07b1db8e473fbf0561b263766735e5cdcf36d4b3aa47280165
b8e537aef3e1f8d5b38443c1f968035a7b29fb0dd0dd559c251c8c634f872df5
cdfd82aa1bc043d77e1c8f93ac3f22fec62f7ef15547999ea795b635d248c3c9
66a1ce8476f827c425cf257f28f6cfb18243559601a496624c1a73f1462ef4fc
f2131a9a5ef9c8bb6554df6cbf4780a8d506383a11394a42a55ef570c302046fTrust 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 965229 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 5a19a394342204d8795308ad30c9f4be76fdf9fbe6e63c338d408d71dc59a6fc; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5a19a394342204d8795308ad30c9f4be76fdf9fbe6e63c338d408d71dc59a6fc, and the block's
timestamp proves the page looked this way at or before that time.