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
Hello,
Per this thread: https://discuss.ens.domains/t/erc-3668-edge-case-for-clientside-http-ssl-errors/19617, it looks like network errors or non-http error responses can prevent CCIP clients from falling back to a secondary gateway URL. I believe this is also impacting the CCIP-read client in ethers.
This would be a great addition to ethers.js as user implemented offchain resolvers continue to grow.
Thanks!
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the Feature
Hello,
Per this thread: https://discuss.ens.domains/t/erc-3668-edge-case-for-clientside-http-ssl-errors/19617, it looks like network errors or non-http error responses can prevent CCIP clients from falling back to a secondary gateway URL. I believe this is also impacting the CCIP-read client in ethers.
This would be a great addition to ethers.js as user implemented offchain resolvers continue to grow.
Thanks!
Code Example
No response
The text was updated successfully, but these errors were encountered: