bchocho / aips

Aptos Improvement Proposals (AIPs)

Aptos Improvement Proposals (AIPs)

Aptos Improvement Proposals (AIP) describe standards for the Aptos Network including the core blockchain protocol and the development platform (Move), smart contracts and systems for smart contract verification, standards for the deployment and operation of the Aptos Network, APIs for accessing the Aptos Network and processing information from the Aptos Network. To vote on AIPs, go to https://governance.aptosfoundation.org/

How to submit an AIP

1. Fork this repo into your own GitHub
2. Copy TEMPLATE.md into your new AIP file in aips/<your-feature-name-NO-AIP-#-here>.md
   • Name your AIP file based on your feature, not the AIP number, which will be picked for your later.
   • e.g., new-zero-knowledge-range-proof-verifiers.md is a good name.
   • ...but aip-14.md or 14.md is NOT a good name.
3. Edit your AIP file
   • Fill in the YAML header (see instructions there)
   • Follow the template guidelines to the best of your ability
4. Commit these changes to your repo
5. Submit a pull request on GitHub to this repo.

AIP Overview

This table contains an overview of all created and tracked AIPs. It should be updated with each new AIP.

Number	Layer	Title	Type	Status
AIP 0		Aptos Improvement Proposals	Informational	Active
AIP 1	Core	Proposer selection improvements	Standard	Accepted
AIP 2	Framework	Multiple Token Changes	Standard	Accepted
AIP 3	Framework	Multi-step Governance Proposal	Standard	Accepted
AIP 4	Framework	Update Simple Map To Save Gas	Standard	Accepted
AIP 5		N/A
AIP 6	Framework	Delegation pool for node operators	Standard	Accepted
AIP 7	Framework	Transaction fee distribution	Standard	Draft
AIP 8	Framework	Higher-Order Inline Functions for Collections	Standard	Accepted
AIP 9	Interface/ Framework	Resource Groups	Standard	Accepted
AIP 10	Framework	Move Objects	Standard	Accepted
AIP 11	Framework	Tokens as Objects	Standard	Accepted
AIP 12	Framework	Multisig Accounts v2	Standard	Accepted
AIP 13	Framework	Coin Standard Improvements	Standard	Accepted
AIP 14	Framwork	Update vesting contract	Standard	Accepted
AIP 15	Framework	Update and rename token_standard_reserved_properties	Standard	Accepted
AIP 16	Framework	New cryptography natives for hashing and MultiEd25519 PK validation	Standard	Accepted
AIP 17	Core	Reducing Execution Costs by Decoupling Transaction Storage and Execution Charges	Standard	Accepted
AIP 18	Framework	Introducing SmartVector and SmartTable to apto_std	Standard	Accepted
AIP 19	Framework	Enable updating commission_percentage in staking_contract module	Standard	Accepted
AIP 20	Framework	Generic Cryptography Algebra and BLS12-381 Implementation	Standard	Accepted
AIP 21	Framework	Fungible Assets	Standard	Draft
AIP 22	Framework	No-Code Token Objects	Standard	Accepted
AIP 23	Framework	Make Ed25519 public key validation native return false if key has the wrong length	Standard	Accepted
AIP 24	Framework	Move Library Updates	Standard	Accepted
AIP 25	Framework	Transaction Argument Support for Structs	Standard	Accepted
AIP 26	Core	Quorum Store	Standard	Accepted
AIP 27	Core	Sender Aware Transaction Shuffling	Standard	Accepted
AIP 28	Framework	Partial voting for on chain governance	Standard	Draft
AIP 29	Core	Peer monitoring service	Informational	Draft
AIP 30	Framework	Implement decrease in staking rewards	Standard	Draft
AIP 31	Framework	Allowlisting for delegation pool	Standard	Draft
AIP 32	Core	Storage Deletion Refund	Standard	Draft
AIP 33	Core	Block Gas Limit	Standard	Draft
AIP 34	Core	Unit Gas Price Estimation	Standard	Draft
AIP 35	Core	Charging Invariant Violation Errors	Standard	Draft
AIP 36	Core	Universally Unique Identifiers	Standard	Draft
...	...

Types of AIPs

• Standard: AIPs focusing on the changes to the Aptos blockchain.
• Informational: AIPs for the purpose of providing additional information, context, supporting details about Aptos blockchain.

AIP Statuses

Status	Description
Draft	Drafts are currently in process and not ready for review. No corresponding GH Issue will be created.
In Review	AIPs are ready for community review and feedback. See suggestions on providing feedback below.
Accepted	AIPs has been accepted and will be implemented soon.
Rejected	A community decision has been made to not move forward with an AIP at this time.
On Hold	Some information is missing or prerequisites have not yet been completed.

Layer

• Framework
• Core (Blockchain)

Providing Feedback on an AIP

• Follow the discussion in the corresponding AIP issue
• If you were designing this change, what would you want to communicate? Is it being communicated in the AIP?
• As a community member, how are you impacted by this change? Does it provide enough information about the design and implementation details to assist with decision making?