MetaMask / MetaMask/metamask-extension
Trying to Add Ronin Testnet, PLEASE HELP
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
This is my first time using github so I have absolutely NO idea which of these is the correct field to use for this request. PLEASE FORGIVE ME if I've entered it incorrectly.
So, I'm trying to add Ronin testnet to my metamask, ufortunately when I use the CHAIN ID 2021 (which is supposed to be the ID for Ronin Testnet) it brings up a completely different network (Edgeware EdgeEVM Mainnet).
According to everything I've found everywhere the correct chain ID for Ronin Testnet is indeed 2021.
I've been able to add Ronin Mainnet with chain ID 2020 but for some reason the Testnet just won't show up/add correctly.
I don't know what to do. Of course all of this had to happen as I FINALLY braved taking a class where I was trying to learn how to deploy an ERC20 and ERC721.
I would GREATLY appreciate any guidance anyone is will to offer.
Thank you
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
Contributor guide
Research direction
The issue does not name a source file, test, or entry point. Start by reproducing the chain ID 2021 network selection in the MetaMask extension and compare the displayed network with the reported Ronin testnet details. Done means MetaMask adds or selects the intended Ronin testnet rather than Edgeware EdgeEVM Mainnet.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100