Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
0fd157efab2012df1ac8a01e0bd2ee6dc8cd63cd90685fc0a23e2a8296ed8553
3534b0f658256577531d91594993a5613a0184567ba1df1cc3794e7aa34cf9e0
456a76493ca385de2072fb9cae896a910401628529cdba50fd9ba38a6f22ca9e
736789658333f00991e867df18cef16f68a63bd31e13910102301bbfb36cc52d
091069fb9b7c32337fd33b282a078400d7f46e9788d629c5d8f6a03cee82a6c2
7ea63337dca44cf6f89009c3a7b6868f497a19e537b082aaf5a9ab95d129b18a
55ed048fde6c792454a7d18e2d73cbe359b15b4af1a5a63ab42fe5ab66ca02c1
a2adaaf7cefe46625412a9d01d90df5653efdaf02ff723291777b4ac84c79d67
01845774ebb564194a07e15c3967f8b7c71b6b934a219e43c9189df11ee8a973
9f47a62bc08f9306a57edb88ac5187b8094f05d2e4305addd43940de9499ad7cTrust 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 963772 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 6e36db03f0b29c6d34bc278a6fc832d316d04f2cee8172b8ae2f4abd38a90451; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 6e36db03f0b29c6d34bc278a6fc832d316d04f2cee8172b8ae2f4abd38a90451, and the block's
timestamp proves the page looked this way at or before that time.