Probably the only solution is to incentivize, or hire, new devs by paying with yUSD and $YFI on a vesting schedule. This is what all tech startups do because it works.
The only problem is there is little-to-no $YFI available to give to new devs. So either a buyback is needed or removing the 30k cap.
It means a need to incentivize developers, especially new ones who want to join to Y team (not only as strategy devs, but also protocol devs). And it would be cool that all Y-devs owned part of YFI pie.
So, maybe to buy YFI from the open market (using performance fees or increased strategy fees) and redistribute somehow between protocol + strategy developers.
âYearn is not owed anything from anyone. Contributors come together and work on this project voluntarily. Nobody has authority over anyone else, and nobody owes Yearn anything. Similarly, nobody has any right to ask anything from Yearn. You get back what you put in.â âYou are asking an already small pool of developers who are at a high level within a new ecosystem to forego their own aspirations and instead come work for you for no real financial alignment or vesting beyond âyou might get paid goodâ . Try hiring a good dev in any coding language irl for your company with no kickbacks to them and see how that goes.â I donât see how you can resolve this tension without charging more fees to pay devs more. Gettting something for nothing is called stealing.
Love how straight-forward and concise this is! looking forward to helping build out applications with yearn, both existing as well as those that are yet to come.
Thanks for starting this discussion, itâs an important one to have.
The free-rider problem you describe isnât unique to yearn. Itâs common in crypto (e.g. here and here) and actually in all public goods like open source software, since free-riding is a public goods problem.
It should be noted though that many open source projects have overcome these problems to succeed. Foundational open source projects like unix and git are what crypto, and most of the Internet, is built on.
So to figure out how to make yearn succeed even though âinvestors outnumber developers so heavilyâ, Iâd look to how pre-crypto open source, with arguably worse developer incentives, managed to keep developers engaged.
The Cathedral and the Bazaar is an obvious guide here. Itâs worth reading in full but here are some of my takeaways:
As a community, we should create an environment where developers can work on problems that scratch their own itch.
We should make it easy for contributors to hand over projects to competent successors when they lose interest, and celebrate them even if they do.
Community members, even non-technical ones, should think of themselves as co-developers who do early user testing and bug reporting.
Of course this should be done in addition to the many existing funding experiments in yearn and elsewhere: yearn monthly grants, gitcoin-type quadratic funding, larger ecosystem players funding individual developers, etc
Great manifesto great that the people involved in Yearn.Finance did one amazing all that was accomplish and all the great things to come from Yearn.Finance
Joined because of manifesto.
Everyone who makes a community better should have the same value in it. You need nurses and doctors. One alone canât do anything.
Coders alone ??? Have what???
My first tweet. I understand nothing. Knowledge only has value when applied.
Code needs application.
I went through all the comments and added those that showed strong agreement and approval of the manifesto as signers.
Some comments showing support I did not add as signers as the intent wasnât super clear to me.
If I got anything wrong please let me know! Happy to remove anyone I have incorrectly listed as a signer and add further signers to the list (just put a +1 in your comment to be added).
Pretty descent apy result , switching for the best.
Pipe pooling large gauge % for more efficiency to respond to main demand.
With the new vaults also.