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
6656666352d783809514cafda74877862c8a5f46eaa29360d2d2f3b95541d7ee
263216f8c36e61558fb111b3c7fdd83c331705fa846f2611a7a4595004c94ca3
94a319bb846d95cd13d511c91e2b097bdf566d1d2d0bcf33e9bb3ce6cdcf8e87
0c8f0ddf0fd5a8fafb15fa8569966c60a733e5819d4ff9fed6a35983016c4c58
cca89c5c0aec09684184febb4c47ea56f52986b652265319664b8329183cecd0
6a3ef6e2b81b4599f840096cf7b766cdc992b7f004709b76369c00e66f051143
a55ff7a2fd4d41b18045d54551916eb2b82f5683e634337ed461bb3733616ba6
8429edca4cb220ec8a6538e5e31c406d88197ff829c5b2a3a778c40de17a6fb7
cba6c03b45142384d47f8574fa84f34c7343a3e7bddbd9b4aaea47f3deb874fb
e0906a80b638c62a8c6a84293b848327671fa1c18765afbd3fea33791445a07eTrust 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 962984 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).
⬇ 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 9d04e6354224bffe9429effb07ae7a1e455970dc7a09b86bc7ef5307124b9f7e; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 9d04e6354224bffe9429effb07ae7a1e455970dc7a09b86bc7ef5307124b9f7e, and the block's
timestamp proves the page looked this way at or before that time.