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
e99144ab4e69e445af814e3c8e196208308181526210b33786dc29525658bb90
b11ac9fd30989153ceb936fbc2183927321d953efc9ea6cf98374d75d142d2aa
6376a466ffe95f24cb7b95d7cf3ab2de7dea39148aa649fc5d0ccc215ffaf2fe
63f090bb02ba79bf6c6dced3ad3fbe2b40d4ecd1de73f41989e803786bcbba62
3313157d00b902fbe5a00335545be0e8196164420b70f5e9094f5cc3c6c9b2a6
03358eb754550a007d846398e1c97875e75f494dacab79909c2d8b7cd309dc52
4d7d9b86185056fe824a3f982b5b463f3d31948bd724af4f523a732f5b1335fd
c915c617485c2b5b1563580ae69997876528df0d9031be5f1f3f4a7629c073f0
777a433e4524636d6f51ad5fb4a1db7952d84f5ad66293e34038e5205dcc6d97
38a1e35b525ed7712c7b20c24a938bc3ad34a888e007db892806bee5b5158de1
da628a59604e596bb8a9b47aeab8bf2b9d029b7ec6f5e94d9a8c9ba3c866ae76
5192bba69a3762de7061923df7ce984bae50f1364d5349d874ae64b763c720eb
9e395af75d4ae0de5267f70af302377c24b6395bc9d30f96e356c59f937b778c
38dfa8d74b2d370c2d663becd35a42e9bd5a25d10edd7f81e0b9ff84a0a75cc4
04f9fa5e97fe191a9c1514e0048d38edbd2b21b674b8aea90d615958832fbfbe
38d0664e743783ff647481a5ad16a1b87994e82bb83090b3de6bf5d6a4c94097
4b74864ce16c3027d3fb4bd6d9ac9c6864e60ff4458b90a32d34a0ac6d96d6ec
1a44cb12b94ef9d8d30cfee211deda5c662859435cdc30abb75c6bbce7733182
b5eeafa85cb783e1502d9b3b2e399f79c23348d3e420ba6877aaed357756d969
d80ed78ddc1a1e48ad359a2be9add25f7222e5deee31dbb90f65ca771fe9b970Trust 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 968691 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 545f45011e1fcd2bf6aa8784a823d9373810b55cde093b28189e6c1625a6d7a9; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 545f45011e1fcd2bf6aa8784a823d9373810b55cde093b28189e6c1625a6d7a9, and the block's
timestamp proves the page looked this way at or before that time.