diff --git a/docs/concepts/security-council.md b/docs/concepts/security-council.md deleted file mode 100644 index 60d8969a..00000000 --- a/docs/concepts/security-council.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -id: security-council -title: "Security Council: A conceptual overview" -sidebar_label: Security Council -description: Learn about the Security Council, a group of individuals who are responsible for managing the risk of the Arbitrum ecosystem through the selective application of emergency actions. -dao_author: symbolpunk -dao_sme: dzgoldman ---- - -import DraftExpectationsPartial from '@site/docs/partials/_draft-expectations-partial.md'; - - - -[The Constitution of the Arbitrum DAO](../dao-constitution) outlines the process for electing members to the Security Council, a group of individuals who are responsible for addressing risks to the Arbitrum ecosystem through the selective application of emergency actions and non-emergency actions. The Security Council is made up of 12 members who are elected by the members of the Arbitrum DAO through a democratic process. See [here](../security-council-members) for the current members of the Security Council. - -### The role of the Security Council - -The primary role of the Security Council is to address critical risks associated with the Arbitrum protocol and its ecosystem. The Security Council is responsible for making time-sensitive and emergency response decisions that protect the interests of the DAO, its members, and the broader Arbitrum community. The Security Council is subject to the oversight and control of the DAO's members, who have the power to remove Security Council members if they're not acting in the best interests of the DAO. - -### How the elections work - -The Security Council is a 12-member council divided into two groups. Every six months, there are elections to fill the seats in these two groups, respectively. - -Every elected Security Council member’s term lasts one year, excluding the first cohort’s member terms, which are truncated by the amount of time between the date of the first election specified in the Constitution and the date of the DAO's launch. - -To become a candidate for the Security Council, you must be a member of the Arbitrum DAO. You must also have support from at least 0.2% of all votable tokens. Once the candidates have been chosen, all members of the Arbitrum DAO can vote for the candidates. The 6 candidates who receive the most votes will be elected to the Security Council. Additionally, the Arbitrum Foundation may set forth further guidelines and procedures for ensuring a fair, transparent and effective elections process. - -No more than 3 candidates from the same organization should be elected into the Security Council. Also, candidates shouldn't have any conflicts of interest that would prevent them from acting in the best interests of the Arbitrum DAO. - -The rules for the Security Council elections can be changed by the members of the Arbitrum DAO, but these changes can't be made during an ongoing election. Security Council members can also be removed from their position prior to their term ending if at least 10% of all votable tokens participate in a removal vote, and at least 5/6 of the votes are in favor of removal. A member can also be removed if at least 9 members of the Security Council vote in favor of removal. - -Note that the [Constitution](../dao-constitution.md) is the most authoritative specification of the Arbitrum DAO's rules. If there are any discrepancies between this document and the Constitution, please feel free to submit an issue, and note that the Constitution takes precedence. - - -### Why elections are important - -The Security Council elections are important because they democratically determine who will be responsible for being vigilant about the security and integrity of the Arbitrum DAO. By holding regular elections, the community can ensure that the Council is made up of members who truly represent the values enshrined within [The Constitution of the Arbitrum DAO](../dao-constitution). - -In addition, the election process allows for the removal of Council members who are not acting in the best interests of the DAO. This helps to ensure that the Council always has the best interests of the network in mind. - - -### Conclusion - -The Security Council and its elections are an important part of the governance of the Arbitrum DAO. By participating in the elections, community members can ensure that the Security Council is made up of members who are trusted to represent the Arbitrum community’s values and to offer subject-matter expertise the community thinks relevant for the Council. - -These needs will generally demand expert-level technical proficiency and experience across a variety of technical domains, but the Arbitrum DAO’s values and needs are likely to evolve over time. Developing an understanding of the Security Council mechanism and its purpose is very important, especially if you’re a delegate or are otherwise active in Arbitrum DAO’s governance. - -If you're a member of the Arbitrum DAO, it's especially important for you to be aware of and support efforts towards risk management and progressive decentralization in order to ensure the long-term success and sustainability of the Arbitrum DAO and the technologies it governs. This includes the management of expectations and perceptions within and beyond the Ethereum community. It also includes continuous, collaborative self-education. diff --git a/docs/deployment-addresses.md b/docs/deployment-addresses.md index b9c935c7..ebb8a670 100644 --- a/docs/deployment-addresses.md +++ b/docs/deployment-addresses.md @@ -60,7 +60,7 @@ _*Note: the Token Distributor contract was [self-destructed](https://arbiscan.io | Security Council (L1, 9 of 12) | Ethereum | | | Security Council (Nova, 9 of 12) | Nova | | -_Note: See ["Security Council Members"](./security-council-members) for addresses of the current members of the Security Council._ +_Note: See ["Security Council Members"](./security-council#current-security-council-members) for addresses of the current members of the Security Council._ ### Security Council Elections diff --git a/docs/foundational-documents/transparency-report-initial-foundation-setup.md b/docs/foundational-documents/transparency-report-initial-foundation-setup.md index ff28042a..59ab320b 100644 --- a/docs/foundational-documents/transparency-report-initial-foundation-setup.md +++ b/docs/foundational-documents/transparency-report-initial-foundation-setup.md @@ -69,7 +69,7 @@ The Security Council was required to be operational at the time the DAO launched The initial Security Council members, split by cohort, are as follows: -_NOTE: The members list below represents the initial security council members, which are not necessarily the current members; for the list of current members, see [Security Council Members](../../security-council-members)._ +_NOTE: The members list below represents the initial security council members, which are not necessarily the current members; for the list of current members, see [Security Council Members](../security-council)._ i. September Cohort diff --git a/docs/how-tos/create-submit-dao-proposal.md b/docs/how-tos/create-submit-dao-proposal.md index a62f6cf1..5d982619 100644 --- a/docs/how-tos/create-submit-dao-proposal.md +++ b/docs/how-tos/create-submit-dao-proposal.md @@ -93,7 +93,7 @@ Welcome to the future of governance! #### Important notes - 1. The Security Council has the power to execute emergency actions and non-emergency actions, as delegated to it by the Constitution. These are unlike traditional AIPs in that they can be approved by the Security Council without going through the above process. See the [Security Council](../concepts/security-council) page for more information. + 1. The Security Council has the power to execute emergency actions and non-emergency actions, as delegated to it by the Constitution. These are unlike traditional AIPs in that they can be approved by the Security Council without going through the above process. See the [Security Council](../security-council) page for more information. 2. The threshold of support required for a proposal to pass can vary depending on the type of proposal and the quorum requirements specified in the Constitution. 3. You can delegate your voting power[^2] to another address whether or not you have enough tokens to submit on-chain proposals. If you hold any $ARB tokens whatsoever, you can participate in Arbitrum DAO's governance. diff --git a/docs/security-council-members.md b/docs/security-council-members.md deleted file mode 100644 index ad6ab6d5..00000000 --- a/docs/security-council-members.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -id: security-council-members -title: 'Security Council Members' -sidebar_label: Security Council Members -description: Current members of the security council -dao_author: dzgoldman -dao_sme: dzgoldman ---- - -The following are the current members of the Security Council; for information about the Security Council, see ["Security Council Overview"](./concepts/security-council). - -i. September Cohort - -1. [0xhombre](https://twitter.com/0xhombre) - - `0xb71ca4ffbb7b58d75ba29891ab45e9dc12b444ed` -2. [Matt Fiebach](https://twitter.com/MattFiebach) - - `0x3bd8e2ac65ad6f0f094ba6766cbd9484ab49ef23` -3. [Harry Kalodner](https://www.linkedin.com/in/hkalodner/) is Co-Founder and CTO at Offchain Labs. Harry started working on building Arbitrum while studying at Princeton University. - - `0xf8e1492255d9428c2Fc20A98A1DeB1215C8ffEfd` -4. [Patrick McCorry](https://twitter.com/stonecoldpat0) has spent most of his adult life working on cryptocurrencies and his time was split across academic research and industry. Before working at the Arbitrum Foundation, he has worked on transaction delivery, layer-2 protocols, atomic swaps, consensus protocols, and applied cryptography. In a past life, he was an Assistant Professor at King’s College London and an accomplished researcher at UCL, UIUC and NCL. - - `0x8f10e3413586c4a8dcfce19d009872b19e9cd8e3` -5. [John Morrow](https://twitter.com/jmo_mx) - - `0x3e286452b1c66abb08eb5494c3894f40ab5a59af` -6. [Omer](https://twitter.com/omeragoldberg) - - `0xb07dc9103328a51128bc6cc1049d1137035f5e28` - -ii. March Cohort - -1. [Rachel Bousfield](https://github.com/rachel-bousfield) has been a software engineer at Offchain Labs since 2021. She is currently leading the development of Stylus. - - `0x5A1FD562271aAC2Dadb51BAAb7760b949D9D81dF` -2. [Justin Drake](https://www.linkedin.com/in/drakefjustin) has been a researcher at the Ethereum Foundation since 2017. He focuses on Ethereum consensus layer upgrades. - - `0x5280406912EB8Ec677Df66C326BE48f938DC2e44` -3. [Bartek Kiepuszewski](https://twitter.com/bkiepuszewski) has been a blockchain architect at MakerDAO since 2017. He also co-founded [l2beat.com](http://l2beat.com/) and TokenFlow Insights. Bartek holds a PhD in computer science from Queensland University of Technology. - - `0x0275b3D54a5dDbf8205A75984796eFE8b7357Bae` -4. [Patrick McNab](https://twitter.com/pat_mcnab) Is a Co-founder of Mycelium which has been developing and deploying decentralised financial infrastructure since 2018. Mycelium (previously Tracer DAO) were one of the first protocols deployed on Arbitrum in 2021 and support the Arbitrum ecosystem through running validators and Chainlink nodes. - - `0x566a07C3c932aE6AF74d77c29e5c30D8B1853710` -5. [Yoav Weiss](https://twitter.com/yoavw) is a security researcher at the Ethereum Foundation and has been building in the Ethereum space since 2017, working on account abstraction (ERC-4337), OpenGSN, L2 security, etc. Yoav brings over 25 years of experience and has developed security technologies used by industry leading companies. - - `0x475816ca2a31D601B4e336f5c2418A67978aBf09` -6. [Patricio Worthalter](https://www.linkedin.com/in/worthalter/) has been working full time in the Ethereum space since 2015. In 2018 he founded POAP, a web3 native public good that mints digital collectibles for the preservation of memories. - - `0xf6B6F07862A02C85628B3A9688beae07fEA9C863` diff --git a/docs/security-council.md b/docs/security-council.md new file mode 100644 index 00000000..f09e39b8 --- /dev/null +++ b/docs/security-council.md @@ -0,0 +1,91 @@ +--- +id: security-council +title: "Security Council" +sidebar_label: Security Council +description: Learn about the Security Council, a group of individuals who are responsible for managing the risk of the Arbitrum ecosystem through the selective application of emergency actions. +dao_author: symbolpunk +dao_sme: dzgoldman +--- + +import DraftExpectationsPartial from '@site/docs/partials/_draft-expectations-partial.md'; + + + +[The Constitution of the Arbitrum DAO](./dao-constitution) outlines the process for electing members to the Security Council, a group of individuals who are responsible for addressing risks to the Arbitrum ecosystem through the selective application of emergency actions and non-emergency actions. The Security Council is made up of 12 members who are elected by the members of the Arbitrum DAO through a democratic process. See [here](./security-council#current-security-council-members) for the current members of the Security Council. + + +### Current Security Council members + +The following are the current members of the Security Council. + +i. September Cohort 2023 + +1. [0xhombre](https://twitter.com/0xhombre) + - `0xb71ca4ffbb7b58d75ba29891ab45e9dc12b444ed` +2. [Matt Fiebach](https://twitter.com/MattFiebach) + - `0x3bd8e2ac65ad6f0f094ba6766cbd9484ab49ef23` +3. [Harry Kalodner](https://www.linkedin.com/in/hkalodner/) is Co-Founder and CTO at Offchain Labs. Harry started working on building Arbitrum while studying at Princeton University. + - `0xf8e1492255d9428c2Fc20A98A1DeB1215C8ffEfd` +4. [Patrick McCorry](https://twitter.com/stonecoldpat0) has spent most of his adult life working on cryptocurrencies and his time was split across academic research and industry. Before working at the Arbitrum Foundation, he has worked on transaction delivery, layer-2 protocols, atomic swaps, consensus protocols, and applied cryptography. In a past life, he was an Assistant Professor at King’s College London and an accomplished researcher at UCL, UIUC and NCL. + - `0x8f10e3413586c4a8dcfce19d009872b19e9cd8e3` +5. [John Morrow](https://twitter.com/jmo_mx) + - `0x3e286452b1c66abb08eb5494c3894f40ab5a59af` +6. [Omer](https://twitter.com/omeragoldberg) + - `0xb07dc9103328a51128bc6cc1049d1137035f5e28` + +ii. March Cohort 2023 + +1. [Rachel Bousfield](https://github.com/rachel-bousfield) has been a software engineer at Offchain Labs since 2021. She is currently leading the development of Stylus. + - `0x5A1FD562271aAC2Dadb51BAAb7760b949D9D81dF` +2. [Justin Drake](https://www.linkedin.com/in/drakefjustin) has been a researcher at the Ethereum Foundation since 2017. He focuses on Ethereum consensus layer upgrades. + - `0x5280406912EB8Ec677Df66C326BE48f938DC2e44` +3. [Bartek Kiepuszewski](https://twitter.com/bkiepuszewski) has been a blockchain architect at MakerDAO since 2017. He also co-founded [l2beat.com](http://l2beat.com/) and TokenFlow Insights. Bartek holds a PhD in computer science from Queensland University of Technology. + - `0x0275b3D54a5dDbf8205A75984796eFE8b7357Bae` +4. [Patrick McNab](https://twitter.com/pat_mcnab) Is a Co-founder of Mycelium which has been developing and deploying decentralised financial infrastructure since 2018. Mycelium (previously Tracer DAO) were one of the first protocols deployed on Arbitrum in 2021 and support the Arbitrum ecosystem through running validators and Chainlink nodes. + - `0x566a07C3c932aE6AF74d77c29e5c30D8B1853710` +5. [Yoav Weiss](https://twitter.com/yoavw) is a security researcher at the Ethereum Foundation and has been building in the Ethereum space since 2017, working on account abstraction (ERC-4337), OpenGSN, L2 security, etc. Yoav brings over 25 years of experience and has developed security technologies used by industry leading companies. + - `0x475816ca2a31D601B4e336f5c2418A67978aBf09` +6. [Patricio Worthalter](https://www.linkedin.com/in/worthalter/) has been working full time in the Ethereum space since 2015. In 2018 he founded POAP, a web3 native public good that mints digital collectibles for the preservation of memories. + - `0xf6B6F07862A02C85628B3A9688beae07fEA9C863` + + +### The role of the Security Council + +The primary role of the Security Council is to address critical risks associated with the Arbitrum protocol and its ecosystem. The Security Council is responsible for making time-sensitive and emergency response decisions that protect the interests of the DAO, its members, and the broader Arbitrum community. The Security Council is subject to the oversight and control of the DAO's members, who have the power to remove Security Council members if they're not acting in the best interests of the DAO. + +### How the elections work + +The Security Council is a 12-member council divided into two groups. Every six months, there are elections to fill the seats in these two groups, respectively. + +Every elected Security Council member’s term lasts one year, excluding the first cohort’s member terms, which are truncated by the amount of time between the date of the first election specified in the Constitution and the date of the DAO's launch. + +To become a candidate for the Security Council, you must be a member of the Arbitrum DAO. You must also have support from at least 0.2% of all votable tokens. Once the candidates have been chosen, all members of the Arbitrum DAO can vote for the candidates. The 6 candidates who receive the most votes will be elected to the Security Council. Additionally, the Arbitrum Foundation may set forth further guidelines and procedures for ensuring a fair, transparent and effective elections process. + +No more than 3 candidates from the same organization should be elected into the Security Council. Also, candidates shouldn't have any conflicts of interest that would prevent them from acting in the best interests of the Arbitrum DAO. + +The rules for the Security Council elections can be changed by the members of the Arbitrum DAO, but these changes can't be made during an ongoing election. Security Council members can also be removed from their position prior to their term ending if at least 10% of all votable tokens participate in a removal vote, and at least 5/6 of the votes are in favor of removal. A member can also be removed if at least 9 members of the Security Council vote in favor of removal. + +Note that the [Constitution](./dao-constitution.md) is the most authoritative specification of the Arbitrum DAO's rules. If there are any discrepancies between this document and the Constitution, please feel free to submit an issue, and note that the Constitution takes precedence. + + +### Why elections are important + +The Security Council elections are important because they democratically determine who will be responsible for being vigilant about the security and integrity of the Arbitrum DAO. By holding regular elections, the community can ensure that the Council is made up of members who truly represent the values enshrined within [The Constitution of the Arbitrum DAO](./dao-constitution). + +In addition, the election process allows for the removal of Council members who are not acting in the best interests of the DAO. This helps to ensure that the Council always has the best interests of the network in mind. + +#### How to participate + +To participate in a given cohort's election, candidates are invited to present themselves to the community by [creating a topic in the Governance Forums](https://forum.arbitrum.foundation/c/security-council-elections/12). + +Candidates should also engage with the community and delegates on whichever platforms they feel confortable in. During election cycles, The Arbitrum Foundation will be hosting numerous events, feel free to contact `scelection@arbitrum.foundation` to get more information. + +Cohorts are elections start on 15 March and 15 September each year, and candidates have a week to sign-up onchain to run for the given cohort. The [Tally Governance UI](https://www.tally.xyz/gov/arbitrum/council/security-council) has support to help candidates sign up for the elections. + +### Conclusion + +The Security Council and its elections are an important part of the governance of the Arbitrum DAO. By participating in the elections, community members can ensure that the Security Council is made up of members who are trusted to represent the Arbitrum community’s values and to offer subject-matter expertise the community thinks relevant for the Council. + +These needs will generally demand expert-level technical proficiency and experience across a variety of technical domains, but the Arbitrum DAO’s values and needs are likely to evolve over time. Developing an understanding of the Security Council mechanism and its purpose is very important, especially if you’re a delegate or are otherwise active in Arbitrum DAO’s governance. + +If you're a member of the Arbitrum DAO, it's especially important for you to be aware of and support efforts towards risk management and progressive decentralization in order to ensure the long-term success and sustainability of the Arbitrum DAO and the technologies it governs. This includes the management of expectations and perceptions within and beyond the Ethereum community. It also includes continuous, collaborative self-education. diff --git a/docs/why-governance.md b/docs/why-governance.md index ba4096f5..7756aebb 100644 --- a/docs/why-governance.md +++ b/docs/why-governance.md @@ -69,7 +69,7 @@ The Security Council is bound by [The Constitution of the Arbitrum DAO](./dao-co The Security Council can also trigger non-emergency upgrades, such as routine software upgrades and maintenance. These upgrades don't require a DAO vote to pass; they instead go through a delay period before taking effect, giving users time to opt out by withdrawing (as with decentralized DAO upgrades). -To learn more about the Security Council, refer to the [Security Council](./concepts/security-council.md) concept doc. For a formal articulation of the Security Council's role within Arbitrum DAO's governance process, refer to [The Constitution of the Arbitrum DAO](./dao-constitution). +To learn more about the Security Council, refer to the [Security Council](./security-council) concept doc. For a formal articulation of the Security Council's role within Arbitrum DAO's governance process, refer to [The Constitution of the Arbitrum DAO](./dao-constitution). ### The future of Arbitrum governance diff --git a/sidebars.js b/sidebars.js index cca4f916..658f093d 100644 --- a/sidebars.js +++ b/sidebars.js @@ -36,6 +36,10 @@ module.exports = { type: 'doc', id: 'network-upgrades', }, + { + type: 'doc', + id: 'security-council', + }, { type: 'category', label: 'How-to guides', @@ -91,10 +95,10 @@ module.exports = { type: 'doc', id: 'concepts/dao-vote', }, - { - type: 'doc', - id: 'concepts/security-council', - }, + // { + // type: 'doc', + // id: 'security-council', + // }, { type: 'doc', id: 'concepts/lifecycle-anatomy-aip-proposal', @@ -109,10 +113,6 @@ module.exports = { type: 'category', label: 'Governance architecture', items: [ - { - type: 'doc', - id: 'security-council-members', - }, { type: 'link', label: 'Sybil detection',