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.

AIPs are intended to cover changes that impact active services within the Aptos ecosystem. In lieu of another medium for posting community proposals, the AIP issue tracker can be used to store exploratory proposals. Though please consider first whether or not the Aptos-Core may be a better location for such discussions.

To vote on AIPs impacting the state of the Blockchain, 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.
6. To start discussing your AIP, create a GH Issue for your AIP using the default Issue template

AIP Index

Note: This is a subset of all the AIPs -- to see the full list of AIPs, please click here.

Number	Category	Title	Author
AIP-90	Framework	Add Apple as a supported OIDC provider	Alin Tomescu (alin@aptoslabs.com)
AIP-91	Framework	Enum Types in the Move VM	AIP Author
AIP-92	Smart Contract	Transaction Simulation Enhancement	junkil-park (https://github.com/junkil-park), movekevin (https://github.com/movekevin), gregnazario (https://github.com/gregnazario)
AIP-93	Blockchain	Consensus Observer	Josh Lind (https://github.com/JoshLind) & Zekun Li (https://github.com/zekun000)
AIP-94	Governance	Reduce stake lockup duration to 14 days and governance voting duration to 3 days per community vote	Tony (https://github.com/tony001242), Eric (eric@amnis.com)
AIP-95	Smart Contract	Collections Permission Update	johnchanguk, briungri
AIP-96	Smart Contract	Federated Keyless accounts	Alin Tomescu (alin@aptoslabs.com), davidiw, heliuchuan
AIP-97	Blockchain	Storage Format Change	grao1991
AIP-98	Governance	Reduce minimal stake required to submit governance proposal from 10M to 1M	sherry-x
AIP-99	Smart Contract	Disable Safe Burn of User-Owned Objects	gregnazario (greg@aptoslabs.com)
AIP-100	Framework	Private Entry Function for Multisig Account Creation	yeptos (https://github.com/yeptos), gregnazario (https://github.com/gregnazario)
...	...

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.
Ready for Approval	AIPs are ready for Gatekeeper approval and feedback.
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.

Category

• Framework
• Core (Blockchain)
• Gas
• Cryptography
• Ecosystem

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?

Notice regarding rejected or stale AIPs

• If an AIP Author is not actively engaging in their PR's and Issues, they will be closed after 14 days due to inactivity.
• If an AIP has been rejected, please review the feedback provided for further guidance.