Proven over what data? The source signs it.
A claim is only as good as the data under it. MIZAN accepts data as a signed source when the source itself signs it, with a key it publishes on its own domain. Every attestation names the source, the key and when it was checked.
Any source that signs its own data as a compact JWS (RFC 7515) with a key published at https://<domain>/.well-known/jwks.json. Accepted algorithms: EdDSA (Ed25519), ES256 (P-256), ES256K (secp256k1). Keys are re-read at least every ten minutes, so a rotated or withdrawn key stops verifying new statements; statements already recorded remain until revoked. Submitting requires an API key.
Not zkTLS. A source that does not sign its own data cannot be attested here. Proving data from a server that did not sign it needs a TLS notary, which is a separate step.
| Source | Key IDs | Attestations | Last verified |
|---|