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
190ae95dde7260e7fe08b2e299d38fb6c75cab3e9a69003a337a667c025f2b73
a7da26f86f8cd1be176baf4a3c49baf92643f933cc79c4530587352a374501b0
7526685b5fc302cece33d7fa2f1079429f219ec55a23f1190670749693043490
72317589625f39a81cc68cde1a5f39ad5f53b29254f56b6615c3d56352d7c6c8
3aaa7a94ec9cc14cdb01a41a0de595d121496ebc1b5631dc6e4a68dc3c4d7030
e51ff95226d667ce2edb72b42168054b606bff5a077c7507260ce9aaf6b0c7f4
58e3c1bef2dae96f1792fecb511d4151cd61f24a0e6c41497a8324b8adcaa1d8
eb9f2a6c67cb1813a5caad0a04b56ee20d7acdc00a11bd94c80207a26496be99
ed7a6698da3d0ee4f27abc882f0509336b108e393ecf23c49f58db7da3f2dbe5
5e2c0bc2295d359f6f740a131d66baa8affa82abc3f2bd7d14936e4452bbbf80
ca84eeb05eca9150fb8979dbf0f2b10f0102c2623da7a0854713e7413f3f5321
2f7272750a9e627cf0ac04ebd66197266ff618c1e047a73035d0d6cbbe9eee65
85c1f07596e77275a32b10a1f8df1898729748c843517f5fa31e510d175c9a00
7c6a24e4eed10f90b129256960da2a0e6f377e9b885a3888f8433126c845644e
ac7078c2860f6b4643fbe017e2937a862d6f67f95084ce98fb58f170b3590691
*
62fb0e78a363fb1a5f1f077e411330086760a66d634108b6fdeb69e9feacdb26
08d49b24ef9238ae3463f30ed84ba1078048549b182b6a00a63c949a95c53e46Trust 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 973421 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 fc3bb844e64505d8a70a884ec513fe1d75ebc60496edaf8bafb906bd529047c7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / fc3bb844e64505d8a70a884ec513fe1d75ebc60496edaf8bafb906bd529047c7, and the block's
timestamp proves the page looked this way at or before that time.