Summary

Some small changes in the process of choosing signers should be approved by the community, to acknowledge its validity. Process :

• The multi-sigs are kept by 8 signers, 5 signatures are needed to execute transactions ;
• After 6 month, a new team is needed ;
• The Top3 signers who were the more active in the past period are renewed in there role (if they agree to) ;
• The 4th, 5th, 6th (Middle3) can be candidates for the next team, but need to participate in the renewal vote ;
• The 2 less available signers (Last2) must let their role to new people : they can't apply for the role in the renewal vote, but will be able to do so the next time ;
• Then, the community vote to select amongst candidates (new candidates or former signers) to fill the spots to have a 8 members multi-sig, with a particular attention to the security et efficiency regarding Multi-sig operations.

Details

• First, when the 6 month period is near to its end, data should be gathered to measure the multi-sigs' activity of the team members. Some existing tools using SAFE API are useful in this process.

• Then, the composition of the 3 Tiers of signers is published, and signers have to choose their option (renewal or not) according of the possibility of their respective Tier.

• After a maximum of 3 mandates in a row (congratulations !), a signer must let is role for a period before he can participate to a vote as candidate. Pascal isn't affected by this last condition, until the community evolves from "operation efficiency for building the protocol" mode to a fully decentralized organisation.

• The community should be aware of the security implication of choosing signers : collusion should be avoid, so available data and messages on forums should be looked at, to know if candidates know each others and to measure their implication in the community.

Some conditions to be candidates should be:

• being present in Jarvis' community for some time and being active,
• having a cold wallet that can be used for signing the multi-sigs operations,
• availability, being quite often connected to the internet,
• having a basic understanding of the functioning of Safe multi-sigs, and the capacity to check what you are ask to sign !

Motivations

Expected benefits :

• improvement of multi-sig speed
• we construct on observable facts and experiences
• everyone have a chance : the roles are distributed and fluid
• avoid the "not enough volunteers" problem and the "we must choose among people we don't know" problem that come with the complete renewal of a protocol multi-sigs' team, and avoid the "set in stone" problem of eternal multi-sigs' teams.

Vote

For, process approved. Against, process refused. Abstain.