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
7d44f5de2c2fddb5ff687a17747f2183753010605cab018f5387e897917a7c4e
b2b8d9a6cc43ceaed3b6e73d9becb37009d6d9e39f84e5d2b940e07eef82763c
29641c98bac2654be10ae98f564d40aa939a5c20426b43ee3b6e8ed8726226a0
fdb84b6e57a98a6f475e714c0ca3350544663937bb11696918bdb0f1600a033c
c25f58277543382dd48892716bae01aa893470e2e0e49ec7e9c9cefb93459f5e
51669cd0a0efa4427a89383bca93745c78343eadf0b293a8071d3d2c19cc3025
57ae94100590e65a1b8dde00f0bd4c7e4f009db131ed43fc9667119c42695428
80940c9eb02dcb1a27af4aff0328ccef4a83843161206fbb7e5f55b4bb2b0c2d
ad01ba7df9cc65d3d0f5337ca34713702c94ea92798d08d9ed44e0a322ecfb7d
d633b1e1b3bc21bec3a4dffed9843b5bef7bb5fa756604306490beab5fe7596b
184d223d733bd28452a4bbf93812d428d1aa092808f9bc00f083ab55eb00a550
12d9b62b7d3c4625a69528fe89a074cbe31165c6d7134ddfcd7681069fd2f8ff
004796ed744f9d769642b8a1784149b479a55f49891a09b1cf972cb021a57687
1e4fcb3dc199eb3c6aec8a08f19e3f7b101f80735337ad4c34376b2f201cd6d8
d27162f90e3945437a182423c8364790af2e94bf57dbe9dc5a456a39e18cc552Trust 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 965041 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 4ef737489639f219d140c0f2dc6c513ca65996943880966fb7a6a71e14416ac3; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4ef737489639f219d140c0f2dc6c513ca65996943880966fb7a6a71e14416ac3, and the block's
timestamp proves the page looked this way at or before that time.