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
727545c37b0e11797f1f969cc5939236580ca91cdf929c89c47f4587dd6cee70
81479050e770548531913a1ab643d3ee410883b9a484eed95afbd8cb72691183
93463e30aee1f6b7b12f6f83b668cdf76b0a68a823e0629ebe669fee2726d51d
e1fbb9a0f8aef97677c4c6038cd24eee06b195b7e24ebe40a059f63c23f4e960
9a10e668ef4a0c4ceba52924926e3e92b4d42cf98d62983f6f71ebd86934a388
822036b4eaa5abcb863738c804b9a24926f89dc75a18ee900746d9633367a710
0e32f434fc32a435272be379379b1081c8ca2db5b9f95a7fa1e84b3cef4e6bf4
08e6c37ed4cbd07360174c53f15f4800f7411cd370f145e3da5682f5d4ce54bc
805a7792355c2d81fcfed5d88cd25fbd90d5c51873d7a9cb80fc8b780bd89d3f
15e15604869c7332cf14c03d3ac9afe508893f9bd37d079edcde05bed858fa5c
a0f7517a96b240421d581d3d0898aed850773869ca167aed916e61abc4f64728
639ad1624910cf9d1dddcfd401ff18866636dfbe567e51d24154b9ea611a8fc9
1387c32f67d37b1e277399ff218d62f4ea8744639f0aabfe2dacbe59161656d3
b4738e91088bfc5b54c9d5f99616e0fc8c58bc38161906f3ee9d95f48d3eff3b
72c9d16599fa2c9f506a2f206cddee21b97b43d967126ddd6ddd1ebc28f9a15d
8975acc267612f823cb5ffd7a9f264bcb83c1605cd6e5ada3e347ca38808ce6d
da656cb9b2f51d4c95bb775180f204f609c171b3425a0bd5fda3c8b78033a4a3
e318f07d7d327827586a9e7e347b26b520c4c56075e5dd3ed6ef0986e1d23c77Trust 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 965158 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 c3f0c2264e2a9f96191e97f4a1232c129410a237657cd314f611faf38874f3f8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / c3f0c2264e2a9f96191e97f4a1232c129410a237657cd314f611faf38874f3f8, and the block's
timestamp proves the page looked this way at or before that time.