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
ccb2eeb18bb5e3a39c2dc1e2bd1c95a4ada48e448f672176d4b3554040d7280b
a3b4add482418a5b5fb4c9a1e5dbbebfaec62393b815f80070de4eb930b0e379
247fdf79eac98bc2248454de6d1a468ba2b6c6de2eaee9b6b50354f2e7d7bf91
b16979769de14ebb17bc2b6d1695804d49edcc2eed2008b721e5934512c0bfe3
6485bf34ebf3496b74ad4db79055b54df7997cba8c812f6325af333fb2fe7ae0
ccd2c499900a06f6fe31edcde0b26cfbaca98c0a026b01626ba3f9714d65c2b8
83f670cd16d950cf64e864ac6a453eb9a4a4b94f41400132120237e63bbeb7ba
f407a59a0247265acc2e3819fbe0461954cf1e5c9b6b12a3cc7648e2a485b384
78de6f14f5bb7a1a884db200b6f48dfc656b3566d67e31676b4077f758ec8788
4bed0788a0d683c631bb403caf3befc1676b81b56e02c943d1bfe13dff951ab4
abbc841bc18ae2ac2f127799abd645c5f546d3e96148d54850cb7a8295bf8e20
8fe270f9c29e191141049c97f36392503bd7c4511a57f8ebdb2b1c04cc0e0d9aTrust 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 971377 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 23dadc73f62f93782ae613a27fa203ea3c085239c30244942b64f1b677f87ce7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 23dadc73f62f93782ae613a27fa203ea3c085239c30244942b64f1b677f87ce7, and the block's
timestamp proves the page looked this way at or before that time.