Yam Finance Closed Its Emergency Migration to YAMv2

Yam Finance’s 72-hour migration from the failed YAMv1 system to a non-rebasing YAMv2 token closed at 16:20 UTC on August 22, 2020. The project reported a final YAMv2 supply of 3,726,411 tokens, ending a tightly timed recovery exercise that had begun at 16:20 UTC on August 19.

The central facts are independently visible in the project record. Yam Finance’s contemporaneous migration notice set the August 22 cutoff, published the migration-contract address and identified the new YAMv2 contract. Ethereum explorer Etherscan records that token contract with a maximum total supply of 3,726,411.616545120934755180424489 YAMv2. The project’s rounded event-day figure and the on-chain supply therefore agree.

A placeholder for governance, not a repaired protocol

YAMv2 was deliberately limited. Yam Finance described it as a standard ERC-20 token without rebases—a temporary instrument through which holders could make decisions while a fuller successor protocol underwent development and review. Holders had to remove YAMv1 from staking contracts, approve the migration contract and call its migration function before the deadline. After 16:20 UTC on August 22, unmigrated YAMv1 was no longer eligible.

That design matters because the migration did not claim to restore YAMv1’s intended economics. YAM had launched only days earlier as an experimental, community-governed protocol with an elastic token supply and treasury. A defect disclosed on August 13 made its rebase mechanism mint an unintended quantity of YAM to the treasury, undermining the voting threshold needed for governance. The migration separated two tasks that had become dangerously entangled: preserving a holder base for governance and rebuilding the financial logic.

The YAMv2 repository also preserved the code and PeckShield audit report for the migration system. That provides stronger evidence than a project announcement alone, but an audit is bounded assurance rather than a guarantee. The immediate August 22 result was a completed token conversion under a published deadline, not proof that any later protocol would be secure.

Why the deadline mattered

YAM’s recovery became an early stress test for the fast-moving decentralized-finance market of 2020. The project had no conventional transfer agent capable of replacing balances by administrative decree. Recovery instead depended on a new Ethereum contract, individual holder action and a public cutoff. In practical terms, governance continuity was reconstructed through voluntary, on-chain conversion.

That made August 22 consequential beyond YAM’s market price. The episode exposed both sides of open financial software: composable code and token incentives could assemble a community quickly, while an error in monetary logic could disable the very governance intended to manage the system. The migration showed that a community could coordinate a technical bridge after failure, but it also shifted losses and deadlines onto users who had to act correctly.

No price conclusion follows from the supply figure. YAMv2 used 24 decimal places, and its high unit price or low token count could not by themselves measure adoption, liquidity or value. This reconstruction therefore does not infer investment performance from the migration.

What was knowable on August 22

By the cutoff, the verified record supported three narrow conclusions: the announced window had closed; the replacement token supply was about 3.726 million YAMv2; and YAMv2 was a governance placeholder while further protocol work was contemplated. A contemporaneous report said a governance forum was scheduled to open on August 24. Whether the community would approve a viable successor, whether another audit would find problems, and whether liquidity would persist were still unresolved on August 22, 2020.