To define the election process, duties, and compensation of the Community Seats on the stake.link DAO governing council.
Rationale
SLURP-1 formalized the two Community Seats on the stake.link council. However, there are no parameters in place regarding elections, responsibilities, or compensation for participants.
Specification
Election process:
Six month epoch, beginning November 1st, 2023
Two week self nomination window beginning October 2nd, 2023
Self nomination via created “Community Seat Nominations” channel in stake.link official Discord server
Must submit reasoning for running / qualifications, public wallet (for stipend), and social channel ID’s
One week election window beginning October 17th, 2023
Node operator addresses will be blocked from voting for Community Seats
Duties:
The only strict requirement for this position is to vote on all SLURPS posted on Snapshot during epoch.
Desired behaviors:
In addition to voting requirements, it is desired that the Community Seat is actively engaged with the community on the stake.link social channels throughout their duration on the stake.link council. Community Seats are allowed to author, and vote on, their own SLURPS.
Stipend: Community Seats should be compensated with “skin in the game” in order to incentivize active participation. $1,000 of SDL tokens will be paid out to Community Seats for each month served and paid in total at the end of the epoch. (USD value, quoted by the close price of SDL on CoinGecko on the first day of each month)
Removal: After missing two SLURP votes, a Community Seat can be immediately removed from the council at the discretion of the remaining Community Seat. The remaining Community Seat would then propose to remove the absent member and then be ratified by a simple majority of the other seats. Upon ratification, there would be one week for community discussion/self nominations and one week to vote for a new seat to fill the remainder of the term. In the chance that both Community Seats miss a second SLURP vote at the same time, a special election must be held to finish out the remainder of both terms. No other SLURPS are to be formally voted on until the new Community Seats are installed via special election.
If we are in the unlikely and unfortunate event that both community seats have failed to vote for two SLURPs in a row (which is already a bad outcome for the protocol), halting all voting until the seats are dealt with is an even worse outcome, as there could be business critical SLURPs that are then blocked, perhaps hurting the interest of all platform participants. Additionally, this would open up the protocol to indirect governance attacks by way of automatically invoking this process in such circumstances.
Alternatively, if voting proceeds as normal, community will be properly incentivized to quickly replace the seats to ensure proper representation. At the end of the day, the council is 5 of 7, so you’d need all 5 remaining seats to vote “yes” in order for a proposal to pass. If that happened, the outcome would be no different than if it had waited for the newly elected members. If a vote is held and fails, but the the community representatives would have voted “yes” resulting in the vote passing, then the vote can always be reheld again by the newly elected community members.
I therefore see no reason to block holding the vote given the platform maintains maximum flexibility and minimum bureaucracy without this limitation.
This all looks reasonable - I like that the SDL compensation amount is based on USD value.
Just a couple of things:
If someone is removed, how are they compensated? Do they lose all compensation? Or are they paid for the amount of months that they fulfilled their duties? I personally think former is better.
So if one Community Seat is removed can SLURPs still progress? There would just be six our of seven members voting?
In the case of two removals (or one, if this would also stop SLURPs progressing) then there could be a community vote (based on either SDL tokens held or by address) on the SLURP in its place until replacements are found. As @Ryan has said, we don’t want a situation where urgent SLURPs can’t be advanced.
I still think that in the highly unlikely situation where there are two members not voting then we could have a fallback community vote on a SLURP. A bit concerning if there was zero community overview of a SLURP.
I personally like this idea of having a backup plan if community seats were to fail meeting their obligations for any reason and replacing their vote by a community sentiment poll. Thanks for sharing your thoughts
I can live with this just to have a formal framework to move forward, but I will be proposing the abolition of community seats in the future. In my opinion this is not legitimate governance and with the rework of tokenomics we can easily move to a model without differentiating between seats, based on staked SDL.
Updated proposal, with added language regarding prorated compensation and community sentiment votes in instances of both community seats being vacated. Timeline of election process may need to be tweaked by team based on bandwidth. I would still like to push for a Nov 1st epoch start.
Abstract
To define the election process, duties, and compensation of the Community Seats on the stake.link DAO governing council.
Rationale
SLURP-1 formalized the two Community Seats on the stake.link council. However, there are no parameters in place regarding elections, responsibilities, or compensation for participants.
Specification
Election process:
Six month epoch, beginning November 1st, 2023
Two week self nomination window beginning October 2nd, 2023
Self nomination via created “Community Seat Nominations” channel in stake.link official Discord server
Must submit reasoning for running / qualifications, public wallet (for stipend), and social channel ID’s
One week election window beginning October 17th, 2023
Node operator addresses will be blocked from voting for Community Seats
Duties:
The only strict requirement for this position is to vote on all SLURPS posted on Snapshot during epoch.
Desired behaviors:
In addition to voting requirements, it is desired that the Community Seat is actively engaged with the community on the stake.link social channels throughout their duration on the stake.link council. Community Seats are allowed to author, and vote on, their own SLURPS.
Stipend: Community Seats should be compensated with “skin in the game” in order to incentivize active participation. $1,000 of SDL tokens will be paid out to Community Seats for each month served and paid in total at the end of the epoch. (USD value, quoted by the close price of SDL on CoinGecko on the first day of each month). Payments will be prorated in cases of removal or resignation.
Removal: After missing two SLURP votes, a Community Seat can be immediately removed from the council at the discretion of the remaining Community Seat. The remaining Community Seat would then propose to remove the absent member and then be ratified by a simple majority of the other seats. Upon ratification, there would be one week for community discussion/self nominations and one week to vote for a new seat to fill the remainder of the term. In the chance that both Community Seats miss a second SLURP vote at the same time, a special election must be held to finish out the remainder of both terms. In the highly unlikely scenario where both community seats are vacated for a SLURP vote, a community sentiment vote would take place and would act as the two votes.
New version just dropped. Only change is:
“* Votes will be based on reSDL held in wallet at time of snapshot”
Abstract
To define the election process, duties, and compensation of the Community Seats on the stake.link DAO governing council.
Rationale
SLURP-1 formalized the two Community Seats on the stake.link council. However, there are no parameters in place regarding elections, responsibilities, or compensation for participants.
Specification
Election process:
Six month epoch, beginning November 1st, 2023
Two week self nomination window beginning October 2nd, 2023
Self nomination via created “Community Seat Nominations” channel in stake.link official Discord server
Must submit reasoning for running / qualifications, public wallet (for stipend), and social channel ID’s
One week election window beginning October 17th, 2023
Node operator addresses will be blocked from voting for Community Seats
Votes will be based on reSDL held in wallet at time of snapshot
Duties:
The only strict requirement for this position is to vote on all SLURPS posted on Snapshot during epoch.
Desired behaviors:
In addition to voting requirements, it is desired that the Community Seat is actively engaged with the community on the stake.link social channels throughout their duration on the stake.link council. Community Seats are allowed to author, and vote on, their own SLURPS.
Stipend: Community Seats should be compensated with “skin in the game” in order to incentivize active participation. $1,000 of SDL tokens will be paid out to Community Seats for each month served and paid in total at the end of the epoch. (USD value, quoted by the close price of SDL on CoinGecko on the first day of each month). Payments will be prorated in cases of removal or resignation.
Removal: After missing two SLURP votes, a Community Seat can be immediately removed from the council at the discretion of the remaining Community Seat. The remaining Community Seat would then propose to remove the absent member and then be ratified by a simple majority of the other seats. Upon ratification, there would be one week for community discussion/self nominations and one week to vote for a new seat to fill the remainder of the term. In the chance that both Community Seats miss a second SLURP vote at the same time, a special election must be held to finish out the remainder of both terms. In the highly unlikely scenario where both community seats are vacated for a SLURP vote, a community sentiment vote would take place and would act as the two votes.
