feat: l2 token approval flow #2260
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Some L2 -> L1 bridge objects sometimes require ERC20s to be approved to their associated bridge contracts. Example: Hyperlane requires
ezETH
to be approved for spending by aHYPERLANE_ROUTER
.This is why we implement a token approval flow for L2 bridges similar to L1 token approval flow.
Approval + xERC20 rebalancing test after change:
✅ rebalance
✅ token approval happened on a prev. relayer run.