Only some changes, need “implementation in the node”. The ones currently discussed only need a parameter update which can just be issued by the signing authorities, governance key holders, IOG, CF, and Emurgo.
In fact, that changes to minPoolCost and k are possible without new node version and without a hard fork was one of the reasons I remember that the poll focussed on these.
Changes that some would have preferred – such as replacing minPoolCost by a minPoolMargin or completely overhauling the reward sharing scheme, making pledge really relevant etc. pp. – would need implementation, installation by SPOs, and a hard fork.
Well, the target date for enactment in
really sounded like we are much further in this process.
And the process itself is not that complicated. It’s signing a trancaction that replaces a 340 with a 170 with enough governance keys and throwing it on the chain. Period. Hopefully this involves some authorised people going to some kind of vault where those keys are stored – so, more involved than me selling an ape on jpg.store, but not that much more involved.
That IOG, CF, and Emurgo should need yet another round of “dialogue” about everything from “their perspective” after all this, after everybody and their dog made up their mind about it weeks and months ago, would be a huge disappointment for all the waiting SPOs for sure.