NEW

Introducing Transporter, a new bridging app powered by CCIP. Go cross-chain.

Back

Proof of Reserve Feed Addresses

To learn how to use these feeds, see the Proof Of Reserve Feeds documentation.

For LINK token and Faucet details, see the LINK Token Contracts page.

Risks for Proof of Reserve feeds using the wallet address manager

Cross-chain Proof of Reserve feeds using wallet address manager contracts can vary in their configurations. If the wallet address manager is self-reporting, these feeds might include reserve balances from onchain addresses that have not been cryptographically verified to show ownership or control. In circumstances where cryptographically verified ownership is not provided, there is a risk that token issuers could manipulate the value of a Proof of Reserve feed by adding more addresses to the address list even if they do not directly control these addresses. Each feedā€™s specific configuration is documented in the contract address section. Chainlink Labs is not responsible for the accuracy of self-reported reserves data. Users must do their own risk assessment for asset issuer risk.

Data feed categories

  • šŸŸ¢ Low Market Risk Feeds: Feeds that deliver a market price for liquid assets with robust market structure.
  • šŸŸ” Medium Market Risk Feeds: Feeds that deliver a market price for assets that show signs of liquidity-related risk or other market structure-related risk.
  • šŸ”“ High Market Risk Feeds: Feeds that deliver a heightened degree of some of the risk factors associated with Medium Market Risk Feeds, or a separate risk that makes the market price subject to uncertainty or volatile. In using a high market risk data feed you acknowledge that you understand the risks associated with such a feed and that you are solely responsible for monitoring and mitigating such risks.
  • šŸŸ  New Token Feeds: Tokens without the historical data required to implement a risk assessment framework may be launched in this category. Users must understand the additional market and volatility risks inherent with such assets. Users of New Token Feeds are responsible for independently verifying the liquidity and stability of the assets priced by feeds that they use.
  • šŸ”µ Custom Feeds: Feeds built to serve a specific use case or rely on external contracts or data sources. These might not be suitable for general use or your use case's risk parameters. Users must evaluate the properties of a feed to make sure it aligns with their intended use case.
  • ā­• Deprecating: These feeds are scheduled for deprecation. See the Deprecation page to learn more.

See the Selecting Quality Data Feeds page for complete details about each category.