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
1649da96077dd39b28c775e6019abe5103edf4f895af92d831750196ba136e94
8ffb0afc99ec5aa45b5c05babd8dc853f3f7e165bee76409af3ae26d7ca0e8cf
49be1a2d28f36e3afd21086b4cb99831e786254ac24ba21ce5b72cc7d9bfc659
1546efc2e4cc1bf1c2edda8370cb4ee89e822d6bad77b0a18518a3c96b7ead22
e289a8c012868d2585f9bd74a1f797d24abff76e17aac7d636a0d6b6c334f177
a837f7471f0fcb136f17b8c1370c55585a1ae236444191d31828bce4faf2e9dd
7656a0def7afe46c56c812b1b614c6ec0109d02aee30eb80135616a8abbf5013
fb8ec8fd80d55d5b194a5cdaf4534a51df608938d5e18b6b2a16ec4d7206aaf9
46b0bdf9d0f2028f2719ef461519fccc8a3d8f7df9a0061643482c1fae7b3c1d
cbd5800bfd43a1f99b706caa8866998c283ebf456a951b29be5ce2626237b81f
215bf8e84e0daf6427d2042789ad6c56ae5992a41b2167315fb6945a3ec2c197
1af18ef41a8af14d4366504b76672e94c873bd69249ea2210064d4e5f76911e4
d3c8503be8ff9f71a125fd179780149a1757bd658e3964b152296bbf9615dd83
e3844560782cd90a7d270546d8f3d26d4ad9964841573396451d9f7096243bdd
bec97ae3bb8404c96378ec46a28ba2363e2f63838bdb445ef6e94aaf83e00391
8e35c683d36674c8a0c8a2266135d25b58f6a2ae242265386c32929d6027eeed
b6281a5cf443a18e162900e09ec78c08b79b935e042723ea3dcda0b2bb7643ea
c795cfed938e65c819495993ca8ca49e8d01f89c8b3de7e7a16582e4dc3d6539
43d7496df466812b490d5294f4f28f366f7c8d8ac4d23a7879f518b8a55c8044
0906b97b4c8478aa8a0c72914e8dc16f8ce6cbadbc1e397047ab9b8af5929cdbTrust 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 973147 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 147fc8e9a161d9ebbf87a01bb9f91c1a5db1ba21a078f8e603c1500f8261fcca; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 147fc8e9a161d9ebbf87a01bb9f91c1a5db1ba21a078f8e603c1500f8261fcca, and the block's
timestamp proves the page looked this way at or before that time.