smartcontractkit / smartcontractkit/chainlink
[FEAT] Support FeedRegistry on all networks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Description
FeedRegistry contract should be deployed and supported on all Chainlink supported networks
Motivation
It currently works only on ETH mainnet. Chainlink launched this feature on mainnet 3 years ago, but since then it never expanded to other EVM chains.
Justification
I've previously requested to support it on BSC, but the issue was simply closed 2 years ago (see https://github.com/smartcontractkit/chainlink/issues/6807). Since then, the situation only got worse, as we now have a plenty of other successful EVM compatible networks.
As I've already explained in the original issue, my product needs the registry otherwise we would have to hardcode all existing and future oracle combination/addresses in order to show quotes to the users, that's unmaintainable.
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 existing FeedRegistry deployment and support path for Ethereum mainnet, then compare how supported EVM networks are configured. Define the deployment and support coverage required for each Chainlink-supported network; done means FeedRegistry is deployed and usable across all of them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100