Web-page notarized

A tamper-evident timestamp of a page's content. Brazil, Thailand, India clarify crypto’s place in law, finance

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-11-03T16:20:24.373Z
manifest sha2568e8eea440a53c934ed3dbf217ded5081fb961d36db7bd2cf39b30429950e97dc
html sha2564a48f3798ef5a7f93e9734f58e7919bcd2c32e5653463e663200b542fac171a5
proof⛓ timestamped on-chain
txidbc3bf85c79b786790b39faeabbbe4d07bd4585e99457c62dfc12603aad28025e
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 973,925 · 844 confirmations
SPV proof & how to re-verify it yourself
block height973925
block merkle root0642fbf85c837e4b2f9cb052baee7632b6bbbdb1927aac24ef9225adc29d55a2
tx index532
branch (11)c14eab7d627c07446bdd5d80c940ed02572075aec3e067b790b50fe302d82c29 0be3ba757dbf6c92714dbf8270d3861194414206d30d84007ed8f66e96f89772 6c7ab13305169185e108ee759379a41387f58b5060acabf3e88fb8edbdfd512a db7c334f873f5faabd048232ba2bad634c89dfbd3f5eda15606a84df2647e1cd dc63e42f6f61a5d91946e7be5d3896e098571ed45e455f93b57b8ea9f71c946b 1ec1773f7a51c0f96f7f1c38e53d4d6487ded458ced0ca9a47d382aaa9edfb6f b81eebdd246dde278cc8c4c1f231125c4b4313f41710d0baf49a57755bdd0f4f d13e6721da87689bfc1e75d59103d489ab0e181bfdfb6c29fb435eb23dc2d18c c5f5b94761c26f34d5c08a7392281bad498d37c48e36ed35ee5ee4cdf467b77c e1739496f3231d96728f727fabb57be1e5e7011caad3e6198956940fb9cd371c 2fda0ca153b4e4f70c8d8097ac8300f399558ec344f9215141f3b2fb237593e5

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

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