Skip to content
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

improve(OVM_SpokePool): Use bridgeERC20To to bridge native L2 tokens if admin decides to support them #520

Merged
merged 10 commits into from
Jun 17, 2024

Conversation

nicholaspai
Copy link
Member

bridgeERC20To can be used to bridge native L2 tokens (without L1 counterparts and specifically does not contain a l1Token() function in the L2 erc20 contract) if an L1 remote token is identified.

This call require the spoke pool to set an allowance on the standard bridge before calling bridgeERC20To

Will allow future OpStack chains to more easily inherit Ovm_SpokePool without having to modify `_bridgeTokensToHubPool` due to custom SNX logic
…if admin decides to support them

bridgeERC20To can be used to bridge native L2 tokens (without L1 counterparts and specifically does not contain a `l1Token()` function in the L2 erc20 contract) if an L1 remote token is identified.

This call require the spoke pool to set an allowance on the standard bridge before calling `bridgeERC20To`
… tokens if admin decides to support them"

This reverts commit 3d09986.
…2 tokens if admin decides to support them"

This reverts commit 4258fdd.
@nicholaspai nicholaspai requested review from mrice32, bmzig and pxrl June 14, 2024 18:05
contracts/Ovm_SpokePool.sol Outdated Show resolved Hide resolved
@nicholaspai nicholaspai changed the base branch from 0624-oz/n04 to master June 17, 2024 19:21
@nicholaspai nicholaspai merged commit 5dd59aa into master Jun 17, 2024
7 checks passed
@nicholaspai nicholaspai deleted the 0624oz/l04-2 branch June 17, 2024 19:25
nicholaspai added a commit that referenced this pull request Jun 17, 2024
nicholaspai added a commit that referenced this pull request Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants