Anticapture Commission Communication Thread

Welcome to the Anticapture Commission Communication Thread!

The Anticapture Commission (ACC) is mandated to represent the interests of individual delegates as a key tokenholder group and to prevent the capture of the Token House by any single tokenholder or group of tokenholders, including protocols, OP Chains, etc. This program, introduced as an experiment in Season 5, consists of high-impact delegates who meet the membership criteria outlined here and have opted in.


  • This program is best understood as a temporary measure to increase votable supply via delegation to a targeted tokenholder group - similar to what we’ve done with the Protocol Delegation Program and proposed Chain Delegation Program. This is meant to be a short term delegation program that increases the voting power of our highest impact delegates.

  • In exchange for receiving this delegation, Commission members will uphold the specified levels of engagement and serve the very important role of bridging communication between the Token House and Citizens’ House.

  • The Commission will create this bridge between Houses by filing two types of reports. The Commission has no decision making power in the Citizens’ House; they may only serve as a warning system. Each report requires 4 delegate approval from Commission members to be considered valid. The Citizens’ House may, of course, choose to disregard or disagree with a report.

Read the full description here.


  • Alisha.eth (Security Council Lead)

  • Dane Lund (Grants Council Lead)

  • Teresa Carballo (Code of Conduct Council Lead)

  • Brichis.eth (Anticapture Commission Lead)

  • Blockchain @ USC

  • Butterbum

  • Ceresstation

  • GFX Labs

  • Gonna.eth

  • Joxes (SEED Latam)

  • Katie Garcia

  • Lefteris

  • L2BEATs

  • Michael Vander Meiden

  • MinimalGravitas

  • MoneyManDoug

  • OPUser

  • PGov

  • StableLab

  • web3magnetic

  • 404 DAO

Internal Operating Procedures

On January 17th, the Anticapture Commission received a delegation of 10M OP from the Governance Fund for Season 5 and 6 contained in this multisig.


Updates - Voting Cycle #17

During our inaugural cycle, we published our Internal Operating Procedures (IOP) and established public communication channels, including email and a Discord channel, with @vonnie610 & @lavande support. Additionally, we tested the Snapshot Space for the ACC, hosted our first synchronous events, and vote from the ACC multisig for the first time:

Upgrade Proposal #3: Delta Network Upgrade

Vote: “For” (15 votes, unanimity)
Quorum: 15/7

Proposal to Reclassify Grant Misusage Enforcement

Vote: “For” (15 votes, unanimity)
Quorum: 15/7

Summary of Code of Conduct enforcement decisions

Vote: No votes
Quorum: 0/7

There have been multiple discussions regarding our role as the Anticapture Commission. We decided to address these topics in our first Internal Meeting, which is available for viewing here. Our initial focus was on the influence of 10M OP in our governance and whether we should vote on all matters or limit our involvement, as our IOP does not specify this. We are currently discussing the process and the voting will start in the coming days and plan to amend the IOP during the Review Period of Voting Cycle #18. Once the draft is prepared, it will be submitted as a proposal in our Snapshot Space. For this cycle, we decided to vote on all proposals due to the lack of a pre-established policy.

Another significant discussion revolved around the frequency of Office Hours. Some members suggested having one Office Hours per cycle for efficiency, considering that alerts may not be frequent. Others viewed it as an opportunity for individual delegates to engage with high context delegates about governance, not just capture, which would slightly alter the objective of the Office Hours. We are currently voting on this here.

The third key discussion concerned the quorum for our Snapshot Space. Initially, 30% was proposed before confirming the final number of members (currently 21). We discussed increasing this percentage, given our delegation’s weight over the votable supply and our active status, making a higher quorum achievable. We are proposing to increase it to 60% and are currently voting on this here.

On Thursday, 25th, we held our first Office Hours. Most attendees were ACC members, so we used this time to discuss concerns about the Upgrade of the Governor Contract. You can find the details here and the ensuing discussion here.

The voting in our Snapshot Space will likely lead to changes in the upcoming weeks, possibly affecting our weekly Office Hours, voting frequency, and quorum. Keep up with the voting in real time here.

See you next Voting Cycle! :sparkles:


Updates - Voting Cycle #18

In our latest cycle, the Anticapture Commission (ACC) continued to refine its processes. Changes are visible in the updated ACC’s Internal Operational Procedures:

  1. Frequency of Voting from the ACC Multisig

  2. Process to step down from the ACC

  3. Anticapture Commission Snapshot Quorum

  4. ACC Office Hours Frequency

As we’ve agreed to vote only on proposals that possess veto rights (currently limited to protocol upgrades) and in special situations as outlined in our IOP, the only vote we cast on Agora was this one:
Protocol Upgrade #4

Vote: “For” (15 votes, unanimity)

Quorum: 15/13

The ACC’s second internal meeting highlighted the challenges of decentralization while balancing efficiency. A significant portion of the conversation centered around the desire for the OP token to control the governance contract and to have a decentralization roadmap around governance structures. Additionally, there was palpable frustration regarding the necessity of double transactions for voting in recent cycles.
Despite an understandable impatience for swift changes, there was agreement on the importance of patience and comprehending the ongoing process. It was recognized that the journey towards decentralization and refining governance is inherently gradual, demanding both time and meticulous thought for successful execution.
Catch the full discussion here: