Proposal Title: User-Friendly Scroll Bridge UI with Force Transaction Feature
Proposal Type: Technical Contributions
Authors: WakeUp Labs
Overview
This proposal by WakeUp Labs requests funding to develop an open-source, user-friendly Scroll bridge interface. It will serve as both a reliable alternative to the official UI and a fallback that allows users to force-include transactions on Ethereum in the event of sequencer downtime or misbehavior. The project will also include comprehensive documentation to support both technical and non-technical users.
This community-maintained interface will strengthen decentralization, protect user access, and build on recent developments like Euclid, positioning Scroll as the only ZK rollup with an accessible force transaction feature.
Summary
WakeUp Labs seeks funding to build, maintain, and host a user-friendly front-end interface for the Scroll bridge with two core goals:
-
Provide an alternative to the official Scroll bridge UI.
-
Offer a fallback path to force-include transactions on Ethereum when the sequencer is down or behaving maliciously.
The interface will be open source and will not charge additional fees beyond those imposed by Scroll’s official bridge smart contracts. It aims to offer a secure, community-driven, and easy-to-use alternative, ensuring accessibility and resilience for all users.
Technically, the UI will rely entirely on Scroll’s official smart contracts. Extensive documentation will be created to serve both technical and non-technical users, promoting transparency and user confidence.
Total budget: ≈ 232,408 SCR (~$85,200)
-
≈199,675 SCR (~$73,200) for development
-
≈32,733 SCR (~$12,000) for one year of hosting and maintenance
Motivation
WakeUp Labs is a boutique Web3 product studio with 16 engineers based in Argentina. Since 2022, we’ve built and maintained zero-knowledge Layer-2 tooling and on-chain governance products. Past work includes:
-
Velora Rewards Distribution: Automated token distributions, removing multisig bottlenecks. [Blog]
-
Arbitrum Force-Include dApp: Enables users to push transactions when the Arbitrum sequencer is offline. [Blog]
-
ZK Identity Toolkit (Optimism): Credential SDK and admin UI using ZK circuits.
[GitHub] -
Sandbox DAO - UGC Platform: Creator-first experience searcher platform [Blog]
We have been closely following the evolution of Scroll and have found an active community we’re eager to engage with and contribute to by leveraging our technical expertise. We’ve been in contact with several delegates, discussing recent protocol upgrades and exploring how we can add meaningful value to the ecosystem.
Upgrades like Euclid have positioned Scroll as the first ZK-rollup to achieve and maintain Stage 1 status within the L2Beat framework, adapting to evolving requirements. Similarly, the Feynman upgrade addressed technical debt while significantly lowering transaction costs—successfully combining the end-game security of ZK-proofs with affordable transactions.
With these strong technical foundations now in place, we believe it’s time for the Scroll community to play a more active role in shaping the protocol’s direction. That includes improving user experience, building and positioning new tooling, and taking full advantage of current and upcoming infrastructure.
As advocates of true decentralization, we at WakeUp Labs believe that in mature ecosystems, essential protocol interfaces should be hosted and maintained by the community. This model allows Core Teams to focus on broader priorities while ensuring that key tools like the Scroll bridge remain open, reliable, and free of any fees beyond standard gas costs.
The interface we’re proposing directly addresses a current gap in the Scroll ecosystem. Achieving Stage 1 on L2Beat reflects substantial technical progress, but it must also translate into practical user benefits. One of those is the ability to withdraw funds from Scroll to Ethereum through a force-inclusion mechanism during sequencer downtime or misbehavior. For this to be truly effective, it must be paired with a simple and intuitive interface that everyday users can rely on when it matters most.
Adding force transaction support to the proposed interface enhances user security by providing an additional safeguard against censorship or downtime, further establishing Scroll as a truly censorship-resistant ZK-rollup.
We have no conflicts of interest with Scroll or other projects. While we’ve delivered similar solutions in other ecosystems, this does not create competition—rather, it demonstrates our capacity and motivation to contribute meaningfully to Scroll’s continued growth.
Finally, we hope this proposal sparks broader conversations around community priorities and how we can best support Scroll’s evolution by putting our expertise to work for the ecosystem and its delegates.
Execution Plan & Use Case
WakeUp Labs will lead development using modern, reliable infrastructure (AWS, Next.js, Node.js, React, Solidity, NOIR, etc.). A project manager will coordinate work, assign tasks, and communicate regularly with the community to ensure the product meets Scroll’s needs.
Front-End Interface Use Case
The interface will function in the same way as the official Scroll bridge. The user selects the source and destination chains, currently Ethereum ↔ Scroll. They will be able to track the transaction status until it is ready to be claimed on the destination chain. If the transaction fails, the user is redirected to the Force Inclusion flow.
This development will be supported by extensive documentation, a user-friendly experience, and the endorsement of the DAO.
The expectations are:
- The solution link will be shared through the Scroll documentation (User: Bridge User Guide and Developers: L1–L2 Bridging), together with its rationale, and listed as a new option in Scroll Bridges via an href/link.
- In the future, if both the community and the Scroll core team wish, this community-driven contribution could replace the official bridge, currently funded, maintained, and operated by Scroll.
- It will meet the necessary standards for force-including transactions, serving as a community solution in cases of censorship or sequencer misbehaviour.
Force Inclusion Flow
Due to Metamask’s and other popular wallets’ security restrictions, Force Inclusion must be executed directly from the user’s console. To make this accessible, the solution will provide:
-
A step-by-step guide on the project’s website and in the open-source GitHub repository.
-
The page will automatically detect censorship (when a user cannot normally execute a transaction) and redirect them to the Force Inclusion path.
-
This path will guide the user through installing the required tools (npm, Node.js, etc.), opening their console, and following instructions to deposit or withdraw funds.
-
Even though the use of the console may seem to require some technical background, the process will be designed to remain intuitive. As the project will be open source, any sensitive inputs (e.g., private keys) will be encrypted to prevent exposure—even in cases where the user’s computer may be vulnerable. This model has already been proven effective in other ecosystems.
-
After completing the Force Inclusion, the user can return to the UI to track their transaction in the standard way.
Outcome: The user successfully retrieves their funds outside the chain, free from censorship, under any circumstance.
No Additional Fees
No fees will be charged for using this solution. It is a community contribution funded by the DAO and not intended as a monetized product. The only fees incurred will be those charged by the official Scroll bridge, if any. Metrics may not always be entirely precise, as funds will flow through both the official bridge and this interface, but both rely on the same underlying smart contracts.
Transparency and Tracking
We commit to providing full accountability for the entire development process. At a minimum, this will include an update thread on the Scroll forum, documenting step by step the tasks being completed. This means that whenever a milestone is closed, a blocker arises during the process, or an expected result is achieved, we will communicate it to the community.
Alongside forum updates, social media posts will be published from the WakeUp Labs’ account to keep the community informed of the progress while also generating some traction (although that is not the primary goal).
This commitment also aims to showcase this development as another product in which we have collaborated. We are bound by the commitment to ensure that anyone who wishes to reach out, provide feedback, or get involved in tracking the process will have room to do so.
In the past, we have shown the ability to maintain clear and transparent communication with the community, even when facing complex technical challenges.
Therefore, additional deliverables to the interface will also include:
-
Guides and demos explaining the logic and rationale behind the chosen technical approach.
-
Wireframes, flow diagrams, an open-source repository, and any other resources needed for a thorough technical understanding.
-
A final project demo showcasing the use case.
Team & Resources
-
1 Project Manager (PM): Serves as the visible face of the project, coordinates directly with the Scroll community, ensures tasks run smoothly, and oversees the overall process.
-
1 Technical Lead (TL): Provides protocol research, validates the technical approach, builds small proof-of-concepts, assists in system architecture, and ensures the documentation meets high standards.
-
1 Designer (UI/UX): Focuses on creating a user-friendly and intuitive interface.
-
1 Sr Developer: Works alongside the TL to implement the technical solution and deliver the product.
While no additional resources are strictly required, maintaining direct communication with the Scroll technical team or DAO contributors would be extremely valuable to validate certain aspects during development.
Timeline & Budget
The project is expected to run for 3 months, divided into two phases:
-
Phase 1 (1 month): Focus on project scope, solution design and wireframes definition. During this stage, the Designer and the Technical Lead will work full-time, while the Project Manager (PM) contributes part-time.
-
Phase 2 (2 months): Implementation and refinement. The TL continues full-time, a Sr Developer joins full-time, and the PM remains part-time to support coordination and communication with the Scroll community.
Development Budget:
-
Designer (1 month, full-time @ $35/hr): $5,600
-
Project Manager (3 months part-time @ $65/hr): $15,600
-
Technical Lead (3 months full-time @ $75/hr): $36,000
-
Sr Developer (2 months, full-time @ $50/hr): $16,000
Total Development Budget: $73,200 USD
Long-term Maintenance Commitment
WakeUp Labs commits to running, hosting, and maintaining the application for 2 years after delivery. This includes handling minor UI adjustments and user feedback when necessary.
-
Year-1 maintenance will be fixed at $1,000 USD per month, covering 12h/week of developer time, hosting, monitoring, and bug fixes. Starting in Year 2, WakeUp will cover the costs of hosting and maintenance as a commitment to the ecosystem.
-
WakeUp Labs will absorb any additional costs beyond this amount to maintain long-term reliability.
The total budget for the project is: $73,200 + $12,000 = $85,200
Evaluation
The desired outcomes of this proposal can be divided into two sections. From an ecosystem perspective, the expected outcomes can be summarised as follows:
-
Presenting the first technical proposal from the community, encouraging everyone to contribute from this point onwards; and
-
Kicking off a transition to an ecosystem where key tools are developed, owned, and maintained by the community and/or the DAO.
Meanwhile, from a technical standpoint, with this proposal, we expect to:
-
Provide users with an alternative interface to use Scroll’s official bridge smart contracts; and
-
Allow anyone to access a user-friendly alternative to force-include transactions from Scroll to Ethereum.
While the first two outcomes can certainly open up a new avenue for innovation and further develop Scroll from a technical and tooling perspective, the technical outcomes of this proposal would contribute to making Scroll more accessible for everyday users. This directly supports the inclusivity that this ecosystem has promoted from its very first day. Moreover, thinking about the future, if this new interface is implemented, it would serve as a revamp of Scroll’s official bridge smart contracts. This would bring the opportunity to launch bridge fee subsidy campaigns to onboard new users to the Scroll ecosystem.
Conclusion
We believe this is the ideal time for Scroll to take this step. After the remarkable achievement of becoming the first ZK rollup to reach Stage 1 within the L2Beat framework, it is now time to give users a straightforward way to fully utilise these advanced features. By providing a community-driven interface that enables force inclusion, Scroll would strengthen its position as the only ZK chain with this capability while safeguarding individual users against sequencer misbehaviour or downtime.
This initiative will also open the door for contributors to collaborate directly with Scroll in a meaningful way. By entrusting bridge interface maintenance to an independent, motivated technical team, the Core Team can focus on higher-level priorities while the DAO gains a reliable solution built around transparency and decentralisation.
Hopefully, this proposal is the start of a long-term relationship, where we can continue to bring expertise and innovation that benefits both Scroll and its users. In addition to that point, the solution aligns perfectly with the broader industry trend toward abstraction and inclusivity, one of Scroll’s core values. A comprehensive bridge with built-in force transaction support not only makes Scroll’s unique capabilities accessible but also creates opportunities for growth, community engagement, and campaigns that attract more users to the ecosystem.
For all these reasons, we expect the DAO and delegates to support this proposal as a way to reinforce Scroll’s leadership, deepen decentralisation, and establish a long-term partnership that delivers ongoing value.