Aztec Ecosystem Grants Allocation to Community Contributors, Operators, and Testnet Validators
This governance proposal allocates 437,215,000 AZTEC tokens from the remaining Ecosystem Grants pool across three buckets: 30% (131,164,500 AZTEC) for builder grants via the existing grants program, 30% (131,164,500 AZTEC) for community contributors (Discord roles) and operator roles, and 40% (174,886,000 AZTEC) for testnet validators meeting KYC and activity thresholds. Distributions for Buckets B and C follow a vesting schedule with a 1-month cliff, 15% unlock at cliff, and linear vesting over 365 days. Eligibility is determined by a snapshot of Discord roles, operator roles, and validator activity, with no stacking within each bucket.
Eligibility: Bucket A: Teams building on Aztec via standard grants program. Bucket B1: Holders of curated Discord roles (AzMod, Language Ambassadors, Cypherpunk Chad, Aztec OG sub-roles) at snapshot, one highest-priority role per wallet. Bucket B2: Holders of operator roles (Homestaker Sentinel, Proposer Commander, High Attester, Queue Master, Prover, Gnosis Sequencer) at snapshot, one role per wallet. Bucket C: Testnet validators who pass KYC/identity verification and exceed 100 validator-relevant transactions/actions in the measurement window (recommended: activity on 7+ distinct days). Same wallet may qualify for both Bucket B and C independently.
Pipeline
Funder track record · does Aztec Labs actually pay grants?
🟡 Some payout evidence · 1 grantee found · last payout 2023-08-14 · checked 2026-10-23 · 0 forum reports, 4 web pages read, 9 unverifiable claims dropped
Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.
| Grantee | Amount | Date | Evidence |
|---|---|---|---|
| AZKR | — | 2023-08-14 page date | “we ultimately funded AZKR with an additional grant to generalize the work that's being done around private voting for NounsDAO” source |
| AZKR | — | undated | “we ultimately funded AZKR with an additional grant to generalize the work that's being done around private voting for NounsDAO” source |
Trust breakdown (3/3 checkable facts verified)
| Signal | Weight | Result | Note |
|---|---|---|---|
| amount | 0.25 | 100% | figure appears in source |
| apply link | 0.075 | 100% | link in source |
| funder | 0.075 | 100% | named in source |
| source quality | 0.15 | 50% | social or search hit |
| model confidence | 0.1 | 85% | model self-report |
Fit breakdown (against the ORG_* profile)
| Signal | Weight | Result | Note |
|---|---|---|---|
| model fit | 0.5 | 70% | model rated 70% |
| ecosystem overlap | 0.25 | 0% | aztec vs aleo |
| category overlap | 0.15 | 33% | community, infra, dev_tooling vs zk, privacy, infra, dev_tooling, security, interoperability |
| tech overlap | 0.1 | 33% | rust, typescript vs rust, leo, zk |
Sources (1)
| Role | Document | From | Fetched |
|---|---|---|---|
| primary | Proposal: Allocate Remaining Ecosystem Grants to Community Contributors, Operator Roles, and Testnet Validators - Governance - Aztec | Web discovery: ecosystem sweep | 2026-10-28 |
History (1)
| v | Changed | Fields |
|---|---|---|
| 1 | 2026-10-28 | created |
Extracted text
[](/u/solodan)
[solodan](/u/solodan)
[Feb 17](/t/proposal-allocate-remaining-ecosystem-grants-to-community-contributors-operator-roles-and-testnet-validators/8465 "Post date")
# [](#p-29845-proposal-execute-tge-payload-to-unlock-aztec-token-transfers-1)Proposal: Execute TGE Payload to Unlock $AZTEC Token Transfers
## [](#p-29845-abstract-2)Abstract
This proposal allocates the remaining tokens in the Ecosystem Grants pool to (1) keep funding builders as intended, (2) recognize community contributors (Discord role holders including moderators), (3) reward testnet validators based on objective activity metrics. The proposal does not change the total Ecosystem Grants allocation or any other tokenomics category; it only sub-allocates the undistributed remainder.
## [](#p-29845-motivation-3)Motivation
1. Make contributor recognition explicit and governance-controlled, using a transparent snapshot + reproducible methodology.
2. Reward community operations (moderation, localization, content) that sustained the ecosystem during the pre-TGE period.
3. Reward infrastructure operators and testnet validators with objective, Sybil-resistant criteria.
4. Preserve long-term runway for builder grants (projects building on Aztec).
### [](#p-29845-current-grants-accounting-inputs-4)Current Grants Accounting (Inputs)
The following accounting is the basis for this proposal:
Item
Amount (AZTEC)
Total Ecosystem Grants allocation (unchanged)
1,111,000,000
Granted out (locked for 4-5 years)
570,285,000
Assigned but not distributed
103,500,000
Still in grant pool (scope of this proposal)
437,215,000
This proposal allocates **only** the **Still in grant pool** amount and leaves the rest unchanged.
## [](#p-29845-specification-5)Specification
30 / 30 / 40 Split of the Remaining Grant Pool
Let G = 437,215,000 AZTEC (still in grant pool). The proposed sub-allocation is:
Bucket
Purpose
% of G
Amount (AZTEC
A
Builder grants / projects (standard grants program)
30%
131,164,500
B
Community contributors: Discord roles + Operator roles
30%
131,164,500
C
Testnet validator rewards (KYC + activity threshold )
40%
174,886,000
Total
100%
437,215,000
## [](#p-29845-bucket-a-30-builder-grants-projects-6)Bucket A (30%): Builder Grants / Projects
**Amount:** 131,164,500 AZTEC.
This bucket remains reserved for grants to teams building on Aztec, following the existing grants program processes (application, diligence, milestone-based disbursement, and vesting as appropriate).
## [](#p-29845-bucket-b-30-community-contributors-operator-roles-7)Bucket B (30%): Community Contributors + Operator Roles
**Amount:** 131,164,500 AZTEC.
Bucket B is split 70% / 30% between (1) Discord community roles and (2) Operator roles, to keep the process simple and to avoid over-fitting to any single snapshot of role counts.
Sub-bucket
% of Bucket B
Amount (AZTEC)
B1 - Discord community roles
70%
91,815,150
B2 - Operator roles
30%
39,349,350
**No-Staking Rule & Priority Order (Bucket B)**
**B1 (Discord Community Roles):** only one role per wallet is counted — the role with the highest priority (MAX by priority). Any additional roles held by the same wallet within B1 do not increase the payout.
\*\* B2 (Operator / Noder Roles):\*\* by default, **MAX by priority** is also applied (one role per wallet) to avoid compounding multipliers from holding multiple operator roles.
If the same wallet is both a community contributor (B1) and an operator/noder (B2), it may be eligible for both parts of Bucket B, since these categories reflect different types of contribution. The **No Stacking rule** still applies separately within B1 and within B2.
## [](#p-29845-b1-discord-community-roles-70-of-bucket-b-8)B1 - Discord Community Roles (70% of Bucket B)
**Amount:** 91,815,150 AZTEC.
This sub-bucket recognizes ongoing community operations and contribution. Distribution is based on curated Discord role assignments at a fixed snapshot time (see ‘Snapshot and Deduplication’). If a user holds multiple Discord roles, only the highest-weight role applies.
Role group
Count (given)
% of B1
Pool (AZTEC)
AzMod
8
10%
9,181,515
Language Ambassadors
20
10%
9,181,515
Cypherpunk Chad
20
10%
9,181,515
Aztec OG
819
70%
64,270,605
**Included in Aztec OG:** Initiated (544) , Archivist (116), Paragon (54), Illuminated (18), Content Chronicler (15), Meme Lord (16), Maestro (56).
**Per-wallet formula:** each role pool is divided equally among the eligible wallets in that role group at the snapshot.
B2 - Operator Roles (30% of Bucket B)
**Amount:** 39,349,350 AZTEC.
This sub-bucket rewards infrastructure operators. The term ‘Operator roles’ is used to avoid confusion with testnet validator rewards (Bucket C). If a wallet holds multiple operator roles, it is counted once; the exact rule is defined in ‘Snapshot and Deduplication’.
**Roles (counts provided):** Homestaker Sentinel (14), Proposer Commander (15), High Attester (14), Queue Master (21), Prover (44), Gnosis Sequencer (317).
Rule
Pool (AZTEC)
Distribution
Gnosis Sequencer role group
19,674,675
Receives 50% of B2; equal per wallet (count = 317).
Other 5 operator role groups
19,674,675
Share remaining 50% equally across role groups; equal per wallet within each role group.
Other operator role group
Count (given)
Role group pool (AZTEC)
Homestaker Sentinel
14
3,934,935
Proposer Commander
15
3,934,935
High Attester
14
3,934,935
Queue Master
21
3,934,935
Prover
44
3,934,935
## [](#p-29845-bucket-c-40-testnet-validator-rewards-9)Bucket C (40%): Testnet Validator Rewards
**Amount:** 174,886,000 AZTEC.
This bucket rewards testnet validators based on objective criteria and is designed to be Sybil-resistant. Eligibility requires: (1) passing KYC (or an equivalent identity verification flow approved by the Foundation), and (2) exceeding an activity threshold of **more than 100 validator-relevant transactions/actions** during the measurement window. Rewards are distributed equally across eligible wallets.
**Per-wallet formula:** payout = 174,886,000 / N, where N is the number of eligible validator wallets at the snapshot.
## [](#p-29845-vesting-and-lockups-10)Vesting and Lockups
To balance contributor recognition with market impact, all distributions in Bucket B and Bucket C follow the same schedule. Bucket A (builder grants) remains discretionary and can keep milestone-based vesting as per grant agreements.
**Schedule for Bucket B and Bucket C:**
* Cliff: 1 month (30 days) with 0% claimable before the cliff.
* At cliff: 15% unlocks immediately.
* Remaining 85% vests linearly over 365 days after the cliff.
* Claimable(t) = 0 for t < cliff; Claimable(t) = 15% + 85% \* min(1, (t - cliff) / 365d) for t >= cliff.
## [](#p-29845-snapshot-wallet-binding-and-deduplication-11)Snapshot, Wallet Binding and Deduplication
* A single snapshot timestamp/block is used for each list (Discord roles, Operator roles, Testnet validators). The snapshot time is published before voting.
* Wallet binding: each Discord account must bind exactly one wallet (signed message or official verification flow).
* Discord roles: if a user holds multiple Discord community roles, apply the highest-weight role only (no stacking).
* Operator roles: if a wallet holds multiple operator roles, count it once (no stacking).
* Cross-bucket eligibility: the same wallet may receive from Bucket B and Bucket C if it qualifies independently under each bucket’s rules.
## [](#p-29845-sybil-resistance-and-anti-gaming-measures-12)Sybil Resistance and Anti-Gaming Measures
* KYC gating for Bucket C: only wallets that pass KYC (or an approved identity verification provider) are included in the validator merkle tree.
* Activity threshold for Bucket C: >100 validator-relevant transactions/actions in the measurement window; exclude pure spam transactions by filtering for protocol-specific validator calls where possible.
* Time-spread requirement (recommended): require activity on at least 7 distinct days to reduce bursty spam behavior.
* Role assignment is curated: Discord roles and Operator roles are non-trivial to obtain and are assigned/verified by community governance/moderation processes.
* Publish methodology and raw lists (or privacy-preserving hashes) prior to voting to allow community review.
## [](#p-29845-implementation-approach-on-chain-13)Implementation Approach (On-chain)
To keep execution safe and scalable for hundreds or thousands of recipients, the recommended approach is to deploy a governance payload that funds one claim contract (Merkle-based) per distribution list (Discord, Operator, Testnet). Users claim individually, amortizing gas across claimants. The claim contracts may either transfer tokens directly or create token vault positions that encode the vesting schedule.
Funding source: the payload should pull from the Ecosystem Grants treasury or the Foundation-controlled grants factory, mirroring the execution pattern used for prior governance payloads.
Governance lifecycle and voting parameters should follow the precedent and format used in the reference TGE proposal (payload deployment, sequencer signaling, proposal creation, voting, execution delay, execution).
## [](#p-29845-rounding-and-leftovers-14)Rounding and Leftovers
All calculations must be implemented in wei. Any remainder dust from integer division should be explicitly handled in the payload. Recommended policy: send remainder to Bucket A (builder grants) to avoid unallocated dust.
## [](#p-29845-references-15)References
* Economic Whitepaper landing page: [Economic Whitepaper](https://aztec.network/economic-whitepaper)
* Auction Terms of Sale (KYC/KYB, sanctions checks, initial supply): [Auction Terms of Sale](https://aztec.network/auction-terms-conditions)
* Token Sale Privacy Policy (KYC/KYB data handling): [Token Sale Privacy Policy](https://aztec.network/token-sale-privacy-policy)
* Aztec governance and proposal process documentation: [https://docs.aztec.network/network/operati](https://docs.aztec.network/network/operation/sequencer_management/creating_and_voting_on_proposals) [on/sequencer\_management/creating\_and\_voting\_on\_proposals](https://docs.aztec.network/network/operation/sequencer_management/creating_and_voting_on_proposals)
* Aztec blog: The AZTEC TGE Vote - vote requirements and timeline: [The $AZTEC TGE Vote: What You Need to Know](https://aztec.network/blog/the-aztec-tge-vote-what-you-need-to-know)
* Reference governance proposal (TGE payload):
832 views 24 likes 2 links 8 users
[ 3](/u/CitizenWeb3 "CitizenWeb3")
[](/u/thylacine "thylacine")
[](/u/solodan "solodan")
[](/u/soft_arc "soft_arc")
[](/u/ethoughts "ethoughts")
read 5 min