The sustainability of the Airswap governance model is dependent on an active community of members engaged in the exchange of ideas, culminating in the creation of AIPs and other activities aimed at improving the project’s success.
Currently, the only incentive for community members to remain active and engaged is via the rewards for AIP creation and voting. This limits the incentivization rewards to the authors of AIPs - and any co-authors they choose to split the rewards with.
AIP 10: New Token Treasury - implemented - allocates up to 15% (49.16M AST) of the treasury over 3 years to Growth:
- Tokens to be distributed through programs that aim to grow the network.
- Tokens to be distributed through programs that aim to grow the community.
- Expect a lot of experimentation in these programs.
AIP 25 aims to propose a mechanism to reward non-AIP related activities that grow the network and/or community.
Create bounties as incentives for community members to be rewarded for non-AIP contributions to the community.
Example Bounties: based on current community activities. Possible to modify as new precedents emerge
- Community tools and dashboards
- Marketing initiatives
- Translation services
- Research into integratable networks for growth
- Research into potential Liquidity Providers
- Being a moderator on Discord
- Updating Airswap website
- Creating/maintaining Airswap presence on other websites - coinmarketcap, dune, defipulse, reddit, coingecko etc.
- Drafting news articles and press releases
- Updating FAQs pages
Since AIP 10 passed vote there is a budget allocated for these types of community services but no defined process to utilize it.
Mechanism to Create Bounty
Bounty creation would run independently from AIPs - which are primarily reserved for high-level policy questions regarding the overall direction of the project.
If someone from the Airswap community has an idea to grow the project or has identified a problem to be solved they can submit a bounty request to be voted on by the Members Community. The threshold of consensus required to approve the bounty is scaled to the size of the reward requested. *Example - 1000 AST bounty would require minimum 10% consensus from the members community. 5000 AST would need 50%. Voting would be time limited. The threshold for consensus can be modified via a configuration vote.
Bounty rewards to be paid in either points or out of Airswap treasury (in sAST) and can only be sent to staked wallets - limiting community engagement bounty rewards to individuals invested in the long-term success of the project.
Since requester of the bounty will not always be the implementer of the solution a ‘finders-fee’ of 10% of the total bounty should be awarded to the requester upon reward of the bounty for completion of work.
Community members eligible for rewards would need some AST staked.
A bounty board or something similar would need to be created on community.airswap.io and/or on the AirSwap website and Web App (AIP 30).
A simple voting mechanism needs to be implemented for bounty creation. Where this vote should occur - discord, activate, community.airswap is TBD. However to avoid confusion, bounty voting should be separate and distinct from AIP voting as there are no points to accumulate from voting on bounties.
If no satisfactory candidate can be found within the AirSwap community to fulfill the bounty then AirSwap has the option to host the bounty externally (gitcoin et al.) and open the eligibility to non-stakers.