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
bd129cb6ebcd3123167691f0a953ebbf53fcfe0facc4cbfe1c1e16933797bfe0
3861cff24f18098d934c1cf5d703344f021a6880fd8b5f80c914dec4cb2f8d49
2fefa849ec70fd6634742e81ffe90b6e894092610a363d9d495add5293e75535
7f43fd64561f89e5022d7613282ff7e8dd8085d35c6e0bf4825d8e330e842b32
0191816e753d009800c884e78f12911ae436eec8039e71950bbea56cefa3016e
98c6221321e2d596e255533f3c527308b93b18fab8a997dff1b6832bd5e43c88
079554ad49bc7da41343194a4cbc25a2209d20d6b71797e9735b69db36084b7f
e64276b782dda331b021c1d4e5a1fd879da577395a6a4f1b35ca9b0a26152e40
e7a9832e0695f59fcb624f270bccd176ce535278b989d1406c8669a548ec8fec
41c33091a363903aaf5390361c12c1e4217fc49efe554c63590cea38412ef66e
a5c95c5234cc5445eeefc44b30f69f7c1cdabbd4e3355bf6527cb41559ccc6fc
e13c4e026a2dfa21cfe521055f48f4464da1b05803c78a650bf034a5e65c308bTrust 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 969371 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 664d7b01781136005ce8c2c34091a2b04f8956c8837cc4ea8f0a26c1f42951f4; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 664d7b01781136005ce8c2c34091a2b04f8956c8837cc4ea8f0a26c1f42951f4, and the block's
timestamp proves the page looked this way at or before that time.