Beanstalk Farms · April 26th, 2023
On Season 6074, as the early dawn light broke across the rolling fields, the Farmers of Beanstalk gathered on the Mayflower, their trusty vessel, ready to set sail towards a new horizon. They had weathered many storms and worked hard to tend to their recovered crops, but they knew that in order to grow and thrive, they needed to adapt and evolve.
Today, Beanstalk Farms is excited to announce the Mayflower Update and an anticipated launch timeline. Note: BIP-34 Sunrise Improvements and BIP-35: Stalk Delegation and Process Amendments were proposed today!
The Mayflower Update consists of three major changes that will significantly improve the way the Beanstalk community experiences farming: (1) Sunrise Improvements, (2) Silo V3 and (3) Basin.
Today, the Sunrise Improvements BIP is live for voting. The Sunrise Improvements upgrade is primarily composed of 2 changes:
When the Bean price is above peg, Beanstalk still issues Soil in order to measure demand for Soil (and consequently adjust the Temperature). However, during times of short-term excess demand for Soil, Beanstalk pays significantly more in Pods than is necessary to attract creditors.
During the Morning of each Season (the first 5 minutes, or 25 blocks), the Temperature offered by Beanstalk is dynamic. Each Morning, the offered Temperature ramps from 1% to 100% of the maximum Temperature.
The Morning Auction should reduce unnecessary Pod issuance, which should improve Beanstalk’s creditworthiness as a borrower. In addition, maximizing Beans borrowed for a given Pod issuance improves Beanstalk’s efficiency.
Here's a preview of the new Field page in the Beanstalk UI:
Sunrise Incentive Adjustment
Beanstalk updates its monetary policy every Season, which occurs upon a successful call of the
sunrise function. It costs gas to call the
sunrise function and Beanstalk often overpays in Beans to incentivize users to call it. The Sunrise Incentive Adjustment upgrade makes it such that how much Beanstalk pays for incentivization of the
sunrise function takes into account Ethereum network conditions (i.e., current gas costs) and Beanstalk economic conditions (i.e., the Bean price).
Reducing unnecessary Bean issuance in the
sunrise incentive reward should reduce sell pressure on Beans.
The Silo V3 upgrade introduces multiple composability and UX improvements to the Silo, one of the core components of Beanstalk.
Removal of the Withdrawal Timer
When Beanstalk was launched in August 2021, Farmers had to wait 24 Seasons before being able to claim Withdrawn assets from the Silo. This lockup period likely served Beanstalk well during its infancy stage. Now that Beanstalk is more established, and more participants understand the incentives of the Stalk System, it has become clear that the Withdrawal timer is an economic inefficiency that creates a supply overhang when there are Withdrawn assets.
Since Replant, the Withdrawal timer has lasted until the remainder of the current Season. Now that the Withdrawal timer is being removed, Bean seigniorage will be distributed based on a time-weighted average, rather than based Stalk at the end of the Season. Distributing seigniorage this way eliminates the profit of a potential attack where a user deposits assets in the Silo, calls
sunrise, earns Bean seigniorage and withdraws the assets all in a single transaction while retaining Bean exposure for zero blocks.
Examples of developments that become possible after the removal of the Withdrawal timer include the redemption of Roots for Circulating Beans in a single transaction, the ability to order Pods on the Market with Deposits, etc.
Tokenization of Deposits as ERC-1155s
Making the positive carry of holding Beans usable in DeFi is critical to the success of Beanstalk. In practice, this means facilitating economic activity in Silo Deposits, given that it is Deposits that earn Bean inflation (and not Beans that are held outside the Silo).
To that end, tokenizing Deposits and having them conform to an established ERC standard like ERC-1155 is a necessary step in this direction. This will immediately provide utility in the form of a permissionless market for Deposits on existing infrastructure like OpenSea.
Dynamic Seeds per BDV
Currently, there is no straightforward way to change the Seeds per BDV rewards for a given Silo Deposit type. After Silo V3, it will be possible for the DAO to adjust the Seeds reward for a given whistlisted asset via BIP. This serves as the technical foundation for a future Gauge System where the DAO can express preferences that lead to Stalk and Seed rewards for various whitelisted assets changing in real time.
Unripe Seeds Parity
Currently, Unripe Bean Deposits receive 2 Seeds per BDV and Unripe BEAN:3CRV LP Deposits receive 4 Seeds per BDV. Most Bean liquidity is underlying Unripe LP, but converting to Unripe Beans results in a loss of Seeds. This seems to be one of the primary reasons for why a significant amount of Unripe LP remains in the Silo despite the opportunity to convert to Unripe Beans to arbitrage the Bean price.
Changing the Seed rewards for both Unripe assets to the same value would remove a significant cost to converting from Unripe LP to Unripe Beans. This may result in more conversions, which would have a significant effect on peg maintenance.
A DAO vote is likely in order to determine what the exact Seeds per BDV values for Unripe Beans and Unripe BEAN:3CRV LP should be set to in Silo V3.
Liquidity pools on the upcoming DEX are known as Wells, but the overall DEX architecture is known as Basin. Give the new Basin Twitter account a follow.
There are a number of problems with current implementations of AMMs on Ethereum. In a post-Merge environment, existing on-chain AMMs are not multi-block MEV resistant. Given that Beanstalk needs to price Beans against other assets (on-chain) and that the goal of Beanstalk is to be as censorship and manipulation resistant as possible, multi-block MEV is an attack vector that should be addressed.
Additionally, most AMMs in DeFi are generally not designed to be composable and have little flexibility in allowing developers customize their liquidity pool implementation. Trading fees, pricing functions, and price oracles are embedded and cannot be customized independently.
Basin aims to solve these problems:
Launching Basin in a way that Beanstalk directly benefits from requires a BIP that integrates the two protocols. Integrating the two protocols means:
Last updated May 24, 2023.