Oracle Update
01Summary
Update the protocol's oracle contract to a new address (0x65c816077C29b557BEE980ae3cC2dCE80204A0C5) with identical code to the current version. The new oracle adds support for FRAX, LUSD, and RAI tokens, which are available for governance consideration but do not represent endorsement for protocol integration. This change consolidates oracle operations and reduces Chainlink's duplicative gas costs.
- Type
- contract upgrade
Key changes
- Migration to new oracle contract at 0x65c816077C29b557BEE980ae3cC2dCE80204A0C5 with identical code to current oracle(high)
- Addition of FRAX, LUSD, and RAI price feeds to the oracle for future governance consideration(medium)
- Reduction of Chainlink's gas costs by consolidating oracle operations onto single contract(medium)
Notable concerns
- Addition of FRAX, LUSD, and RAI does not constitute protocol endorsement and their integration requires separate governance votes
- All existing markets retain current configuration during migration
Generated by Kvorum
02Description
Oracle Update
The proposal updates the protocol's oracle from here to here. The contract code is identical, all existing markets retain the same configuration, and we introduce FRAX, LUSD, and RAI to the mix.
Chainlink is currently paying double gas costs to maintain prices on the current oracle and the pending oracle.
FRAX, LUSD, and RAI have been added to the oracle on a best-efforts basis and exist for governance's consideration in future asset-specific governance votes. Their addition to the oracle is not our endorsement or opposition for their addition to the protocol. They are there so votes can occur to add the assets to the protocol, and the full merits of each asset should be considered at that time.
03Mismatch analysis
The single decoded action calls _setPriceOracle with the exact address (0x65c816077C29b557BEE980ae3cC2dCE80204A0C5) that the description names as the new oracle. This matches the core claim of the proposal: switching the protocol's oracle to the new contract. The description's mention of FRAX, LUSD, and RAI being added 'to the oracle' refers to functionality already built into the new oracle contract's code (as linked), not a separate on-chain action requiring a distinct calldata entry — so their absence from the decoded actions is expected and not a discrepancy. No numeric parameters, recipients, or additional side-effects are claimed in the prose that are missing from calldata, and no calldata action does something unmentioned (the single action is exactly the oracle swap described). Confidence is high because the proposal is simple and the calldata directly maps to the described action with matching target and argument.
Generated by Kvorum
04Actions
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setPriceOracle(address)
- Arguments
{ "0": "0x65c816077C29b557BEE980ae3cC2dCE80204A0C5" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- compoundexecutedOracle Improvement77%
- compoundexecutedOracle Update73%
- compoundexecutedUpgrade Compound v2 Oracle To Disable UAV72%
- compoundexecutedCompound Oracle Upgrade v371%
- compounddefeatedAdd Market: MATIC & Update Price Oracle70%
- compoundexecutedCompound UAV v3 Upgrade69%
- compoundexecutedOpen Price Feed69%
- lidoexecutedOmnibus vote: 1) Add oracle named 'Rated' with address 0xec4bfbaf681eb505b94e4a7849877dc6c600ca3a to Lido on Ethereum Oracle set;62%
- compoundexecutedAdd Market: USDP60%
- lidoexecutedOmnibus vote: 1. Remove the oracle member with address 0x140bd8fbdc884f48da7cb1c09be8a2fadfea776e from HashConsensus for AccountingOracle;59%