The following is a guide for contributing AirSwap Improvement Proposals (AIP).
Anyone is welcome to create an AIP. Each proposal outlines a problem or opportunity and specifies a solution and its tradeoffs. Proposals cover all sorts of topics like new protocols, smart contracts, network tooling, applications, marketing, tokenomics, and more!
The structure of a proposal is as follows (See: AIP 1). Each proposal includes a summary, specification, rationale, and copyright.
Summary — A short (200 word) summary describing the proposal.
Specification — Technical specification for the proposal.
Rationale — Motivations, justifications, arguments for and against.
Copyright — All proposals are public domain via CC0.
To draft an AIP, create a new issue on the GitHub repository. Drafting an AIP is often done with community support. Authors are welcome to discuss their proposals and solicit feedback from the communities on Discord and on GitHub.
Each proposal follows three main stages.
After initial brainstorming, the author creates a new topic on the GitHub.
Discussion is generally a combination of:
Brainstorming on Discord where comments happen in real-time and community members build on each others ideas rapidly. A great way to iterate on fresh ideas.
In-depth discussion here on GitHub where slower moving comments contribute to our longer term memory and feedback gets integrated directly into proposals.
Once ready, the author requests to call a vote. Authors will need to come to a consensus in the governance circle about which AIPs are ready to go for voting.
Authors must stake at least 1000 AST to call a vote. To stake AST, navigate to Codefi Activate and follow the instructions on the AirSwap governance portal. To verify your staked balance, type “!join” in the Discord to confirm your stake, which gives you the Author role.
After discussions, authors will decide which proposals will be called to vote in the current voting cycle. This takes place in the #authors channel in Discord.
Accepted proposals are placed on the project roadmap. If rejected, the author can solicit feedback from the community on how to improve the proposal.
At the end of each voting cycle, authors allocate GIVE tokens to other authors on Coordinape to reward other authors based on their contributions in that cycle. At the end of the cycle, AST rewards are paid out based on their allocation of GIVE tokens.
Reach out to community managers in Discord if you would like to get added to the governance circle!
You can get help from your fellow members in the Discord #authors channel. Collaborating with other members leverages our collective knowledge and can lead to better proposals overall. If the discussion gets very long mixed in with other threads, you can create a new thread for your proposal.