SubDAO Interop Model
ZKNetwork's governance is organized as a network of semi-autonomous SubDAOs, each specializing in specific domains while remaining interconnected through the Meta DAO.
Structure
The MetaDAO anchors the ecosystem — providing meta-governance standards, treasury funding, and epoch review cycles. SubDAOs inherit charters from the MetaDAO while operating autonomously within their domains. Cross-collaboration links connect SubDAOs on shared work: MycoFi works with DAO Dev on constitutional logic and with Commons Hub on local methods; Education shares ZK identity tooling with DAO Dev and IoT deployments with Infra; Greenhouse prototypes with Commons Hub; Campaigns collaborates with Commons Hub on documentation and workshops. Shared tooling (Snapshot, Safe, zkNFTs/Passport, Scorecards, Discourse) is used across all SubDAOs.
SubDAO Charter Model
Each SubDAO operates under a charter defining:
- Scope — Domain, budget, timeline
- Authority — Decision rights, spending limits
- Accountability — Reporting, metrics
- Exit conditions — Dissolution, reassignment
Charter Parameters
| Parameter | Description | Example |
|---|---|---|
| Domain | Focus area | Aztec Integration |
| Budget | Quarterly allocation | 50,000 USDC - $xZKN/$ZKN |
| Authority | Max single spend | 5,000 USDC - $xZKN/$ZKN |
| Term | Duration | 6 months |
| KPIs | Success metrics | 3 integrations |
Cross-SubDAO Coordination
Treasury Routing
Protocol revenue flows through the Regenerative Tokenomics Router, with portions allocated to SubDAOs based on:
- Active proposals approved by Token Assembly
- Charter-defined allocations
- Performance-based bonuses
Resource Sharing
SubDAOs can share:
- Infrastructure — Shared node clusters, RPC endpoints
- Knowledge — Documentation, research, specifications
- Personnel — Contributors with multi-subDAO roles
ZK Voting Interop
All SubDAO votes use the same Noir-based ZK voting system:
- Unified voter registry
- Cross-SubDAO proposal visibility
- Privacy-preserving delegate voting
SudDAO Types
Operational SudDAOs
| Name | Function |
|---|---|
| Governance Ops | Infrastructure, tooling, processes |
| DePIN Operations | Physical hardware, mesh networks |
| Community | Engagement, education, support |
Technical SudDAOs
| Name | Function |
|---|---|
| Aztec Integration | Noir contracts, Aztec SDK |
| Research & Development | ZK algorithms, privacy research |
| Mixnet Protocol | Network layer, Katzenpost |
Ecosystem SudDAOs
| Name | Function |
|---|---|
| ReFi & Regenerative | Sustainability, carbon credits |
| Enterprise Solutions | B2B, compliance, integrations |
| Ecosystem Growth | Partnerships, grants, hackathons |
Lifecycle
Creation → Proposal → Charter → Operation → Review → Renewal/Exit
- Creation — Proposal to Meta DAO identifying need
- Proposal — Token Assembly vote on charter
- Charter — Formalize scope, budget, authority
- Operation — Execute mandate
- Review — Quarterly performance assessment
- Renewal/Exit — Continue, modify, or dissolve
See also: Governance