[CONTRIBUTION] [BUG] Chainlink Price Feeds stale on Polygon, Ethereum, etc

[thestabull]

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.

dune.com/queries/5959887

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?

[0xBoxer]

hi @thestabull thanks for raising this issue!

I think updating these pricefeeds is a reasonable consideration, however I would like you to see if we can get out of hardcoding the variables here to be more adept for any future upgrades and to make multichain deployment of this data pipeline easier.

Let me know what you think!

[thestabull]

@jeff-dude @0xBoxer
I dont know enough about how you usually discover new contracts, but heres some ideas...

Problem:

1. discovering new chainlink oracles (chain, feed_name, decimals, proxy_address, aggregator_address) as here: https://dune.com/data/chainlink_ethereum.price_feeds_oracle_addresses
2. periodically mapping oracle proxy_address to oracle aggregator_address (aggregator updated periodically with new versions)

Solution:

• Chainlink docs API: https://reference-data-directory.vercel.app/feeds-mainnet.json Solves 1. and 2. but guessing not preferred.
• No Proxy or Aggregator Factory. Bytecode matching doesnt work on aggregator addresses since they are deployed with feed_name (e.g. EUR/USD) as immutable variables.
• The only events i can find to discover proxy addresses are from these chainlink Flags contracts (oracle registry): https://docs.chain.link/data-feeds/contract-registry the FlagRaised event has proxy_address as subject. But this still doesnt expose the aggregator_address mapping. (there is a function/method aggregator() and description() on the proxy contract, to get the aggregator address and feed_name).