Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
c836bca39a963ef653336e6854b7cd4af27a31a8772616be8d203e40dd4d210a
e28c8ce30bf86981cc9b259ecde019d0b095b817932f360d6c058c6f9b22366b
c54624e84db597adbed87d41da9c3dd45414b5b79036bf0db22094996b70c769
0e2709dde84c38b6ad974c93c8a0ab68f3a53b0d658bd3113c81072bd7def4fb
9d8d348c9d2f70d70081dd6f0c37571de57271b8d231b62b356b7bf370a2cd4e
69c9259064d7e2d6ff93a7254e120c9511a73b35a5fd09cbd396a72dfbaf7014
ac64a361ea150bdb9f42588de4fab81f9848ec4b3af4ba4f5069e90a2354bdf5
068a8f6b47075a73474c029c0d1f36cf3ce775f5f76feeffc60075665a28eae5
3968acb22b6ed806f1d134b95c3536da66fe9e3b191f6fe2685d057cbd415b53
aa20df0bcb417486c202cc3c99f7eadb4c3a11cfc725801cc18b44452180302e
caa160430d58ee97a1550d858d94e74c5bfd891f1cea651f151095cfb2fa053b
1bd17afefd1e7e8aa7eef8a189f3a57596add4efdb2c910f532a7cac88b25e03Trust 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 963610 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 cc872251d46d5c11066c1b04b874158430f2e4e1957e6635312c31969ec8a957; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / cc872251d46d5c11066c1b04b874158430f2e4e1957e6635312c31969ec8a957, and the block's
timestamp proves the page looked this way at or before that time.