Skip to content

Mention Airnode mnemonic rotation in searcher docs #195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 23, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/oev-searchers/in-depth/data-feeds/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -247,6 +247,12 @@ To know which encoding to use, you can check the length of the
both `address` and `bytes32` are encoded using 32 bytes. For a beacon set, the
length depends on the number of beacons encoded.

::: warning ⚠️ Airnode Mnemonic Rotation

Data providers rotate their Airnode mnemonics every 6 months as part of Api3's security practices. This results in new Airnode addresses being generated. Please refer to the [Api3 Market](https://market.api3.org) or directly on-chain data for the latest Airnode addresses.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd add:

Suggested change
It's recommended that searchers periodically refetch the data feed in from the chain or subscribe to `SetDapiName` event emitted by the Api3ServerV1 contract.

:::

::: info ℹ️ Example

Say there is a dApp proxy that uses the `ETH/USD` dAPI. We can compute the
Expand Down