March 2026 Security Council Election: Member Election

The Member Election phase (the final round of voting) of the March 2026 Security Council election process commenced today, April 12th, at ~14:30 UTC: Member Election | Arbitrum Security Council Election.

What is the Member Election Phase?

  • During this phase, delegates must vote for their preferred candidate(s) here.
  • The 6 candidates with the most votes at the end of this phase, will join the Security Council.
  • Delegates can split their votes across multiple candidates.

When is the Member Election Phase?

  • This phase runs for 21 days, from April 12 until May 3, 2026.

  • This phase runs in 2 parts:

    • Full Weight Voting (April 12 - April 19): Delegates can vote with full voting power in the first 7 days.
    • Decreasing Weight Voting (April 19 - May 3): To encourage delegates to cast votes early, voting power will linearly decay if not used within the first 7 days.

Who are the Candidates?

What makes a good candidate?

  • Choosing the right Security Council members is crucial to the security of the Arbitrum ecosystem due to the authority granted to them.
  • This guide and thread highlight some things to consider when evaluating candidates.

What is the Security Council?

  • The Security Council is a committee of 12 members who are signers of multi-sig wallets. They are responsible for combatting any critical risks associated with the Arbitrum protocol by making time-sensitive & emergency response decisions. Accordingly, the Security Council is key to securing the Arbitrum ecosystem.
  • Security Council Elections are held every 6 months, and allow the DAO to elect 6 new Security Council members.
  • Actively participating in Security Council Elections is one of the most important responsibilities of the ArbitrumDAO.

To find out more about the Security Council and the Security Council elections, please refer to the following resources:

What about the Security Council Election Process Improvement proposal?

There is an ongoing proposal to improve specific technical aspects of the Security Council election process at the smart contract level. This proposal passed its temperature check in September 2025 and will be taken to an onchain vote in the coming months. If approved by the DAO, these changes would only take effect for future elections, however, would impact the durations of the September 2025 cohort and the incoming March 2026 cohort. Accordingly, it is important for the community to understand these potential changes.

Remember to Vote!

We’re counting on you to vote for the next cohort of Security Council members to secure the Arbitrum ecosystem!

2 Likes

VOTING RATIONALE

Putting it here cause it seems like the right spot…?

I made my first comment for nominees here:

Again I made two rounds of votes.

First votes (early signal)

My first votes were meant as an early signal of support to communicate clearly to the community who I believe are strong candidates and should be considered.

I voted for:

  • Pablo Sabbatella
  • kemmio
  • Gustavo Grieco
  • Michael Lewellen
  • Yoav
  • blockful (Alex Netto)
  • Certora
  • Cyfrin

I would have voted for others too but they were way ahead and didn’t need my signal of support

Second votes (final allocation)

Toward the end, with a couple hours left before the decaty started, I added my votes to support candidates who were at risk of not making it but who I strongly believe should be on the council.

In order of most votes to least:

  • kemmio
  • Pablo Sabbatella
  • Gustavo Grieco
  • Yoav
  • blockful
  • Certora
  • Cyfrin

I would have happily also voted for the others on the list. There are a lot of rockstar applicants. If it stays how it is, I’m very happy with the next cohort of members I will get to work with!

3 Likes

Here’s a clean English version you can post directly:

Griff in your first vote you mentioned using it mostly as an ‘early signal’ and then later adjusted your ‘final allocation’. How did you balance risk diversification versus personal conviction when making those adjustments? Did you follow any quantitative framework for this, or was it primarily a qualitative judgement call? @Griff

SEEDGov Rationale

We’ve voted for Tino because he represents exactly the kind of profile the Arbitrum Security Council needs: technically resourceful, operationally experienced, and already deeply embedded in the ecosystem. His background goes from smart contract and protocol analysis, multisig management, to governance infrastructure, so he deeply understands the big picture.

He has also shown hands-on experience within Arbitrum’s own technical programs, such as Stylus Sprint, and has served in active governance roles in other L2 ecosystems, giving him both the technical fluency and the “instincts” the role demands. Beyond his technical credentials, Tino is a widely respected contributor across teams and ecosystem actors and across the broader landscape, bringing the trust and collaborative relationships that are as essential as technical skills in a role of this responsibility.

1 Like

The March 2026 Security Council Member Election results are here! We extend a warm welcome to the newly elected members who will be joining the March 2026 cohort:

  1. Michael Lewellen
  2. DZack23
  3. yoav.eth
  4. Certora
  5. bartek.eth
  6. Pablo Sabbatella

The grace period is underway through May 21. This allows the election results to register with the Security Council contracts across relevant chains. Stay tuned!

1 Like