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
0222c651da9a37b4a1ac03dff334175739fa7d6d5826f84b110d35f76f72dfb9
29e2bdec644688b9c2ee5ddcadd6472377a4e0913522d42863a57a456e920480
9c9b957e1b6c45487441ca049ec6d909de87964ffa7d89e32640e4fb2736dce0
9bacc3f6147d019bdf96cdd27cc3f54a13d29244f36b3ec6328fa886dc45fe8c
acce1b5efbfa386bbc6e5dcf59634e5d9943b94a66a6494c760c4bd071a29426
5c962a7f32ad1d6427da99d919bc93ec1fe1e509b4f63514b60e2cc4baeb6602
b79e3385e9e0759f961fc12be32d65b16e07ef3301a624166c1e25573dfc695a
328edc72a36cee62dd3cdc0d16f4826b05bdfd14053641f7a3fa61e43bcbc34b
664042b8c9b99bf6328c7803e858aa8cfc13a37789ba6e43a2d63b1a93175b65
3ddefa34d221ebb98fac8bf731aa64b935b552ec2c851e968e6d43654a2e3f1a
b926fbb7fa7025d38c0717f48488ad757e8cd7b48c05d95215a2f08551fee56f
c6267e6197135c6f6ffcdb0cf54696d50b13e854f637f895a46217d9d07ab8ff
162aad15e5ef4a4ebdd9c18e94a13e8753517828ec50dfcc7dfd7976b132092e
21bb7d5c9c71ee60888d3064c9a834d9bdd9e1610e9266fe26fe8f659865dcf1
1d6547c029929717f6a375008ba531bf60188909ada3d252a6b4b5182f6c0e88
deaf87633f82c40c362174d84703dd544cb16b9a7055f8a2c446bdbe52ee7243
15de204099da6150c578026ddea837a31064740b6c0f4b3e285a280f94864516
0932ef041bf76dc95095a2cf65ec24232ab31b2a966cd01ae0fc557fae9068c7
cc57989f3151bbbd65814bacd5a87b3521252a07dcf3788052d130e1fd03d196
34698da3aa134f341f71097ce8e16ba885f842997dec49843de90452c131f9cc
fb70ec30a571165660a4d2a52d442151754751952eab8de8121b44fc192b9e17Trust 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 973549 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 999fec0c749829f575a006c0caed139b78b4dbbae55db492ceb9e452e2291816; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 999fec0c749829f575a006c0caed139b78b4dbbae55db492ceb9e452e2291816, and the block's
timestamp proves the page looked this way at or before that time.