Skip to content
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

drop polygon mumbai #620

Merged
merged 1 commit into from
Apr 12, 2024
Merged

drop polygon mumbai #620

merged 1 commit into from
Apr 12, 2024

Conversation

avichalp
Copy link
Collaborator

  • This PR removes support for polygon mumbai as it will be deprecated on April 13th 2024.
  • Until we have Polygon Amoy support ready, this PR changes the default network to Ethereum Sepolia

Polygon has informed us that they will deprecate Mumbai on April 13. We are planning on keeping our Mumbai nodes for Polygon running until this date. However, in the past we have seen extreme instability in networks leading up to deprecation. While we will do our best to keep it running, we cannot guarantee that this network will be usable until April 13. It is in your best interest to migrate to Amoy immediately. If you try to send requests to these nodes after Alchemy support ends, your requests will fail with a DNS resolution error.

Signed-off-by: avichalp <hi@avichalp.me>
Copy link
Collaborator

@brunocalza brunocalza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Although, I think the ideal transition would be to first offer Amoy, so users have a chance to migrate first, then drop Mumbai. But since we still don't have an Amoy contract, I don't think we have an option.

@avichalp avichalp merged commit 4c74c67 into main Apr 12, 2024
5 checks passed
@avichalp avichalp deleted the avichalp/drop-maticmum branch April 12, 2024 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants