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
691acf1e741fb61812b49b3f9fc929772808cdbb55242d1bbf8d93ecb846c33f
33af4e58d62e2f44bcf5ac3774864daa0c7038f7548eafde66db30da68888679
faa50d7ed6f13f76aa09e85cbf98abe76e087d13ed80b451692ee10d95c513c9
98d7c5cb7521a39f57a881a53c27e0da984f294b5e7856a55bc522a8eb429662
49cf967b7a80c3772d7e6f2e46d9d047b5b82d9ab0da3c929cb83fc70d326326
bf42c02ff3dcd9675acc6f167fb2a7378df78331f115bd33ebbbe0d7cc0cd804
c3bb1dd029384241ac88ed02383e5e0fac2c953312a5ca3cc35a70c6bad78644
0951bdc4b623758f9d3e600830e7dd335c15ad9229c12f7005d4036d8a53eef2
783275b2cd651dce3593be40dc31c837cba6a00f7e5e106cb7ea01c1327030eb
3d32a308e92d16d0472dee440b3b71fd5f61b64bf47ce16e426d423f407eaa59
f4ab8aaf9b293547a6b043fbac30273b5b2ccf38599a1aebd713953426b74e18
d46aa1f62ec7022715dda408e8aa5da359c6a29ab7714676dbe9995c03069a16
b661c95d39963e67e276c0f26790a5c44584161cb0048ff52f0f80b47386122aTrust 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 971135 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 aac4b620b722e9850206ea70a74abca88cdbeefe668503344859006cdba10ad9; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / aac4b620b722e9850206ea70a74abca88cdbeefe668503344859006cdba10ad9, and the block's
timestamp proves the page looked this way at or before that time.