Skip to content

Correlated token oracles

Correlated-token oracles price a receipt, staking, or yield-bearing token from an exchange rate and the USD price of a related underlying asset. The directory contains more than one deployed generation; constructor and permission models must be selected per address.

FamilyDeployment shapePricing and control model
V1 uncappedusually a transparent proxy with constructor immutables in the implementationlive exchange rate × underlying USD price; no snapshot-growth cap
V2 cappednon-proxy immutable deployment in current artifactsoptional exchange-rate growth cap, AccessControlManager setters, and permissionless interval-based snapshot updates
Special implementationsproxy or non-proxypurpose-built logic such as SFrxETHOracle; do not assume the common-base ABI

The current CorrelatedTokenOracle source is V2. It is not ABI-compatible with every older proxy implementation that remains deployed.

The addresses below come from the oracle v2.16.0 deployment artifacts. Code was also present at BNB Chain block 118367342 and Ethereum block 25845949 on August 27, 2026. This is version evidence, not proof that a ResilientOracle currently consumes an instance.

NetworkInstanceAddressVersion
BNB ChainAnkrBNBOracle0x4512e9579734f7B8730f0a05Cd0D92DC33EB2675V2 non-proxy
BNB ChainAsBNBOracle0x652B90D1d45a7cD5BE82c5Fb61a4A00bA126dde5V2 non-proxy
BNB ChainBNBxOracle0xC2E2b6f9CdE2BFA5Ba5fda2Dd113CAcD781bdb31V2 non-proxy
BNB ChainSlisBNBOracle0xDDE6446E66c786afF4cd3D183a908bCDa57DF9c1V2 non-proxy
BNB ChainWBETHOracle0x49938fc72262c126eb5D4BdF6430C55189AEB2BAV2 non-proxy
BNB ChainStkBNBOracle0xdBAFD16c5eA8C29D1e94a5c26b31bFAC94331Ac6V1 transparent proxy
EthereumSFraxOracle0x1aDCE75BB3164bBf6060a4f44262df5414473110V2 non-proxy
EthereumSFrxETHOracle0x5E06A5f48692E4Fff376fDfCA9E4C0183AAADCD1special transparent proxy
EthereumWeETHAccountantOracle (weETHs)0x47F7A7f3486b08A019E0c10Af969ADC4B6E415CdV2 non-proxy
EthereumWeETHOracle, equivalence route0xaB663D4a701229DFF407Eb4B45007921029072e9V2 non-proxy
EthereumweETH, non-equivalence route0x92469958A4C00101F9F290cc3AC32959Af497EAfV2 OneJumpOracle
EthereumWstETHOracleV2, equivalence route0x6b51Ee3aF70b350AaADc05f418502b330c5Aad7cV2 non-proxy
EthereumWstETHOracleV2, non-equivalence route0x6ecf38558B0D1fFc6Ea28bEC6BD39F9F0Fdd6631V2 non-proxy

OneJumpOracle and PendleOracle have both V1 and V2 deployments across several networks and maturities. Their pages describe the two ABIs explicitly.

  1. Read the asset’s current ResilientOracle.getTokenConfig and identify the enabled role and oracle address.
  2. Determine whether the address is a proxy, and resolve its implementation if it is.
  3. Match that exact bytecode to V1, V2, or a special implementation.
  4. For V2, read snapshot, growth, gap, and ACM configuration at the same block.
  5. Treat a dated or still-deployed address as lifecycle evidence only after checking consumers and outstanding market duties.

See the deployed oracle registry for address discovery, then confirm all dynamic configuration onchain.