We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description This issue is about resolving ENS address for all chains. Created after this comment https://github.com/cowprotocol/cowswap/pull/5044/files#diff-115105906c7a4010bd5c51ceb31345ffc8e28ecaf60e27603be71d87324b9dc1R15
Proposal Keep an RPC for mainnet that can be used for ENS resolutions, no matter the chain you are in.
Alternatives do it in BFF, but seems more centralised option
Additional context https://github.com/cowprotocol/cowswap/pull/5044/files#diff-115105906c7a4010bd5c51ceb31345ffc8e28ecaf60e27603be71d87324b9dc1R15
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
This issue is about resolving ENS address for all chains. Created after this comment https://github.com/cowprotocol/cowswap/pull/5044/files#diff-115105906c7a4010bd5c51ceb31345ffc8e28ecaf60e27603be71d87324b9dc1R15
Proposal
Keep an RPC for mainnet that can be used for ENS resolutions, no matter the chain you are in.
Alternatives
do it in BFF, but seems more centralised option
Additional context
https://github.com/cowprotocol/cowswap/pull/5044/files#diff-115105906c7a4010bd5c51ceb31345ffc8e28ecaf60e27603be71d87324b9dc1R15
The text was updated successfully, but these errors were encountered: