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
d00e701e11495023ada3c2e7947f37c56a8fe0b32df8050de17b93602d6d762c
d016e1042fdf37b830b91d3b908078a0d189dc8ec973e75e0331b1201b2a7298
c76663aaf768d41a3a262303cef7c71558c9bf2a22bdf5a3f0982f700cad2a03
5f7975b9a19abbcb8d49a0183ec592affa9e5a1cdf7330fe5cb1ced6bdbd278f
fe891373ca74b0542a58e727b515f14e69826a5d580d7ec35b40b87e483926de
ca3a8c497ad8f4a7496263a5845dfaf2d049d79b621e166c86161c6ddfc619df
dc30555d674272e4898ae4b54b6688936aa4c112bf5a3cffbae4905b2fe2f132
d2e5fa4fe90da3401edd3e8e92d99516fe825e862e9dad9047a189eadf2d84c3
f4646b204fc05ef3c445a8094673e1c9618adbc6a828804ff5cd784d7e19ca5f
c00fafc036b0e182500211d2ee55fcd2e83bcff18054db1e3d2c423b34e7e7ac
3a103d04fae4686144dc8b7d36d9023c66b236ac42f7e788ed563daabc3c46dc
b4f0773a4200669c5737e353141c96eac734c105d2c3e11548cc104a44bd13fc
7cd40929c654c8c6b4700c7b9b33ce0e540ea84649cfc9d49d8921129f19fb24
e6a6afd1595ac3db4108466fba483d638ff6bcf24011c4b312ab2d84e9b52a57
b4a7f1308bf3774b061fe39b050db5f7f28565fca0bf340b1e2cea93d184e6e9
7819d2a6247bcb07fd6f0f27f6c19ca311e27340bb660812e70fd88a33d874d0
755ec26d0698e5793ace24f7e63ab67655fbc44cf3a17651d4fce082117a276b
12a5b9c6d37d136ead52f0b6af83ffa2a74379ba49c84e14d2b150aba4393e9dTrust 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 964330 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 02210466c9c28691af277c34fb08a17392d99df8aaca084211006f7a532a63a3; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 02210466c9c28691af277c34fb08a17392d99df8aaca084211006f7a532a63a3, and the block's
timestamp proves the page looked this way at or before that time.