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
fe8eed3d09749fe801b51cb228aa84eb56bae00ecea50c54bcec86802e11c96e
7cd60ec8004b358fcf0a79747b95ad6fa0c5359ed967a5595f41a74638744b52
a5ed1fe43f15ce0aad2f14566f576236951881e3d2157d38dfd613f9879140ab
69ec1234b89666cb4fbb341a5ec9476bac1c79cd24801a7a50d7c9aa66f1bbc1
95e5b558befc4a89f1944cda247db6d522fb52f9e115d720ed387fe2bf4c1e87
0bbe7dc4ee6a11e8f0a31772ccb57e1a8f7fb2a56a8578eeca75514e785f71aa
2f2216c8e2b0e5fbf5f63c32fa1f407395c8815ea164cec6c4e6e28401c4f0fc
26d5c30b0c7ee03a7774325275f5be5a0acf1f4e4d1c936a9d0d4039086ee086
67c436c4d0c29ce25697d97f4885cf89f441738fe584cb7e766aadcc77863d93
fe012189af156808df8564ad7ec6eb5b2149b7520bc78171acf72de27b6012ce
3321610ac150437b94c542f224b7f8e3f07eebd4a4b9d3f978f73d6bf3c7e14b
d3eded43a6ed5ba434d5f6dc34b80e6fe8298b7570eb7a34e8f359570d43a059
9583eac34959e185fcb1332eb91ff29d96c62e08a5f548c5054b8ad60d795299
e6c0f6a6c33b72123af02be09ac98fce2527c65c5b80078ac12dfbaf829ca655
275542271e2681e49653352c851505d8eece3d24cfaa07bccf2081b8b4c75e71
6d2329b360ddd9a9bb6dad63a19f100776a6da766bfecb402f73fa8a163e17ca
b2e2a4a7973d091bb46ac859a7c28ca6f312ff429f2aa0491581591c2b25c863
ffe86995b6d88a2759dd1ef984b52090e12680be28f82ae796082fb810590eda
18a78c08aaac0c513acaeb5c0aec7b9221ba87259051d548bf2b64a509dc0833Trust 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 972093 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 aac1760e5e44f5d51dd0b7ad672e0de95083859e7f335d74065ffc6812a4eada; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / aac1760e5e44f5d51dd0b7ad672e0de95083859e7f335d74065ffc6812a4eada, and the block's
timestamp proves the page looked this way at or before that time.