As I understand the voting process at the time, first a signaling poll was required to gauge sentiment. If there was enough interest then one could create a YIP with a binding vote.
When we started using snapshot that added some confusion since we were using it for both signaling polls (in place of the built in forum poll which is vulnerable to sybil attacks) and for binding votes.
As Andre’s proposal to burn the keys was the first post and vote on that topic, I believe that was a signaling vote and non-binding.
So technically, we could mint more YFI. I’m really not sure that’s a good idea though, but I do agree with the sentiment of this thread: that we need a bigger warchest.
We have other options that we should discuss. We’ve been working on a new version of @RyanWatkinsproposal to use staking rewards for YFI buybacks. Similar to what @gilfroy has suggested above. That would accomplish a similar goal to minting. We were going to publish that here today.
I am open to this discussion and very curious what the community thinks.
Our core team is incredibly important and we need to ensure they are well incentivised to continue delivering value.
That said, minting more $YFI would be a huge transgression of the existing social contract. Whether or not the 30k hardcap is binding or not doesn’t matter, the community has strong expectations of maintaining the hardcap, and Andre himself has publicly stated that there should only be 30k tokens.
The scarcity meme is strong too and debasing $YFI would cause huge damage to the credibility of Yearn.
I do not support this proposal. Instead, we should ship V2, which many of us within the community know to be a very strong release (market leading, no other project has comparable capabilities in this product vertical). This in turn should drive massive AUM growth and strong revenues. These revenues are what should be deployed for developer incentives.
I disagree with the social contract of 30k hardcap.
Bitcoin has the same mindset, and they’re getting blown out of the water by Etehreum because of it. 3% ownership to devs is more important than that social contract. Our job should be to have minimal viable issuance, just like Ethereum, in my opinion.
What’s the logic here? Let’s not be Bitcoin. This idea of hard caps for start-ups is very romantic but not necessarily the best execution path for maximal value. I’d rather have a smaller piece of a bigger pie, so long as my piece is bigger than the altnerative.
Love the proposal you & co put up–thank you. I agree–we should strive for minimal viable issuance, and be extremely hesitant about the minting of any additional coin.
If the community is willing to give up all revenue to our developers for the foreseeable future, that may solve the problem. I am not sure if it will though–it’s been three months since Watkin’s proposal and nothing has happened.
Completely agree. Minimal viable issuance is a must–and we want to make sure any additional issuance is conducted extremely wisely. I just hate the Bitcoin idea of a hard cap–they’re going to lose to Ethereum because of their ossification. It’s an idea worthy of pursuit, but I’ve never seen a successful startup not conduct additional equity issuance along the way.
I am in FULL support of giving YFI to Core Dev’s. I have a tremendous amount of respect and gratitude for each and every one of them. Moreover, I hold all Designers, Researchers and Content creators in the same light.
However, I do not agree with minting more YFI.
I have just read and voted ‘FOR’ a proposal that outlines all YFI rewards be redirected to buying back YFI. I would amend the above proposal to allow this market bought YFI to be redistributed to the Core team.
I simply feel that allowing minting of any kind sets president that opens the doors to future abuse.
I am still a proponent of burning the keys.
With the buy back policy, I believe there will be more than enough YFI to be redistributed.
Price fixes any supply concerns and this approach aligns incentives on all sides.
Revenue will fix itself when v2 launches.
The lacklustre in rewards imo has simply been people withdrawing to purse yield elsewhere.
Opacity around v2 capability with respect to yield (while understandable) is also not helping.
So to reiterate. v2 launch = clarity on capability = more excitement = more participation = more revenue for yearn = more YFI bought = YFI price up = more value for Core team AND holders.
the use of wholly inappropriate phrases like “indentured servitude” to describe something completely diffetent, and
name dropping Andre without evidence he would participate in the incentive / bonus pool / whatever the minted YFI would become.
Andre has rejected previous attempts by the community to gift or compensate him for his efforts. Absent a statement from him, it seems reasonable to expect the same outcome would happen again.
Moreover, there is a question of how incentives are structured for fair long term compensation. Would JPM hire the current dev team and compensate them handsomely? Maybe. Would they let the team define their own incentive structure? Obviously not. They would be vested over time and based on milestones or similar objective criteria. Some here dislike that idea, but a carte blanche approach has a high risk in case a team member pulls a Gi***r.
Let’s see how the buyback plan goes first. But I just want to highlight few points about this:
The proposal is actually not a bad idea. If no other plan can fairly compensate the core devs, then we need to look into this option.
@undefinedza comment here is very true and challenging one. But maybe we could workaround that by communicating it properly:
Yearn community is a progressive and pragmatic one. Decisions change as needed to fit the dynamic challenges.
The counter meme that we are the Ethereum of Defi not Bitcoin (as @yfi_lit mentioned)
There is another point which I don’t know if it’s possible: Is it doable to mint 1k YFI then introduce some mechanism in the future to burn up to 1k YFI? In this way the 30K cap will hold true most of the time, with some capital reallocation mechanism, if needed.