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
abc62a34adedeed5ece6b2bc7f37fe405e899fff954e2bf4148a62991fc8a1a7
10104d51b5b6bf5e7cb7ac48ec0e1297224e6ed09f9831785832b64f2a6384e6
6b2ea06b5c9a84a969849c6c733e4323df84c78218d06e175affa6a1cc92c068
6538d5e2c1c2a21f20239a44df594d461e22f2c9d26140377a1c91b8c38e34f3
d3600e39b03aed47f01b5891c1382ae15a4f1ec9314a4f429aab9722d1755c07
7855052777c2ee4f73aea71dada32665c4c527403375ac6ba2ac3a60c3ffb6f5
18aedd654022abcf8b97a0cf70cf6dfd6e153a5b045b970970e116fb0f6977ce
300ca7a89be92e72d470d00934fdbd69a1e59556e3093ab45bf9f64f1825f34e
274364bcd0823fdde66e19166b5e17af6eaf7fc9e45ef411ed8783c400d6b79b
bf808c574ffaaaeb76ba70d67964dc8a7b41b6b92e430b795d720b53dfb40c5b
2ad8253db5beaa1868ecda56aca8511ab53a02b019df552258324ff6a2f1aa5c
6f0b0e50a9b8389559bc6491c8a50fd8cc342e67f18ea71e46e3beea9e2df91cTrust 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 974217 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 68e348d573b6851174a2738b58bee4442c3735c2aa3dcf42970008fb46177c72; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 68e348d573b6851174a2738b58bee4442c3735c2aa3dcf42970008fb46177c72, and the block's
timestamp proves the page looked this way at or before that time.