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
ecfcd076089de34ae143b59c0dd7f7ae667cbce725e1ac332292493cee7a6a79
fe57656653803e0ca84bd17bd936aec4a000f5213d94fb05ca8c67c07eeab95a
d4140a21de3b8671187bb1d80820f16e3b8c81688ce6c1004f5dfbf4aacc7d97
8e03851e4949711dcabce00e2d80425e777d99e425e82e5de51844a42bd6941b
8937db498ef555e19843cda2de0e31b55d770d70669d214c2b4dd620abee7dba
45bb59b2cb71a94e0eac4e93d60b7095ffefdd1c479deee5413908305a20efd6
be27fa97b9920a239ad3f00fc990a37d682d257e97e0c05647bde2a1d95ab343
2eeafd4cb23dfbb1bd3a808a3c4147ed3d12578f0d472fcf725aa6e12b56b5ba
9589e2fc9ebcdd4bf38f49c2d8dc57d0e084c712f71e05f3f46e5c74bf0f97c8
c11970cd81e9a5a6b5056df0d15dd7bb975c14f9ab9559a18429e5ba8d0e79e1
f8caca288cc63bacd6346b320d7899281bbe5d92d4c9c5276f6af8f7ea8866b4Trust 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 965325 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 287ff70090ecd07ac6144ed0eac5ae3ef90871f58e3971613ad6971700bbb316; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 287ff70090ecd07ac6144ed0eac5ae3ef90871f58e3971613ad6971700bbb316, and the block's
timestamp proves the page looked this way at or before that time.