Extendable Bridge Adapter #685
Closed
Conversation
This file contains hidden or 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 pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Makes Bridge adapter infinitely extendable.
Now there is a single bridge adapter that handles all chains. The large list of liquidity sources is broken down in groups
BridgeAdapterGroup1andBridgeAdapterGroup2. that theBridgeAdapterwill dispatch between by BridgeProtocolIdI re-did this changes because there were a lot of changes on top and rebase wasn't working very cleanly.
I have used simbot to test on a few different chains. First i would remove all of the liquidity sources to prove my override worked. then after seeing many failures I would put the liquidity source back and run simbot again making sure that the run was clean.
Testing instructions
Types of changes
Checklist: