AIP describes standards for the Aventus Ecosystem, including core protocol specifications and processes. These AIPs are technical communication processed off-chain and recognised formally. This is not a substitute for the governance process run here but it is a collection of sound and forward-thinking solutions and functionalities for the network. However, they do not represent a commitment of any form towards existing projects.
The following is the standardization process for all AIPs in all tracks:
Draft - The idea has been formally accepted on the github repository by merging the draft into the submissions folder.
Community review - The submitted proposal will be announced on various channels for 2 weeks OR The submitted proposal will be voted on by AVT holders. The result of the vote will either be accept or reject.
Proposed - This has been tested in a sandbox environment and is believed to be working. Also, an approved plan to implement this on the mainnet has been constructed and accepted. Further changes are unlikely at this stage.
Active - The proposal is deemed to be working and has passed all checks and is now deployed on the Aventus mainnet.
On Hold - Work on this has been halted either due to the author/submitted putting the proposal on hold or a decision was made to halt it.
Obsolete - A more recent proposal supersedes it in capabilities and value.
Rejected - Concerns have been raised around the proposal.
There are five types of AIP:
Core (2) - Improvements to the components of the substrate build of the Aventus Network such as pallets and any other changes that affect the blockchain protocol. This includes changes to the block or transaction validity rules and other network protocol changes.
Layer 1 (0) - Improvements to the smart contracts on Layer 1.
Interface (0) - Improvements to the communication mechanism between the Aventus blockchain and other blockchain networks such as Ethereum, Polkadot, etc. This also includes improvements around the client.
Ecosystem (0) - Improvements to the various tools built on the network such as Explorer, Wallet, Governance, etc.
Informational (1) - Describes an Aventus design issue, or provides general guidelines or information to the Aventus community, but does not propose a new feature.
To understand more about the current state of the Aventus network, check out our whitepaper.