★ Immutable oracle address
Ethena's assessment for RD-F-180 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[★ CRITICAL-CANDIDATE, PD-017] UNVERIFIABLE. EthenaMinting V2 has no oracle address field in on-chain storage; minting oracle is entirely off-chain (Pyth/Redstone API). No immutable oracle declaration exists in the deployed EthenaMinting contract. The Chainlink PoR feed addresses are not declared as immutable in any Ethena smart contract. Oracle replaceability at the off-chain infrastructure layer cannot be confirmed from on-chain evidence alone. If Ethena's backend has hardcoded Pyth/Redstone feed IDs that cannot be swapped without a redeployment, F180 would apply. Curator must obtain off-chain infrastructure documentation or governance-forum-posted oracle configuration procedures to resolve this gap. Score yellow pending curator confirmation.
Sources #
- GitHubhttps://github.com/ethena-labs/bbp-public-assetsretrieved 2026-04-28
- https://docs.ethena.fi/solution-design/use-of-oraclesretrieved 2026-04-28
- https://github.com/code-423n4/2023-10-ethena/blob/main/contracts/EthenaMinting.solretrieved 2026-04-28
Methodology #
Determine whether any collateral oracle address is marked `immutable` in protocol config with no admin-replaceable adapter wrapper, preventing the protocol from repricing when the upstream asset depegs.
See the full factor methodology and distribution across all protocols →