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
a8d486e6cfcd3d932132cf3df58f23f3359161c7f565897837893448243942ab
2f1e061213bfbbbc6f83543ad02132a71287d557ee7b19bd94274ab49c40c0eb
a954536c4b60e3cc3b9b9409e7e9cf705e6b27324f6627acc47557b867d03eab
2ec125f4e89d943d8455ce9fe512422046a71dd266993c70e7c44692010b5a7a
65757e2ad3ad760c61f0e343b063fb4b72d3a9aa0376265366a3d1522453888c
4cc88a46032baa7d32d8739e89296755dc6a1064c8c4536a2469375a05cec78a
2d948376610d2e4f6e2d1df3ffe40cef02c5bbcc8327fc90634889cebbe68a8c
3dea2077c26f5eaa540c9363b6e23baeb6e350c7cbf69933f52353a04477510c
c077d4b5cf941a0b4669fb02365c253c65160f6581e044e6911e636f4db87092
02d220e0e3bb26b73d76af0fbcb518fba927a01f8d9a440802d18bfb3cab9011
d964710fcad40a1bb0510c48af0fae2b44620bd2f6a1706a4ae3055fbb3a7363
2b76c29e970701895576692870ab2051e2dd79b313d9ae935af14fb79a653b1f
a094540241cb4005127ffafb3b11d30b7ffc306fa640aeb117ca447724b8b70c
1f0853eaf4f7ddcb15b117cbb0982f0cf68dce185678d97369fddb5f4d8b74c7Trust 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 962712 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 42c008688797f27b1bb81edf06f997dabf6500bc6bd7f82cb6edc76c260c192d; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 42c008688797f27b1bb81edf06f997dabf6500bc6bd7f82cb6edc76c260c192d, and the block's
timestamp proves the page looked this way at or before that time.