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
2539cba4328eeab8ee9ec0c0db43fc816244e1454d182d6526652b8bef51ed6b
a27f40ce0bde7ea702fa3e82738afc54148a8dc24d0622ee1c5834148f5a29bb
0d378d39390c1279eb13e9d8c59f9079d5c43dc62785862b390088b3f1555780
1602563ef1b94aedf5d082a93c7f76ed58dd46ef5984f9c6012899be0980fa50
5dfba433f2847d3beedf6f169a4a944fab2e5aba729e67db2b3cf73fc52207d3
4db949febffa375242858befb65186b032b41c4013c917c8e21a17d618acf59b
19034939e63b0f67bbb8f32ae0ae5344f6c7286a2cca152706c288bf8365f7dd
8d25a2a9268fee56eeb0823b13d01d95af6058dfa54a81cab8c95447247dbf8c
66970cd2e3dead6de03c1e96705d4ea5f9d372cf5c47f0b7117e182fbc4c26c0Trust 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 961944 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 8be6a908e2879b1cc01c011593576c39041afb18d04d78752bdf7344d4916586; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 8be6a908e2879b1cc01c011593576c39041afb18d04d78752bdf7344d4916586, and the block's
timestamp proves the page looked this way at or before that time.