The SWAN DAO governance system is the backbone of the SWAN ecosystem. It keeps decision-making decentralized, transparent, and community-driven while guiding long-term growth, financial stewardship, and the core principles of a DAO.
- Committee Structure
Representation spans SWAN token holders, core developers, builders, and other contributors so decisions reflect diverse stakeholder perspectives. Members are elected through transparent community votes. - Decision-Making Pipeline
Any community member can submit proposals. Approved proposals move from community voting to implementation by responsible teams or sub-committees, with voting power often reflecting token holdings and tenure. - Community Engagement
Forums, chats, town halls, workshops, and webinars keep contributors informed and involved so everyone can participate in an informed way. - Treasury Management
The DAO allocates the treasury across staking rewards, community programs, and strategic investments. Regular audits and clear compensation frameworks balance incentives for builders and Universal Basic Income (UBI) for computing providers. - Continuous Evolution
Governance processes adapt to community feedback, ensuring protocol upgrades and organizational refinements keep the SWAN network resilient and forward-looking.
An SIP is the official, permanent record for any change, upgrade, or policy within Swan Chain, Swan Cloud, SwanFi, or the Swanchain Foundation. SIPs move through community review, DAO voting, and implementation so every change remains transparent, versioned, and verifiable on-chain and in this repository.
| Category | Example Proposals |
|---|---|
| Protocol / Technical Change | Adjust L2 parameters, modify ZK task logic, update Swan SDK specs |
| Economic / Treasury | Token allocation, UBI formula update, Foundation or Grant distributions |
| Governance | Add new voting mechanisms, adjust quorum rules, create subDAO or committee |
| Ecosystem or Policy | Partner onboarding, community reward programs, or SwanFi changes |
| Documentation / Meta | Updates to SIP format, new governance frameworks |
Place every proposal in the SIPs/ directory using a sequential filename such as:
SIPs/SIP-001-adjust-fcp-ubi-curve.md
Copy SIPs/SIP-template.md when drafting a new proposal. The template includes the canonical front matter:
---
SIP: 001
Title: Adjust Fog Computing Provider (FCP) UBI Curve
Author: Charles Cao (@charlescao-swan)
Status: Draft
Category: Economic / Protocol
Created: 2025-10-07
Discussions-To: https://github.com/swanchain/governance/discussions/13
Requires: None
Replaces: None
---- Summary – One-paragraph description of the proposed change.
- Motivation – Why the change is needed and the problem it solves.
- Specification – Detailed technical, economic, or governance modifications, including parameters, formulas, token distributions, or contract addresses.
- Rationale – Design decisions and alternatives evaluated.
- Implementation – Rollout plan, timeline, and responsible teams (e.g., Swan Cloud Inc., Swan Foundation).
- Governance Impact – Effects on token holders, computing providers, and DAO operations.
- References – Links to discussions, whitepapers, dashboards, and related proposals.
| Stage | Description |
|---|---|
| Draft | Initial version under discussion in GitHub Discussions |
| Review | Reviewed by Swan Foundation / core contributors |
| Snapshot Vote | On-chain or off-chain voting period for community approval |
| Accepted | Approved and queued for execution |
| Implemented | Deployed or enforced via DAO operations |
| Rejected / Superseded | Not approved or replaced by a later SIP |
- Post an idea in GitHub Discussions and iterate with feedback.
- Convert the idea into an SIP using the template and save it as
SIPs/SIP-###-descriptive-title.md. - Submit a pull request titled “Formal SIP Submission” for community review.
- Engage with feedback from maintainers (
@swanchain-governance) and contributors until consensus is reached. - Move the SIP to Snapshot or on-chain voting.
- Once approved, maintainers merge the SIP and coordinate implementation.
README.md— Governance overview and SIP process guide (this document).SIPs/SIP-template.md— Canonical template for drafting new SIPs.
Questions, improvements, or new proposals should start in Discussions before becoming formal SIPs.