Jess

Jess

Jess

Comms at WakeUp Labs.

Comms at WakeUp Labs.

Comms at WakeUp Labs.

June 17, 2024

June 17, 2024

June 17, 2024

Empowering the Arbitrum Ecosystem: WakeUp Labs' Proposal

Empowering the Arbitrum Ecosystem: WakeUp Labs' Proposal

Empowering the Arbitrum Ecosystem: WakeUp Labs' Proposal

Lately, we proposed creating an interface that allows users to push transactions through even when the Arbitrum sequencer is offline. After posting our proposal on Tally, we were chosen to develop it with support from the Arbitrum community for WakeUp Labs to take on this project. Want to learn more? Dive into the details here!

Lately, we proposed creating an interface that allows users to push transactions through even when the Arbitrum sequencer is offline. After posting our proposal on Tally, we were chosen to develop it with support from the Arbitrum community for WakeUp Labs to take on this project. Want to learn more? Dive into the details here!

Lately, we proposed creating an interface that allows users to push transactions through even when the Arbitrum sequencer is offline. After posting our proposal on Tally, we were chosen to develop it with support from the Arbitrum community for WakeUp Labs to take on this project. Want to learn more? Dive into the details here!

The problem.

The Arbitrum Sequencer plays a vital role in the Arbitrum network, handling users' transaction submissions to L1.

But here's the catch: it's a potential single point of failure. If something goes wrong with the Sequencer, transactions could be delayed or even blocked.

Sure, there are workarounds, but they're not exactly user-friendly. 


The proposal.

That's where our proposal at WakeUp comes in. We want to make things safer and easier by offering an alternative pathway for submitting transactions. This not only boosts the network's resilience but also gives users more control and confidence in the Arbitrum ecosystem.

But here's the kicker: for this to really work in a worst-case scenario, we need more teams to be able to set up their own versions. That's why we're all about embracing an OpenSource approach from day one. It's all about making the project more reliable and valuable to the Arbitrum community.

We're all about boosting decentralization, giving users more power, and ensuring trustless security on Arbitrum's Network. By letting users submit transactions directly to L1, they can bypass Sequencer issues or censorship, keeping their ability to make transactions uninterrupted. Plus, it makes sure that the Arbitrum Rollup stays true to its trustless security model, even if certain parts of the system aren't working right.



Arbitrum’s Forum

Last February, we submitted a proposal to the Arbitrum Foundation Forum. It garnered considerable attention, with numerous exchanges and suggestions from community members that helped us improve our proposal with their feedback. This was done to assess the sentiment related to our proposal and to enhance it based on community feedback.

You can check the full proposal here 👇

https://bit.ly/Arbitrum_WU

We've also held an open call to discuss and share all the insights of our proposal to Arbitrum in a meeting 👇 


Later on, we conducted a successful snapshot sentiment check.

👉 https://bit.ly/Sentiment_Check_ARB


With over 99M votes in favor and less than 1% against.


The Tally formal proposal

To move forward, we posted our proposal on the Tally platform. After giving Arbitrum members time to vote on its value to the community, we were selected to develop the interface.

👉 https://bit.ly/Arbitrum_WUproposal


Conclusions

Developing a front-end interface to facilitate force-including transactions during Sequencer downtime is a vital necessity within the Arbitrum ecosystem. This development will empower users by guaranteeing transaction functionality even in the absence of the Sequencer. By doing this, it aligns with Arbitrum's objectives of decentralization and improving user autonomy.


This achievement wouldn’t have been possible without the support of the active participants in Arbitrum governance, who helped shape the initiative from the very beginning.

Special thanks to @Cattin0x from @SeedGov for suggesting ideas, debating them, and always being willing to discuss.

To @Sinkas_ from @l2beat, whose office hours ensured our proposal aligned with the goals of the DAO and the Arbitrum Ethos.

To @raamcc for being open to conversations from the moment this proposal was just a concept.

And to @0xFrisson for his advice on everything related to @Tally.



Thank you! 🤗



Follow us on X (Twitter) and LinkedIn to stay updated with the latest news about WakeUp! ✨

The problem.

The Arbitrum Sequencer plays a vital role in the Arbitrum network, handling users' transaction submissions to L1.

But here's the catch: it's a potential single point of failure. If something goes wrong with the Sequencer, transactions could be delayed or even blocked.

Sure, there are workarounds, but they're not exactly user-friendly. 


The proposal.

That's where our proposal at WakeUp comes in. We want to make things safer and easier by offering an alternative pathway for submitting transactions. This not only boosts the network's resilience but also gives users more control and confidence in the Arbitrum ecosystem.

But here's the kicker: for this to really work in a worst-case scenario, we need more teams to be able to set up their own versions. That's why we're all about embracing an OpenSource approach from day one. It's all about making the project more reliable and valuable to the Arbitrum community.

We're all about boosting decentralization, giving users more power, and ensuring trustless security on Arbitrum's Network. By letting users submit transactions directly to L1, they can bypass Sequencer issues or censorship, keeping their ability to make transactions uninterrupted. Plus, it makes sure that the Arbitrum Rollup stays true to its trustless security model, even if certain parts of the system aren't working right.



Arbitrum’s Forum

Last February, we submitted a proposal to the Arbitrum Foundation Forum. It garnered considerable attention, with numerous exchanges and suggestions from community members that helped us improve our proposal with their feedback. This was done to assess the sentiment related to our proposal and to enhance it based on community feedback.

You can check the full proposal here 👇

https://bit.ly/Arbitrum_WU

We've also held an open call to discuss and share all the insights of our proposal to Arbitrum in a meeting 👇 


Later on, we conducted a successful snapshot sentiment check.

👉 https://bit.ly/Sentiment_Check_ARB


With over 99M votes in favor and less than 1% against.


The Tally formal proposal

To move forward, we posted our proposal on the Tally platform. After giving Arbitrum members time to vote on its value to the community, we were selected to develop the interface.

👉 https://bit.ly/Arbitrum_WUproposal


Conclusions

Developing a front-end interface to facilitate force-including transactions during Sequencer downtime is a vital necessity within the Arbitrum ecosystem. This development will empower users by guaranteeing transaction functionality even in the absence of the Sequencer. By doing this, it aligns with Arbitrum's objectives of decentralization and improving user autonomy.


This achievement wouldn’t have been possible without the support of the active participants in Arbitrum governance, who helped shape the initiative from the very beginning.

Special thanks to @Cattin0x from @SeedGov for suggesting ideas, debating them, and always being willing to discuss.

To @Sinkas_ from @l2beat, whose office hours ensured our proposal aligned with the goals of the DAO and the Arbitrum Ethos.

To @raamcc for being open to conversations from the moment this proposal was just a concept.

And to @0xFrisson for his advice on everything related to @Tally.



Thank you! 🤗



Follow us on X (Twitter) and LinkedIn to stay updated with the latest news about WakeUp! ✨

The problem.

The Arbitrum Sequencer plays a vital role in the Arbitrum network, handling users' transaction submissions to L1.

But here's the catch: it's a potential single point of failure. If something goes wrong with the Sequencer, transactions could be delayed or even blocked.

Sure, there are workarounds, but they're not exactly user-friendly. 


The proposal.

That's where our proposal at WakeUp comes in. We want to make things safer and easier by offering an alternative pathway for submitting transactions. This not only boosts the network's resilience but also gives users more control and confidence in the Arbitrum ecosystem.

But here's the kicker: for this to really work in a worst-case scenario, we need more teams to be able to set up their own versions. That's why we're all about embracing an OpenSource approach from day one. It's all about making the project more reliable and valuable to the Arbitrum community.

We're all about boosting decentralization, giving users more power, and ensuring trustless security on Arbitrum's Network. By letting users submit transactions directly to L1, they can bypass Sequencer issues or censorship, keeping their ability to make transactions uninterrupted. Plus, it makes sure that the Arbitrum Rollup stays true to its trustless security model, even if certain parts of the system aren't working right.



Arbitrum’s Forum

Last February, we submitted a proposal to the Arbitrum Foundation Forum. It garnered considerable attention, with numerous exchanges and suggestions from community members that helped us improve our proposal with their feedback. This was done to assess the sentiment related to our proposal and to enhance it based on community feedback.

You can check the full proposal here 👇

https://bit.ly/Arbitrum_WU

We've also held an open call to discuss and share all the insights of our proposal to Arbitrum in a meeting 👇 


Later on, we conducted a successful snapshot sentiment check.

👉 https://bit.ly/Sentiment_Check_ARB


With over 99M votes in favor and less than 1% against.


The Tally formal proposal

To move forward, we posted our proposal on the Tally platform. After giving Arbitrum members time to vote on its value to the community, we were selected to develop the interface.

👉 https://bit.ly/Arbitrum_WUproposal


Conclusions

Developing a front-end interface to facilitate force-including transactions during Sequencer downtime is a vital necessity within the Arbitrum ecosystem. This development will empower users by guaranteeing transaction functionality even in the absence of the Sequencer. By doing this, it aligns with Arbitrum's objectives of decentralization and improving user autonomy.


This achievement wouldn’t have been possible without the support of the active participants in Arbitrum governance, who helped shape the initiative from the very beginning.

Special thanks to @Cattin0x from @SeedGov for suggesting ideas, debating them, and always being willing to discuss.

To @Sinkas_ from @l2beat, whose office hours ensured our proposal aligned with the goals of the DAO and the Arbitrum Ethos.

To @raamcc for being open to conversations from the moment this proposal was just a concept.

And to @0xFrisson for his advice on everything related to @Tally.



Thank you! 🤗



Follow us on X (Twitter) and LinkedIn to stay updated with the latest news about WakeUp! ✨