Anticapture Commission Communication Thread

Pumbi · February 25, 2025, 1:22pm

Regarding our latest updates, on February 18th, ACC members held an extraordinary meeting during which all former multisig signers were removed to clean up the multisig and ensure that only the addresses of the current season’s members have signing authority.

This post also aims to serve as a record to guide future iterations of the ACC on how to address these types of situations.

The Problem

When attempting to remove former signers in a batch transaction, after obtaining all the necessary approvals and trying to execute the transaction, it kept failing.

Each Safe has a list for the owners. It’s a linked list. That means that for each owner in the list, it points to the owner before them and the owner after.

So let’s say we have a safe with 4 owners, the list would look like this:
Owner 1: Address, link to owner 2, link to owner 4
Owner 2: Address, link to owner 1, link to owner 3
Owner 3: Address, link to owner 2, link to owner 4
Owner 4: Address, link to owner 3, link to owner 1

This means that any time we remove or add an owner to the list, we have to update the owner and owners around that owner. So if we wanted to change owner 3, the contract needs to update owner 2 and owner 4.

This is why each removal and add needs to be its own transaction, that needs to be executed before a new one is added.

We had no issues adding new signers, but we did face problems removing the former ones.

The Solution

The only way to resolve this issue was to remove the former signers one by one.

But this meant: creating the transaction, reaching the approval threshold, and executing the transaction. Once completed, the same steps had to be repeated over and over until all former signers were removed.

After coordinating among the ACC members, we successfully completed this task in a single session of approximately 20 minutes.

For transparency purposes, we are sharing the details of the transactions carried out during that session:

Trxs

OP Mainnet Transaction Hash (Txhash) Details | OP Mainnet Etherscan

Special thanks to @vonnie610 for helping me understand the problem and find the solution. Also, to all ACC members who contributed to making this process run smoothly.

Pumbi · March 20, 2025, 2:46pm

Updates - Voting Cycle #33

For this VC, no voting proposal was submitted, so there was no need for the ACC to participate.

Maintenance Upgrade: L1 Pectra Readiness

Pectra is an upgrade to the Ethereum protocol composed of Prague (Execution Layer) and Electra (Consensus Layer) which will activate soon on testnets and mainnet. It contains consensus changes which, by default, would cause all OP Stack chains to halt.
The expected outcome is that OP Stack chains continue to operate as before (they do not halt) when Pectra activates on their respective L1 chains. This is a critical piece of maintenance affecting all operators and users of OP Stack chains.

This was an optimistic approval proposal. This means that we only needed to vote if we were against the proposal.

The ACC held a vote on Snapshot to reach internal consensus on whether to vote against or abstain (thereby supporting the proposal). Unanimously, the members decided to abstain, thereby supporting this update due to the necessary improvements it implements.

The results of the Snapshot vote can be seen here.

Updates - Voting Cycle #34

For this cycle, the Commission was required to vote on the Upgrade Proposal #13: OPCM and Incident Response improvements.

Once again, the Commission conducted an internal vote on Snapshot to reach consensus on how to proceed. Unanimously, the members decided to vote in favor of the proposal, as it provides more robust incident response processes and technical improvements to contracts and their management. It also offers simplified processes, allows for smaller and more frequent upgrades, and enables more flexible and less disruptive ways to respond to potential incidents in the OP Stack fault proof system.

The results of the Snapshot vote can be seen here.

On Tuesday, March 18, we held our internal meeting for VC#34 to briefly review the protocol upgrade proposal and had a space to discuss various activities taking place within the Collective, as well as some adjustments to improve the Commission’s internal workflow.

A special thank you to all the members who joined and actively participate in all Commission activities.

The ACC successfully cast its vote, and the transaction can be found here: ACC Multisig TX#33

ACC · April 10, 2025, 2:33pm

Updates – Voting Cycle #35

For this cycle, the Commission was required to vote on two protocol upgrades: Upgrade Proposal #14: Isthmus L1 Contracts + MT-Cannon and Upgrade Proposal #15: Isthmus Hard Fork.

The ACC reached internal consensus by voting unanimously through proposals created on Snapshot.

You can find the links to the Snapshot votes here:

The transaction to vote through the ACC Safe was generated, reached the required signature threshold, and was successfully executed. The ACC’s vote was successfully cast.

The transactions can be found here:

Internal Process Improvements

A clearer timeline was set to streamline the process between the Snapshot vote, the ACC internal meeting, and the Safe vote, ensuring that voting happens after the internal meeting to allow time for any questions or concerns that may arise.

The ACC held its third internal meeting for VC#35 on Tuesday, April 8th. During the session, we provided a brief overview of the protocol upgrade proposals and took time to discuss different initiatives happening across the Collective. We also explored ideas to improve the Commission’s internal workflows and refine its mandate for future seasons.

We’re grateful to all members who showed up and continue to stay actively engaged in the Commission’s efforts.

ACC · July 9, 2025, 7:04pm

Hi Collective!
We wanted to share a quick update from the ACC to give the community more visibility into what we’ve been working on over the past few months:

Maintenance Upgrade: Absolute Prestate Updates for Isthmus Activation & Blob Preimage Fix

Although this proposal was Optimistically Approved, the ACC held a Snapshot vote to determine whether to support or oppose it.

The outcome was positive (no Safe trx was needed). We believe this Maintenance Upgrade is important as it sets the activation time for the Isthmus hard fork and includes a critical fix for the blob preimages bug.

Additionally, it did not introduce any new technical risks.

Governor Update Proposal: Removing Abstain Count from Quorum

This proposal outlines a targeted improvement to the Optimism Governor contract by removing Abstain votes from quorum calculations. The change resolves an edge case where Abstain votes could unintentionally reduce the vote threshold needed for proposals to pass.

This proposal sparked strong and divided opinions across the broader community (special thanks to Griff for raising an important point and kicking off a thoughtful discussion, which can be viewed here).

Interestingly, that level of debate didn’t surface within the ACC itself. There wasn’t a deep internal discussion on the proposal’s nuances.

The ACC held a Snapshot vote to decide whether to support or reject the proposal. The outcome was nearly unanimous in favor of supporting it, and the transaction was subsequently executed via Safe.

Upgrade 16 Proposal: Interop Contracts, Stage 1, and Go 1.23 Support in Cannon

This upgrade prepares for Superchain interop by including all of the smart contract changes required to support the interop launch date, though it does not turn interop on yet. The upgrade also increases OP Stack decentralization and security by removing a permissioned role and guaranteeing that the OP Stack continues to meet L2Beat’s updated Stage 1 criteria. Additionally, Upgrade 16 includes a number of maintenance features and improvements to the OP Stack experience.

The ACC held a Snapshot vote, and the result was unanimous in support of the proposal. It’s clear that we’re all eager for the arrival of Interop, which we hope will become a reality in the coming months.

Once the Snapshot vote concluded, we proceeded to execute the transaction via Safe.

Over the past few months, we also worked on a collaborative discussion document, which we shared on the forum a few weeks ago. In it, we explored potential paths forward for the ACC:

We also conducted a retrospective on the ACC’s participation during Season 7:

We’re grateful to all ACC members for their active participation throughout this season.

Topic		Replies	Views
The Future of the Anticapture Commission acc , season-7	6	295	June 29, 2025
Anticapture Commission - Season 6 Retrospective Council Communication Threads	4	227	December 5, 2024
Anticapture Commission - Season 7 Retrospective Council Communication Threads retrospective	4	152	June 17, 2025
Season 7 Anticapture Commission Charter Amendment Elected Representatives 💼 season-7	25	666	January 30, 2025
Anticapture Commission - S7 Internal Operating Procedures Internal Operating Procedures season-7	0	84	February 7, 2025