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
captured2026-08-27T16:20:05.051Z
manifest sha256c925c616b1f1848f00c5c209ea83615611ff4823e6cb1d18f982651dc15c2cd0
html sha2564be7bdc1c37c48b269b90ed0722b4c4db4a8b8db68e4edc2a3c15103258ba46f
proof⛓ timestamped on-chain
txide2af41665aa88908865779c2a2ad6adb685092d01fed044da5eb36fd1549d14e
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,158 · 10,611 confirmations
SPV proof & how to re-verify it yourself
block height964158
block merkle root23efdf8fdeb0744a6a8cb3e1e3480d3f30ddc591c0de55087eb7041a03242980
tx index260
branch (10)40d2519fea87b0c2bd06827f2109ac604ae3ed790008db473cd7d8197d2a67f5 fe9ded6e40197234daa39d4dcfd755e5c6a2cf7a84e01cd788f9f2cbcd5b564e 11b846b7a3d2199495d368b0f5b44a6422be444200a1ebe50659afcd4d575b16 7713485c22893851de19c4d72b7675cc17835a0b36f7bf7ad13d61dfe810ecdd 2482ae3e16c7a25040ee2ec3a107d1a0a1cdb50bb7a9071ddda63111a036bd7d 68855873aaa823b94035231485afee58c306f17dd48b182c76c76d6eaffb0588 55ae1392f9c46c0a938e345f4f83c78ba5c340f6e0395bd2ca143a69e8b072e8 1f182edbbe51a1823911054b2ab58d6875f05b5ec23eaad90c0553306d006f52 7e77c7cbb6621834c163d0791955a2c00c5654bb491c9702381422fda2a76c74 2d9ff6ffaa4b08229cb18f05bfc0513b9f56625db4fa152134b36bfc70d3413d

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 964158 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.

⬇ page HTML · manifest JSON

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 c925c616b1f1848f00c5c209ea83615611ff4823e6cb1d18f982651dc15c2cd0; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / c925c616b1f1848f00c5c209ea83615611ff4823e6cb1d18f982651dc15c2cd0, 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