Capability status
What is real today
Designed for a future Midnight proof adapter. Current V1 runs locally in your browser.
Implemented in V1
- · Local, deterministic inspection of a plain-English data request.
- · User-controlled minimisation: add, remove, and mark which categories are actually necessary.
- · The Margin: an explicit pause showing approved and withheld field names before you choose what to share.
- · A minimum-disclosure response prepared locally — field names only — copyable and downloadable.
- · No field is ever preselected: the minimum selection starts empty and only the user decides what is necessary.
- · A metadata-only privacy receipt for both approve and decline, with a Web Crypto SHA-256 integrity fingerprint.
- · JSON and PDF receipt export, plus browser-local receipt verification.
Not implemented
- · No direct transmission to requesters: Midnight Lens never sends your prepared response anywhere.
- · No requester or business integration in V1.
- · No Midnight wallet connection.
- · No Compact contract, zero-knowledge proof generation, or on-chain verification.
- · No Midnight City integration. If Midnight City is mentioned anywhere, treat it as an unconfirmed future showcase possibility, never a dependency.
- · No identity verification: Lens never confirms that a fact about you is true.
- · No account, backend, database, analytics of your inputs, cookies, or storage of what you type.
- · No monitoring of your device, browser, or network. Scope is only the request you enter here.
On the fingerprint
- · It is an unkeyed SHA-256 digest stored inside the same JSON receipt.
- · MATCH means only that the stored fingerprint equals a fresh digest of the canonical metadata — the file is internally consistent.
- · Anyone able to edit the metadata can also recompute the fingerprint and produce another MATCH.
- · So it does not prove originality, history, authorship, identity, issuer, authority, recipient acceptance, time of existence, or tamper resistance, and it is not a zero-knowledge proof, Midnight proof, or on-chain verification.
- · CHANGED means the stored fingerprint no longer matches the current metadata. INVALID means the file fails the supported receipt structure and format checks.