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
8f717c70c905e462e5d7ccc23afd9ebbcc3c393a0828c292fe0af64cf9bbf241
887755200ad55e254d88e3bd848e8537e144a7563185c75fea2a705213ecef23
53fcff4745b872665060a7b3e05023e512e3d1bfddbd6e41794bb98dac2b3bf8
89797361364bf5e3cc46e44a6e647001860e246860cef9f026e15468357fa5ba
8bf7ef2cd1f0633180e2709011561c513986e70af3da2a394394a98145b04d53
dc8035f0089a39faa91e1733a40fcbbab7153ee6a2d0a3d3194b052cf5d2b17f
11f365738e01e0cdb3602d50459ae5e41a5f6ed7f6cfeb80defaeff826907594
d07679c788a69c763f2ae80ffa3788776c178bd03d69a52b180721c917e333e0
5b05a1dadce894724c8e7cd21881a10632aab24d08254e153f3774d682de7e3d
3a83c9853b093a6832e6b62d0b7d94c3668df7b0c33b0f39d8c480f361f8300a
831f6ee9c655f1e29eea92961e823f9c35719e78661e1be1b70f88f77b35f3d3
a58427c09d5dc5c2939cfff2b482e6a9452fb117bbcc83e0d3f6bcf693bf24c9Trust 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 962771 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 7e517fcecae9e5491fed9262d225d03ba22dc7d2523895d0c873888739d748cc; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 7e517fcecae9e5491fed9262d225d03ba22dc7d2523895d0c873888739d748cc, and the block's
timestamp proves the page looked this way at or before that time.