duneanalytics / duneanalytics/spellbook
[CONTRIBUTION] [BUG] Chainlink Price Feeds stale on Polygon, Ethereum, etc
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 1.4k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 22
Description
Description
Chainlink price feeds are stale across multiple chains (ethereum, polygon, bnb, avalanche). As shown below, the last timestamp from these models was around Aug/Sep 2024. optimism, gnosis, fantom & arbitrum appear unaffected.
Sub-project: chainlink
Models:
- chainlink_***_price_feeds
- chainlink_***_price_feeds_oracle_addresses
Issue
Old aggregator_address are being referenced in /chainlink***price_feeds_oracle_addresses
- price_feed source events are recorded from the aggregator_address (the proxy_address does not emit required events).
- aggregator_address's are hardcoded as in /chainlink_polygon_price_feeds_oracle_addresses.sql
- aggregator_address's are sometimes updated / rotated by chainlink, as they were in Aug/Sep 2024. Currently referenced addresses are no longer used or emitting events.
Solution
I can update all the aggregator_addresses's to the new address for each affected chain as a PR, but is there anyway to backfill the last 12months of missing data?
Also, any guidance for replicating these models for base chain?
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 with the chainlink_*_price_feeds_oracle_addresses models, especially dbt_subprojects/daily_spellbook/models/chainlink/polygon/chainlink_polygon_price_feeds_oracle_addresses.sql, and compare the hardcoded aggregator addresses with current Chainlink rotations. Check the affected Ethereum, Polygon, BNB, and Avalanche models and determine whether the missing 12 months can be backfilled. Done means affected feeds reference active event-emitting addresses and the backfill approach is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- blockchain, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100