Despite Yam’s first post-relaunch rebase executing successfully, its developers are planning many more changes to the protocol.
Yam, the decentralized finance (DeFi) sector’s original food-themed clone protocol, has successfully completed its first rebase since its V3 relaunch.
Yam’s relaunch on September 18 followed the spectacular failure of Yam V2 last month — where a bug in the protocol’s unaudited code rendered governance impossible after only two days by rebasing the token’s supply 10 times higher than its design intended.
The Yearn.finance style protocol describes itself as “an experiment in fair farming, governance, and elasticity,” with Yam seeking to maintain a peg of 1 yUSD per token through adjusting or ‘rebasing’ its supply at 12-hour intervals. If Yam’s price is between $0.95 and $1.05 yUSD, no rebase will occur.
Yam V3’s first rebase took place on September 21, adding $571,000 worth of yUSD to its treasury and expanding tokens holders’ YAM positions by 2.49 times — driving down the price of YAM from $20 to $7.
Some statistics on the first $YAM rebase!
$571k in @iearnfinance yUSD added to the treasury
$5.71k contributed to public goods via @gitcoin
2.49x increase in YAM balanceshttps://t.co/RLoRxIVUQF— Yam Finance (@YamFinance) September 21, 2020
Despite the rebase, Yam emphasizes that its protocol is not yet fully optimized.
It notes that while Yam V3 retained “most parameters from V1” to “enable an efficient governance and audit process,” improvements still need to be made to the governance, liquidity incentivization, and rebasing processes underpinning the protocol. It recommends that in future rebasing should be executed with greater frequency to reduce the market impact of purchases made by the Yam treasury.
On-chain governance is expected to go live in the coming days, with Yam’s developers also hoping to launch on-chain analytics, improvements to Yam’s Uniswap routing, and detailed documentation in the near future.
Yam also hopes to establish greater rewards for community contributors, including core developers, community moderators, and infrastructure contributors.
