-
Notifications
You must be signed in to change notification settings - Fork 67
feat: Handle cases where a deposit's inputToken and originChain cannot be mapped to a PoolRebalanceRoute #2177
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
base: master
Are you sure you want to change the base?
Conversation
…t be mapped to a PoolRebalanceRoute Relayer: - Refuses to fill such deposits Dataworker: - Does not let such deposits affect bundle LP fees and running balance calculations
@@ -580,90 +577,4 @@ describe("InventoryClient: Refund chain selection", async function () { | |||
expect(possibleRepaymentChains.length).to.equal(4); | |||
}); | |||
}); | |||
|
|||
describe("In-protocol swap", async function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this test isn't doing what we think its doing currently. Currently the determineRefundChain
should throw if input token and output token are not "equivalent" here and in this test, the input token is native USDC which has no pool rebalance route mappings to bridged USDC, so it should not allow determineRefundChain
to return successfully.
Relayer implementation based on across-protocol/sdk#970
Relayer:
Dataworker: