AUT Utility and Supply Design
AUT should be read as a network coordination asset, not as the commercial front door to Authryl. A bank, workforce platform, or enterprise verifier can run Authryl in a private contract setting without ever touching AUT. The token only becomes relevant when several parties rely on the same shared trust surfaces and need common incentives or common discipline around them.
Total supply
250,000,000,000 AUT
Where the token boundary starts
Private verifier policies, private audit snapshots, and customer-specific onboarding rules should remain software features. AUT starts at the network edge, where one party's behavior affects the quality of trust decisions for many others.
That shared edge includes:
- certified verification gateways that answer queries for more than one counterparty
- issuer and jurisdiction registries that many verifiers may depend on at the same time
- common policy packs for freshness, assurance, and revocation interpretation
- dispute and review channels that require funded handling and published outcomes
AUT exists to keep those shared surfaces accountable. It is not there to manufacture artificial product demand.
Utility surface
| Function | What AUT does |
|---|---|
| Gateway bond | posted by certified gateway operators and put at risk if service quality or attestation integrity falls below standard |
| Registry and dispute funding | funds shared issuer review, dispute handling, and jurisdiction-pack maintenance |
| Policy-pack governance | participates in admission and revision of common freshness, revocation, and assurance packs |
| Shared network incentives | rewards verified onboarding, registry maintenance, and high-quality gateway participation |
Allocation
| Bucket | Share | AUT |
|---|---|---|
| Ecosystem incentives | 29% | 72,500,000,000 |
| Foundation treasury | 21% | 52,500,000,000 |
| Core contributors | 16% | 40,000,000,000 |
| Issuer bootstrap grants | 14% | 35,000,000,000 |
| Strategic partners | 12% | 30,000,000,000 |
| Liquidity and market ops | 8% | 20,000,000,000 |
Release logic
- Core contributors unlock after a 12-month cliff and vest monthly over the following 30 months.
- Strategic partners follow a 9-month cliff and monthly vesting over 24 months, tied to signed integration and operating commitments rather than headline announcements.
- Ecosystem incentives release against measured onboarding, gateway uptime, issuer-registry maintenance, and dispute-resolution throughput. Unused emissions remain locked instead of rolling into discretionary spend.
- Issuer bootstrap grants are reserved for admitted issuers and sector launch programs that add real credential coverage. They should not be used as generic marketing subsidies.
- Foundation treasury unlocks quarterly over 48 months and is intended for registry operations, standards maintenance, audits, and dispute funding.
- Liquidity and market ops stays largely dormant until AUT is actually used in public network coordination. At launch, no more than 20% of this bucket should be activated in the first year.
Initial circulation discipline
Authryl should not begin with a large floating supply. The network works best if circulating AUT grows behind actual registry use, gateway activity, and policy-pack governance rather than ahead of them.
What AUT does not represent
- no claim on protocol revenue
- no guaranteed yield
- no requirement for private enterprise deployments
- no governance right over customer-specific internal verification decisions
The simplest test is this: if a workflow can be handled entirely within one enterprise's private credential program, it should not need AUT.