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
8c7219070585b353dbf443ceaff73bd0e2e08e619a981af1b1287717cad8ce28
b5424d9547a35a329b4024430df1f7117561d7819dba876c16a3fd6f304408a2
3ef40b31cdd78346f03b63b05db4708f591166ae197c16db27bb5dca6424dbc9
33dd301dac652e02e3b06ac684c0c4ef3204f3dcda1832aacb96f2b103059d9b
e3ca2a3c5c4014f005e725bc2fe5e00e87e148a82f3fe7d06ade239526dbff8e
e98262ce4ef1ff83f47f57e42ce0bc69c89fecd0685d7cdbfa2bf4a48999d06d
592ff2e0462b309ca30832ab36b5aea065e36b3e7ffa0b5bdae411216112efe2
618b1b5bc33e7f39807efe2932f7466d6edc34411e43a6fce8eea63a0d4f2520
cee579665a014a1932eaac6a16ca232f25594a5a8551f4bcb08b5f05b7f085c7
e4fca5e1f2cdc36b6e99cb2c4c508a88e980edd62b5ee68379cbfccb36b1943e
bdb184ea65afcab5d9c6a6369ca1e583b203c5fdbbb2f7dba4ce87fe7e161d30
11283c1171478061e7274267176cdc9a538d461ebcd3f682fd198f8f04ece11cTrust 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 962735 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 629889a4468ee74cba80cef9302a6cc9b014fc79addd323a9f72e79a5a8cc612; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 629889a4468ee74cba80cef9302a6cc9b014fc79addd323a9f72e79a5a8cc612, and the block's
timestamp proves the page looked this way at or before that time.