Skip to content
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.

Quoter vs QuoterV2 address #82

Open
Florian-S-A-W opened this issue Sep 1, 2023 · 2 comments
Open

Quoter vs QuoterV2 address #82

Florian-S-A-W opened this issue Sep 1, 2023 · 2 comments

Comments

@Florian-S-A-W
Copy link

I noticed that the Addresses for the Quoter point to different contracts on different networks. This also happens in the Docs.

For Celo the address points to the QuoterV2 Contract.
For default chains e.g. Mainnet the address points to the Quoter Contract.

I would like to access the QuoterV2 Contract address from the v3-sdk.
I would suggest adding both addresses in the sdk-core ChainAddresses as optionals.

@Florian-S-A-W
Copy link
Author

@just-toby

@Florian-S-A-W
Copy link
Author

The QuoterV2 actually seems to be deployed on all supported chains while Quoter is only deployed on the default chains. So maybe let's make quoterAddress optional and add quoterV2Address as non-optional.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant