diff --git a/docs/partials/_constitution-content-partial.mdx b/docs/partials/_constitution-content-partial.mdx index f289b6ab..21ea6fff 100644 --- a/docs/partials/_constitution-content-partial.mdx +++ b/docs/partials/_constitution-content-partial.mdx @@ -20,9 +20,10 @@ the ArbitrumDAO took effect on the date upon which AIP-1 was posted, located at

Section 2: DAO Proposals and Voting Procedures

The following process governs the rules and procedures by which the ArbitrumDAO may propose, vote on and implement Arbitrum Improvement Proposals (AIPs). No AIP may be in violation of applicable laws, in particular sanctions-related regulations.

    -
  1. Phase 1: Temperature Check (1 week) (Optional but Recommended): The AIP is suggested on the public forum and discussed/debated for 1 week. The AIP should be accompanied by a Snapshot poll or other method as determined pursuant to the governance process, which can only be submitted by an address that can vote at least 0.01% of the Votable Tokens. The Snapshot poll also runs for 1 week, and is decided by a simple majority with no required participation threshold. An AIP that fails the temperature check should not be submitted for a vote. If an AIP fails the temperature check, or has not undergone a temperature check, as a matter of good governance practice, it is recommended that voters strongly consider voting to reject it.
    2. +
  2. Phase 0: Forum Post (1 week) (Optional but Recommended): The AIP is suggested on the public forum and discussed/debated for 1 week.
    3. +
  3. Phase 1: Temperature Check (1 week) (Optional but Recommended): The AIP should be accompanied by an off-chain temperature check poll or other method as determined pursuant to the governance process, which can only be submitted by an address that can vote at least 500,000 of the Votable Tokens. The off-chain temperature check runs for 1 week, and is decided by a simple majority with no required participation threshold. An AIP that fails the temperature check should not be submitted for a vote. If an AIP fails the temperature check, or has not undergone a temperature check, as a matter of good governance practice, it is recommended that voters strongly consider voting to reject it.
  4. -

    Phase 2: Formal AIP and call for voting (3 days): The AIP is submitted via governance contracts on Arbitrum One, with a user interface available on Tally. The AIP proposer is required to have an address that is delegated at least 1,000,000 Votable Tokens.

    +

    Phase 2: Formal AIP and call for voting (3 days): The AIP is submitted via governance contracts on Arbitrum One, with a user interface available on https://alt.gov.arbitrum.foundation/. The AIP proposer is required to have an address that is delegated at least 1,000,000 Votable Tokens.

    After 3 days, a voter distribution snapshot will be taken and the voting period will begin; this gives interested parties time to discuss the AIP and gather votes before the voter distribution snapshot is taken.

    Each AIP must be labeled as Constitutional or non-Constitutional.

    A Constitutional AIP is one that:

    @@ -113,10 +114,10 @@ the ArbitrumDAO took effect on the date upon which AIP-1 was posted, located at

  5. Phase 6: L1 Waiting Period (3 days): Following the completion of Phase 5, there will be an additional 3 day waiting period. This ensures that users who initiated withdrawals or other L2-to-L1 messages have time to execute them on L1 before the AIP takes effect.

  6. Phase 7: Implementation: The AIP is fully executed and implemented. This may happen on L1 or via a transaction sent from L1 to one or more Governed Chains.

-

This AIP process as specified will typically require 37 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 27 days for a Non-Constitutional AIP. An AIP may optionally specify further delay before its implementation.

+

This AIP process as specified will typically require 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. An AIP may optionally specify further delay before its implementation.

Section 3: The Security Council

The Security Council is a committee of 12 members who are signers of a multi-sig wallet, which has powers to perform certain Emergency Actions and Non-Emergency Actions, as delegated to it by the ArbitrumDAO and The Arbitrum Foundation, and is responsible for upholding this ArbitrumDAO Constitution. Through the submission, approval and implementation of a Constitutional AIP, the ArbitrumDAO is able to modify the Security Council's powers or to eliminate the Security Council entirely.

-

Equivalent "copies" of the Security Council multi-sig contracts exist, one on Ethereum and another on each ArbitrumDAO-governed chain.

+

Equivalent "copies" of the Security Council multi-sig contracts exist, one on Ethereum and another on each ArbitrumDAO-governed chain. A Security Council Member can independently rotate their signing key in the multi-sigs, but the rotation must go through Phases 4 to 7 of the AIP process. In Phase 4, it adheres to the waiting time for an L2 to L1 message.

Emergency Actions:

The Security Council has the power to execute any software upgrade or perform other required actions with no delay in order to respond to a security emergency, should one arise (such actions, "Emergency Actions"). Performing any Emergency Action requires a 9-of-12 approval from the Security Council. The Security Council must not use its power to perform Emergency Actions except in a true security emergency, such as a critical vulnerability that could significantly compromise the integrity, confidentiality, or availability of a chain governed by the ArbitrumDAO.

After performing any Emergency Action, the Security Council must issue a full transparency report (at an appropriate time after the security emergency has passed) to explain what was done and why such Emergency Action was justified.

@@ -127,14 +128,14 @@ the ArbitrumDAO took effect on the date upon which AIP-1 was posted, located at

Section 4: Security Council Elections

The Security Council has 12 members, who are divided into two Cohorts of 6 members.

The initial Security Council Cohorts were determined by randomly splitting the 12 members into two 6-member cohorts - 6 members in the ‘First Cohort’ and 6 members in the ‘Second Cohort’. The members of the initial Security Council Cohorts are detailed in a transparency report here.

-

The first Security Council election is scheduled to begin on the 15th September 2023 or the earliest possible date. The election can only begin upon the availability of an on-chain election process that is approved and installed by the Arbitrum DAO. This first election replaces the 'First Cohort'. The next election replaces the 'Second Cohort' and so forth.

-

The date chosen for the first election will form the basis for all future elections. Every election should begin 6 months after the previous election has started and it will replace its respective cohort of 6 members.

+

The first Security Council election commenced on 15th September 2023, following the availability of an on-chain election process that was approved and installed by the ArbitrumDAO. This first election replaced the 'First Cohort'. The next election replaced the 'Second Cohort' and so forth.

+

The date chosen for the first election formed the basis for all future elections. Every election should begin 12 months after the previous election has started and it will replace its respective cohort of 6 members.

All Security Council members are expected to serve their term until the election is complete and the new Security Council members are installed.

The following timeline governs an election that starts at time T:

  1. Contender submission (T until T+7 days): Any DAO member may declare their candidacy for the Security Council, provided that a current Security Council member in one cohort may not be a candidate for a seat in the other cohort.
    2. -
  2. Nominee selection (T+7 until T+14 days): Each DAO member or delegate may vote for their declared contender. Each token may be cast for one contender. To the extent that there are more than six contenders, each eligible contender must be supported by pledged votes representing at least 0.2% of all Votable Tokens.
    3. -
  3. Compliance process (T+14 until T+28 days): All candidates will cooperate with the Arbitrum Foundation and complete the compliance process. The Arbitrum Foundation is responsible for removing any candidates that fail the compliance process. In the event that fewer than six candidates are supported by pledged votes representing at least 0.2% of all Votable Tokens, the current Security Council members whose seats are up for election may become candidates (as randomly selected out of their Cohort) until there are 6 candidates.
    4. +
  4. Nominee selection (T+7 until T+14 days): Each DAO member or delegate may vote for their declared contender. Each token may be cast for one contender. To the extent that there are more than six contenders, each eligible contender must be supported by pledged votes representing at least 0.1% of all Votable Tokens.
    5. +
  5. Compliance process (T+14 until T+28 days): All candidates will cooperate with the Arbitrum Foundation and complete the compliance process. If candidates need to rotate their signer addresses during a Security Council election, they must do so before day T+25 (during the compliance process). The Arbitrum Foundation is responsible for removing any candidates who fail the compliance process. In the event that fewer than six candidates are supported by pledged votes representing at least 0.1% of all Votable Tokens, the current Security Council members whose seats are up for election may become candidates (as randomly selected out of their Cohort) until there are 6 candidates.
  6. Member election (T+28 until T+49 days): Each DAO member or delegate may vote for any declared candidate. Each token may be cast for one candidate. Votes cast before T+35 days will have 100% weight. Votes cast between T+35 days and T+49 days will have weight based on the time of casting, decreasing linearly with time, with 100% weight at T+35 days, decreasing linearly to 0% weight at T+49 days.
  7. At T+49 days: The process for replacing the cohort of security council members with the 6 candidates who received the most votes will be activated. The installation process must be executed via the on-chain governance smart contracts and it may take several days until the new security council members are installed.