Security Council — Season 6 Retrospective

[Alisha]

Hi @kaereste and @Sinkas. I appreciate your response and am looking forward to being able to cover my replies in more details in upcoming calls.

@kaereste

no one is explicitly responsible for validating the contents of proposed upgrades within the Security Council

1. For each upgrade, the Security Council simulates and verifies the contents of the proposed upgrades. Here is an example of the a signing ceremony used by the SC. Please let me know if your expectation is that someone within OP governance (or whether the SC specifically) should be validating the contents of proposed upgrades over and above this level.

@kaereste

the exact calldata of the upgrade that the Security Council is signing is known only to the Security Council

2. This is a great point. The Security Council is excited to support OP Labs over the coming months in it’s work to revise the process for signing upgrades, so call data is public and can be verified by anyone. This is obviously a preferred path forward in terms of both security and transparency.

@kaereste

We would like to highly encourage enabling participation as a multisig as this allows for much better operational management and security of this role.

3. Another great point. The inclusion of multisigs adds a meaningful level of complexity to tooling development. Up to now, the Security Council has been reliant on OP Labs to develop such tooling. In the Season 7 Security Council Budget has requested OP for an Infrastructure and Experiments category and specifically included R&D related to multisig tooling within that category.

@kaereste

the Security Council fully relies on OP Labs and/or Foundation to serve this role, as individual Security Council participants are not expected to run their own system monitoring tools.

4. An area of focus in the Season 7 budget is putting monitoring tools in place so that the Security Council is able to independently carry out its responsibility as a Challenger.

@kaereste

the Github repository mixes the contracts that are being verified with the code being executed while verifying/signing

5. This consideration will certainly impact the work being done on revising the superchain-ops repo. I will tag @mds1 here to confirm visibility to OP Labs, who will be leading this work.

@kaereste

the Token House might be simply forced to accept any budget that SC proposes as the situation in which SC does not have any approved budget is an existential threat to the whole ecosystem.

6. I believe in the ability of the Security Council to be responsive to any concerns related to its operating budget in a given Season, so that the Token House doesn’t feel it is effectively held hostage by the SC. The Security Council is very open to feedback on the Season 7 budget from Delegates in the week ahead of voting. I am looking forward to participating in public calls related to council budgets over the next week.