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
1b37c238f942b40f72ed792fb01afc7e4afb8beb88c5962e95d1f94d2443a593
bac311df5314e598f97fcdc51c8882c0ac5d069efae737950fb0feef548dae04
360d8e1ddad269a6e730afdd4c11c6f8ec51d3e0e1c9788b2d66c09eaab34c58
91708efb948008807d3a6089cf633f074251844d1a253a3b2a0fd67fd528d8f4
ed34da93ec20521ec3853c64ec802d51f89238a7a69a561236fc5cf6bfab7b1d
baa960d0a3bef7e2ceedadf85425c757b8fbd4df3b854893ff19fdcb1ea26cee
3f4a91135932cac788e1148ce85a9de0e6ec73abe0260ee0f6ce2d8ef8b2e42e
90c700ef0b6d1014753139946bf39c2ad258945a094dd8b44282af1d0beb66ca
4cb94fabde0ed2d94ea4fa3a7f5228682eb0532bc3cbe832997c887ce283247b
fcb21519c3875a02e0b4d0e5a80ad8b084180253e5f388a4bc3a3eb59e82a76b
45c6aa0c6d2a1d8daa7b9145ac05fd4bee1c3431d6962217f51e91c1862fd998
1cf8eb340dadfd3b9cac1ae1e1fe061eb73a5cb1a104a428c88cec116a3c27db
2505ec439f2fdfe348ea20d7c6cc2d8f50e326f323d14aaeef819a7f3add585b
f1f5699d66d0b9062b9908db85a817436d12fef5f39936b800c25178e9e3de05
0c476a5091d40edcded245251e4f858ed358ff5af5bf01eb37007c7b958f2f4c
3e8df9f1fa7fa2516b2940ea112769426bcfb544134c178d5214efc458161925
a994ba46d5eb2f5619fd45883e597a5868fa55bf7ee9f6d3dadcbbbe86485709Trust 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 965343 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 adf8b46d064b11ffb15b740d6976761b206c22218e0d49e66def0815a5155f2c; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / adf8b46d064b11ffb15b740d6976761b206c22218e0d49e66def0815a5155f2c, and the block's
timestamp proves the page looked this way at or before that time.