The Incident
On September 12, 2019, MakerDAO completes the second part of its Oracles V2 rollout, a technical presentation led by Nik Kunkel that details the foundational infrastructure upgrade powering the protocol’s transition to Multi-Collateral DAI. The upgrade arrives at a critical moment for the largest DeFi protocol on Ethereum, with total value locked approaching $500 million and the community preparing for the most significant architectural change in MakerDAO’s short history. Single-Collateral DAI, backed exclusively by Ether, has served as the backbone of decentralized lending since its launch in 2017, but its limitations have become increasingly apparent as the DeFi ecosystem expands.
The Oracles V2 upgrade is not merely a technical improvement — it is the prerequisite infrastructure that makes Multi-Collateral DAI possible. Without reliable, tamper-resistant price feeds for multiple asset types, the entire concept of multi-asset backing collapses. The stakes could not be higher: a faulty oracle could trigger unwarranted liquidations, destabilize the DAI peg, and erode billions in value across the interconnected DeFi ecosystem.
Technical Post-Mortem
The Oracle V2 architecture introduces a fundamentally redesigned price feed system. The original oracle relied on a relatively simple set of price reporters feeding data into the Maker Protocol. V2 implements a multi-layered defense system: decentralized oracle networks, medianizer contracts that aggregate multiple price sources, and delayed price updates that give the community time to respond to potential manipulation attempts.
The technical centerpiece is the Oracle Relayer contract, which sits between the raw price feeds and the Maker Protocol’s core contracts. This relayer validates price data against sanity bounds — predefined minimum and maximum values that prevent catastrophic failures from clearly erroneous data. If ETH suddenly reports a price of $0 or $1 million, the sanity bounds trigger an automatic circuit breaker rather than cascading liquidations through the system.
Nik Kunkel’s presentation details the migration path from the existing single-price-feed architecture to a multi-feed system capable of supporting ETH, BAT, and eventually dozens of collateral types. Each collateral type requires its own oracle configuration — unique price sources, update frequency, and sanity parameters. The complexity scales linearly with each new collateral type, making the oracle system one of the most engineering-intensive components of the entire Maker Protocol.
The V2 system also introduces the concept of Oracle Governance — a framework where MKR token holders can vote to add, remove, or modify oracle feeds. This represents a significant expansion of MakerDAO’s governance scope, moving beyond monetary policy (stability fees, debt ceilings) into infrastructure management.
Governance Impact
The Oracles V2 upgrade surfaces a governance challenge that will define MakerDAO for years to come: the tension between decentralization and operational reliability. Oracle feeds require constant maintenance — price sources go offline, exchange APIs change, and market conditions shift. Who bears responsibility for keeping the feeds operational? The Maker Foundation has shouldered this burden during the protocol’s early years, but the stated goal is progressive decentralization.
The September 12 presentation reveals that the oracle system currently depends on a relatively small number of trusted price reporters. While the architecture supports adding more reporters over time, the onboarding process requires governance approval, technical vetting, and ongoing reliability monitoring. This creates a practical bottleneck: the system is theoretically decentralized, but operationally concentrated among a handful of trusted entities.
For MKR holders, the governance implications extend beyond oracle management. Multi-Collateral DAI will require ongoing governance decisions about which assets to accept as collateral, what risk parameters to set for each asset, and how to adjust those parameters in response to market conditions. Each decision carries financial risk — a poorly calibrated collateral ratio could lead to undercollateralization during a market crash, while overly conservative parameters could limit DAI supply growth and protocol revenue.
TVL Shifts
The oracle upgrade is occurring against a backdrop of shifting DeFi dynamics. MakerDAO remains the dominant protocol by total value locked, with approximately $500 million in ETH collateral backing roughly 85 million DAI in circulation. But the landscape is becoming more competitive. Compound has been gaining traction with its interest rate model, Synthetix is expanding its synthetic asset offerings, and the Tether migration to Ethereum is flooding the network with stablecoin liquidity that competes directly with DAI.
Multi-Collateral DAI is designed to address several TVL-related challenges simultaneously. By accepting multiple collateral types, MakerDAO can expand DAI supply without being constrained by ETH price movements. During periods of ETH volatility, the protocol can maintain stable DAI issuance through alternative collateral sources. This diversification should theoretically reduce the systemic risk that comes from relying on a single volatile asset as the sole backing for a stablecoin.
The data from DeFi Pulse shows that MakerDAO’s dominance as a percentage of total DeFi TVL has been gradually declining as new protocols launch and capture capital. Multi-Collateral DAI, combined with the oracle infrastructure to support it, represents MakerDAO’s bet that broader collateral acceptance will reverse this trend by attracting capital from multiple asset communities simultaneously.
Long-Term Prognosis
The Oracles V2 rollout positions MakerDAO for the most consequential upgrade in its history. If Multi-Collateral DAI launches successfully — and the oracle infrastructure appears ready — MakerDAO will transform from a single-asset lending platform into a decentralized central bank capable of issuing stablecoins backed by a diversified portfolio of digital assets. The implications for DeFi are profound: a more robust DAI means a more stable foundation for every protocol that depends on it.
However, the risks are commensurate with the ambition. Oracle failures remain the single largest technical risk facing the protocol. The V2 architecture provides multiple layers of defense, but no system is immune to sophisticated manipulation attacks, especially during periods of extreme market stress when accurate pricing matters most. The famous example of the 2017 DAO hack looms large in the Ethereum community’s memory as a reminder that smart contract complexity and high stakes are a dangerous combination.
The long-term success of MakerDAO’s oracle strategy will depend on the community’s ability to progressively decentralize the price feed infrastructure while maintaining the reliability that the system demands. If they succeed, the Oracles V2 architecture could become a template for every DeFi protocol that requires external data. If they fail, the consequences will ripple across the entire DeFi ecosystem. There is no middle ground when your stablecoin backs half a billion dollars in value.
Disclaimer: This article is for informational purposes only and does not constitute financial advice. The cryptocurrency market is highly volatile, and readers should conduct their own research before making any investment decisions. Past performance is not indicative of future results.
$500m TVL and the entire system hinges on oracles not failing. Nik Kunkels presentation was basically saying please trust us with your money
dai_whale_ $500M TVL riding on oracle accuracy is wild when you think about it. one delayed price feed from a single source and the peg breaks. the median feed design was the only thing standing between DAI and a death spiral
median_feed_ the median design saved DAI on Black Thursday. if it was a single oracle the peg would have snapped. people dont realize how close it got
median_quorum_ single oracle on Black Thursday and DAI goes to zero. the median feed was 3 lines of code that saved billions
peg_defender_ median feed saving DAI on Black Thursday is the most underappreciated architectural decision in crypto history. one line of code prevented a cascading liquidation spiral that would have killed DeFi
peg_defender_ the median feed with 3 independent oracles was genius but relying on fewer sources means a single compromised feed has outsized influence. the safety was always thin
the multi-collateral DAI transition was the biggest architectural risk Maker ever took. one bad oracle feed and billions in cascading liquidations
the cascading liquidation risk wasnt theoretical either. a few months later during Black Thursday the oracles actually did lag and liquidations piled up
Tobias R. cascading liquidation risk wasnt theoretical, it was a preview. black thursday in march 2020 played out exactly the scenario Kunkel was warning about. oracle lag plus ETH flash crash equals mass liquidations at stale prices
Black Thursday was the stress test nobody wanted. oracle lag plus ETH crashing 50% in a day was the worst case scenario playing out live
oracle_maxi Black Thursday proved the oracle lag risk was real. ETH drops 50%, oracle lags 10 minutes, liquidations pile up at wrong prices. theory became reality fast
Black Thursday proved the oracle design was decent. It lagged but it didnt break. Liquidations were brutal but the system survived
single collateral SAI to multi collateral DAI was smooth in the end but nobody slept well during that upgrade window
priya_mcd the SAI to DAI migration was smooth but the oracle infrastructure was the scary part. one delayed price feed during volatility and the peg breaks
i was running a keeper bot during that window. the latency on oracle updates had us all sweating, every second felt like an hour
nervous_validator running keepers during SAI to DAI migration without a kill switch is something you only do once. never again
running keeper bots during the SAI to DAI migration was the most stressful 72 hours of my life. one delayed feed and liquidations cascade at wrong prices
SAI to DAI migration was the most stressful week in early DeFi. upgrading the core collateral mechanism on a live protocol with real money in it. no pause button, no safety net, just hope the oracle feeds hold
SAI to DAI migration was the original stress test for every mechanism that matters. oracle feeds, liquidation ratios, collateral types. all validated under fire with real money
Kunkel presenting the oracle v2 calmly with 500M TVL on the line. the stakes were insane and most people in the room didnt fully grasp what could go wrong
Nils E. is right about the stakes. 500M TVL with no kill switch. DeFi was wild west back then. now we have pause functions
Kunkel kept his cool during that presentation despite knowing one oracle misfire could tank half of DeFi. respect
Kunkel presenting that calmly while knowing the stakes is peak defi energy. billions riding on oracle uptime and dude was just vibing
Felix W. presenting calmly while knowing a single oracle misfire could cascade through 500M of TVL. peak builder mentality right there
running keeper bots during SAI to DAI migration with real money on the line and no pause button. early DeFi devs had actual nerves of steel
Aleksandra W. no pause button on a live migration of the biggest DeFi protocol. those early devs had iron stomachs. today a Uniswap v3 fee tier change requires a governance vote