The following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
As with the previous elections’ nomination period, we selected the applicants we voted for based on the following high-level criteria:
- Strong technical knowledge
- It’s imperative for each member of the security council to be able to independently verify what they’re signing and understand the underlying technology and code. We are willing to support members who bring other skills, like deep knowledge of legal implications, that add significant value to the security council.
- Reputation at stake
- While we respect the wish for some community members to remain anonymous, we believe that members of the security council should have their identities known so that if they misbehave or fail to act on time, they risk slashing their public reputation. We are willing to make an exception only for well-known anons with exceptional reputations.
- No connection to OffChain Labs or Arbitrum Foundation
- We wanted to limit the support for individuals or entities that are related to the original founding team (OffChain Labs and Arbitrum Foundation) as we believe that the Security Council should serve as a third-party guardian that protects the users of the protocol.
- Location
- Security Council members should be spread around the world to cover most time zones and various jurisdictions as that would help with reaction speed in case of emergency and would mitigate the risk of legal implications.
With that in mind, we voted in favor of the following nominees, even though some did not qualify for the elections eventually.
- Bayge
- Caleb
- Chuygarcia.eth
- Code4rena
- Cyfrin
- Dedaub
- Hacken
- Wakeup Labs
- Immunefi
- Guardian Team