Skip to content

feat: ERC20MigrationOutbox #339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 10 commits into
base: develop
Choose a base branch
from
Open

feat: ERC20MigrationOutbox #339

wants to merge 10 commits into from

Conversation

gzeoneth
Copy link
Member

@gzeoneth gzeoneth commented May 6, 2025

ERC20MigrationOutbox

Overview

This PR introduces the ERC20MigrationOutbox contract, a new component designed to facilitate the migration of native tokens from the Arbitrum bridge to an external bridge on custom fee token orbit chains.

Purpose

Some custom fee token orbit chains may want to have their native token managed by an external bridge rather than the built-in native bridge. This contract enables permissionless migration of native bridge collateral without requiring changes to the vanilla outbox implementation, while also preserving the message passing and deposit functionality of the native bridge.

Technical Requirements

  • Must be allowed as an outbox in conjunction with the vanilla outbox contract
  • Nonzero value withdrawals via the native bridge (ArbSys) must be disabled on the child chain to prevent funds and messages from being stuck as the native bridge will not hold collaterals

Resolves BLK-336

@gzeoneth gzeoneth requested review from godzillaba and TucksonDev May 6, 2025 11:32
@cla-bot cla-bot bot added the s label May 6, 2025
godzillaba
godzillaba previously approved these changes May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants