What happens if the sequencer fails, and how are risks mitigated?

In case of sequencer failures, there are risk mitigation measures in place:

• Forced Batches: These are designed as a backup mechanism to bypass the sequencers. If the primary system (sequencer) misses or neglects a transaction, forced batches ensure that the transaction still gets processed. It can be pushed onto the blockchain using forced batches.

• Current Status: During the initial phase of the Mainnet Beta Launch, users may not immediately push transactions to Ethereum Layer 1 (L1). However, it's part of our plan to enable this functionality approximately one month after the launch. Initially, it will be available on the ongoing testnet, followed by the mainnet.

• Why the Delay?: While the feature is already prepared in our code, we are conducting thorough safety checks to prevent any issues when it goes live. Ensuring a smooth experience is our top priority.

• Timeline: Regarding the timeline for the Polygon zkEVM roadmap and the L2Beat risk circle, we do have plans in place, but we cannot provide exact dates at this moment. Our current focus is on refining and perfecting all aspects of the system.

Future Upgrades: We are actively planning upgrades that will allow users to push their transactions, especially in the event of a system failure. More specific details will be available after certain governance decisions are made.