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
9e0489b0760a006e6e8972546850bcc4a8693273e64506a6f140ed9e81f17313
1ca3aa5c54ae527ea559e0ea3cb1bc8e5603816a03ea3868a070202eab18ce85
48e21fd0b2ff3c868b6ed0b9d2ee8436140afcca86a2e951724dc75b8cd5ab45
eb9d89d4732baa5a297fd2c68d191db18c117337a47321b589d68a81db24e932
d4a7cab9fe80c67e30d5fa82aac19d8ea999a9aea6a9f14d83d9dba3efc9a301
2e347d971c24d3c792d10614ae4c657b4f4f15d2e5996f17737b5c68d2a79cc7
ce7d322121793b80a35644e56b31a1e94e2dfa54fd5882460efe854279982135
57531893e0710dfe39b138866f017f4912af0fd0c2815d2791f91fea572b0caf
7247bc9916a28548ca85e2ba2a2a785f3f1fbf5f22a1146de378f0f2fbd9e298
dc893111e834f04b14f2a70640e9fb4de6b1b688a27ce55efe3d881517c848a3
b2c0559a76294404dddc71ee930fb3c2c1814a55dd01873c4b7ab682920d91d4Trust 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 971836 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 f4c08376004d7be7992981bd33d8d5d7ddf6f0981df897319de965f49db6ce06; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f4c08376004d7be7992981bd33d8d5d7ddf6f0981df897319de965f49db6ce06, and the block's
timestamp proves the page looked this way at or before that time.