|Author||Andy T CF|
This SIP proposes to supersede the current SCCP signaling process outlined in SIP-90, with an extended version that features a delegated voting system. Delegated voting is more in line with the preexisting Synthetix Governance framework on Discord while also providing the benefits of Snapshot voting.
Following SIP-90, the existing Snapshot space will be renamed to the “Spartan Council” while an additional snapshot space called “Synthetix Proposals” will be created.
Each space will still have the benefits provided by using Snapshot as covered in SIP-90, however, the strategies and purposes of each space are outlined below:
- Spartan Council - houses the election process of Spartan Council members, will use the existing weighted debt strategy as outlined in SIP-90.
- Synthetix Proposals - a space where proposals will be voted on by Spartan Council members. Council members are assigned 1 vote each.
The current implementation of SIP-90 was too large of a paradigm shift from historical forms of Synthetix Governance, reducing the influence of individuals who have alternative skin-in-the-game (reputation) while providing large SNX holders with a disproportionate amount of voting weight reducing the influence of the majority of token holders.
There are two major components of the new proposed governance system:
- Spartan Council
- Synthetix Proposals
Spartan Council - As a result of SIP-90, we have transitioned into a system that was previously “1 identity = 1 vote” to “1 identity = N votes” while also removing individuals who possess alternative skin-in-the-game from the governance process. The Spartan Council will consist of nominees who are voted in by the Synthetix token holders, re-enabling the influence of community representatives who are able to debate and distill technical changes while also not directly providing large SNX holders a disproportionate voting weight in the outcome of proposals.
Synthetix Proposals - Changes in the protocol (initially SCCPs, but eventually SIPs) that are submitted to the SIPs Github repository will be posted on the Synthetix Proposal space. Proposals must reach an supermajority agreement on a option for it to be enacted.
Within a Council Epoch, votes are liquid, so voters can remove or change their votes at any time.
If a Council Member loses enough votes during a Council Epoch to below a non-member, then the protocolDAO will manually retrieve the NFT from the departing Council Member and issue it to the new Council Member, giving them Council voting rights. This is a manual process, so there may be some lag before the protocolDAO carries this out. The protocolDAO will check the election standings before implementing any successful SCCP (or, in the future, SIP).
Initially, SNX payments to Council Members will be paid manually by the synthetixDAO at the end of a Council Epoch, but there are plans to move to a streaming process. In the case of sufficient Council Member’s votes being pulled out before the end of a Council Epoch to remove them from the Council, they will receive SNX rewards proportionate to their time in the Council during that Epoch, up until the point at which their NFT is retrieved. The replacement Member will receive SNX rewards proportionate to their time in the Council after which their NFT is issued.
Despite the council reaching a consensus on a proposal, the protocolDAO still retains discretion over any changes to the protocol in this version of governance if required. However, this is only a last resort in case of emergency — the processes should all be optimised to minimise this potential occurence. Indeed, all of SIP-93 is intended to minimise the protocolDAO’s discretion.
Any SCCP’s that relate to configuring the values of this SIP will need to be voted on by the Spartan Council members. In order for this SCCP to pass, the Spartan Council must reach an unanimous decision.
Above is the example timeline for the genesis election, with helps understand the terminology of configurable values.
From the feedback acquired in SIP-90 discussions, alternate designs included increasing the quadratic weighting to cubic, considering time when weighing the debt, calculating escrowed balances and other similiar ideas.
Although many of these solutions are valid in reducing the impact of large SNX holders, their outcomes are too different from the status quo of the preexisting governance structure.
The current use of the Spartan Council is more in line with the future goal of delegated voting within the Synthetix system and this SIP aims to slowly iterate towards it.
- Protocol DAO (pDAO) will need to create a modified version (or custom contract) of an NFT which can be revoked and issued to EOA’s (Externally Owned Addresses), signifying a wallet is part of the Spartan Council.
- Modifications to the current “Synthetix” space on Snapshot, to house the Spartan Council Election process.
- Addition of a new “Synthetix Proposal” space that utilizes a new strategy to explicitly count the pDAO issued NFT.
Configurable Values (Via SCCP)
- Council Nominations Deadline - initially set at 48 hours prior to when the Election Period begins.
- Election Period Length - at the end of the Election Period the council members will be issued NFTs (voters may still change their votes within the current Council Epoch).
- Council Epoch - the period after which token holders must redelegate their votes to new and existing council members (to prevent stagnation and ephemeral power) - initially set at 1 month with the genesis election being 1st December 2020 (0:00 UTC)
- Timelock period - period where the proposal is in review before being implemented, initially set at 24 hours.
- Spartan Council seat numbers - the number of seats available on the Spartan Council and thus a supermajority
(N/2 + 1 - if N is even or to Ceiling(N/2) - if N is odd)is the required number for a decision to reach consensus.
Copyright and related rights waived via CC0.