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
fde87ddc6faadd406ea8c652824506340d99ad8db45b224e2ebe3e11c31789d9
ccb79018ff782b7439febd29a75ca10547b59eed0e158b3aaa26deafaa65e6a7
21e6c0ed973c14f2e1198d4efba58911b8bdaaf2f1d1085b9af03648104640a3
ce6625cd1d694f3fce308a337ece71d54981480d898a68f5e85c35082cc706e3
e2ca818c778f1cd5616ec88d7ffdce6ccd518e654e15082dbee82d9a4a9f74c0
e9f8f64677497d7260df7f6d3bb51295f5b6ba1c6e88ba29a265f95435c53650
1917832bc61c911e79d513160ce1990f1d46fa2940d2a34e2e1e7396e017963a
0a5be91600201d995845712b800753e9120bb7791607b23b62f2f86b051d441c
dc115afe63633078ca96420483774230a79d2b8611d4ced1f0793d9c46b8945c
5d94afeaa2cacc4f530e62a5a7ef4e259378cce868581b0b8782106b85c4ca36
2e392824d278afbdd92219a193dc0978e6b7426dab70d794b4f5685793823919
fef919497864d5d43e8aca6b2382add43985c37c827a65136d1ed5cf5c26c169
7f7dafcb395f09de121065e1fdde3148742b190785e3d2935c7e67579ce17650
b6010279a68640f47a903ee0001fc130f8d716b172289020583a986b0132e26cTrust 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 962448 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 a598d603f376650ae090872bf0bf732fc6e73311038ba5e3390e204bf545a004; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a598d603f376650ae090872bf0bf732fc6e73311038ba5e3390e204bf545a004, and the block's
timestamp proves the page looked this way at or before that time.