Aere Identity
Prove who you are, what you are allowed to do or that a fact about you holds, without handing over your data; verifiable offline, on open standards.
Most identity systems make you show everything to prove one thing. Identity is the set of published components with which an issuer signs a credential once, the holder reveals only the claim a verifier needs, and the verifier checks it from the files alone, offline, with signatures that a quantum computer does not break.
What exists today, measured
Every line below names the date its module was published in the public repository, the page or the contract behind it. Each module ships its README, its tests and its negative controls; nothing here asks you to take our word.
- Post-quantum credentials, 2026-09-30, updated 2026-10-05. Credentials signed with ML-DSA-65 (FIPS 204), bound to the holder's key, with selective disclosure, delegation to devices, agents and short-lived session keys, revocation and an issuer status list; everything verifies offline, by anyone, from the files, in Node.js 24 with no dependencies. The same keys issue and verify standard SD-JWT as IETF RFC 9901 specifies. Module identity, with its conformance run and two negative controls.
- Passkey accounts. Accounts on chain 2800 that sign with a passkey instead of a seed phrase; the sign-in page and the account factory are live, repaired and re-measured on 2026-10-15.
- On-chain identity registry. A DID registry where a wallet publishes a profile and allow-listed attestors issue revocable claims, a post-quantum key registry with proof of possession and an agent DID with session keys; deployed and self-tested on chain 2800, independent audit pending. Live dapp: identity registry.
- Post-quantum identity of the validators themselves. Since block 20,836,228 (2026-09-30) the validators of chain 2800 are named in consensus by post-quantum ids, not by classical addresses; the registry and its epochs are published and checked by the public anchor verifier.
What it is not, yet
- Not a finished KYC-with-zero-knowledge product. The pieces exist (credentials with selective disclosure, an on-chain compliance layer that carries no third-party traffic yet); the end-to-end path has not been proven with a real verifier on the other side.
- No integration with the European digital identity wallets yet; the credentials follow the same IETF format those wallets will read, which is why the format was chosen.
- No third-party audit of the module or the contracts has been published yet.
How it uses the engine
Revocation lists and issuer keys can be notarized on chain 2800 so that a verifier working offline can still check, later, that the list it holds was the one published. The chain is the notary; the credential, the presentation and the verifier never depend on it. The network is described at Developers.
Verify it yourself
git clone https://git.aere.network/aere-network/aere-quantum cd aere-quantum/identity node conformitate.mjs # the conformance run of the module node control-negativ-identity.mjs # a forged credential must be refused, by name node control-negativ-sdjwt.mjs # a tampered SD-JWT must be refused, by name