CIP-9 Updatable params require a hard-fork event? Should be soft-fork. about cips HOT 5 CLOSED

Hey, that's not quite how it works. In the discussion thread, I believe Duncan really meant '5' and not '4', as the current quorum parameter is set to 5.

What Duncan explains in this comment is that a hard-fork ships with a code change, so a super majority of nodes must have adopted the code change before the genesis delegates pull the trigger and submit/vote a proposal. This is effectively done by submitting an protocol parameter update that increase the protocol major version.

In a comparison, a soft fork is merely updating an existing parameter, within the existing semantic known to all nodes. So there's no particular need for synchronization. Every node will keep working the same after the parameter update, there's no need to ship a code update.

from cips.

They are in different CIPs @ch1bo:

• Alonzo -> CIP-0028
• Babbage -> CIP-0055

With the CIP-0001's rework, we are also planning some better categorization of the CIPs which should help to find those. We could also have them reference one another to ease navigation.

from cips.

@ccgarant with the answers to the questions above, and the merged #370 linking the proposals together as in #369 (comment), would you be satisfied if we close this one?

from cips.

Thanks for reviewing @KtorZ.

I guess from reading the CIP, it's not abundantly clear what exactly are the benefits of the updatable vs non-updatable parameters. I feel like there should be more explicit ultra-clear delineation between the two. Currently they seem to be exactly the same from the text.

Also, there seems to be misinformation around the updatable param updates requiring 4 signatures. I am among them 😅.

A clarification update and public info sharing would probably go a long way for us Normies.

from cips.

I just realized that CIP-9 is a bit out-of-date as well. At least it does not include updates of Alonzo and Babbage?

from cips.