SymbolonTrust registryBuilt
Verified there. Trusted here.
A person who has been properly verified should not have to prove themselves from scratch to every organisation they deal with. Symbolon decides when one organisation may rely on another’s verification — claim by claim, under a signed agreement, and never without the person’s consent.
The name
In ancient Greece a symbolon was a token broken in two. Each party kept a half; when the halves fitted, strangers knew they could trust each other.
Simulation
Runs entirely in your browser.
Reuse what holds. Ask only for the gap.
Pick a scenario. Each claim is decided on its own: reused, asked for again, or refused — and the reasoning names the rule that decided it.
Scenarios
- · Agreement in force
- · No exclusion applies
- · The person consents
- · Each claim fresh enough
| Claim | Established by | Decision |
|---|---|---|
| Legal name | document + face match | deciding |
| Date of birth | document | deciding |
| National identity number | registry check | deciding |
| Residential address | proof of address | deciding |
| Sanctions and PEP screening | screening | deciding |
The reasoning
A second organisation needs the same person verified. The first already did it well. Does the person go through it all again?
- RequestThe relying organisation asks, claim by claim, to rely on a verification another organisation already made.
The rules
Reliance is a decision, not a data share.
- Per claim
- Each claim is judged on its own: who established it, through which provider, and how long ago. A verification is never trusted wholesale.
- Distrust first
- An organisation can exclude another organisation, a provider or a product. An exclusion always beats an agreement.
- Single hop
- An organisation may rely on the one that verified the person, never on someone who was itself relying.
- Consent
- The person’s consent for this reuse, for this purpose, is a record the decision reads. Without it nothing is reused or disclosed.
- Ask only for the gap
- When the relying organisation’s standard needs something the original never covered, or a claim is too old, the person is asked for exactly that, and nothing else.
- Decided purely
- The decision is a pure function over the registry’s graph, so the same facts always give the same answer, and every answer can be explained.
Agreements
Both halves, signed.
A reliance agreement goes through due diligence, is signed by both organisations, is established by a second person, and carries a review date. It records what each regulatory purpose requires, including what one check covers that another does not.
Wallet relying parties
Who may ask a wallet for what.
Symbolon also registers wallet relying parties: it issues registration certificates that state what each may request, and publishes signed lists of trusted entities. A wallet that checks the certificate refuses a request for more than the registration allows.
- Registration certificates
- Issued and verified to ETSI TS 119 475.
- Built
- Lists of trusted entities
- Built and signed to ETSI TS 119 602.
- Built
- Registry queries
- Answering “is this party authorised?” over the Trust Registry Query Protocol.
- In progress
Kept apart
Trust and suspicion live in different places.
Symbolon answers whether reliance is permitted. The fraud graph answers whether something looks wrong. They are separate systems with separate stores, sharing nothing but vocabulary — so the registry of trust can never become a register of suspicion.
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.