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
639e44e4bd28f61739495e85d32b5a4ab4745010f26ae5ee3412a8d0d789dfb0
80a913fbe93043e055ca27388582edb0c59f7d46bacd68a4ff65e3c13b7dbb07
fa1279b7b585e33603ca0e8f387c5c21066a67c9292f92e8fab12b236d230444
1629fb16a1b4f86372234b8d8b84506dae45e66925707eafc1502cc4f542a9ca
4d67d802c12e7b5879f590d7573b296a1ca95e3cc38c7f6879544cdc4dddae7c
cd47ecc57db7c65b452c18005a06fccf40e10deb4634b2d227d330ffaf03a89c
eaa2fe79cbebad83d521d022f388316be0a3aa80cfa45ed8ccf9823eb2d2e96b
67a4eef42224d24a26e844182572fd9e40ede3128106a6c951abe6ac66ea74d4
4ffc8171ce149496f3d03c714a1de05c962a983116da48eee64d670cabe67d03
4f9e04a5e10f02abb02790e10a4abb58d021cf4206cd83285d520e2bc21826c8
b848b8fe6cac3dce30dc58635ff0f56d7d1975eab931b340a16de1d70aa7b0be
4e89aa8f14beb291b8a018dfbd1e1f0b279bd8caf1f5e31965f51ad919387588Trust 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 962134 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 3f78a133afa12f53df6c8b4b82e074b60d9b90d0c6d62bf042743a540917f7f5; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3f78a133afa12f53df6c8b4b82e074b60d9b90d0c6d62bf042743a540917f7f5, and the block's
timestamp proves the page looked this way at or before that time.