Aurigraph's native DAO governance enables decentralized decision-making across validators, token holders, and community members, with transparent voting, signed ballots (ML-DSA-87, FIPS 204, as the target signature scheme), and constitutional protections.
Tier 1: Validator Governance (100 validators)
Tier 2: Token Holder Governance (Unlimited)
Tier 3: Community Governance (Public)
Phase 1: Ideation (7 days) ├─ Community member proposes idea on forum ├─ Open discussion and feedback ├─ Minimum 100 community upvotes to proceed └─ Refine proposal based on feedback Phase 2: Formal Proposal (2 days) ├─ Author submits formal on-chain proposal ├─ Attached to blockchain with the author's signature ├─ Community can deposit AUR as bond (proof of intent) └─ Bonds returned if proposal passes or 10% rejection threshold met Phase 3: Voting (7 days) ├─ Validators OR token holders OR community vote ├─ Voting open to appropriate tier (based on proposal type) ├─ Real-time vote tallying on blockchain └─ Transparent voting records (public on-chain) Phase 4: Execution (Varies) ├─ If approved: Proposal execution smart contract activated ├─ Executor (multisig) implements approved changes ├─ All execution publicly auditable └─ Failed execution → proposal reversal procedures
Validator Votes (Critical Changes)
Change consensus algorithm ↓ Requires: 67% validator approval (67/100) ↓ Voting period: 7 days ↓ Each validator signature: ML-DSA-87 or Ed25519 (dual-accept today) ↓ Tallying: Automatic (smart contract counted)
Token Holder Votes (Economic Changes)
Approve 1M AUR budget for marketing ↓ Requires: 40% participation + 50% majority ↓ Voting power: 1 vote per AUR token staked ↓ Voting period: 7 days ↓ Voter signature: address verification ↓ Tallying: Automatic (weighted by stake)
Community Votes (Non-Binding)
Recommend new feature development ↓ Requires: Simple majority of votes cast ↓ Voting power: 1 vote per participant (equal weight) ↓ Voting period: 3 days ↓ Tallying: Automatic ↓ Result: Recommendation sent to validator council
Validators can adjust these parameters through governance:
Validator proposes: Increase gas limit from 30M to 50M ↓ Vote happens (67% approval needed) ↓ If approved: Smart contract automatically updates parameter ↓ New parameter active on next epoch (10 blocks) ↓ Auditable on-chain history of all changes
Hard Constraints (Cannot be changed even by votes):
1. NIST post-quantum signatures (ML-DSA, FIPS 204) are the required target scheme 2. 67/100 validator quorum requirement immutable 3. No retroactive confiscation of validator stakes 4. No modification of historical blocks 5. Open-source code requirement for protocol changes
Soft Constraints (Can be changed by governance, but not retroactively):
1. Transaction fees 2. Block size limits 3. Validator rewards 4. Inflation rate 5. Slashing percentages
Changing a Constitutional Parameter:
Requires special "constitutional amendment" vote: ├─ 75% validator approval (not just 67%) ├─ 60 day voting period (not just 7 days) ├─ 30 day implementation delay (to allow node updates) ├─ Broadcast warnings to all stakeholders └─ Still cannot violate immutable constraints
Attack #1: Plutocratic Takeover (wealthy holders vote themselves fees)
Defense: Tier separation ├─ Validators (100 equal votes) control protocol ├─ Token holders control treasury ├─ Community votes non-binding └─ Result: No single group can unilaterally change protocol
Attack #2: 51% Token Holder Vote (attack treasury)
Defense: Multi-sig execution ├─ Approval: 50% + 1 token holders vote ├─ Execution: Requires 5/7 multisig signers (different addresses) ├─ Time delay: 48 hours between vote and execution └─ Result: 48 hours for community to object/fork
Attack #3: Validator Collusion (34+ validators attack protocol)
Defense: Slashing penalties ├─ Equivocating validator caught: 100% stake slashed (1M AUR = $10M) ├─ Attack requires coordinating $340M+ stake loss ├─ Economic infeasibility: ~99.9% probability of being caught └─ Result: Economically irrational to attack
Situation (illustrative, not measured on production): network latency increases to 150ms, causing missed block proposals
Proposal:
Title: Increase block time from 90ms to 120ms Justification: Reduce missed blocks from 2% to 0.5% Risk: Slightly reduced throughput (100k → 90k TPS) Timeline: 7 day vote, 2 day implementation Proposer: @ValidatorCouncil
Voting Results:
For: 72 validators (72%) Against: 28 validators (28%) Result: ✅ APPROVED (>67% threshold) Implementation: - Code change: HyperRAFT block_time_ms = 120 - Testing: 2 days on testnet - Deployment: Automatic on epoch 1000 - Reversal: Can be reverted by same process
Situation: Marketing team requests 1M AUR budget for awareness campaign
Title: Allocate 1M AUR for Q1 2026 Marketing Scope: Conference sponsorships, media, influencers Budget: 1M AUR (~$10M) Expected ROI: +500K users, +$100M market cap Proposer: @MarketingTeam
Participation: 25M AUR staked (40% of 62.5M) For: 13M AUR (52%) Against: 12M AUR (48%) Result: ✅ APPROVED (>40% participation + >50% majority) Execution: - Approved on day 7 of voting - 48-hour delay - 5/7 multisig signers execute on day 9 - Funds transferred to marketing multisig wallet - Quarterly reporting required
Situation: HyperRAFT 2.0 offers 50% latency improvement
Title: Upgrade to HyperRAFT 2.0 Technical: New message batching + pipelining Benefit: 90ms → 60ms block time Risk: Requires validator node updates + retesting Timeline: 14 days development, 7 day vote, 30 day phase-in Proposer: @CoreDevelopers
For: 70 validators (70%) Against: 30 validators (30%) Result: ✅ APPROVED (>67% threshold) Constitutional Amendment Needed: 75% required for algorithm change For: 76 validators (76%) Against: 24 validators (24%) Result: ✅ AMENDMENT APPROVED (>75% threshold) Timeline: - Vote passes: Day 7 - Implementation delay: 30 days - Broadcasts to ecosystem: Day 8-37 - Validators update nodes: Days 8-37 - Activation: Day 37 - Audits verify upgrade: Days 37-40
# View active proposals aurigraph governance proposals --status=active # Vote on proposal aurigraph governance vote \ --proposal-id=42 \ --vote=FOR \ --signature=<quantum-safe-signature> # View voting results aurigraph governance results --proposal-id=42 # See governance history aurigraph governance history --limit=50
# Check treasury balance aurigraph treasury balance # View spending history aurigraph treasury history --period=90days # See approved budgets aurigraph treasury budgets --status=active
# Register as validator aurigraph governance validator-register \ --stake=1000000 \ --public-key=<dilithium5-pubkey> # Participate in votes aurigraph governance vote --proposal=42 --vote=FOR # Monitor governance participation aurigraph governance dashboard --validator=<address>
# Stake tokens for governance aurigraph governance stake --amount=1000000 # Vote with your stake aurigraph governance vote --proposal=42 --vote=FOR # Track voting power aurigraph governance power --address=<wallet>
# Create community proposal aurigraph governance propose \ --title="New Feature Suggestion" \ --description="..." \ --tier=community # Vote on community proposals aurigraph governance vote --proposal=42 --vote=FOR # See proposal history aurigraph governance proposals --tier=community
Explore: About · Products · Features · Whitepapers · Sustainability · Tokenized carbon credits · Real-world asset tokenization · SDK · Blog · Plain-text site index · Sitemap · Contact: contact@aurigraph.io