Trust registriesBuilt
Trust is a record, not an assumption.
Every answer Aegis accepts comes from someone it has decided to trust: another tenant under a signed agreement, a credential issuer on a trusted list, a wallet with a valid registration. Each of those decisions is written down, checked at the moment of use, and explainable afterwards.
Between tenants
Tenants that trust each other, claim by claim.
Symbolon is the platform’s own trust registry. Two tenants enter a reliance agreement; from then on one may rely on the other’s verification of a person — for the claims the agreement covers, within their age limits, and only with the person’s consent.
- Reliance agreements
- Requested and signed by the tenants, established by the platform with a second person and a recorded regulatory clearance. Each records what each regulatory purpose requires.
- Built
- Per claim, single hop
- Each claim is judged on who established it, how and when. A tenant relies on the one that verified, never on another relier.
- Built
- Exclusions win
- A tenant can refuse another tenant, a provider or a product. An exclusion always beats an agreement.
- Built
- Ask only for the gap
- Where the relying tenant needs more than the original covered, the person is asked for exactly that and nothing else.
- Built
Issuers
A credential is only as good as its issuer’s standing.
Before a credential is believed, its issuer is looked up in the trust lists that govern it, its signature chain is followed to a trust anchor, and its status is checked at that moment.
- Trusted lists
- National and European trusted lists read to ETSI TS 119 612, with the list of lists followed to each member state.
- Built
- Trust anchors
- Issuer certificates for mobile documents and identity wallets verified to their roots, with every link checked.
- Built
- Status at use
- Revocation read from status lists at the moment of verification, so a withdrawn credential fails at once.
- Built
Wallets and verifiers
Who may ask, for what.
Symbolon also registers the parties that request credentials from wallets, so a wallet can refuse a request for more than a verifier is registered to ask for.
- Registration certificates
- Issued and verified to ETSI TS 119 475: what each relying party may request, signed.
- Built
- Lists of trusted entities
- Built and signed to ETSI TS 119 602 for wallets to read.
- Built
- Registry queries
- Answering “is this party authorised?” over the Trust Registry Query Protocol.
- In progress
Kept apart
A registry of trust, never of suspicion.
Whether reliance is permitted and whether something looks wrong are answered by separate systems with separate stores. The trust registry never learns what the fraud graph suspects.
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.