The below response reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
We value the enthusiastic approach Event Horizon has towards governance experimentation with novel approaches. While we’re not entirely sure of the impact such an experiment is going to have, we’ll be voting in favor of the proposal during the temp check because we’re interested in seeing its potential.
We see this whole proposal as an experiment and we want to treat it as such, both in theory and, more importantly, in practice. Instead of just implementing the proposal, letting it run its course, and then coming back to review what was done, we want the DAO to follow along and help Event Horizon iterate where and if needed.
While the people participating in the voter’s block are the ones who decide how the franchiser will vote, the DAO should be in charge of how the experiment is driven forward. To that end, we want to ask Event Horizon to set up a monthly call where they’ll provide a quick update on how the experiment is going and discuss with delegates on how the experiment should proceed.
On another note, as the DAO Advocate for the ARDC, we’ll be assigning the security member of the ARDC to review and assess the possible technical risks associated with implementing the proposal before it moves to an on-chain vote.
Lastly, in a previous comment, we suggested (and 404DAO shared the concern) not having the delegation be optimistically extended past the proposed timeline and instead holding another vote to decide whether to continue or not. While we understand Event Horizon’s hesitation to go through the entire governance process to continue the delegation, we believe it’s important for the DAO to ratify or veto the continuation formally. That’s why we’re declaring already that we’ll put up a snapshot vote at the end of the proposed timeline to ratify the continuation of this program.