Beanstalk Farms · October 6th, 2021
The Beanstalk Roadmap is constantly evolving in light of new information. This post has been written with the following goals in mind:
This roadmap may change based on community feedback.
An overarching long term goal is to ensure Beanstalk is not dependent on Publius indefinitely. While the protocol itself doesn’t require significant additional development from Publius, in order to succeed Beanstalk must attract a strong and resourceful community that grows — and helps Beanstalk grow — organically without Publius’ direct and perpetual involvement.
Reliance on Publius presents both an existential risk to Beanstalk, and one of its biggest challenges. This is reflected throughout the list, but also in a few specific instances worth highlighting:
1. Dev Budget — We will propose one-time BIPs that will mint new Beans and allocate them to a development fund. In the short term, we expect Publius to be responsible for approving payments from the dev budget to developers. Over time, we expect to decentralize this process.
The dev budget will allow us to incentivize:
We expect community feedback on the specific amount and structure of the dev budget. If you have thoughts on the structure of the dev budget, want to get paid in Beans to work on Beanstalk or know someone that might, come chat in our #dev Discord channel here.
2. Community Organizer — Finding a community member interested in serving as Community Organizer is an essential step to moving Beanstalk away from reliance on Publius. In the future, the goal is to fund this through a BIP as a full time position.
Finding the right community organizer presents a tall task. They must have:
We hope to source potential options from the community in the coming weeks.
The BIPs to fund both a dev budget and Community Organizer would require approval from the community according to the normal governance process.
We have declined to give hard estimates on timing, and instead group the various items in blocks. This is reflective of both the ever-changing nature of this document, as well as the difficulty in giving exact due dates for technical development.
With all of that being said, here is the Beanstalk Roadmap for the coming months as of 10/6/21.
Our estimation is that in total the initial funding BIPs will total at most a few hundred thousand Beans. We intend to create a vesting schedule on all payments made from BIPs.
Some important future developments of Beanstalk did not make the list. Below are brief explanations as to why they are not currently on the roadmap.
1. L2: Making Beanstalk — and passive USD Deposit accounts — widely available to smaller Farmers remains incredibly important to us. However, the most natural way for Beanstalk to scale to L2 is to have a totally independent Beanstalk deployed on each additional chain. In the short term, our primary focus is on having the original Beanstalk successfully maintain its peg. Doing so will greatly enhance the ability of other Beanstalk to be successfully deployed on other chains and for other assets. Launching another Beanstalk before the original has established itself as reliable will create competition between the two, which is not appropriate at Beanstalk’s current stage.
2. Alterations to the Economic Model: In general, we are thrilled with the functioning of Beanstalk during its first debt cycle. In the near future we will be publishing a more detailed analysis of the first debt cycle and explain why we have thus far decided against proposing any of the various economics-related BIPs we have been considering.
Subscribe to The Bi-Weekly Bean and we'll send major Beanstalk updates straight to your inbox.