AIP 94: AirSwap Grant Proposals

Summary

• This AIP proposes to establish AirSwap Grant Proposals.
• AGPs welcome individuals and teams to request treasury AST to fund projects that aim to advance the development, growth, and adoption of AirSwap.

Specification

The proposal structure and process are as follows.

Structure

Each proposal includes a summary, owner, scope, amount, timeline, and copyright. Each AirSwap Grant Proposal (AGP) should be titled AGP XX: .

• Goals and Summary — A short summary describing the proposal.
• Project Owner — The person or people accountable for completing and delivering the project.
• Project Scope — A list, illustration, or description of components of the system or initiative to be delivered.
• Request Amount – Full amount or tranches (in AST) with an explanation of the use of funds.
• Timeline with Milestones — A list with dates, time windows, or steps that the project owner aims to hit including proposed final delivery date.
• Copyright — All proposals are public domain via CC0.

Process

Each proposal follows a process from idea to implementation.

• Draft — Project owner drafts and iterates on the proposal on Discord at least 3 weeks prior to vote.
• Voting — Project owner proposes a vote to finalize the proposal which is then voted on by AirSwap DAO members during the monthly voting cycle.
• Acceptance — If the vote passes (accepted by > 50% of participating AST), the project is funded according to the scheduled release cycle.
• Implementation — Project owner is to report according to the timeline as the project is delivered. AirSwap contributors have the final say over project acceptance and disbursement of AST to project owners.

Rationale

The main goal is to boost AirSwap’s growth by welcoming individuals and teams to request funding for projects that aim to advance the development, growth, and adoption of AirSwap. The AGP program will be announced with a call for projects to garner interest in building dApps on AirSwap protocols.

The AGP program also aims to improve partnerships between project teams and the AirSwap DAO. Projects building on AirSwap would be able to provide rapid feedback about the AirSwap protocol to Contributors, such as unclear documentation, new feature requests, etc. Similarly, AirSwap DAO members will also be more aware of projects building on AirSwap, increasing the transparency of the ecosystem.

We believe that AirSwap DAO governance is mature enough to assess the merits vs budget of each AGP, and DAO members are encouraged to participate in discussions with the project teams before voting commences.

Copyright

All proposals are public domain via CC0.