MetaMask / MetaMask/detect-provider
Make compatible with EIP-6963
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 238
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
It appears that [EIP-6963](https://eips.ethereum.org/EIPS/eip-6963) is headed for finalization. Once this EIP has been implemented in all MetaMask clients, this package should be updated as well. In particular, we should define a new export `requestProvider` (as implemented [here](https://github.com/MetaMask/providers/pull/263)), and deprecate (but not remove) the other exports / functionality of this package. Clients should continue to emit `ethereum#initialized` for backwards compatibility.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading EIP-6963 and the referenced MetaMask/providers pull request #263 to understand the requested provider API. Inspect this package's existing exports and initialization behavior, then verify that requestProvider is available, existing functionality is deprecated rather than removed, and ethereum#initialized remains emitted for compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100