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
62d2e403e81901f2f4321983a79a45a153a81e187f2f417795f321b279b7a122
8a9375d114eded3e817fd3b7957f0bdc37fcd78372be7e4cada35bb123e7fec1
8bc70510135b69a6e794eeced965ef70a9e52017bfd3d950681f37245708b952
ca17a405aea8454443ee53c11d08041458d5f398b3aff134abc7e7e3d6d6b52d
e95b2a1980a7f2da7138ccd1ef26727cbe00360a5fc9246b59b6defa0323e6de
3541e98ab090469f46cb4b5c49a7c6ff3f9608afbb3e27e66f51601912dd4798
bfa041daf5882007745d279671351ae73e08ed979777ef3691df3d1d2c8b1cd0
adc0508eed6d073ea195e7a9e74b2114c7155000df54c77669fd1330bdb82b86
f527e4b7dc337578625f2ac8d6a5cd9ad12578c86e1c028ab9a83411acf1a84a
0e2bfc02932e11be265e04e9307d6ce446371d77fe7c949e4e14e6c8ef9a2204
5354f80b0fb2f210b337c328021e9985174f10524470be37ec1f0cbdc9d6f1aa
709e06bd3c4ca9298a81f87d250e8d0701e10afe2b09bb5a89b6ab7ccea4b32d
09d13463b5129792d562dfb236c3a61803c95b8273063adade1cf72dd786cbd0
b6d342e52cc3e24ec236e7ca1bd766619481e00fa30d58014964bc76cc3cc3ed
239d635856b6677865a8596155f3395adbb39d42cc34b2503a8b9c0955413333
269f6c9bf359cd4bfbac3ca91626ebd25d61231190733834feaf43a6950022ad
668dc4443c1d0b27a439578b8c87f347d535dabcf3cf00f243571008af859990
33e534e0ff82590c0f3b7645be51505e2d2defddde489ec9fac5a8c10ded9721
d5ead7fb7d68092e71da933a3ca62eba91e6f874097ad2c4415f2413cb5db797
6cebcae41db633139db07ae01876ede665aa05b2c7a3bc001da22dda0acf906a
8361c0af51c72c1a4bed87c6ffd50034d7ab31e5c70836c0dfbe04563e9d694f
227e9fdf52f9e32e53d85f25a915f2bb9bb1d7559e899def9e6e9227455d67fdTrust 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 973479 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 878d48a2b60104170df25951041f1cab51074124a1249ab3a96471ea829fffff; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 878d48a2b60104170df25951041f1cab51074124a1249ab3a96471ea829fffff, and the block's
timestamp proves the page looked this way at or before that time.