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
38535b521505f8c85669a205a714e62912bd6f0ceb4d28fb14beb34fb39270dc
945aa672b8fcc2ff827528c97dbec6d6bf73ea2a4b201327c9eadfd14cc86c00
2086b65ddcf1d89fd1b7cbe04d07a75107cd17e385d36f5416e128a690c792b7
527bcfb599a6f58aa89e0fff21fe69c021cf1ba724ea76eb1588327a1b783378
a88f81b03addba30cea25b62566e2278fd91f6dee8df37b669577a2e40808a5a
bfb5553ea27f482489fbb1201a8d5960ba4aaacbd5da82d55219886e8766e5c5
b182a89b910762788c3a880ef57bd51c8513f1af8bcda260b6d9737c97d5c5e3
d4c2a77b2e72c81f96a99fe0d82dad864cb98b02eca8c28e3bcb5e42b2ce2860
64b90b75684f478b2bd3d135125d7956c468a979004752a7ba11cdd7b3e064ec
24e4a4ee40e57624ca085079b48dcfc48103ab17cf2e3319972f2f98d7e2520c
086b0b89e22746ac522ddc38ca7c5f1d75aff733d79f56e7edba928bcb530cd3
2dffcbd583104e5856a868438ae97704a076b02a4f4f6a0e7558c514986f630c
27928e13580fa48b18f37d24231e40f6e3cb4614bff60c14aaf0b0d691f5db81
3d3a84ed93ba7504691d4f6f0e228f434d965c08e09fd528c714d5b769270bcc
0b2aa966befc642ff4b0144ff2149d34eafb4da250b9c89da450773c204431c2
3089ba78d7c60253e6b116442ff9d57361f093e62c9cb6b3bc5fda3785c0e099
590ae4f95ac76856ba773d4137656398159a4a603491c7fa56fa2ef688efafd7
73d1a332880628ecc16cba795c2674ba239e84860ad6d90def65b168fc2ebe3e
9ad2ac0fd6899bb2ba53b746a858d765f1e576cbdf69c8d9f37a76a91a15cf11Trust 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 973098 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 814208ebb3102a26032320c9d8c38be99f551a1434f312eb5f1ed50e3d117bab; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 814208ebb3102a26032320c9d8c38be99f551a1434f312eb5f1ed50e3d117bab, and the block's
timestamp proves the page looked this way at or before that time.