The first implementation of the Spartan Council provided for by SIP-93, “Supersede SIP-90 to Delegated Council Governance,” has resulted in a successful first round of voting with some outstanding issues to be addressed.
Issue 1. Stability. The top 7 council members by Weighted Debt vote has shifted like quicksand, with a tiny fraction of 1 WD showing an ability to add or remove a member from the council. This can create logistical problems, and leads to a situation where a council member can go to sleep, wake up in the morning, and no longer be on the council.
Pragmatically this creates completely unnecessary overhead. It also produces a situation where an 8th member must always be “on-call” to participate at a given moment’s notice and not be compensated. Furthermore, given that such a small WD can shift the council composition, the scenario is not “game theoretically stable” as noted by Spreek.
Issue 2. Liquidity. The council needs a mechanism whereby the council and/or its members can be declared invalid by Token Holders. If no such mechanism exists, the council cannot be said to be liquid.
To retain structure and composition for the Council, votes for candidates will be locked through the duration of the epoch (1 month.) This allows for the council composition to reach a stable state. This is how we solve for stability.
Recall votes. If a sufficient number of token holders are wholly dissatisfied with the Council’s performance, token holders can elect to dissolve the Council in its present form with 2/3 vote. Token holders can reach out to Council members directly to have their concerns and interests represented, but a recall provides a formal mechanism for an inadequate Council to be dissolved. This recall would precede the formation of a new Council after the non-performant members are relieved of duties.