{"componentChunkName":"component---src-pages-sccp-sccp-markdown-remark-frontmatter-sccp-tsx","path":"/sccp/sccp-300/","result":{"data":{"markdownRemark":{"fileAbsolutePath":"/vercel/path0/content/sccp/sccp-300.md","frontmatter":{"sip":null,"sccp":300,"title":"Set council minimumActiveMembers to n-1","network":"Optimism","author":"Ethernaut (@theethernaut.eth)","type":"Meta-Governance","proposal":"https://snapshot.org/#/snxgov.eth/proposal/0x8a7aeb398dfa590b46ddcd548f211ac0dd00732a7771074f74cba983a2fe51ca","implementor":null,"release":null,"created":"2022-07-05T00:00:00.000Z","updated":null,"status":"Implemented"},"html":"

Simple Summary

\n\n

Set all councils' minimumActiveMembers setting to n-1, where n represents each council's current seat count.

\n\n

Abstract

\n\n

The current minimumActiveMembers setting is 1 on all councils. With the current code implementation, this setting basically controls, when an \"emergency election\" is triggered upon member dismissal by the council owner. At the moment, the owner of all councils is the pDAO, but in the future it may be other entities, such as the Spartan Council. An emergency election, for the time being, is simply a fast forward in the epoch's Administration period to the Nomination period, without modifying the epoch's schedule.

\n

Motivation

\n\n

Even though this SCCP may trigger a lot of concerns and discussions about the concept of an emergency election, the idea is to leave such discussions for other SIPs, and simply focus on not leaving the parameter at 1 during this epoch. The emergency election feature is clearly pretty raw right now, but having a non 1 value for this setting is a slight step forward.

\n

Copyright

\n

Copyright and related rights waived via CC0.

"}},"pageContext":{"id":"f107814b-0676-5e87-85ab-9e04f0b157ce","frontmatter__sccp":300,"__params":{"frontmatter__sccp":"300"}}},"staticQueryHashes":[]}