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
40b1fe071c791cc03f763f5c7d4347f557604cd8b11f8a7c67db3ee59366d41b
13fb2f1fb5fd92e4a2cfc724ae4ca3194ca482b76efaf23e0f99a9fde36e06d3
b778243c6f127efaab91d6d9d190b195bc27c26af3b2dee393db90dae2d04b57
31579b9a78b1a63fcc8ab59a4d0ee6b9959d55e7d27c1e627f4d786001870d3c
d46e85c468ac06d7ee3e66da4fdaed7e898c73adeb28fdf7f58b68395f8ef1e4
03ec069d763f524f8fd92487be9095f68338da4b5689ac0794ee6c32cad5f93a
015a9dd5c783b690894f1230130f560544fdee67173ef795efe783abd5f0a5e8
7fea3771b34c63f8ffe1c1fdf63416c227c4de1623e9ad6913839ed307a23ebb
e4fd2e104dbf1145e56503bdef46daa07579079ffed76aa1317be3ac6cadcde4
cc6ed49aa7cc7476fc6336c18be59f9fd35f511021f9a7e7ddfb5b6ee56f8159
3ee26f7962b80b5684e99e1f8d8dd57105e72f960ed5e1519e93a0b9ba0e4f82Trust 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 968149 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 eec167bfc02e90c4e933f6d92c609c3193ff2a8b7b870ef1a86e6318691335f8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / eec167bfc02e90c4e933f6d92c609c3193ff2a8b7b870ef1a86e6318691335f8, and the block's
timestamp proves the page looked this way at or before that time.