OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Use a shared database of chain ids
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
We currently have a hardcoded map of chainid -> name.
We could use the list at chainid.network.
I have some concerns about the names potentially changing with time, and this losing the state on a network. This can already happen if an unknown network becomes known with a name. We have to support this situation gracefully.
Contributor guide
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 locating the hardcoded chain ID-to-name map described in the issue and review the chainid.network list. Determine how network names are persisted and how unknown networks are handled, then define behavior for newly recognized networks and names that change over time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100