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
2b367ff5a658a4545055e833272288c8726a5915f932811d126e21194a16c92a
fc83a08dcf7b811626b997370d830e8774c937f8aba4c1a2b1ed99d594cc7d64
66190649f5b2b7d771476d1100bd1803437877b62068a89385704b02c71df185
4bd1848b8e8d882965d9a885dd3bfe2bc5a42389c7ee192a7bebe5c6f92a4c3f
2b92215913a50b577b9da41ae73e5e635cd9af39a38d63bdf3fbd27685aad8f9
875d9076d3acc1aa7df2563cefd3efb8e98e79caac86ae3a2c524512e144e194
7575f65f2aae9e7daa031b73af5a849f1592161dd6155c9713ac555f43a8704d
46c25cd5ed6b122f0336f01305b9a48349baec0ac89df0b42e336ff72abf7e55
90ec5cc07c54498bb3c4c36303db013746d1d6700e2f90859d087c9ea657b3b2
e42828eb420ac67a4c0b556ed14d8ea9d6054816a93706012670de287cffd6d6
8827c7c511853f9e05a9b590079b2e589f09762bdb185e0ccbfd21bcf1a3d89a
06a84b2ae3cd2a48e19167f5aea4337738dc19fcc5a1dec262a7b2c4ea0f6502
0afffe64639ca139e928b2736941b3e69e8f09e8e98203ce512a18de7a1289af
1911a992af83b55eb9f4dd7c69d5f655c68dd903342e80ca4fbc26a8da1804c1Trust 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 965712 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 16ac83410015c1ef7b13dcf51504cf21ce7c3a69ba37416d69f1266a8ab3fba7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 16ac83410015c1ef7b13dcf51504cf21ce7c3a69ba37416d69f1266a8ab3fba7, and the block's
timestamp proves the page looked this way at or before that time.