You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it would be good to be able to bridge tokens from the sequencer to the evm which are represented as ERC20s (or some other non-native token), as currently, bridged funds are minted as the native token.
considerations:
gas cost (paid on the l2 from the sender's account? what if they have no native token?)
how does the rollup know the contract/methods associated with the bridged asset? how does mint permissioning work for a bridged token?
The text was updated successfully, but these errors were encountered:
## Summary
implement withdrawals of ERC20 tokens that are of type
`AstriaBridgeableERC20` (see implemented contract).
## Background
we want to be able to withdraw ERC20 tokens that are bridged to a
rollup.
## Changes
- implement `AstriaBridgeableERC20` which is a standard `ERC20` contract
with additional functionality for minting (not used by the withdrawer,
implemented/tested here
astriaorg/astria-geth#20) as well as
functionality for withdrawing
- implement `IAstriaWithdrawer` which is implemented by both
`AstriaWithdrawer` and `AstriaMintableERC20`.
- the withdrawer now interacts with a `IAstriaWithdrawer`. both native
assets and ERC20 withdrawals have the same event signatures, so no
additional code was needed for the withdrawer itself.
- to use the withdrawer with an `AstriaBridgeableERC20`, the
`ASTRIA_BRIDGE_WITHDRAWER_ETHEREUM_CONTRACT_ADDRESS` is set to some
`AstriaMintableERC20`, and
`ASTRIA_BRIDGE_WITHDRAWER_ROLLUP_ASSET_DENOMINATION` is set to the
rollup asset's denomination as represented on the sequencer. for
example, if the asset is represented on the sequencer is
`transfer/channel-1/usdc`, that is the rollup asset denomination. the
`name/symbol` of the ERC20 contract are not relevant.
- also update the build script to write the generated abigen contract
bindings to files, this is easier for debugging and unit testing.
## Testing
unit tests
## Related Issues
closes#924
it would be good to be able to bridge tokens from the sequencer to the evm which are represented as ERC20s (or some other non-native token), as currently, bridged funds are minted as the native token.
considerations:
The text was updated successfully, but these errors were encountered: