We vote FOR the proposal on Tally because we believe it’s important to provide a non-developer friendly UI to force transaction inclusions possibly regardless of sequencer being down or not for less trust assumptions.
1 Like
We previously voted FOR this proposal at the Snapshot stage, and we maintain our support in this on-chain vote.
The key reasons we believe this proposal deserves support are:
- Empowering users to force-include transactions during sequencer downtime enhances Arbitrum’s resilience and aligns with the goals of decentralization.
- Providing a user-friendly interface for this capability improves accessibility for non-technical users.
- The open-source approach enables other teams to run their own instances, strengthening the solution’s availability.
- The team has relevant expertise and is committed to maintaining the service post-launch.
- The cost and timeline seem reasonable for the scope of work.
While there may still be some open questions around edge cases and specific implementation details, overall this proposal tackles an important issue in a practical, user-centric way.
Therefore, on behalf of the Arbitrum delegators who entrusted us with their voting power, we are voting FOR.
1 Like
Savvy DAO has voted FOR this proposal.
See the voting rationale here:
1 Like
A cheap price to pay for such an important decentralization step. One day, we won’t need it and we’ll be able to interface with a decentralized sequencer, but for the moment, this is very important to the DAO.
1 Like
The following 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’re voting for this proposal as we did during the temp check, with our rationale remaining the same. We appreciate @Gonzacolo’s responsiveness to feedback both from us and also from other delegates and his persistence to move this proposal forward.
OpenZeppelin, in the context of ARDC, has performed a security analysis of the executable of the proposal, and they noted that they do not anticipate any issues with its execution.
(Please note that the security analysis was conducted on the associated executable of the on-chain vote, which refers to the movement of funds from the DAO’s treasury to the Hedgey contracts and the function of the Hedgey contracts afterward - it’s not an analysis of the contents of the proposal).
2 Likes
Voting FOR also on the onchain voting, with the same rationale expressed before.
Good progress on this.
1 Like
By developing a user-friendly interface that enables direct L1 transaction submissions during Sequencer downtimes, the proposal addresses a critical vulnerability in the Arbitrum network.
With a proven track record in blockchain infrastructure, WakeUp Labs guarantees a robust, open-source solution that other teams can deploy independently, further strengthening the network’s reliability and trustless security. This initiative is crucial for maintaining operational integrity and user autonomy.
1 Like
DAOplomats voted in favor on Tally.
We weren’t able to vote on this proposal during the temp check but we were happy to support it during the onchain vote. Enabling this interface to force transactions during downtime is super important and the compensation requested is reasonable.
Just to add, once this goes live, it will be nice to see some educational contents to inform users about the benefits and its operations.
1 Like
Although PBC missed the onchain vote due to a scheduling issue, we’d like to reiterate our support for the proposal. We supported it in the Snapshot phase (as we believe making force-inclusion significantly more accessible is important for maintaining Arbitrum’s lead on decentralization), and would’ve supported it onchain as well!
1 Like
For tracking purposes: I voted for on this proposal, as I believe that this is a much-needed tool to ensure that users can continue to broadcast their transactions.
2 Likes
Updates about this proposal, which I’ll explain tomorrow in the bi-weekly open governance call, will be shared openly in this forum thread.
WakeUp Labs: Front-end interface to force transaction inclusion during sequencer downtime
1 Like