Reduce the committeeMinSize parameter from 7 to 5

System1mo ago8 posts
Participation47
Reactions10
Last activity15d ago
System1mo ago

On-chain governance action (Parameter Change).

Intersect’s Civics Committee and Technical Steering Committee propose to change the minimum Constitutional Committee size (committeeMinSize) from 7 to 5 in order to improve operational resilience while maintaining constitutional safeguards.The ratification of this Governance Action depends on the enactment of another live Parameter Change Governance Action (gov_action1eqhnsdyf3exhp5mqt7sdjtl7xy69wqg8tvg854psns2jt72cra3qqrcnr8r), which will change a number of Plutus cost model settings in preparation for the van Rossem hard fork.

  • Proposer return address: stake1uyvjdz9rxsfsmv44rtk75k2rqyqskrga96dgdfrqjvjjpwsefcjnp
  • Deposit: 100,000 ADA
  • Submitted: epoch 635
  • Expires: epoch 642

View in explorer

Latam CardanoDRepVoted Yes1mo ago

It's a good idea to provide some buffer by keeping the CC size at 7 but having the minimum at 5. This provides the community the opportunity to react and elect any departing CC member without halting governance.

ADAtainmentDRepVoted Yes1mo ago

It’s really good to have a little more buffer, but the goal should be to get all 7 CC members and not settle for 5 otherwise, we’ll run into the same problem soon.

jonahkochDRepVoted No24d ago

I have a question about how the threshold would be effected if the minimum size was reduced to 5. Does the pram % for ratification of a CC action change depending on the committee size?

From 5 of 7 to 3 of 5 depending on the number of sitting members at the time. Can this be gamed, by a CC dropping off mid voting period for any given proposal?

what happens if CC was to drop down to 6 CC members and have stalemate (tied) results, how would this be addressed?

ADAtainmentDRepVoted Yes24d ago

Thanks for asking this question. There are three different things we should not mix up:

  • committeeMinSize (the parameter being changed here from 7 to 5): the floor of active members below which the CC cannot act at all.
  • CC threshold (2/3): the fraction of sitting members that must vote "Yes".
  • Number of seats (currently 7): explicitly not changed by this action

The action only changes the floor. The 2/3 threshold and the 7 seats stay as they are. The percentage does not change based on the committee size, but the absolute vote count does. (in the governance action text there is a table provided that addresses this)

A drop-off affects the running tally, because ratification is checked at each epoch boundary against the committee state as it stands then. After a resignation, that member's existing votes no longer count for actions that have not yet been ratified, and expired members can no longer vote on gvernance actions.

On the tie question: At 6 members with 2/3, you need 4 "Yes", a 3:3 split would mean 50%, so below 67%. The action is simply not approved by the CC. (There is no tiebreaker and none is needed: threshold not met means the action fails on the CC component, that's it)

jonahkochDRepVoted No22d ago(edited)

Thank you for the detailed response. My current apprehension is the possibility of a split vote that would lead to a ratification impasse, due to a 6 member CC body. This could potentially be very likely if the minimum threshold is reduced to 5. I believe q member would be more likely to resign if they knew governance wouldn't stall upon their departure, even thought the increased risk of impasse was introduced. I'm a big big fan of "can't do harm" rather than relying on the best intentions of others "won't do harm". With the CC minimum size set to 7 the expectations is clear and the risk to inaction is also clearly defined without the need to rely on the best intentions of others or hope we don't end up in a 50% impasse.
By reducing the requirement to 5 we introduce additional states of non ratification from one to two, making inaction (non ratification) a more likely outcome.

ADAtainmentDRepVoted Yes19d ago

My key point was: lowering minSize doesn't add a failure state, it removes one. Today at minSize 7, a single resignation (6 active) means the CC can ratify nothing at all (governance would be stalled, we had that before), and that's the more severe form of inaction.

At minSize 5 the CC keeps working, and only a genuine 3:3 split fails, which is just the 2/3 threshold doing its job at any committee size. So the change makes the CC moreable to act, and not less.

It's also worth remembering what a CC vote actually is: it's not an opinion or preference vote, it's an assessment of whether an action is constitutional. That's a much narrower, more objective question, so a clean 3:3 split is quite unlikely in practice. Members are reading the same Constitution against the same action, not weighing personal preferences. (even though we've seen that before, but not from three CC members at the same time)

jonahkochDRepVoted No15d ago

I'm again I'm in the minority (I voted no for Constitution v2.4), and also voted "No" on this. One of my concerns is we are often not accounting for irrational, and selfish decisions humans make everyday based of emotions, as an example right now, the floor being set at 7 creates a powerful structural incentive to maintain full membership. Every CC member knows that their departure doesn't just reduce quorum, it breaks governance entirely. That feature concentrates accountability, so by lowering the floor to 5 doesn't just create a buffer; it also reduces the cost of resignation for any individual member, making departure marginally easier to rationalize.
Maybe the tie scenario is a washout but it's underweighted IMO. At 6 active CC members with a 2/3 threshold, a 3:3 split fails. With 7 no tiebreaker exists.
The root cause is process, not parameters. The precedent we set is real, once 7→5 passes, the next "operational resilience" argument for 5→3 is structurally identical. The proposal says this isn't the intent, but intent and outcome diverge over time, especially as different governance participants cycle in and out.