Developer Andre Cronje launched iEarn as an automated way to move user deposits between lending protocols to seek better interest rates. This early product set the core idea that later defined Yearn: software that reallocates funds on-chain to improve returns without manual switching.
Yearn introduced YFI as a governance token, distributed to users providing liquidity rather than reserved for the founder or investors. The goal was to move control of key parameters and upgrades toward a community voting process, rather than a single developer deciding alone.
As Yearn grew quickly, community discussions highlighted practical governance concerns such as phishing risks and the need to standardize official domains. These early threads show that “governance” was not only about token economics, but also about protecting users and coordinating operations.
Yearn’s Vaults v1 expanded the project beyond rate-switching by letting users deposit into vaults that run automated strategies (for example, farming rewards and compounding them). This made “vault strategy design” a central governance topic, because vault behavior could change risk and returns for depositors.
As vault usage increased, Yearn’s community formalized how the system should evolve and how ongoing work would be funded. This period helped shift Yearn from a fast-moving experiment into a DAO-like organization with explicit proposals and responsibilities.
Yearn pursued a series of integrations described as mergers, aimed at sharing development and expanding product capabilities. The SushiSwap merger announcement was a prominent example, reflecting a strategy of building an ecosystem rather than a single standalone app.
Yearn introduced Vaults v2, designed to support multiple strategies per vault rather than relying on a single strategy. This change mattered for governance because it expanded how strategists could propose improvements and how risk could be diversified or managed within one vault.
Yearn governance approved YIP-57, a plan to mint 6,666 additional YFI to fund development and retention packages. This was a turning point: after emphasizing a fixed-supply “fair launch,” the community chose inflation to sustain long-term operations and incentives.
An attacker used flash loans and price manipulation to exploit Yearn’s v1 DAI vault strategy, causing large reported losses at the vault level. The incident highlighted that legacy vaults could remain risky even after newer vault versions launched, and it increased pressure to deprecate older contracts more aggressively.
Yearn’s website update added v2 vault listings and tooling to help users move funds from v1 to v2 (often called “zaps” for one-transaction migrations). This was an important operational step: governance and engineering changes only reduced risk if users could realistically migrate to newer vaults.
Yearn began publishing regular vault-focused updates summarizing new vaults, strategy changes, and protocol metrics. These reports helped governance by making vault activity easier to follow, especially as vault strategies became more complex and varied across assets.
By the end of 2021, Yearn’s vault system had moved from early v1 experiments to a v2-centered approach with clearer funding, reporting, and migration practices. The period’s key legacy is a governance-driven vault lifecycle: launch strategies, revise them, migrate users forward, and respond to incidents with process changes rather than ad hoc fixes.
Yearn Finance vaults and governance (2020–2021)