forked from across-protocol/relayer
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(generic bridges): use scroll's canonical bridge function (across-…
…protocol#1708) Fix Scroll cross-chain adapters: - Use the native ERC20 bridge for WETH, rather than the AtomicWethDepositor. - Correct the gateways used for USDC transfer tracking. - Add Scroll tests. - Fix an issue in the new Arbitrum cross-chain adapter. This new adapter is not active in prod yet. --------- Signed-off-by: bennett <[email protected]>
- Loading branch information
1 parent
5b0b852
commit d57c91e
Showing
16 changed files
with
413 additions
and
368 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
// This file emulates a Scroll ERC20 Gateway. For testing, it is used as both the L1 and L2 bridge contract. | ||
|
||
pragma solidity ^0.8.0; | ||
|
||
contract ScrollBridge { | ||
event DepositERC20( | ||
address indexed l1Token, | ||
address indexed l2Token, | ||
address indexed from, | ||
address to, | ||
uint256 amount, | ||
bytes data | ||
); | ||
event FinalizeDepositERC20( | ||
address indexed l1Token, | ||
address indexed l2Token, | ||
address indexed from, | ||
address to, | ||
uint256 amount, | ||
bytes data | ||
); | ||
|
||
function deposit(address l1Token, address l2Token, address from, address to, uint256 amount) public { | ||
emit DepositERC20(l1Token, l2Token, from, to, amount, new bytes(0)); | ||
} | ||
|
||
function finalize(address l1Token, address l2Token, address from, address to, uint256 amount) public { | ||
emit FinalizeDepositERC20(l1Token, l2Token, from, to, amount, new bytes(0)); | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.