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
957221e38b5549aab13aa4095abce386ac4d11699832fd5166db6e02601616c1
524707f2bdc5a1bed6167714320c620b52a177176253e2d25f47cb2b8d1f9779
937fe4f73508ff7a893793077076a7a2899dcf4a855992a79c2da2469a361241
462b0b987d8e6930a0bc75aa45f4085d4dc12dce556ab7f5e6fb784c62c7e807
f17ea71807aeb83f6fe76d6d2ffe06ea37179bf6def4536c6d10c19179125915
eb4d867f6475adc417c24c0ddf681118cf2b5684d08aff2d419fd6ebec13c233
4e2f59dd5937f7567fee59a89247ca143354097ec44f0a84b3fba9f03d6acb6a
b4fd2a0a9e5ac60d294876d7a6d8f64f4c286aa30366cf48939a6a38d4e9f8ad
19fe0a78054c8909641ae5cfecd372f47517a4bba0adba3e579f5ac578155513
a37d64902f1930a78e9413037bbb1df4a4058fa1e73b94b96eef6e6b90d1d1b4
7996da4770b540fbbfad952005501c6d24c4f014a3ab109806f41202b6ce417e
c7e3507b250e692da17d0b3d9a3bca6238376b9a4b8866a68af42152adee9a39
865a606d71c0e77afb0ff41057671d5097f8e41d3f81deafd68bc5a27a0b2042
d58c068194b8e147ef8607e9b2e71f264d9fe7dc1c10c5f01c52002f995b09e9
6aeb9dae150704f06b1ec5218069bff69a56608c87881b04131880b52a3e9062
6cdbe492ac82b18cea75c67e12ba231956306ce117d98f8753976e7a1331b4ee
7c837088f83f62e08e9e02e2d9f548693e7e843abe9a57ab6e8455b95ca332bbTrust 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 962329 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 200e76aa5f689c23e31cbede72fe79562ae6ed672a0d6c023b2913952f729873; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 200e76aa5f689c23e31cbede72fe79562ae6ed672a0d6c023b2913952f729873, and the block's
timestamp proves the page looked this way at or before that time.