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
222cb45b4d2ac1555b4097238da041c632b1496c3b0666a9b72b1a7fba758f2a
6abfd177de0214ee236ced118afe49400608b2e709dfbc718957f00b9de61312
cda58a18c09f7dd02cb35800510e6ecd06ece65049dd736e2aef817ad690d597
8817693c93a0bba31215c0dfcff61515b45739162ca5cfe38d6c4f1150b5f9d3
5eefd1dd34cd636cd51f16a6d5274aaea6c2edf8c994224ce6a2e6b7f0b0ebbb
f57838ebae5989bf11f7bb7341282b712321d96eb90f8bab5ba9587b8216ffc1
1f2e53871cffecefc058c98734f3211fbdc55c5a83ea3348a41a4021dea7c2a5
3dfe3a26b87d6ce5453648fadd046a57fc16da21dac951e4616aa7a47f15d5ae
5f26ed54154ddf091a8bd0afa633de11dab874752b5c8701f11900df07addba9
bf54e5faaa00aab5dc40d49276da53f0be1560f18bcd141c6d091c9084105116
759d8ce465221e94b26e2a2c41ec885d0dbbf987e751df568d158f34d421b2bc
450f0f2d18473893142b758ceda8a32cb17aa3fe75160ba8f6849ea576439a12
5ccb158979ed249dcb29abe67bfd64138f84109f6d874dcb9949d682113658eaTrust 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 970313 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 d3436f9efb006e30d829daf3f6d91df03d3d91e4426262390adca4c9eb1512a6; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d3436f9efb006e30d829daf3f6d91df03d3d91e4426262390adca4c9eb1512a6, and the block's
timestamp proves the page looked this way at or before that time.