Chainlink Developers

Welcome to the Chainlink documentation site. You'll find comprehensive guides and documentation to help you start working with Chainlink as quickly as possible, as well as support if you get stuck. Click here for an introductory walkthrough on how to create a Chainlink request on the Ropsten test network!

Building on Chainlink? Click here to get started!

Get Started

Developer Communications

Price feed upgrades

We continue to add many new improvements to Chainlink. As the DeFi ecosystem matures, our smart contracts and software will evolve to keep up with the increasing demand for new feeds, security and scalability features and resilience around network congestion.

We are committed to communicating these changes with you in advance. This page will provide information on our current communication channels and detail active notifications / upgrade plans with timelines.


Stay up to date with the latest upgrades

🚧

Important: Sign up for update notifications

Developers should subscribe to update notifications via any of the following channels:

Subscribe to the channels above for future notifications about the newest resiliency, scalability and security updates to Chainlink reference data.


Current notifications

Aug 2020 Flux Aggregator Update

️ Required

Please follow the Migration Instructions and update to the latest Price Feed Contracts to ensure your contracts always reference the most up to date aggregator. If you do not upgrade after the timeline in this document, your consumer contracts may not receive the most accurate price data.

The update to FluxAggregator adds congestion resilience capabilities and gas optimizations for reports involving median calculations over the previous version.

  • A new function latestRoundData has been added. It returns roundId, answer, startedAt, updatedAt, and answeredInRound. This allows consumers of reference data to make decisions around if the data is acceptable in a single function call (ex: if answeredInRound < roundId could indicate stale data).
  • A description view has been added. This shows the name of the price feed (e.g. ETH/USD).
  • A decimals view has been added. This indicates the number of 0s to the right of the decimal point (e.g. 18).
  • Backwards compatible: existing interface functions from old aggregators are still supported.

Migration timeline

24 Aug 2020: Upgrade Information Released
Please visit our Migration Instructions or go directly to the latest Price Feed Contracts page to update today.

1 Sep 2020: First Upgrade Notice

At this date, we will begin notifying smart contracts pointing at legacy data feeds to update their feed addresses.

An onchain study will be done to investigate if calls are still being made to legacy data feeds, and we will make our best effort to contact smart contracts that have not yet updated. On specific legacy data feeds where all users have fully migrated, update frequency will be reduced. The frequency of updates will be available with increased resiliency on the new feeds to which users have migrated.

15 Sep 2020: Second Upgrade Notice

We will once again notify all users via email and discord. On specific legacy data feeds where all users have fully migrated, update frequency will be reduced. The frequency of updates will be available with increased resiliency on the new feeds to which users have migrated.

22 Sep 2020: Final Upgrade Notice

We will post a final notification message before beginning to deprecate legacy feeds.

Over time, the frequency at which the legacy aggregators are updated will be reduced. This means that if you do not migrate, your contracts will not consume the most up-to-date price data available. The frequency of updates will be available with increased resiliency on the new feeds to which users have migrated.

We are here to help. If you require assistance or more time to make updates to your contracts, please get in touch with our team on the Discord developer chat.

Updated about a month ago

Developer Communications


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.