Assurance tiers
An assurance tier says how well an income event is attested — not how much it is worth, and not who it belongs to.
| Tier | Meaning |
|---|---|
| 1 | Issuer-attested — a registered issuer signed it, verified in-circuit against its registered key. |
| 2 | Rail-observed — observed on a payment rail, unsigned by the payer. |
| 3 | Self-declared — asserted by the holder. Provably unverified. |
Lower is stronger. A verifier states a minimum tier, and the tier is bound into the proven statement, so a proof at tier 1 will not construct over tier-3 income. Self-declared income cannot be presented as issuer-attested — the circuit that would have to lie to make that happen does not exist.
This is the opposite direction from binding schemes, where higher is stronger — see Accounts. The two orderings were defined at different times for different reasons, and getting them backwards is the easiest mistake to make in this codebase.
An aggregate is only as strong as its weakest input
Composition lets many income events, at different tiers, accumulate into one account's aggregate. The aggregate's tier is not an average and not the strongest tier present — it is the numerically highest (weakest) tier among its contributors. One tier-3, self-declared event mixed into a thousand tier-1 events yields a tier-3 aggregate.
This is deliberate, not a limitation: an aggregate's tier is a claim about what a verifier can trust the whole total to mean, and a total is not more trustworthy than its least-trustworthy component. Tier monotonicity is enforced in-circuit, both when an issuer's income accrues into an account's own aggregate and when a source's aggregate folds into a principal's — see Composition.
Where the tier actually comes from
An issuer is registered at a tier by the protocol's issuer registry, and that registration — not the issuer's signature — is what governs the tier an income event enters at. An issuer's signed claim carries a tier field, but the circuit that records the claim asserts the signed tier equals the issuer's registered tier: an issuer cannot promote its own claims by signing a stronger number than it is registered for. Overstating a tier only stops the claim from being accepted.
A verifier that pins minTier: 1 in a request — see
Verifying a disclosure — is asking
for a proof that every income event behind the aggregate was signed by a
registered, active issuer at tier 1. Nothing weaker will construct that
proof.