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
d45adc257dd2bfc586d4c686658042697bf2a88e15a9ddc4051f446b751703c2
847cba668a084e2514a2835f55b18f8d87979a2073dedd88585fd301571814b4
af91d735059d88ad68bbd781939d13a06d5da2ad47a777df73e95697689e2c2a
c0c8af541705429ce0314a50b3f3891168ba0e4d80a78b082d81e6f9da5b889f
b523f7fdea95188e9260744557c28df009098567609bd46ffa436157d5a1bae2
f3c465101f89ea9505ecc156fb7ffa1b74ddb33e9329be5ae748e6f0e5688f63
3224486a446fb78568f2d7dfbddb85faa60308e60632e4fdfd5d96a8fc136467
610a643c78dfe7f3d459584885f03cca65fede16c48789f443a17fe4ce74622f
4a8f587acdb7fc0a8416aa1d046de2ea82bb1d73043bedf589f7a3da51af9e3b
be8e8e295e3a28f4ce748b766c8b6b7ddeb5491dae518955c0389635fd6860b4Trust 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 962800 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 26211925c31f12bd4296df23139bb3ecdc086a7c1ff3e6a4360cb13d9337c797; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 26211925c31f12bd4296df23139bb3ecdc086a7c1ff3e6a4360cb13d9337c797, and the block's
timestamp proves the page looked this way at or before that time.