Web-page notarized

A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one

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

off by default; remembered for future views

page snapshot

captured2026-08-26T20:20:05.655Z
manifest sha256c4cefef5fe00acadbb16103b437373c9bfb187ed20bf16b6e3b3993e7bc9c3af
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid6b843977a79d255ca18ddb53bca0d3b828d7fbdfc7dba3002769f9b8c2a3dc00
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,042 · 10,727 confirmations
SPV proof & how to re-verify it yourself
block height964042
block merkle root2ebdd44a5e46ca2656c5fa30cf1ee6995ba4bca8776e2ce05d8167e60d616c16
tx index162
branch (8)5b24ee53303e52fafbc9a69c141201bc00244dd837966c373c0f06e292c71bfc 1bddf9fd382679221969f068d7d7fd9f9c51524496386bd4cf20d91d6352946f 6c993597a54403d7d8fd4de9587e349a347add11d7f02a931bd693c1ecedb3fd f3257cfb862da7fd452b7fc8c29d3486baf5883edb3c147da45a30d25f401752 9d6fe162377d8fa82369b921040cc7bb8998bb651bbc5529b3c67232cd7c7986 c6887e2df1147255aa36f853270ee01dd61919ccfb95d66e42078eec3d652064 4ce2846c598dd3901ec88ae32c60ad5367f233afd472077564bfb3ca284106bb e20469831bfe7cc0cc643d099b4e58520fa5856fb7f39452e6b0a35761a9fe3b

Trust 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 964042 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).

keep your copybsv.cx stores this snapshot as a convenience and does not guarantee to host it forever. Download your own copy now — with it you can prove this timestamp yourself, indefinitely, without depending on us.

⬇ 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 c4cefef5fe00acadbb16103b437373c9bfb187ed20bf16b6e3b3993e7bc9c3af; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / c4cefef5fe00acadbb16103b437373c9bfb187ed20bf16b6e3b3993e7bc9c3af, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (185)

← back to bsv.cx · JSON · saved HTML · ⚠ Report