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
32b071c9aa870202e998886d40bfd31cc5666b04e28045c654235628a0fb8d85
132c076b738e59eb676ce8ee1ec4a887e5d4176dd072d943dbae634e2e859bf7
964e0a1faa409f63d061c462b850def0d8784250dbd3ec725373e40edc988794
38d794f562086a19848b6862d5fcd318e2f3a5e6b09cc7bc267d5b155b181475
e687f0a688aa2f376154da7a675cf2820813d3c06179ef478ccff7bd54a11878
b602707bce17561eec7c443f64232baf8663b913c954d27dcab4b330c425be3f
1ef8bc233450ac7a5bceebd44493bf5084aa8e33c0c7d51787ee21c90ee4ed38
7d783947d838dcd0898ecacaacf32692ac58ef3fa1192c44eda504d4605a37a8
2cf1b8061d822b512c97b2d0815d866faf32d0b5bd045c7d2b346f466ddbcb60
cbb033649748978bd8e25fae77da0ad1377c75b6ef3351da9c6bcaa8e88c92a5
f93f70ca1d83ff8736d5fc3182d2e5a6643f052883abb6ec645888b6c2bae132
c6a99490900569f948ec6af5c15a6f0b7d27ff01c2227fe4f2df6ea951e96440
968ddb392df1a26deeade90dd5c6b90807ff44be3f1e093853e99c5f2f3b8281
73f905d194ab90e9af436d2a3f226d8eedf5dd94224f0f0dbed5afac839c95f8
f4844298f6832a3fc3590f4ea17d430dde40e48d67ab978ad7fc615548b9f860
5e2ba48899614f70da2127a2bebee561607c13e174cb0f86ff35f40b300d6ba7
a38dee1032127d1bd387e7796eeeb50403d1624c2df0edf6fb85e2cb1b56f492
0ecdd7b5c977f1006a210603b14803e220d2cb5835fe206f77550a23f5311bea
5adc366f8510320cd3ae7cc355976ded3022612cafd8a990bc17a25831d2be5bTrust 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 969662 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 73668632773ff3ebaf76b245fefcef6161f7d1c9ba101be4241157f189a0d355; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 73668632773ff3ebaf76b245fefcef6161f7d1c9ba101be4241157f189a0d355, and the block's
timestamp proves the page looked this way at or before that time.