Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
acf48ab945ab22c2e4ee582d25f7f79ca7fcf66186130e100499fdfa0eeade4f
14d557f03265eb4dc9136d2062d9b19c8bebd0d4f29412b37dd6618359cec8d3
cd804c3e04b1912a427159e78e207083adc9aa4d3b82e39f98c8366243df923d
c6cb631aa0d771028bb8d712b9187c0288d054d048d51d3adcf36d8bfdb8d6a8
141a6890325d9a8ad1f32319429712bfd2f9e1fe2ecfeb12444f89dcfebf6197
36c5f0a254c81d8e8604692cbabfead0c1a7115de17c0942b3c431bbc8b6f2da
dc4486f25c4667f105f9bfff5ecb0d8c1cdcf8d733007106e104c730ca027568
b66a82e5aedda72cb24e940b74590a0ecb4de73195ae72bec19f0f5f4b0e1275
e11959ffd38e1aa89179eae3bf8976a88b0176b76c26cab55dfe2f76c521810f
0886ecb36a7df2a31fe9ea1e42f00b393e61e61ba2bdac6f42704a848afd8165
2e47c3e10991938623faadcaa9143949951f51fb43e9c162f7aa49609053471b
096812ab8f0c3561af0e305bdec2c0af60e99f6d306bddbdc343d08698bde16f
a1c5f80a79a7e57febc3770c04c15b6c9d333b819e87555b04113a4d8276594c
ad9cc685555c92ed20d5db31c5e0d3c1571948a8b07060ffc74a3dda23139c98Trust 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 965784 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 4271d02bedf1af34c2bfb57b9f77bf75a2f4a594c8255407ffa08a727ce6cea9; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4271d02bedf1af34c2bfb57b9f77bf75a2f4a594c8255407ffa08a727ce6cea9, and the block's
timestamp proves the page looked this way at or before that time.