Is the force inclusion mechanism possible on any Orbit Chain?

DAO Programs & Initiatives
1

This was a question we asked ourselves and set out to solve, which led us to begin this work.

TL;DR:

In this thread, we’ll share our progress on building a tool that keeps transactions running, even if the sequencer misbehaves on any Orbit Chain.

ARB L3
ARB L31200×627 12.3 KB

WakeUp Labs developed Arbitrum Connect ( https://www.arbitrumconnect.xyz/ ), a tool designed to keep transactions running smoothly on Arbitrum L2 even when the sequencer misbehaves. For instance, users could still submit critical transactions directly to Ethereum L1, ensuring business continuity and avoiding disruptions.

We checked that it works perfectly for the Arbitrum <> Ethereum network, and now we are advancing to address a new challenge: Orbit Chains. We’re creating a system that ensures transactions can still be processed when the sequencer of the Orbit Chains experiences misbehaves. This new solution leverages a feature called the Delayed Inbox, which acts as a fallback mechanism to handle transactions during sequencer downtime. It allows users to submit transactions to the previous layer (if the user is on L3, it goes to L2; if on L2, it goes to L1), ensuring uninterrupted operations for both L2 and L3 Orbit Chains.

:globe_with_meridians: Why Orbit Chains?

Orbit Chains empower developers to build their own Layer 2 or Layer 3 chains using the Arbitrum stack. By incorporating reliable transaction tools, we aim to make these chains more secure for end users.

What’s next?

Follow along as we continue this journey, collaborating with the Arbitrum DAO and the broader community to bring this vision to life.

2 Likes
2

Milestone #1 Achieved: Research Update on Orbit Chains Forced Inclusion

TL;DR:

We’ve completed Milestone #1. This milestone focused on researching Force-Inclusion mechanisms and laying the groundwork for our development.

Key Points from the Research

  • Conducted an in-depth analysis of the Orbit Chain stack to identify its strengths and weaknesses.
  • Researched Delayed Inbox mechanisms to improve transaction handling during misbehaviors.
  • Produced detailed documentation to help developers implement these tools effectively.
  • Partnered with Arbitrum DAO and other ecosystem collaborators to plan the next phases.

:link: Explore the full research here: Research Document

Building on the foundation of Arbitrum Connect, this milestone marks significant progress in making Orbit Chains more resilient. We invite developers and community members to review our findings and contribute to the discussion.

What’s next?

With the completion of Milestone #1, our next steps include designing and implementing the Force-Inclusion mechanisms based on the insights gathered during the research. This involves:

  • Test the Force-Inclusion features on different types of Orbit Chains.
  • Updating the user interface to make popular Orbit Chains easily accessible.
  • Creating a back-end system to store and manage custom Orbit Chains for users.
  • Documenting the entire process, including solutions and challenges encountered during development.

Stay tuned as we transition from research to implementation.

Twitter

https://x.com/wakeuplabs

Linkedin

https://www.linkedin.com/company/wakeuplabs