Blue Cockatoo on Warpcast

Content pfp

0 reply

18 recasts

21 reactions

Blue Cockatoo pfp

I wanted to see how much damage overstaking is doing so I finally sat down and figured out how to write a Dune query. Since this is my first query, I welcome someone checking my figures/calculations, but it looks pretty valid to me. If you don't want to click through, here's the results as I write: Lost Allowance Amount: 392,174 Total Overstake Amount: 33,989,745 Total Locked Amount: 390,023,685 Below Allow. Cap Above Allow. Cap % of Stakes 81 19 # of Stakers 6,736 47 Staked Amt. 315,298,133 74,725,552 So about 9% of allowances are lost that could have been distributed to smaller stakers because of overstaking. Some people may think that's no big deal, but it is to me. Small stakers need all the help they can get and their allowances will continue to go down as more people lock up their DEGEN. They are stuck for 3 months like this... https://dune.com/queries/3912382

17 replies

3 recasts

9 reactions

Jonas ツ pfp

The craziest part of this is that you could've not had these user errors, or manipulation through under/over-tipping, or any of it, if you had what a 1st semester design student could've explained: List all the things you don't know. Spend 1.5 day educating yourself about them. Could be reading the many observations of perverse incentives in groups, human unintentional error spiles for systems without direct cause / effect state reactions, etcetera

2 replies

0 recast

0 reaction

Mkkstacks pfp

This is what stands out to me. I consider game theory and how working together can produce better outcomes. We had a chance to chime in about parameters, but I think more time to understand implications and potential outcomes could have helped. And more information about how it might all work. Decision and implementation felt rushed. I haven't locked any degen because I'm not comfy making the decision yet.

1 reply

0 recast

1 reaction

Blue Cockatoo pfp

We had some input but a lot of it was ignored. I encouraged no locks, myself, and Jacek actually responded that my idea was good, but obviously it wasn’t what he went with. None of the implementation details were discussed publicly until the lock was already set up and released. People could have pointed out these flaws if given a few days to think about it, but with a 3 month lock, once people started aping in millions it was too late to change anything. It’s just a really amateur way to do something this important. And almost seems predatory if it’s not just inexperience. Locks are just bad for everyone but the devs and whales who get in first.

1 reply

0 recast

1 reaction

Jonas ツ pfp

Sounds about right for a poorly managed / rushed, open source-ish, bullshit process My problem with a velocity-horny-“just ship your way through it” ethos is that it’s very often the best option in normal cases, but since nerds make it a whole-ass philosophy, the train sometimes run through an elementary school

0 reply

0 recast

0 reaction