Happy new year!
Update on what we’ve been up to between October 2024 and December 2024.
Voting
Governor Update Proposal #3: Enable Onchain Treasury Execution - Voted FOR
We didn’t post a full rationale when we cast our vote, so we’re sharing it here instead.
Enabling onchain treasury execution is a significant first step towards greater decentralization and empowering the token house with greater control over the DAO’s treasury. Although the Foundation still retains control of submitting proposals, we believe it’s a reasonable middle-ground before enabling permissionless proposals from being submitted.
Having reviewed Trust’s audit, which didn’t highlight any critical errors, we were comfortable that the upgrade will not cause any issues.
Season 6: Standard Rollup Charter Ratification - Voted FOR
As with the vote above, we didn’t post our rationale when we cast our vote so we’re sharing it here.
The Standard Rollup Charter introduces a set of criteria that a Standard Rollup on the Superchain should adhere to, and ratifying it is sensible so we can all be on the same page regarding expectations.
However, there are some things that are left unaddressed, and we’re not sure what to expect. Specifically:
- There’s no mention of whether there’s going to be any sort of enforcement mechanism that the token or citizen’s house will control. As things are right now, we do not see an avenue for the Collective to enforce that chains adhere to the criteria set forward by the Standard Rollup Charter outline without having to involve the Foundation.
- What happens if the configuration of different parameters of the Standard Rollup Charter changes? For example, the
fault_dispute_gameversion is 1.3.1 at the time of writing this. If that is upgraded to, say, version 1.3.2, how will that value be upgraded? There’s a myriad questions that stem from this question, such as:- Who or how is the process started?
- Are the member chains expected to upgrade first, and then the registry is updated, or is it vice versa?
- Are all chains expected to upgrade their parameters at the same time? What is the timeline to do so?
- It is stated that in the event of sequencer censorship, the community can submit a vote to Optimism Governance to remove the Chain Governor as the
SystemConfiOwnerand appoint a new, non-censoring sequencer. Similar to the question above, that statement creates other questions that are not addressed:- Is anyone in the community able to do that or is that the responsibility of any particular actor(s)?
- At this time, the proposing function is permissioned and only the Foundation can propose things. So what does ‘submit a vote’ mean in this case?
- Can any sequencer nominate themselves to be appointed or are there criteria that need to be met beforehand?
- Lastly, as it’s written, the collective fee split is not supposed to be changed before December 2029. What happens after that date? Is it just that the ‘no amendments’ period expires, or is there a planned change that will occur at that time?
Rolling Mission Requests: Voting Cycle 28 - Voted FOR
We voted in favor of the mission request as we believe in the potential of local stablecoins to act as enablers for many crypto use-cases, particularly in non-EUR/USD economies.
Upgrade Proposal #11: Holocene Network Upgrade - Voted FOR
After reviewing the breakdown of the changes by the DAB and after having our research team look into them as well, we voted in favor of the proposal. We did agree with others in the thread, however, that we should reconsider the auditing policy for code upgrades going forward.
Season 7: Anticapture Commission Amendment - Voted FOR
Although the ACC wasn’t -thankfully- needed at any point, we do not see any valid reason to depreciate it. As a result, we voted in favor of renewing it for another season.
Code of Conduct Council Dissolution Proposal - Voted FOR
We voted in favor of dissolving the Code of Conduct as we believe it wasn’t as effective as we’d have hoped for. We do, however, see the need for an avenue to conflict resolution, and we believe we should revisit the idea of a CoC in the future.
Season 7: Intent Ratification - Voted FOR
We voted in favor of the Season 7 Intent Ratification but we expressed our view that the Collective should be more involved in the process of setting the intent, at least from the standpoint of feedback.
[Test Votes] Onchain Treasury Transfer + Cancellation
These were test votes for which there was no rationale necessary.
Discussion
Security Council — Season 6 Retrospective
In the Season 6 Retrospective of the Security Council, we offered our thoughts and feedback and provided some suggestions that could prove to be useful in the next Season(s).
Season 7 Budget Discussions
We (L2BEAT) hosted and facilitated 2 separate public calls to discuss the Season 7 budget proposals for the Grants Council, the Milestones and Metrics Council, the Developer Advisory Board, and the Security Council for Season 7. The calls were recorded and shared publicly for anyone who couldn’t attend.
L2BEAT’s Optimism Office Hours
We want to remind to everyone that in order to further our communication with our constituents and any interested party in the community, we’re hosting recurring Office Hours on Google Meets.
The office hours are held every Tuesday at 3 pm UTC/ 11 am EST
During Office Hours, you will be able to reach L2BEAT’s governance team, which consists of kaereste (Krzysztof Urbanski) and Sinkas (Anastassis Oikonomopoulos) and discuss our activity as delegates.
The purpose of the office hours is to gather feedback from the people who have delegated to us, answer any questions in regard to our voting activities and rationale, and collect input on things you’d like us to engage in discussions about.
You can add the L2BEAT Governance Calendar in your Google Calendar to find the respective Google Meets links for every call and to easily keep track of the Office Hours, as well as other important calls and events (e.g. voting deadlines) relevant to Optimism that L2BEAT governance team will be attending or hosting.