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
981f5e4545c2d2a86fcbfed6d8c7113ac1da31d9e9dc9eb8ea8e3cbcb6ec14b6
2fd6f3b26b690c270cd23947df476ba9b5ff17a2e5cf1e6eb03a1ca2140123dc
c270b916504cddc16635e9fa733aa55bc67a4618f0b4a5539d93fc1ca353ed07
2d735d734452bdc84a395cd7d127ab60f47e8d0d184e6bc9ec164fc58a8ea9d4
8b2e7856b2c4c51ca3b561ab7b1e4ea34d56cefdeb85985639289eee01f8b5e2
5f03bd9ca0bda88b6de8d7f1566c971b63151f206db622d6ca8927ac194665d3
bab0fa49b47a51e1ba0af4130385173e5427c96f93712206580f28195a71bf2e
2a210f78306bf0dd76feb5aa7292b91a61a31ffc68be39bc4086e805d6a0f41c
a1deccb91267552b50104b7e7132e457c515cc82e8920c43e3cc9342e876ba4c
2310c77d0ee04608809e6e8a8d1921308e18fa1bcf2fe2f3fdcc5160bcc1bd93
5a1c08f27f76a57914f1f713f98b94896dc72f9da64f2abd4b69a9f291a1c561Trust 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 971742 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 7ef139bc365a06d9015d7276e6d9f5f891e9d735d2360eb10052c2edffcd0efe; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 7ef139bc365a06d9015d7276e6d9f5f891e9d735d2360eb10052c2edffcd0efe, and the block's
timestamp proves the page looked this way at or before that time.