The evolution of Yearn Finance from launch to 2026 overhaul

The 2020 Launch and Early Expansion

Andre Cronje launched Yearn in 2020 as a solo developer to automate yield optimization for stablecoin holders. The protocol rebranded from iEarn and uses smart contracts to move assets across lending platforms like Aave and Compound. The team minted 30,000 YFI tokens through a fair launch where no pre-mine or founder allocation existed. Users earned these tokens by staking yCRV LP tokens from the Curve pool. The initial distribution included 10,000 tokens for the yCRV pool and 10,000 tokens for two separate Balancer asset management pools. By September 2020, the protocol reached over $750 million in total value locked and ranked 5th among all DeFi protocols. The Quantstamp audit in July 2020 preceded the launch of the v2 vault codebase. This codebase allowed the protocol to go multichain with the launch of Fantom vaults like yvWFTM, yvUSDC, yvDAI, and yvMIM. The total value locked reached a peak of $7 billion in December 2021. During the early years, the YFI token saw a 10,000x price run and provided staking yields of up to 1,000%.

Structural Shifts and Market Volatility

Cronje left the project in 2022, and the protocol transitioned to a collective of independent contributors. This shift brought new difficulties when market conditions changed. In June, a governance post by developer Banteg called for a 67.6% reduction in compensation for contributors. A subsequent proposal, YIP-69, established that the protocol will not deploy funds to any strategy offering below a 2.5% APY before fees. The protocol also faced security challenges during periods of high volatility. An attacker exploited an accounting flaw in the legacy yETH pool on November 30, 2025, and drained $9 million. In 2023, a different vulnerability in an older yUSDT contract resulted in an $11.6 million loss. You probably remember the community debates regarding whether the treasury should compensate victims of such code bugs. In October 2023, the community introduced a new vote escrow token model, but it failed to gain traction because only 3.8% of the YFI supply locked in that system. The governance structure also underwent changes to address the rise of non-revenue-earning teams and the resulting coordination inefficiency. The protocol also implemented YIP-55 to formalize the introduction and implementation of all Yearn Improvement Proposals. The protocol manages different fee structures across its products:

The 2026 Revenue Model and Governance

The Yearn DAO implemented a major overhaul through YIP-88 to align stakeholders and kickstart growth. This proposal reorganizes contributors around revenue-earning teams and requires all teams to use on-chain revenue splitters to solve the free-rider problem. The new system routes 90% of protocol revenue to stYFI holders to increase interest in the governance token. The transition deadline for existing teams to reorganize was October 31, 2025. The total value locked in the protocol stabilized at $800 million following the January 2026 launch of the yvUSD cross-chain stablecoin vault. This vault runs nine active strategies with zero management and zero performance fees. A Debt Allocator manages how the vault distributes funds across the nine strategies. The yvUSD strategy allocates funds across Morpho Blue lending, Pendle principal tokens, Sky Savings Rate deposits, and leveraged Morpho positions. The DAO also plans to distribute 1,700 YFI tokens through strategic contributor incentives. The DAO-ops team maintains the governance infrastructure and the YFI tokenomics. This minimal team also handles the administrative tasks required to keep the protocol running. The transition to this new operational model involves the reorganization of the entire Yearn DAO around autonomous, revenue-generating units to ensure that all team budget requests remain strictly accountable to the actual income the protocol generates on a regular basis. Will the current revenue split provide enough incentive to attract new contributors to the DAO?