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

SemaphoreEthers doesn't handle mumbai as a network value #527

Closed
cedoor opened this issue Jan 8, 2024 · 0 comments · Fixed by #528
Closed

SemaphoreEthers doesn't handle mumbai as a network value #527

cedoor opened this issue Jan 8, 2024 · 0 comments · Fixed by #528
Assignees
Labels
bug 🐛 Something isn't working

Comments

@cedoor
Copy link
Member

cedoor commented Jan 8, 2024

Description:

SemaphoreEthers changes the network to maticmum when the value equals matic, but matic should actually be mumbai as Semaphore doesn't support the Polygon mainnet yet.

@cedoor cedoor converted this from a draft issue Jan 8, 2024
@cedoor cedoor added the bug 🐛 Something isn't working label Jan 8, 2024
@github-project-automation github-project-automation bot moved this from 🏗 In Progress to ✔️ Done in Semaphore Board Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
Status: ✔️ Done
Development

Successfully merging a pull request may close this issue.

2 participants