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
fc22558f7fa58c07bf783fed956c13206db82c6bb7a6ab3c12aa926c70ca909e
db518807858aee3ee6262c5fda36814cd441145292e29683dd0c49144884c4bb
4aee867c3c1588f90ff02b830ab77e15ef17776cfe36d5e1dc8228c4ac4e8749
9a976e30ef4a1c1db7472ddff441a8fa674d7468849045c65e50835920885302
cd31ec3ccc77af564a7eac0df139f320240b72041c82a3660b72e31276ff3807
1440ced58bbbbb9e0c3deb964e3f757e1047617148a18fd40933857ea8a244f2
bfc4d54b173cb9e90976b25b16462a01e8010bcf642e24d1119b7e7d19c5b901
dca07758fa092cc038dc9cd97f4892515fed54615b4b1f3e1d06061ce85cf7a3
fb9f4e0372d06a9212866cacb98d3c484c54b5a923ae7b57736e8fad891646e1
ef5cd3136d265d4f906608d8c951821aa2b9930be8000971123405d4718e6dff
ea431815e55d61739b9801619b99c00b3036fda536e42fde3519ac25ededd983Trust 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 969246 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 5ae5e9c565a0f8a718157740de476ca2207e42938778940eb0767b18fd55e585; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5ae5e9c565a0f8a718157740de476ca2207e42938778940eb0767b18fd55e585, and the block's
timestamp proves the page looked this way at or before that time.