CredentialsBuilt
Verified once, held by the person.
When Aegis verifies someone, the result does not have to stay in a database. It becomes a signed credential in their wallet that any verifier can check — without calling Aegis, and without Aegis ever learning where it was used.
Demonstration
Runs entirely in your browser. No real credential is involved.
Share what is asked. Withhold the rest.
Choose who is asking and which claims to share, then switch format to see what the verifier actually receives: a disclosure, a digest it cannot reverse, or a proof that reveals nothing but the answer.
Who is asking
The credential in the wallet
Each claim is a separate salted disclosure. The issuer signed only their digests, so an undisclosed claim is a hash the verifier cannot reverse.
What a venue receives
- Given namedigest only
- Family namedigest only
- Date of birthdigest only
- Over the age thresholddisclosed
- Nationalitydigest only
- Document numberdigest only
- Residential addressdigest only
issuer-signed JWT ewccYiEIioOAUgKaIwyMCs.AICOaWGkOwckAaqCGwqCIu.gsAw-qGUQcO-o-oMcaMssm ~ age_over_threshold cAcEQAMWemgkYQCkaAyaAe ~ key-binding JWT Mqi-SKuQQAOoIIEiIaGCco
Issuance
Issued to a wallet that proves what it is.
The credentials service is an OpenID4VCI issuer. Every token it hands out is bound to the wallet’s key, and a wallet must prove it is a genuine, unmodified instance before it is issued anything.
- Pre-authorised flow
- An offer the person accepts straight after verification, protected by a transaction code.
- Built
- Authorisation-code flow
- With pushed authorisation requests, proof keys for code exchange and wallet attestation.
- Built
- Sender-constrained tokens
- Proof of possession binds every token to the wallet’s key; a stolen token is useless to anyone else.
- Built
- Keys never in process
- Every credential and certificate is signed through a managed key service, so no issuing key ever sits in a running process.
- Built
- Anonymous credentials
- AnonCreds issued over DIDComm, with revocation and zero-knowledge predicates.
- In progress
Formats
One verification, every format a verifier expects.
- SD-JWT VC
- Salted, selectively disclosable claims with key binding, for online presentation.
- Built
- ISO mdoc
- The mobile-document format of driving licences and national identity, for in-person and online presentation.
- Built
- W3C Verifiable Credentials
- Linked-data credentials with Data Integrity proofs, and JWT-secured credentials.
- In progress
- AnonCreds
- Unlinkable presentations and predicate proofs: prove a threshold without the value behind it.
- In progress
Verification
Accept credentials from any conformant wallet.
Aegis is a verifier as well as an issuer. Its verification step requests exactly the claims a flow needs, checks every signature, chain, status and binding itself, and refuses what it cannot verify.
- OpenID4VP with DCQL
- Cross-device by code, same-device by link, signed and encrypted responses, several documents in one request.
- Built
- Browser credential requests
- The verification surface asks the browser for a credential through the Digital Credentials API.
- Built
- Mobile documents online
- ISO/IEC TS 18013-7 presentation of mdocs to the verifier.
- In progress
- Trust anchors
- Issuers are trusted through managed anchors and published trusted lists, never because a credential says so.
- Built
Status
Revoked means revoked, without a phone call home.
The credentials service owns a status list for everything it issued. Verifiers fetch the list, not a per-credential lookup, so checking a credential tells the issuer nothing about who is checking or why. A credential can be suspended, reinstated or revoked, and a verifier that cannot read the list fails closed.
Build on identity that is proven, not assumed.
Aegis is built by Protoworks and offered to partners on request. Tell us what you need to verify, issue or accept, and we will show you the platform running.