Start activation target is 75% of pool stake. Not 90-95%.

👍🏼

Thanks for your work Chris! Sad to see you retiring as a DRep! To delegators, if you wanna redelegate, please checkout drep.me/martinlang To take a look at my past voting decisions, thx!

🇪🇺 JUST IN: Cardano Foundation urges the EU against expanding MiCA to DeFi and staking, calling for rules based on financial risks rather than technology.

Its the NOW year.

first, can you describe to me what an "unfair amount of money" should be? you know that a stakepool is a business? you know that larger community pools have worked for 6+ years to get delegations? minPoolCost was introduced for a reason. to make the chain basically survive on there own by paying SPOs for there service. its the same with minMargin, but with the difference that it removes the block reward threshold. you make more, i make more. you make less, i make less. minMargin is not there to make SPOs rich. after activation, every SPO must adjust its own parameters accordingly. which i many cases will lead to a reduction or removal of poolCost.

And to anyone who os wondering whats the big deal? With minMargin in place we can remove the minPoolCost threshold for small stakepools. So no entry bar anymore. Every delegator gets the same rewards. minMargin will represent a reasonable value to provide income for pool operators and makes the chain/protocol basically able to survive on its own.

SPOs - we did it! minMargin CIP23 will be fully included in the upcoming Dijkstra Hardfork to PV12 and not in PV13 many months away! Was not easy, but the CoreDevTeam showed that they are listening and are willing to make things possible. ❤️ So a big thank you to the DevTeam, lets keep working together. 🫱🏻‍🫲🏽

Where is the use L and leave k=500 option?

currently in conversations with heads of departments to bring minMargin with PV12 so we can get rid of minPoolCost.

@kenerik No BLS certificate, no incentive to run Leios code, no poolHotVotingKey, no minPoolMargin with PV12 (still fighting)... at some point, a hf blockade by SPOs will not only be a theoretical thing. The dev<>user(SPO) feedback cycle is totally broken. It was never there in the first place tbh. SPOs are always just getting the result, learning from important changes via an SPO call maybe that was not even recorded until recent ones where we debated to make it possible. Once SPOs learn about something and provide feedback about practability, the usual reaction is "ah, sorry but now its too late!". This cannot go on and on and on...

i thought you're 4 days offline?

SPOs needs to be prepared for Leios, bcs the hardware load demand will be much higher compared to now.

YES!

A 1-2week delay would be highly apprreciated by the spo+drep community to get it in. As Alexey said, not really much code.

never buy from a reseller 🤷🏻‍♂️

lets talk via dms

We will try to push full cip23 support to PV12. Its worth a try. I really would not disrupt the current Cardano Delegators with a k change. Thats a very very high risk of delegators leaving the ecosystem during this bear market! Its not a bull market like last time. Cip50 should show what it can do first imo.

Simulation shows it should be way higher than 0.8%. Because some will keep there minPoolCost and many small pools will set it to 0. So a range between 3-8% looks reasonable to keep systems costs the same. And 80% of the rewards are already going to 100% margin pools. They dont care at all.

activating with pv13. will believe it when i have seen an tested it on a testnet 🤣, but very good job @Cerkoryn 👍🏼 cardanoupgrades.docs.interse…