diff --git a/docs/concepts/lifecycle-anatomy-aip-proposal.md b/docs/concepts/lifecycle-anatomy-aip-proposal.md index 74b1849a..7a4566a4 100644 --- a/docs/concepts/lifecycle-anatomy-aip-proposal.md +++ b/docs/concepts/lifecycle-anatomy-aip-proposal.md @@ -1,48 +1,46 @@ --- id: lifecycle-anatomy-aip-proposal -title: "The lifecycle and anatomy of an Arbitrum Improvement Proposal (AIP)" +title: The lifecycle and anatomy of an Arbitrum Improvement Proposal (AIP) sidebar_label: Lifecycle and anatomy of an AIP -description: Learn about the process and infrastructure that supports the Arbitrum Improvement Proposal (AIP) protocol, as defined in the Constitution of the Arbitrum DAO. +description: Learn about the process and infrastructure that supports the + Arbitrum Improvement Proposal (AIP) protocol, as defined in the Constitution + of the ArbitrumDAO. dao_author: symbolpunk dao_sme: dzgoldman --- - import DraftExpectationsPartial from '@site/docs/partials/_draft-expectations-partial.md'; -An Arbitrum Improvement Proposal (AIP) is a proposal submitted by a member of the Arbitrum DAO that proposes a change to the Arbitrum ecosystem. There are two types of AIPs: Constitutional and non-Constitutional: +An Arbitrum Improvement Proposal (AIP) is a proposal submitted by a member of the ArbitrumDAO that proposes a change to the Arbitrum ecosystem. There are two types of AIPs: Constitutional and non-Constitutional: -- **Constitutional AIPs** are those that modify the text or procedures of the Constitution or AIP-1, install or modify software on any chain, or take any action that requires "chain owner" permission on any chain. -- **Non-Constitutional AIPs** are all other AIPs, such as those that request funds/grants or provide general guidelines or information to the community. +* **Constitutional AIPs** are those that modify the text or procedures of the Constitution or AIP-1, install or modify software on any chain, or take any action that requires "chain owner" permission on any chain. +* **Non-Constitutional AIPs** are all other AIPs, such as those that request funds/grants or provide general guidelines or information to the community. In this conceptual overview, we'll evaluate the lifecycle and anatomy of both types of AIPs. - ### The anatomy of an Arbitrum Improvement Proposal (AIP) import AnatomyAIPPartial from '@site/docs/partials/_anatomy-aip-partial.md'; - ### The lifecycle of an Arbitrum Improvement Proposal #### Technical overview For a technical overview of implementation details, visit the [Governance Repo](https://github.com/ArbitrumFoundation/governance/tree/main/docs): - - [Governance Action Contracts](https://github.com/ArbitrumFoundation/governance/blob/main/src/gov-action-contracts/README.md) - - [Arbitrum Governance: Technical Overview](https://github.com/ArbitrumFoundation/governance/blob/main/docs/overview.md) - - [Proposal Lifecycle Example](https://github.com/ArbitrumFoundation/governance/blob/main/docs/proposal_lifecycle_example.md) - - [Roundtrip Governance - Diagram](https://github.com/ArbitrumFoundation/governance/blob/main/docs/roundtrip-governance.png) +* [Governance Action Contracts](https://github.com/ArbitrumFoundation/governance/blob/main/src/gov-action-contracts/README.md) +* [Arbitrum Governance: Technical Overview](https://github.com/ArbitrumFoundation/governance/blob/main/docs/overview.md) +* [Proposal Lifecycle Example](https://github.com/ArbitrumFoundation/governance/blob/main/docs/proposal_lifecycle_example.md) +* [Roundtrip Governance - Diagram](https://github.com/ArbitrumFoundation/governance/blob/main/docs/roundtrip-governance.png) #### High-level overview -The proposal submission process starts with a temperature check, where the AIP is suggested on the Arbitrum DAO governance forum along with a Snapshot poll. It's discussed/debated for 1 week. If the AIP passes the temperature check, it moves on to the next phase, which is the formal AIP and call for voting. In this phase, the AIP is submitted via governance contracts on Arbitrum One via [Tally](https://tally.xyz/gov/arbitrum)'s user interface. After 3 days, a voter distribution snapshot is taken and the voting period begins. - -Each AIP must be labeled as Constitutional or non-Constitutional, and must also clearly specify which Arbitrum DAO-governed chain(s) it will affect. If the AIP passes, it moves through a series of phases that include L2 and L1 waiting periods, and eventually, the implementation of the proposal. This process typically takes 34 days for a Constitutional AIP or 21 days for a Non-Constitutional AIP, but may take longer if specified by the AIP. +The proposal submission process starts with a temperature check, where the AIP is suggested on the ArbitrumDAO governance forum, discussed for at least 7 days, followed by a temperature check that runs for another 7 days. If the AIP passes the temperature check, it moves on to the next phase, which is the formal AIP and call for voting. In this phase, the AIP is submitted via governance contracts on Arbitrum One via the [on-chain governance UI](https://alt.gov.arbitrum.foundation/). After 3 days, a voter distribution snapshot is taken and the voting period begins. +Each AIP must be labeled as Constitutional or non-Constitutional, and must also clearly specify which ArbitrumDAO-governed chain(s) it will affect. If the AIP passes, it moves through a series of phases that include L2 and L1 waiting periods, and eventually, the implementation of the proposal. This process typically takes at least 42 days from the beginning of the temperature check in Phase 1 until an AIP is finally executed in Phase 7 for a Constitutional AIP, or at least 27 days for a Non-Constitutional AIP (but may take longer if specified by the AIP). ```mermaid graph TD; @@ -57,32 +55,31 @@ graph TD; H --> I["Phase 7: Implementation"]; ``` - -#### Phase 1: Temperature check (optional but recommended) - 1 week in duration +#### Phase 0: Forum post (optional but recommended) - 7 days in duration This is the first phase of the Arbitrum Improvement Proposal (AIP) process: - 1. The proposed AIP is submitted following the procedure outlined within [How to submit a DAO proposal](../how-tos/create-submit-dao-proposal). - 2. A discussion is initiated on the [Arbitrum DAO governance forum](https://forum.arbitrum.foundation/c/proposals/7). - 3. A Snapshot poll is created to help gauge the interest of Arbitrum DAO members - either at the same time as the forum post, or after the forum post has facilitated initial discussion. This poll can be initiated only by an address that can represent at least 0.01% of the votable tokens. - 4. The poll runs for 7 days and is decided by a simple majority with no required participation threshold. +1. The proposed AIP is submitted following the procedure outlined within How to submit a DAO proposal. +2. A discussion is initiated on the ArbitrumDAO governance forum for at least 7 days. +#### Phase 1: Temperature check (optional but recommended) - 7 days in duration -This is an optional step, but it's recommended as a due-diligence governance best practice. If an AIP fails this temperature check, the original AIP author is encouraged to refrain from proceeding, and voters are encouraged to reject it if the author proceeds. If an AIP proposer decides to skip this step, voters should consider this as a factor in their vote. +1. A temperature check poll is created to help gauge the interest of ArbitrumDAO members, after the forum post has facilitated initial discussion. This poll can be initiated only by an address that can represent at least 500,000 votable tokens. +2. The poll runs for 7 days and is decided by a simple majority with no required participation threshold. +This is an optional step, but it's recommended as a due-diligence governance best practice. If an AIP fails this temperature check, the original AIP author is encouraged to refrain from proceeding, and voters are encouraged to reject it if the author proceeds. If an AIP proposer decides to skip this step, voters should consider this as a factor in their vote. #### Phase 2: Formal AIP and call for voting - 3 days in duration -In this phase, the AIP is officially submitted via governance smart contracts on the Arbitrum One chain. The proposer of the AIP must have an address that can represent at least 1,000,000 votable tokens. After the AIP is submitted, there's a 3-day period for interested parties to discuss the proposal and gather votes before a voter distribution snapshot is taken. During this phase, the AIP must be labeled as either Constitutional or Non-Constitutional. Additionally, the AIP must clearly specify which Arbitrum DAO-governed chain(s) it will affect. This phase is important as it defines a clear, formal protocol for proposing and voting on AIPs. - +In this phase, the AIP is officially submitted via governance smart contracts on the Arbitrum One chain. The proposer of the AIP must have an address that can represent at least 1,000,000 votable tokens. After the AIP is submitted, there's a 3-day period for interested parties to discuss the proposal and gather votes before a voter distribution snapshot is taken. During this phase, the AIP must be labeled as either Constitutional or Non-Constitutional. Additionally, the AIP must clearly specify which ArbitrumDAO-governed chain(s) it will affect. This phase is important as it defines a clear, formal protocol for proposing and voting on AIPs. #### Phase 3: On-chain DAO vote - 14-16 days in duration -During this phase, members of the Arbitrum DAO can vote directly on-chain for (or against) a submitted AIP. For the AIP to pass, more Votable Tokens must vote in favor than against, and a certain percentage of all Votable Tokens must vote in favor. This percentage is 4.5% for Constitutional AIPs and 3% for Non-Constitutional AIPs, and is referred to as "Threshold 2" within the [Constitution](../dao-constitution.md). +During this phase, members of the ArbitrumDAO can vote directly on-chain for (or against) a submitted AIP. The proposal must receive more votes in favor than against. Additionally, Constitutional AIPs must receive ‘For’ and/or ‘Abstain’ votes from at least 50% of delegated tokens (within the range of 150m to 450m $ARB); while non-Constitutional AIPs must receive ‘For’ and/or ‘Abstain’ votes from at least 40% of delegated tokens (within the range of 100m to 300m $ARB). This is referred to as "Threshold 2" within the [Constitution](https://docs.arbitrum.foundation/dao-constitution#section-2-dao-proposals-and-voting-procedures). The voting period for an AIP ends 14 days after it starts. However, if Threshold 2 is reached within the last 2 days of the voting period, the voting period is extended by 2 days. If the AIP fails to pass, the process ends after this Phase 3. If it does pass, Constitutional AIPs move on to Phases 4 through 7, while Non-Constitutional AIPs skip Phases 4 through 6 and go straight to Phase 7. -#### Phase 4: L2 Waiting Period (3 days for Non-constitutional or 8 days for Constitutional): +#### Phase 4: L2 Waiting Period (3 days for Non-constitutional or 8 days for Constitutional): After an AIP has passed Phase 3, there is a 3 day waiting period for spending from the treasury and an 8 day waiting period for upgrades to the smart contracts. During this time, people who do not agree with the AIP have the chance to withdraw their funds or take other action on L2. This period is meant to give everyone time to consider the decision and make any necessary adjustments to their investments or actions. @@ -98,21 +95,18 @@ After Phase 5 of the voting process, where the decision is recorded on the Ether This waiting period is important because it minimizes the risk of an AIP negatively impacting transactions that were initiated prior to the DAO's approval of the AIP. Once this waiting period is over, the AIP takes effect. - #### Phase 7: Implementation -Phase 7 is the final step in the voting process in which an approved AIP is fully executed and implemented. An AIPs implementation can happen in one of two ways. It can happen directly on Ethereum mainnet, or via a transaction sent from L1 to one or more of the Layer 2 chains that are governed by the Arbitrum DAO. This L1-to-L2 mechanism ensures that changes made by an approved AIP are recognized and supported on both L1 and L2 chains. Once the AIP has been fully executed and implemented, its changes will be active until another AIP is passed to make further changes. - +Phase 7 is the final step in the voting process in which an approved AIP is fully executed and implemented. An AIPs implementation can happen in one of two ways. It can happen directly on Ethereum mainnet, or via a transaction sent from L1 to one or more of the Layer 2 chains that are governed by the ArbitrumDAO. This L1-to-L2 mechanism ensures that changes made by an approved AIP are recognized and supported on both L1 and L2 chains. Once the AIP has been fully executed and implemented, its changes will be active until another AIP is passed to make further changes. #### Additional waiting periods (optional) -When an AIP is passed, it means that changes are going to be made to the Arbitrum DAO's governance system. These changes can be "breaking changes" - changes that cause other parts of the governance system (or third-party systems) to stop working or behave differently. - -To ensure that the owners of these downstream dependencies have enough time to adjust to these types of changes, proposal submitters may optionally specify an extra waiting period that needs to be honored before the AIP's changes take effect. This is recommended for AIPs that require Arbitrum DAO's stakeholders to spend some time preparing for the AIP's proposed changes. This mechanism helps ensure that both Arbitrum DAO's systems and third-party systems can remain available and stable during and after any given AIP's implementation. +When an AIP is passed, it means that changes are going to be made to the ArbitrumDAO's governance system. These changes can be "breaking changes" - changes that cause other parts of the governance system (or third-party systems) to stop working or behave differently. +To ensure that the owners of these downstream dependencies have enough time to adjust to these types of changes, proposal submitters may optionally specify an extra waiting period that needs to be honored before the AIP's changes take effect. This is recommended for AIPs that require ArbitrumDAO's stakeholders to spend some time preparing for the AIP's proposed changes. This mechanism helps ensure that both ArbitrumDAO's systems and third-party systems can remain available and stable during and after any given AIP's implementation. ### Conclusion -The entire AIP voting process, including all seven phases, typically takes 37 days to complete for Constitutional AIPs, or 27 days for Non-Constitutional AIPs, from the start of the temperature check in Phase 1. This process is designed to allow for thorough consideration and voting, ensuring that everyone has a fair chance to voice their opinions and concerns. +The entire AIP voting process, including all seven phases, typically takes at least 42 days to complete for Constitutional AIPs, or at least 27 days for Non-Constitutional AIPs, from the start of the temperature check in Phase 1. This process is designed to allow for thorough consideration and voting, ensuring that everyone has a fair chance to voice their opinions and concerns. -This conceptual overview presents a beginner-friendly elaboration upon the AIP process detailed within [The Constitution of the Arbitrum DAO](../dao-constitution.md). This process is designed to ensure that proposed changes align with the Arbitrum community's mission and guiding values, and that the community's various stakeholders have the opportunity to discuss, debate, vote on, and prepare for proposed changes before they're ultimately implemented. +This conceptual overview presents a beginner-friendly elaboration upon the AIP process detailed within [The Constitution of the ArbitrumDAO](../dao-constitution). This process is designed to ensure that proposed changes align with the Arbitrum community's mission and guiding values, and that the community's various stakeholders have the opportunity to discuss, debate, vote on, and prepare for proposed changes before they're ultimately implemented.