AIP#: <# to be assigned>
Title: <AIP title>
Author(s): <List of authors' names and/or email addresses and GitHub handles>
Contributors: <List of contributor's names and/or email addresses and GitHub handles>
Tags: template
Category: Binding (Executable Purely On-Chain) vs. Signaling (Non-Binding Social Consensus Signal)
Status: <Assigned by AIP Editor>
Date Proposed: <yyyy-mm-dd>
Date Ratified: <yyyy-mm-dd>
Dependencies: <List of dependent AIPs>
Replaces: <List of AIP it is replacing>
License: <Sdded by AIP Author>
- A list of supporting materials referenced by this AIP.
- A short description of what the Astroport Improvement Proposal (AIP) is focused on. Suggest 30 words max.
- A 3-5 sentence description of the full AIP going through the problem it solves, how it's solved and who will and how it will be implemented.
- A short description of the motivation behind the AIP.
- Proposed process standard details - describes the new process or feature and the problem it is solving.
- The final code that can be used directly in the Assembly vote to accept or reject the AIP.
- For the implementation or testing of the proposed code
- This is one of the most important aspects of the Technical AIP proposal. The purpose of this section is to proactively document any security-relevant design information, decisions, potential failure modes, implementation details, and important discussions related to the proposed change. This section helps to optimize the AIP process by providing proactive guidance on security considerations when proposing a change that will affect the Astroport Protocol.
- This section includes the audit partner details and the final audit report for the proposed code.
- Recommended licenses for developed code:
- MIT: Expat/MIT/X11 license
- BSD-2-Clause: OSI-approved BSD 2-clause license
- BSD-3-Clause: OSI-approved BSD 3-clause license
- CC0-1.0: Creative Commons CC0 1.0 Universal
- GNU-All-Permissive: GNU All-Permissive License
- Apache-2.0: Apache License, version 2.0