• Recordings
• Meeting Notes
• Big Items Up Front
• Beanstalk Project Funnel
• Seed Gauge
• wstETH Migration
• Multi Flow V1.1.0
• Misc. Improvements
• Beanstalk 3
• Subgraph updates
• Uncoolzero Updates
• Are there plans to increase voter engagement?
• Does it make sense for the budget BIPs to also include the project BIPs?
• Thoughts around timelines
• Thoughts around the EBIP idea
• Do the devs think about what would be good utility for Beanstalk?
• Transcript

Recordings

Meeting Notes

Big Items Up Front

• BIP-45 Seed gauge, BIP-46 Hypernative Hypernative, Temp check 4 Debt restructuring, Temp check 5 L2 migration is now live

Beanstalk Project Funnel

• A couple of small changes, Debt restructuring, and L2 migration have been added to the top of the funnel. Hardhat to foundry test suite is being worked on right now

Seed Gauge

• Voting is live! Go vote! Guy mentions that most of the next couple of BIPs assume this BIP passes. From Beanstalk Farms’ perspective, it is hard to know why BIPs aren't passing.

wstETH Migration

• Currently in remediations from the codehawks audit. The target date assumes that the previous BIP is passed and deployed. This goes for all future BIPs too. wstETH is hard to ship without Seed Gauge.

Multi Flow V1.1.0

• Currently in the remediations of the audit

Misc. Improvements

• The dev work is done and we are currently in the judging phase of the audit and nothing big has been found.

Beanstalk 3

• This is a combination of a lot of various other BIPs, such as Tractor, Gen Convert, and Secure Beanstalk. In the past audits have been a big bottleneck, and combining all of these smaller projects into one bigger BIP. Whitelist V1.1 will reduce the friction of whitelisting assets in the Silo. In the past, there has been bugs with the UI where it will not show users balances. There currently isn't a read balances function and the website has to make a lot of calls of the RFC the user is using. It has to make a lot of calls and this will cause rate limits. Beanstalk 3 will change this to be only one RPC call.
• Currently, Flood will only Flood the Well with the highest liquidity, and this needs to change to Flood all Wells.

Subgraph updates

• Basin has been uploaded to CoinGecko, this is a key part because a lot of other websites require a project to be listed on CoinGecko. The subgraph now tracks a Peg cross when it is just triggered by the price of ETH. There is now an all-time history of Delta-B and price. The updated calculation for L2SR with Seed Gauge. Locked Beans are Beans leftover if everyone Chopped. Other sites that Soilking is trying to get listed are Etherscan, DeFiLlama, and DeBank. The Beanstalk analytics UI will allow you to zoom in on a specific time.

Uncoolzero Updates

• The Beanstalk analytics UI will allow you to zoom in on a specific time. The goal would be to allow farmers to have more control over what and when they see it. Spacebean is working on the Deploy a Well page. It is unclear what a Whitelisting Well UI would look like.

Are there plans to increase voter engagement?

• Rex thinks that it is pretty hard to increase voter turnout because of how much of the DAO is anonymous. It is really hard to increase voter turnout. Guy thinks that it is pretty unclear, the DAO should try to increase people’s engagement either for or against.

Does it make sense for the budget BIPs to also include the project BIPs?

• As Rex understands it they are two different things. The budget BIPs are to allow funding and the project BIPs are because there is a change to the codebase. At the time of the Budget BIP, the project BIPs are not ready yet, and in some cases, there is a parameter that needs to be set by the DAO.

Thoughts around timelines

• TylerB thinks that the Devs should have a timeline to help attract other devs. Rex thinks the devs are doing a lot as is, but thinks there is room for more timelines.

Thoughts around the EBIP idea

• Nasjaq thinks that an E-BIP is not defined well, and could an EBIP be used to pass a normal BIP. Rex mentions that an EBIP should be used for only imitating things such as funds at risk BIPs. Guy thinks that this would totally undermine the entire idea of the multi-sig.

Do the devs think about what would be good utility for Beanstalk?

• Rex mentions that the devs are really focused on how to make the best Beanstalk product ever. There is a lot of work on making the local experience really good and really safe. Rex thinks that the better the local experience the more people will come.

Transcript

so we'll we'll kick things right off and get moving full screen this all right big items up front so just as yet Big Items Up Front another reminder we've got bip 45 and bit 46 uh which I'm for to put in that it's the hyper up for up for vote right now and then temp check four is also up for vote and actually just as another quick mention so Breen's temp check for the L2 migration is now live as well I've got that down at the bottom of this this slide um but yeah if whenever anybody gets a chance to run over to the governance site right after they vote on the bips that are up they can take a look at both temp check 4 and temp check 5 now and get their get their voices heard so as for upcoming and ongoing items so rap Ste and multiflow version 1.1 are currently in Auto remediation so moving forward with those um something that folks will notice as we go through this presentation is that we've had some consolidation of components so track oh there there's a missing comma to jeez tractor and secure bean stock all over the place looks like uh tractor and secure bean stock have been combined with other improvements so generalized convert uh generalized flood and a handful of others into what we're calling beanock 3 so obviously any of the devs can comment but the way that I see this is really it's it's maybe the right way to look at it is like an audit package so a group of improvements that for the sake of making the audit move as efficiently as possible kind of been grouped together and we actually we've got a we've got a slide on that a little bit later in the presentation and folks that are are watching will see the combination of some of those items you'll see some stuff that we previously had its own slide dedicated has now been Consolidated so um really just trying to make sure that that group of code is as as clean and well packaged as possible to make the auditing process move any questions about any of these items besides my typos all right hearing none and I will clean these up and I'll actually I'll reissue this deck as soon as as soon as we're done so projects and Beanstalk Project Funnel initiatives so we've got a handful of small changes a couple additions the ones that I would point out so primarily uh in that top of the funnel we've got the addition of the two temp checks that we've been talking about uh so debt restructuring in the L2 migration so those since they're in temp check they're in a little bit more active discussion there's you know some talk about how to approach those so we put those in the top of the funnel so that you they could be identified as as being closer to active development and then just looking through some notes and having some conversations I added hard hat Foundry test Suite change and and for what it's worth from a user standpoint that change isn't going to have much practical effect on day on day-to-day usage it's an important change on the backend and there's I'm sure there's a little bit more information that could be could be found or posted about you know just that that change in terms of testing suite and how that makes Not only some of the dev work a little bit easier but also a lot of the auditing work sounds like Foundry is a uh is a more widely used and more robust in terms of tools so generally a better choice so making that change from hard hat to Foundry on the back end over time I think everything else has has been talked about or covered in past Dow meeting so I'll open it up quickly any comments or questions on this information okay so down someone just come off mute okay must have been real quick so so to get down into the projects themselves so seed gauge you know obviously everyone's familiar with the project itself and and situation Seed Gauge we're you know coming down to the second set of votes again if you have not had a chance to go over to the governance site and put your votes in please do that we still few hours left still a little ways away from Quorum so yeah if you have a chance to and have not yet please go over and and vote on that item probably not much more to cover here for now so we'll jump down to WAP steeve migration I guess I would just add that sure feels like you know kind of an underlying Assumption of a lot of these slides and the ones upcoming are assuming you know bip's pass the first time or so so you know it's hard to know at this point it looks like it looks like we're like 77 is% towards Quorum so think you know nonzero chance we're able to get there this time but it's not looking particularly bright so yeah it's unclear I guess one thing that I don't think made it onto these slides is that Quorum change proposal under Town Square that would encourage everyone to check out and read and share thoughts on you know at least being stock Farms perspective it it's a little bit hard to know why exactly uh the bips aren't passing you know obviously it's it's like ultimately you just have to input a lot of the qualitative data in the Discord with regards to what people are talking about whether people are talking about being for or against the the seed gauge weip or whether there's you know comments or fud about other stuff so a bit hard to know in practice but at least in my opinion think think it would make sense at least attempt some sort of governance change given that there doesn't seem to be a whole lot of input with regards to you know the gauge system being bad or or implemented improperly or or things like that yeah agreed all right yeah I will actually that's another good item for me to add to to this deck I'll just add it into I'll add it up into that that prior slide about with the with the funnel chart so to jump down to W the so we're wstETH Migration we're now in remediation for those code Hawks audit items um so obviously the process is moving along well there again to to kind of highlight guys point you know we've got um the week of June 17th as a as a as a Target deployment time period but again there is an assumption there that you know that like the other items that these are are passing on the first round of proposal I would just add that the way that these are implemented sort of assume that the previous bip is implemented you know I.E in this case the wraps teeth you know white listing and migration although you know somewhat fairly separate in principle does assume a lot of the gauge system infrastructure changes are made so obviously if there was a lot of push back on hey guge system bad rap St is good you know that work could probably be done to separate them but given that uh there isn't that discussion or commentary feel like I just want to point out that this one is is difficult to ship before the gauge system passes if that makes sense thanks they okay so these do have to be proposed sequentially to some extent not have to for the reasons I described earlier but you know it's that certainly would be the the path of least resistance if that makes sense all right jumping down to multiflow 1.1 again Multi Flow V1.1.0 probably not a whole lot to cover in terms of rediscussed everyone seems pretty familiar but you know again just to to Loop backward now into the remediations portion of you know the audit so a lot of good progress there and now it's just the process of of taking care of those those remediation items all right miscellaneous Improvement so in this case you know we're again through the Misc. Improvements vast majority of development we're into the judging phase so active conversations happening with the coach team right now personally have not seen a lot that you know that indicates any any major questions or concerns through that judging phase obviously dead man Bren guy feel free to to add any color or anything but it seems like that that process is moving along pretty smoothly yeah and just to make the same point I made earlier that the missile you know the path of least resistance as shipping the miscellaneous improvements pip after the rap pip okay beanock 3 so as i' mentioned earlier there were a handful Beanstalk 3 of items skier bean stock tractor gen convert uh that have been Consolidated and packaged into essentially the beanock 3 audit package so you know right now we've got the cipon team engaged the code Hawks team engaged and starting to move forward with that audit process yeah there's just there's a lot of stuff to cover here a lot of things that people have been talking about for quite a while I don't know if there's anything that that the team wants to talk about specifically but yeah we're seeing a lot of items in this package that you know that have gotten a lot of discussion around the farm for the last really the last handful of months I mean I guess to talk a little bit about the rationale for combining some of these things it feels like with these development you know design development Cycles the audit in particular has been a bottleneck and particularly with with regards to you know these sequential bips for example where you know the gauge system bip ended almost two months ago the rap steth bip audit ended at the end of April and you know we're still we're we're more or less catching up and well you know clearly were ready to propose the SE gauge bip a couple weeks ago when it was proposed but uh there's been this sort of lag and at least in my view since we sort of made this call to combine a few of these and try to launch something on the beanock anniversary on August six that you can see in like the lower right corner of this slide I think that development has really picked up so you know as Rex mentioned a couple of these have already been talked about at length although you know happy to answer questions myself or I know a couple people working on these changes are in the on the call as well with regards to you know gen convert tractor Etc but just to mention or highlight a couple things that I don't think have been discussed too much and is one of which is what's called wh list v1.1 I think Breen could probably say more about this than I can but at a high level you know think it there's clearly been a lot of friction with regards to whitelisting Assets in The Silo whether for deposit for conversions for minting and not that we'll be at a point where you can click a couple buttons in the UI and get there but with regards to you know development effort generalizing things like you know the Oracle that beanock uses to calculate Delta b in a particular well things like that uh generalizing components like that will make it a lot a lot lower friction to to Whit list new assets and obviously the value value proposition of of whitelisting new assets post AG system and gen convert is uh high I would argue one of the other things that a few people few of the people working on both the front and end the contracts talked about yesterday is you know even today and over the last you know year and a half there's been you know more or less like a handful of problems with people loading their balances which is very bad obviously you know that's one of the worst things that uh the UI could do is is show someone that they don't have a balance that they do have and it's obviously obviously a very bad ux and a very scary ux and part of the reason that that's the case is that you know previously bean stock was heavily optimized around optimizing gas costs versus well basically at the cost of anything else and and in this case in particular you know the developer experience of working with the UI and because there's no view functions that you can just call on beanock to get your deposits given a particular address or get your plots for example what the website has to do at the moment is when you load it it has to read all the events from the beginning of time or rather from you know the deployment of beanock if you will and them manually to determine the state of your balances and because of that it has to make a lot of calls to whatever RPC the user is using for the in their wallet and we we often run into a rate limit and you know I think maybe unle zero can chime in but I believe at one point someone someone on the front end team told me you know was having to make hundreds or maybe even low digigit thousands of calls each time the user loads the website and uh with these with these new view functions that we want to add in beanock 3 because you know the meta at least in the beanock development Community seems to be shifting away from optimizing for gas costs for optimizing for you know security among other things which has been talked about at previous Dow meetings you know that'll be reduced to just one RPC call and and Hope at least I'm pretty excited about the prospect of not having those sorts of issues in the UI anymore but those are just a couple highlights you know see if anyone else wants to chime in add anything that they're working on well appreciate that guy yeah I mean if anybody else that's been working on any of these items there's anything you want to cover we'll give you just another quick chance and also with regards my earlier comment around you know combining these you know combining these upgrades and and audits in order to you know speed up development timelines you know if you just you know take a look at these slides take a look at the list of rfc's slth list of rfc's that were listed in the budget proposal for 2024 and I could be I believe that all of them will have been implemented by by beanock 3 except for Blacklist mitigation which is pretty exciting agree you know and then some of course as mentioned nasak I just saw your question we'll come back to it here in a minute subgraph and other updates just kind of unmute did you want to say something pizza man yeah I could talk about Jen flood for a second I suppose I don't think that been mentioned much before um yeah so the main problem now is that the flood will only flood the highest highest not volume but the highest liquidity well and so you know if hopefully with multiple Wells getting white listed in the near future um sooner or later we're going to want to make sure that the the flood works correctly for those two and so yeah the code for that doesn't seem to have been too complicated uh I feel like it's mostly wrapped up actually uh probably need some more review uh from other contributors and a bit more testing but yeah that was that was not too too complex to implement so hopefully that'll be able to be squeezed in with this upcoming audit here appreciate that all right so jump down so yeah kind of want to just open up the floor quick for you know any upgra or any updates on subgraph or or any other items that haven't been covered thus far in the deck yeah so I have some stuff to share Subgraph updates you may have seen earlier this week was announced that we actually have Basin is listed on coin gecko now so that's pretty exciting there's still some more stuff we need to work with their team on there to you know get like all of the historical data available for the the different swaps and liquidity and whatnot but I mean at least on my end for like the dev work like that's all done so just need to kind of be coordinating with them and I think that's that's particularly pretty exciting because you know at least a lot of these other these other sites that we were looking to integrate with as well it's kind of the the the first thing that has to be done is got to be on coin gecko so now that that's done that kind of opens up some some possibilities down the road as well so so yeah so I guess more to come with that and as far as the subgraph is concerned there was a change some new analytics were deployed maybe a couple weeks ago at this point it was mainly three three major things so the first one is that now we're actually tracking a peg cross when just like when the the price of ether fluctuates so you'll notice like both in the in the peg cross's Discord chat and then also on the on the site on on the analytics page you know that that actual fluctuation without having someone having to make a trade and as a result there's actually a lot more Peg crosses uh that we weren't tracking previously so I think the number of Peg crosses is actually like 2,000 higher or like a th000 I think it's maybe like 17 or 1,800 higher than what we thought it was now that we started tracking that since you know before replant and then after replant so that was pretty cool and then we also added support for prices time so both the in instantaneous prices time weighted average prices and then the Delta b as well for since since like all time before replant so now when you look on the UI for for those charts if you go to the alltime view you can actually see everything so that's that's also pretty cool and then the third major thing this is relating to seed gauge but this was changed on the analytics ahead of that deployment which is the updated calculation for the L2 Sr so just to talk briefly about that basically with seed gauge the l2s is not including the locked beans so lock locked beans are basically those beans that are um it has to do with the unripe I mean maybe Breen could explain it better than I could but it's basically the beans that are that are locked that can't be withdrawn like even if if hypothetically everyone were to chop like the amount of beans that would that would kind of be left over and so as a result the L2 Sr is more like a more accurate value that you can see on the analytics page I think it's I think before I want to say it was maybe like 40ish perc and now it's 73% on the new calculation I'm seeing so just you know more accurate to reflect the fact that a lot of suppli is locked and I think that's that's it for for for my updates for what's been deployed good stuff appreciated soing so couple questions follow-ups for you in the chat I see one from nas jaac saying what other sites are you looking at integrating with let me see here yeah I have a list that I've written none of these I've none of these I've started working on yet just kind of things that I've taken a note of you know it's it's unclear when when these actually get worked on because you know at least with a lot of the the the contract upgrades that are planned and coming up uh you know there's there's a lot of work that has to be done with that as well but I have written down here as well ether scan obviously getting the price updated there which if I haven't actually checked but if I'm not mistaken that should be good now that we're on coin gecko we want to get on defi Lama we want to get on Dex screener dbank you know maybe some other ones I think there I think coin gecko has like a gecko terminal it was called which I think the work we did to get on coin gecko would also be enough to get us on there we just have to submit the listing once we get the other information finalized with them good stuff appreciate that extra information and nasck said thank you to say related to related to some of the pre- exploit data that Sook King's been adding to the subgraph you know in the form of preex exploit ltsr you know price Delta B Etc things like that I guess we already had price but at least Delta B and ltsr among other things you'll notice if you're a curious farmer that likes to look at the alltime chart and look at previous beans stock data it's very difficult to read data that's far in the past and the more time that passes the the more scrunched up everything gets and uh on the other hand on the Basin UI it's very easy to pick a period in time by just dragging your cursor or or perhaps it's using the scrolling actually I don't quite remember off the top of my head but it's very easy to look back in time at like a particular you know date range and so I think uncool Zer has been working on a revamp to the analytics UI to be able to do do that in the beanock UI for all of those charts which will be very handy I think right now when you hover over the pre- exploit price you can't actually even hover over the the $ four Peak which is kind of disappointing good stuff so I guess so you mentioned UI updates guy I mean anything else so you mentioned a discussion that happened yesterday that was was really good give an opportunity for anybody that was part of that discussion to you know talk about some of the things that they were talked about or anything they want to add from a from a UI standpoint or really any other maintenance or updates Uncle zero you know want to give you a chance if there's something you want to talk through definitely want to give you that opportunity can you guys hear me that sound good yeah y you're good awesome so Uncoolzero Updates yeah like like guy just said there's a big revamp to the to the analytics page coming up and hopefully you'll be able to have more finer control over what what kind of data you're seeing and the time range you're seeing without like relying on the the presets that we currently have so that should make it that page way more powerful and way more useful actually so that's coming up and I believe this was mentioned before there's some view functions coming up as well and you know U sadly this is something that's you know highlight worthy it shouldn't be right the UI should should not should get out of the way and just let the user do its thing but sadly due to gas optimizations we we really have to load a lot a lot of data into the UI and a lot of RPC servers don't don't support that kind of that kind of true but so having view functions will really make this a lot a lot easier and hopefully solve all of our issues coming forward good information appreciate that all right Tyler Tyler be's question who asked well the setup you are to create Wells and whiteless token The Silo be part of beanock 3 so I believe space Bean who recently started working on beanock this week actually is working on first thing that he's working on is the deploy o well page and that was designed by sweet red beans about a month ago I think they've done some great work and so excited to see that go live I mean given that governance is still offchain I think it's unclear exactly what a wh listing tokens UI would look like but you know it's an interesting point but from my perspective you know Step One is being able to deploy the well easily yeah I think that's an important distinction to make you know that that idea of deploying well being kind of the first step in getting that well whitelisted and yeah the the idea of being able to do that permissionless is it's great well good you hit on a related note the the the wh list v1.1 thing that I was talking about earlier with regards to generalizing you know wh listed tokens oracles among other things will make it a lot easier at some point in the future to potentially explore a UI that can do that good stuff all right you hit Tyler be's question which is great so that gives us the ability to jump back up to NAS jaak's question so nasck asks does the team have any plans for how to increase voter Are there plans to increase voter engagement? engagement and to just speak for myself you know I know that I've thought about this a lot and I know that a lot of folks thinking about you know how to increase engagement and you know one of the one of the difficulties that that I run into is or you know I would say probably anyone does that's trying to you know trying to increase engagement or or let's call it voter turnout is just the anonymity of our users and you know I I I know at a couple points in the past and I personally you know looked at did some wallet comparisons and you know sent sent secure messages through ether scan and you know try my best to reach out to folks but that I that even itself has some some limitations I don't know if there is a really good answer for increasing engagement other than just trying to find as many places as possible to get the word out and and doing whatever individuals can on their own to try to reach out to people they know you know I know that you know there are messages passed back and forth about hey you know has so and so talked to this person has you know have we reached out to this other person you a lot of that a lot of those discussions happen you know between different individuals but a lot of it is just pavement pounding and and trying to to figure out who you haven't talked to in a while I don't know if anybody else has has any input but I know it's been been something I think everybody's been a little bit frustrated about it but there's just there aren't a lot of really good answers all right I would just Echo that you know similarly frustrated and similarly think it's unclear exactly but I think what is clear is that you know the community's ability to to do that you know in terms of like getting people to participate you know whether for or against was kind of kind of going to you know make or break how these next couple bips go so you know feel like this is one of the best forms to bring up ideas for that talk about it so would encourage people to do so if they have any so a couple couple folks are T typing but Nas Jack followed up with how do we expect to pass Quorum reduction in that case and I would say that you know that's that's not completely clear you know I think that there's there'll be an effort that goes along with that just like there's been an effort with the other bips that are that are currently up and yeah just going to going to be a pull by the community okay looking through I see Tyler NE as typing re I think we missed s sop's question oh I'm sorry I'm sorry all right yep no that sorry about that sofocles so all right Sophocles writes do we think there's benefit in making the budget bips as the Does it make sense for the Budget BIPs to also include the project BIPs? yes no vote for protocol updates seems rather annoying that we have to vote for both the work or what to work on and then also to push the development was there an initial reason for doing it this way so I'll give a quick answer and anybody certainly can follow up as I've understood this concept historically really so why we've got separate votes it's because it's kind of two fundamentally different concepts the first is you know the budget bip is to is to spend funds to to spend the funds of the Dow and then the the bips to actually push development work are more focused on the idea that with the passage of that bip there's going to be a change to the protocol code itself that will be implemented and because those ideas are separate there is a desire to have the votes be separate and of course you know someone understands that differently if I've got a misunderstanding definitely jump in um but that's historically how it's how it's been discussed and I guess I would also say to get back to the actual question there's a lot of different ways to potentially approach governance and and you know if there are ideas from the community about potentially changing that part of the approach you know it's it's certainly worth worth bringing up in discussion sorry guy go ahead no no worries I was just going to say that you know the issue is that at the time of the budget proposal the proposed work is not implemented yet and you know I'm not going to sit here and suggest that you know every individual farmer is like auding auditing the code uh personally but in particular for a lot of these bips there are parameters that need to be decided on somehow by the community and by the Dow you know in the case of the gauge system there's probably you know more than five in the form of the target Seasons to catch up the minimum being the max LP ratio the maximum ratio etc etc and because the work isn't implemented by the time at the time of the budget proposal it it almost can't really be known what those parameters will even end up being until until that work is further designed so you know perhaps there's an argument to make that Quorum should be structured different for minting beans versus protocol upgrades but on the other hand you can just upgrade the protocol to you know add a function that mint beans so it's like hard to really draw a line between the two but who knows maybe there's something there I'm not sure appreciate the additional color of their guy so nasck followed up with some questions about having Ben be part of the meeting or or have him talking I can't answer really on on his behalf I would definitely encourage you to reach out to him if you if you want to ask them so Tyler B follows up one of the things he Thoughts around timelines can help is get the D more involved in what features the dev should work on next fre each fature devs can give more explanation on how it will grow the protocol I believe this could help definitely good suggestion I know there's been you know discussion about a prioritization um process I've been thinking about that myself over the last you know handful of really handful of weeks the other thing that that I have come to understand again over the last few weeks is you know just how much how much the devs are working on and you know the the the amount of work that they are doing I do think there probably is a there's room for some type of you know Dow involvement in and making those suggestions to what should be worked on next and and having a you know a good robust discussion about what the priorities are what they what the Dow thinks they should be I also think you know looking at especially you know the the work that's been worked on for or that's currently being worked on for beanock 3 the devs are pretty well are pretty well stacked up in terms of their schedule for you know really through the summer into the early fall um so you know I think there probably is a place for that that ability to to have additional input I would also say it probably wouldn't have a big impact until you know we're into that well into that fall period so some something we can think about between now and then but yeah there's there's room for this suggestion process and we can figure out what it might look like you know over these next few months Nas Jack asked any Thoughts around the EBIP idea thoughts on the EIP idea admittedly I'm not familiar with the EIP idea I mean so I sorry I wasn't able to talk earlier so I've been texting but I posted it in the chat but also just like the EIP like EIP is pretty broad it's for protecting Bean if we assume that the inst can't pass anything like is it a protection to actually just be able to like change the form or something because otherwise we stagnate and might die and especially nobody's voting against it so it's just inactive stock or are we just going to wait until there's enough active stock but the longer we wait the more it becomes inactive yeah it's it's a it's a good question and again I say it's definitely a point of frustration and of course someone else can jump in if if they'd like a my understanding of the ebip process I'm I'm glad you pointed me to the your comment in general because the familiar with eips I I didn't have the context around that particular question you know as as I understand them ebips are used primarily in the event that something actively dangerous to the protocol or that would cause either immediate failure or some type of immed immediate issue were to happen you know that's the context in which an ebip would be used so I mean I guess it raises the question of you know at what point does the community think that that we've crossed that line it it seems like it seems like that wouldn't necessarily be the right use of an ebip but I'm sure it's probably something worth discussing guy do you have any thoughts about it I mean I'd have to take a look at the language but just you know philosophic speaking and speaking as a individual participant in beanock I feel like that would totally undermine the concept of the multisig I mean I agree I just don't see how we're gonna pass anything to reduce quarm or pass anything I don't know you know unless we keep minting and then people come back I think that's the only yeah it's hard to know I wish I had an answer for you yeah agree yeah I I figured I'd ask you since you wrote it yeah I mean I also think the other thing like I said in my comments is like you know if Ben was out there talking to people I think that inspired a lot of people so it'd be interesting to know where Ben's at I think that'd be a good good message to shoot to Ben frankly you know I I don't disagree with you in the sense that I think that you know he's very smart guy with a lot of you know really good insight and you know I think passing that let's say that you know those compliments along to him I think is is is worth it because you know he's yeah I he wants what's best for bean stock so yeah I think it's that'd be a good thing to to pass along so Tyler B Do the devs think about what would be good utility for Beanstalk? asks do the devs think about what will be good utilities for being in the defi ecosystem personally you know based on what I would say is becoming a better and better view of the the folks that are working on beanock you know what I see is a group of developers that want to build a really solid set of functions and internal capabilities for our users there's a lot of focus around you know what can be done to make beanock and Basin work really well with the the desire to make a really good really safe really useful user experience you know hard to speculate on anybody's priorities outside of that but there is a lot of you know active work focused on making the local experience really good really safe really efficient and and and really robust and you know I think it is safe to say that what goes along with that is the concept that the better the local ecosystem gets the more attractive it'll become and you know we're we've been going through some really interesting Cycles recently you know obviously it was pretty good day for you know for for for cryptocurrency in general and you know defi yesterday but you know it seems like the goal within this team as I see it is is building a really good experience that people can come to and use and with you know with the hope that as that happens it'll draw more interest from the outside again you know that's that's just me thinking out loud anybody else can definitely comment if they see something different or or additional okay at the bottom of the chat for The Voice Channel worry Harry I do see your your ultimatum too but at the bottom of the voice Channel I don't see anything Tyler be's question we got that in the barnyard chat so that's good excuse me and I don't see anything else in general so I will give one more minute just for closing comments in case anybody has anything to add and then we'll let everybody go okay hearing nothing additional one more time if you haven't gotten a chance to already go over and Closing statements vote love to see these bips pass and and be able to keep moving forward um we will keep everybody updated as voting closes and thanks again for your time and have a good rest of your day thanks everyone