From 404d3a01e004f17548ac0caade13f0b4f02cbb63 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Fri, 28 Jul 2023 12:43:48 +0200 Subject: [PATCH 01/15] Update council_member_election_guidelines --- council_member_election_guidelines | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/council_member_election_guidelines b/council_member_election_guidelines index 8b13789..8bfadd9 100644 --- a/council_member_election_guidelines +++ b/council_member_election_guidelines @@ -1 +1,22 @@ +# Moving towards a fully elected council +The Grin Community Council (CC) originally concisted of four trusted community members with a proven track record and an additional two council members were elected based on community voting. +Based on input from the community, it was decided to move towards a fully elected council while implementing some minimal conditions on community members applying for a position on the council. +To balance a) protection of funds an knowledge in the council and b) moving towards a fully democracy it was decided to implement these guidelines for council member elections. +## Conditions to become a CC members +To become a CC candidate in an electio, a community council member needs to meet the following conditions: +* A proven track record of constructive contribution to Grin as project +* No track record of malicious or toxic activities related to Grin +* A minimum of one year being an active community member + +## Endorsement / support from existing council members +Candidates needs endorsement/support from the majority of the existing Community Council members. In case of six council members this translates to needing support from at least four council members. +To avoid candidates from explicitly having to ask for support, this endorsement is implemented as no-objection unless specified otherwise. This means that unless a council member specically formulates and communicates a public objection to a candidate, it is assumed the council member endorses the candidate. +As in every decisson in Grin governance, proper argumentation needs to be provided for an objection to be considered. Simply objecting because a council member does not like a candidate is not supported. +The above specified minimal requirements and the fails-safe of allowing CC members to object against candidates provides the CC with the tools to protect the functioning of the council, and more importantly, functions to deter any attacker from even considering an attack on Grin governance. + +## Election process +When one or more CC memebrs step down, an election is organised. The CC encourages trusted community members to step forward as council candidates. +Candidates for a CC election can step forward based on an invitated as well as step forward on their own valition. Any community member can become a candidate if he/she/it meets the minimal requirements. +All candidates are asked to put a summary of their candidacy on the forum. If all candidates have postec on the forum, an election period of approximately on month is started in which community members can vote for their candidates. +A list of all candidates with links to their forum post is provided in the newsletter. Voting are tallied by likes of the post by candidates, only accounting votes from community members who are part of the community before the call for a new election was communicated From 83ab86d292a0f45dd4581ea56c4d63fbc044ed2e Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 30 Jul 2023 20:43:39 +0200 Subject: [PATCH 02/15] Update council_member_election_guidelines Edited to remove some of the sloppiness, typos and language errors. --- council_member_election_guidelines | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/council_member_election_guidelines b/council_member_election_guidelines index 8bfadd9..7276eb2 100644 --- a/council_member_election_guidelines +++ b/council_member_election_guidelines @@ -1,22 +1,24 @@ # Moving towards a fully elected council -The Grin Community Council (CC) originally concisted of four trusted community members with a proven track record and an additional two council members were elected based on community voting. +The Grin Community Council (CC) originally consisted of four trusted community members with a proven track record and an additional two council members which were elected based on community voting. Based on input from the community, it was decided to move towards a fully elected council while implementing some minimal conditions on community members applying for a position on the council. -To balance a) protection of funds an knowledge in the council and b) moving towards a fully democracy it was decided to implement these guidelines for council member elections. +With these procedural guidelines and minimal requirements, we aim to a) protect funds, knowledge and experience within the council and b) move towards a fully democratically voted council. ## Conditions to become a CC members -To become a CC candidate in an electio, a community council member needs to meet the following conditions: +To become a CC candidate in an election, a community council member needs to meet the following conditions: * A proven track record of constructive contribution to Grin as project * No track record of malicious or toxic activities related to Grin * A minimum of one year being an active community member ## Endorsement / support from existing council members -Candidates needs endorsement/support from the majority of the existing Community Council members. In case of six council members this translates to needing support from at least four council members. -To avoid candidates from explicitly having to ask for support, this endorsement is implemented as no-objection unless specified otherwise. This means that unless a council member specically formulates and communicates a public objection to a candidate, it is assumed the council member endorses the candidate. -As in every decisson in Grin governance, proper argumentation needs to be provided for an objection to be considered. Simply objecting because a council member does not like a candidate is not supported. -The above specified minimal requirements and the fails-safe of allowing CC members to object against candidates provides the CC with the tools to protect the functioning of the council, and more importantly, functions to deter any attacker from even considering an attack on Grin governance. +Candidates needs endorsement/support from the majority of the existing Community Council members. In case of six council members this translates to needing support from at least four council members, like how any spending decisions requires 4/6 approvals. +To avoid candidates from explicitly having to ask for support, this endorsement is implemented as no-objection unless specified otherwise. This means that unless a council member specifically formulates and communicates a public objection to a candidate on the grin forum, it is assumed that the council member endorses the candidate. +As in every decision in Grin governance, proper argumentation needs to be provided for an objection to be considered. Simply objecting because a council member does not like a candidate is not supported. +The above specified minimal requirements and the fails-safe of allowing CC members to object against candidates, provides the CC with the tools to protect the functioning of the council, and more importantly, functions to deter any attacker from even considering an attack on Grin governance. ## Election process -When one or more CC memebrs step down, an election is organised. The CC encourages trusted community members to step forward as council candidates. -Candidates for a CC election can step forward based on an invitated as well as step forward on their own valition. Any community member can become a candidate if he/she/it meets the minimal requirements. -All candidates are asked to put a summary of their candidacy on the forum. If all candidates have postec on the forum, an election period of approximately on month is started in which community members can vote for their candidates. -A list of all candidates with links to their forum post is provided in the newsletter. Voting are tallied by likes of the post by candidates, only accounting votes from community members who are part of the community before the call for a new election was communicated +When one or more CC members step down, an election is organised. The CC encourages trusted community members to step forward as council candidates. +Candidates for a CC election can step forward based on an invitation as well as step forward on their own volition. Any community member can become a candidate if he/she/it meets the minimal requirements and has endorsement of the majority of the existing council members. +All candidates are asked to put a summary of their candidacy motivation on the forum. If all candidates have posted on the forum, an election period of approximately one month is started and officially announced on the forum. In this period, community members can vote for their candidates. +Votes on multiple candidates are allowed since this can be used to negative vote on any council members he or she does not endorse. +A list of all candidates with links to their forum post is provided in the newsletter once the election period is officially announced. Voting is tallied by likes of the post by candidates, only accounting votes from community members who are part of the community at least one month before the announced election period. + From e362be8f91dccbe5d514d80884e6fbde0de01bd3 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Mon, 31 Jul 2023 16:44:25 +0200 Subject: [PATCH 03/15] Rename council_member_election_guidelines to council_member_election_guidelines.md Added file extension .md --- ...r_election_guidelines => council_member_election_guidelines.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename council_member_election_guidelines => council_member_election_guidelines.md (100%) diff --git a/council_member_election_guidelines b/council_member_election_guidelines.md similarity index 100% rename from council_member_election_guidelines rename to council_member_election_guidelines.md From eff59959aa55414a9134c19e15ee0567c0aa437e Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Mon, 31 Jul 2023 16:46:51 +0200 Subject: [PATCH 04/15] Update council_member_election_guidelines.md Some minor textual improvements --- council_member_election_guidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/council_member_election_guidelines.md b/council_member_election_guidelines.md index 7276eb2..c1b5771 100644 --- a/council_member_election_guidelines.md +++ b/council_member_election_guidelines.md @@ -1,7 +1,7 @@ # Moving towards a fully elected council The Grin Community Council (CC) originally consisted of four trusted community members with a proven track record and an additional two council members which were elected based on community voting. -Based on input from the community, it was decided to move towards a fully elected council while implementing some minimal conditions on community members applying for a position on the council. -With these procedural guidelines and minimal requirements, we aim to a) protect funds, knowledge and experience within the council and b) move towards a fully democratically voted council. +Based on input from the community, it was decided to move towards a fully elected council while implementing some additional safety measurements since a fully elected council is more prone to attack. +We created some procedural guidelines and minimal requirements for council members with the aim to a) protect funds, knowledge and experience within the council while b) moving towards a council consisting of fully democratically voted members. ## Conditions to become a CC members To become a CC candidate in an election, a community council member needs to meet the following conditions: From c13139a0559e9873edf6cdd7388672ea1eb6ab56 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 11:23:51 +0200 Subject: [PATCH 05/15] Update council_member_election_guidelines.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Major rewrite, taking into account feedback on the forum. The aim is to balance democratic and technocratic considerations while maintaining proper security of the funds. I think the document is quite balanced, but any further input, refinement or simplification is appreciated 😄 --- council_member_election_guidelines.md | 46 ++++++++++++++++----------- 1 file changed, 27 insertions(+), 19 deletions(-) diff --git a/council_member_election_guidelines.md b/council_member_election_guidelines.md index c1b5771..36bdc4e 100644 --- a/council_member_election_guidelines.md +++ b/council_member_election_guidelines.md @@ -1,24 +1,32 @@ -# Moving towards a fully elected council -The Grin Community Council (CC) originally consisted of four trusted community members with a proven track record and an additional two council members which were elected based on community voting. -Based on input from the community, it was decided to move towards a fully elected council while implementing some additional safety measurements since a fully elected council is more prone to attack. -We created some procedural guidelines and minimal requirements for council members with the aim to a) protect funds, knowledge and experience within the council while b) moving towards a council consisting of fully democratically voted members. +TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. In case of any unforeseen situation, the CC can fall back to these principals of allowing motions by anyone, but only considering motions when accompanied by proper argumentats. + +# Community council election guidelines +The Grin Community Council (CC) originally consisted of four by the OC appointed trusted community members with a proven track record and two council members which were elected based on public community voting. +Based on input from the community, it was decided to move towards a fully elected council. Having a fully elected CC council is however more vulnerable to attacks, spam and sabotage and unnecessary drama. To protect against such attacks, these guidelines implement additional safety-measures while empowering the community to elect or remove council members. In this document we will outline procedural guidelines for the election process, minimal requirements for council members and minimal requirements for community members to vote with the aim to balance a) protection of CC funds, knowledge and experience within the council and b) enabling community members to elect or remove council members. + +## Election process +When one or more CC members step down, an election is organised. Candidates for a CC election can step forward based on an invitation by CC members as well as step forward without any invitation. Any community member can become a candidate if he/she/it meets the minimal requirements and has endorsement of the majority of the existing council members. +All candidates are asked to put a motivation of their candidacy on the forum. If all candidates have posted on the forum, an election period of approximately one month is started and announced on the forum and publicised via the newsletter with a link to the motivation letter of each candidate. In this period of one month, community members can vote for their candidates. +Community members are allowed to vote on multiple candidates since this can be used to down vote any other candidate(s). +Voting is tallied by likes of the candidacy post. Oly votes from community members who are part of the community before the election period has started and with a minimal Grin forum Trust Level of 1 are counted. ## Conditions to become a CC members -To become a CC candidate in an election, a community council member needs to meet the following conditions: -* A proven track record of constructive contribution to Grin as project -* No track record of malicious or toxic activities related to Grin -* A minimum of one year being an active community member +To become a CC candidate in an election, a community council member needs to meet the following three requirements: +*1) A minimal trust level of 1 on the forum +*2) A proven track record of mainly constructive contribution to Grin as project +*3) A minimum of one year being an active community member -## Endorsement / support from existing council members -Candidates needs endorsement/support from the majority of the existing Community Council members. In case of six council members this translates to needing support from at least four council members, like how any spending decisions requires 4/6 approvals. -To avoid candidates from explicitly having to ask for support, this endorsement is implemented as no-objection unless specified otherwise. This means that unless a council member specifically formulates and communicates a public objection to a candidate on the grin forum, it is assumed that the council member endorses the candidate. -As in every decision in Grin governance, proper argumentation needs to be provided for an objection to be considered. Simply objecting because a council member does not like a candidate is not supported. -The above specified minimal requirements and the fails-safe of allowing CC members to object against candidates, provides the CC with the tools to protect the functioning of the council, and more importantly, functions to deter any attacker from even considering an attack on Grin governance. +## Endorsement by existing council members +Candidates needs endorsement/support from the majority of the existing Community Council members. In the current situation of six council members this translates to needing support from at least four council members. These requirements are in line with the Security and [Funding Approval sheme]([url](https://github.com/grincc/docs/blob/Anynomouss-patch-4/approval-scheme.md)) which defines that any decision regarding funds and security requires 4/6 council members to approve a decision. +To avoid candidates from explicitly having to ask for support, this _endorsement is implemented as no-objection unless specified otherwise_. Any objections must be well formulated and communicates publicly on the grin forum. Any community members can file an objection to a council member candidate. +Like with every decision in Grin governance, proper argumentation needs to be provided for an objection to be considered. Simply objecting because you do not like a candidate will be dismissed. +The above specified minimal requirements and the fails-safe allowing all community members to protect the CC funds. -## Election process -When one or more CC members step down, an election is organised. The CC encourages trusted community members to step forward as council candidates. -Candidates for a CC election can step forward based on an invitation as well as step forward on their own volition. Any community member can become a candidate if he/she/it meets the minimal requirements and has endorsement of the majority of the existing council members. -All candidates are asked to put a summary of their candidacy motivation on the forum. If all candidates have posted on the forum, an election period of approximately one month is started and officially announced on the forum. In this period, community members can vote for their candidates. -Votes on multiple candidates are allowed since this can be used to negative vote on any council members he or she does not endorse. -A list of all candidates with links to their forum post is provided in the newsletter once the election period is officially announced. Voting is tallied by likes of the post by candidates, only accounting votes from community members who are part of the community at least one month before the announced election period. +## Managing the CC Multisig wallet +An additional 1 key is created for any new CC Bitcoin Multisig wallet to be hold by an OC or otherwise trusted community member. In the current setup this translates to a 4/7 Multisig. This extra key protects and deters against attacks on the CC where without this extra key only three council members could take CC funds hostage or even destroy funds simply by refusing to sign any transactions. The key-holder of this extra key will only be asked to sign a transaction if the funding or the functioning of the council is at risk. +To prevent having to generate a new Multisig wallet for all changes in council members, which requires significant coordination and time, a maximum of two keys can be shared by with new council members by their predecessors before generating a new Multisig if deemed safe by the CC. To allow more flexibility in appointment of temporary or long-term CC members, council members can ask a community member to become their representative with voting power while the CC member only maintains their responsibility as key-holder. This is a great option for allowing community member to give Grin governance a try without having to 'commit' for the longer term to the council. In case a representative step down, the key-holder can simply jump to activity again to prevent any disruption to the council’s governance. + +## Review and removal of council members +Upon prolonger inactivity, failure to sign transactions or inability to perform basic CC tasks, any council member can be requested to step down. A review of an existing council member can be initiated by any community member with trust level 1 on the forum. Any decision will be based on proper argumentation and would require 4 out of 6 council members to endorse the request to force a council member from stepping down. In such a decision, other factors like a) the availability of community members to replace a council member b) a representative and key-signing couple, c) other contribution to governance and c) technical contributions such reviewing code or design input, will be considered. +It is adviced to innitiate the review of any council member after serving for four years. Such a review is a good chance to step back, get (re)-invigorated by positive feedback on the forum or simply reflect if and how you want to contribute to the project. From 1ffcb0a20edd46953a59a994b4e4f775cd4513b3 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 11:24:31 +0200 Subject: [PATCH 06/15] Update council_member_election_guidelines.md Added bold to TLDR --- council_member_election_guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/council_member_election_guidelines.md b/council_member_election_guidelines.md index 36bdc4e..9506d47 100644 --- a/council_member_election_guidelines.md +++ b/council_member_election_guidelines.md @@ -1,4 +1,4 @@ -TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. In case of any unforeseen situation, the CC can fall back to these principals of allowing motions by anyone, but only considering motions when accompanied by proper argumentats. +**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. In case of any unforeseen situation, the CC can fall back to these principals of allowing motions by anyone, but only considering motions when accompanied by proper argumentats.** # Community council election guidelines The Grin Community Council (CC) originally consisted of four by the OC appointed trusted community members with a proven track record and two council members which were elected based on public community voting. From 3d101fb40a3ddff30f72a18a90da93bdcf1bf8f4 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 11:25:11 +0200 Subject: [PATCH 07/15] Update council_member_election_guidelines.md typo fix --- council_member_election_guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/council_member_election_guidelines.md b/council_member_election_guidelines.md index 9506d47..3b0eb3f 100644 --- a/council_member_election_guidelines.md +++ b/council_member_election_guidelines.md @@ -1,4 +1,4 @@ -**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. In case of any unforeseen situation, the CC can fall back to these principals of allowing motions by anyone, but only considering motions when accompanied by proper argumentats.** +**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. In case of any unforeseen situation, the CC can fall back on these principals of allowing motions by anyone, but only considering motions when accompanied by proper argumentats.** # Community council election guidelines The Grin Community Council (CC) originally consisted of four by the OC appointed trusted community members with a proven track record and two council members which were elected based on public community voting. From fb7f02f3a68623968a5580ec81a1cf05d374a22d Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 11:27:57 +0200 Subject: [PATCH 08/15] Update council_member_election_guidelines.md typo --- council_member_election_guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/council_member_election_guidelines.md b/council_member_election_guidelines.md index 3b0eb3f..ceb1929 100644 --- a/council_member_election_guidelines.md +++ b/council_member_election_guidelines.md @@ -1,4 +1,4 @@ -**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. In case of any unforeseen situation, the CC can fall back on these principals of allowing motions by anyone, but only considering motions when accompanied by proper argumentats.** +**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. In case of any unforeseen situation, the CC can fall back on these principals of allowing motions by anyone, but only considering motions when accompanied by proper arguments.** # Community council election guidelines The Grin Community Council (CC) originally consisted of four by the OC appointed trusted community members with a proven track record and two council members which were elected based on public community voting. From 29cc5cc81a7073cd066768d7613ce5ba0def4052 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 11:53:21 +0200 Subject: [PATCH 09/15] Update council_member_election_guidelines.md few simplifications --- council_member_election_guidelines.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/council_member_election_guidelines.md b/council_member_election_guidelines.md index ceb1929..4b71113 100644 --- a/council_member_election_guidelines.md +++ b/council_member_election_guidelines.md @@ -1,4 +1,5 @@ -**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. In case of any unforeseen situation, the CC can fall back on these principals of allowing motions by anyone, but only considering motions when accompanied by proper arguments.** +**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. +In case of any unforeseen situation, the CC can fall back on these principals of a) allowing motions by any community member and b) only considering motions when accompanied by proper arguments.** # Community council election guidelines The Grin Community Council (CC) originally consisted of four by the OC appointed trusted community members with a proven track record and two council members which were elected based on public community voting. @@ -27,6 +28,6 @@ An additional 1 key is created for any new CC Bitcoin Multisig wallet to be hold To prevent having to generate a new Multisig wallet for all changes in council members, which requires significant coordination and time, a maximum of two keys can be shared by with new council members by their predecessors before generating a new Multisig if deemed safe by the CC. To allow more flexibility in appointment of temporary or long-term CC members, council members can ask a community member to become their representative with voting power while the CC member only maintains their responsibility as key-holder. This is a great option for allowing community member to give Grin governance a try without having to 'commit' for the longer term to the council. In case a representative step down, the key-holder can simply jump to activity again to prevent any disruption to the council’s governance. ## Review and removal of council members -Upon prolonger inactivity, failure to sign transactions or inability to perform basic CC tasks, any council member can be requested to step down. A review of an existing council member can be initiated by any community member with trust level 1 on the forum. Any decision will be based on proper argumentation and would require 4 out of 6 council members to endorse the request to force a council member from stepping down. In such a decision, other factors like a) the availability of community members to replace a council member b) a representative and key-signing couple, c) other contribution to governance and c) technical contributions such reviewing code or design input, will be considered. -It is adviced to innitiate the review of any council member after serving for four years. Such a review is a good chance to step back, get (re)-invigorated by positive feedback on the forum or simply reflect if and how you want to contribute to the project. +Upon prolonger inactivity, failure to sign transactions or inability to perform basic CC tasks, any council member can be requested to step down. A review of a council member can be initiated by any community member on the forum. Any decision will be based on proper argumentation and would require 4 out of 6 council members to endorse the request for a council member to step down. In such a decision, other factors like a) the availability of community members to replace a council member b) a representative and key-signing couple, c) other contribution to governance as well as technical contributions such reviewing code, will be considered. +It is adviced to innitiate the review for all council member after they served for four years. Such a review is a good chance to get (re)-invigorated by positive feedback on the forum, to step down or simply to reflect on how you want to contribute to the project. From caee07dce685890e86e17740bb9769d6a9b71493 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 12:02:02 +0200 Subject: [PATCH 10/15] Update council_member_election_guidelines.md language fix --- council_member_election_guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/council_member_election_guidelines.md b/council_member_election_guidelines.md index 4b71113..7993f96 100644 --- a/council_member_election_guidelines.md +++ b/council_member_election_guidelines.md @@ -24,7 +24,7 @@ Like with every decision in Grin governance, proper argumentation needs to be pr The above specified minimal requirements and the fails-safe allowing all community members to protect the CC funds. ## Managing the CC Multisig wallet -An additional 1 key is created for any new CC Bitcoin Multisig wallet to be hold by an OC or otherwise trusted community member. In the current setup this translates to a 4/7 Multisig. This extra key protects and deters against attacks on the CC where without this extra key only three council members could take CC funds hostage or even destroy funds simply by refusing to sign any transactions. The key-holder of this extra key will only be asked to sign a transaction if the funding or the functioning of the council is at risk. +An additional 1 key is created for any new CC Bitcoin Multisig wallet to be hold by an OC or otherwise trusted community member. In the current setup this translates to a 4/7 Multisig. This extra key protects and deters against attacks on the CC where without this extra key only three council members could take CC funds hostage or even destroy funds simply by refusing to sign any transactions. The key-holder of this extra key will only be asked to sign a transaction if the funds or the functioning of the council is at risk. To prevent having to generate a new Multisig wallet for all changes in council members, which requires significant coordination and time, a maximum of two keys can be shared by with new council members by their predecessors before generating a new Multisig if deemed safe by the CC. To allow more flexibility in appointment of temporary or long-term CC members, council members can ask a community member to become their representative with voting power while the CC member only maintains their responsibility as key-holder. This is a great option for allowing community member to give Grin governance a try without having to 'commit' for the longer term to the council. In case a representative step down, the key-holder can simply jump to activity again to prevent any disruption to the council’s governance. ## Review and removal of council members From a7772cd20c44561688faa80ea1ed1a5d6e16f4b3 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 12:03:11 +0200 Subject: [PATCH 11/15] Update council_member_election_guidelines.md another language fix --- council_member_election_guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/council_member_election_guidelines.md b/council_member_election_guidelines.md index 7993f96..d6e635f 100644 --- a/council_member_election_guidelines.md +++ b/council_member_election_guidelines.md @@ -1,5 +1,5 @@ **TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. -In case of any unforeseen situation, the CC can fall back on these principals of a) allowing motions by any community member and b) only considering motions when accompanied by proper arguments.** +In case of any unforeseen situation, the CC can fall back on the principals of a) allowing motions by any community member and b) only considering motions when accompanied by proper arguments.** # Community council election guidelines The Grin Community Council (CC) originally consisted of four by the OC appointed trusted community members with a proven track record and two council members which were elected based on public community voting. From cf351c33d6befc1e7f7025deaccaadbac843abdf Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 15:37:27 +0200 Subject: [PATCH 12/15] Rename council_member_election_guidelines.md to election_guidelines.md Shortened file name --- council_member_election_guidelines.md => election_guidelines.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename council_member_election_guidelines.md => election_guidelines.md (100%) diff --git a/council_member_election_guidelines.md b/election_guidelines.md similarity index 100% rename from council_member_election_guidelines.md rename to election_guidelines.md From f7d87765a50f544038712058e2b0ec161b59e67e Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Sun, 6 Aug 2023 15:43:23 +0200 Subject: [PATCH 13/15] Update election_guidelines.md another minor improvement --- election_guidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/election_guidelines.md b/election_guidelines.md index d6e635f..3119c49 100644 --- a/election_guidelines.md +++ b/election_guidelines.md @@ -1,5 +1,5 @@ -**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments (technocratic) are provided while providing proper security to the funds. -In case of any unforeseen situation, the CC can fall back on the principals of a) allowing motions by any community member and b) only considering motions when accompanied by proper arguments.** +**TLDR: these guidelines allow council members to be appointed or removed by any community member (democratic) but only when proper arguments are provided (technocratic) while implementing measure to secure the funds. +In case of doubts, the CC can fall back on these basic principels of a) allowing motions by any community member and b) only approving motions when considered valid based on their argumentation.** # Community council election guidelines The Grin Community Council (CC) originally consisted of four by the OC appointed trusted community members with a proven track record and two council members which were elected based on public community voting. From 98b0c4e7b1f64c867c97368fd1fcdfd489b225f9 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Mon, 7 Aug 2023 15:53:33 +0200 Subject: [PATCH 14/15] Update election_guidelines.md Again, some textual improvements. --- election_guidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/election_guidelines.md b/election_guidelines.md index 3119c49..5f1ba12 100644 --- a/election_guidelines.md +++ b/election_guidelines.md @@ -28,6 +28,6 @@ An additional 1 key is created for any new CC Bitcoin Multisig wallet to be hold To prevent having to generate a new Multisig wallet for all changes in council members, which requires significant coordination and time, a maximum of two keys can be shared by with new council members by their predecessors before generating a new Multisig if deemed safe by the CC. To allow more flexibility in appointment of temporary or long-term CC members, council members can ask a community member to become their representative with voting power while the CC member only maintains their responsibility as key-holder. This is a great option for allowing community member to give Grin governance a try without having to 'commit' for the longer term to the council. In case a representative step down, the key-holder can simply jump to activity again to prevent any disruption to the council’s governance. ## Review and removal of council members -Upon prolonger inactivity, failure to sign transactions or inability to perform basic CC tasks, any council member can be requested to step down. A review of a council member can be initiated by any community member on the forum. Any decision will be based on proper argumentation and would require 4 out of 6 council members to endorse the request for a council member to step down. In such a decision, other factors like a) the availability of community members to replace a council member b) a representative and key-signing couple, c) other contribution to governance as well as technical contributions such reviewing code, will be considered. -It is adviced to innitiate the review for all council member after they served for four years. Such a review is a good chance to get (re)-invigorated by positive feedback on the forum, to step down or simply to reflect on how you want to contribute to the project. +A council member can be requested to step down after prolonged inactivity, inability to sign transactions or inability to perform basic CC tasks. A review of a council member can be initiated by any community member on the forum. However, any decision will be based on the provided argumentation and will require 4 out of 6 council members to endorse the request. It should be noted that for such descission all facts and arguments will be taken in consideration. Other factors like a) the availability of community members to replace the council member b) optional representative and key-signing structure and c) other merits and contribution to governance such reviewing code or high quality input, will be taken into consideration. +It is adviced to innitiate a review for all council member after they served for four years. Such a review is a good chance to get (re)-invigorated by positive feedback on the forum, to step down or simply to reflect on how you want to contribute to the project. From eadafda7631275df31ad437248c1fc31d73b30d5 Mon Sep 17 00:00:00 2001 From: Anynomouss <85170856+Anynomouss@users.noreply.github.com> Date: Fri, 11 Aug 2023 10:49:08 +0200 Subject: [PATCH 15/15] Update election_guidelines.md Made clarifications based on Mac's input: https://forum.grin.mw/t/community-council-restructuring/10658/38?u=anynomous --- election_guidelines.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/election_guidelines.md b/election_guidelines.md index 5f1ba12..939f8f1 100644 --- a/election_guidelines.md +++ b/election_guidelines.md @@ -9,7 +9,7 @@ Based on input from the community, it was decided to move towards a fully electe When one or more CC members step down, an election is organised. Candidates for a CC election can step forward based on an invitation by CC members as well as step forward without any invitation. Any community member can become a candidate if he/she/it meets the minimal requirements and has endorsement of the majority of the existing council members. All candidates are asked to put a motivation of their candidacy on the forum. If all candidates have posted on the forum, an election period of approximately one month is started and announced on the forum and publicised via the newsletter with a link to the motivation letter of each candidate. In this period of one month, community members can vote for their candidates. Community members are allowed to vote on multiple candidates since this can be used to down vote any other candidate(s). -Voting is tallied by likes of the candidacy post. Oly votes from community members who are part of the community before the election period has started and with a minimal Grin forum Trust Level of 1 are counted. +Voting is tallied by likes of the candidacy post. Only votes from community members who are part of the community before the election period has started and with a minimal Grin forum Trust Level of 1 are counted. ## Conditions to become a CC members To become a CC candidate in an election, a community council member needs to meet the following three requirements: @@ -24,8 +24,8 @@ Like with every decision in Grin governance, proper argumentation needs to be pr The above specified minimal requirements and the fails-safe allowing all community members to protect the CC funds. ## Managing the CC Multisig wallet -An additional 1 key is created for any new CC Bitcoin Multisig wallet to be hold by an OC or otherwise trusted community member. In the current setup this translates to a 4/7 Multisig. This extra key protects and deters against attacks on the CC where without this extra key only three council members could take CC funds hostage or even destroy funds simply by refusing to sign any transactions. The key-holder of this extra key will only be asked to sign a transaction if the funds or the functioning of the council is at risk. -To prevent having to generate a new Multisig wallet for all changes in council members, which requires significant coordination and time, a maximum of two keys can be shared by with new council members by their predecessors before generating a new Multisig if deemed safe by the CC. To allow more flexibility in appointment of temporary or long-term CC members, council members can ask a community member to become their representative with voting power while the CC member only maintains their responsibility as key-holder. This is a great option for allowing community member to give Grin governance a try without having to 'commit' for the longer term to the council. In case a representative step down, the key-holder can simply jump to activity again to prevent any disruption to the council’s governance. +An additional 1 key is created for any new CC Bitcoin Multisig wallet to be hold by an OC or otherwise trusted community member. In the current setup this translates to a 4/7 Multisig. This extra key protects and deters against attacks on the CC where without this extra key only three council members could take CC funds hostage or even destroy funds simply by refusing to sign any transactions. The key-holder of this extra key will only be asked to sign a transaction if the funds or the functioning of the council is at risk and has not voting power. +To prevent having to generate a new Multisig wallet for all changes in council members, which requires significant coordination and time, a maximum of two keys can be shared by with new council members by their predecessors before generating a new Multisig if deemed safe by the CC. To allow more flexibility in appointment of temporary or long-term CC members, council members can ask a community member to become their representative with voting power while the CC member only maintains their responsibility as key-holder. This is a great option for allowing community member to give Grin governance a try without having to 'commit' for the longer term to the council. In case a representative step down, the key-holder can simply jump to activity again to prevent any disruption to the council’s governance. Any community member can bring forward an objection to appointment of a representative or innitiate a review of a representative the same way they can for full CC members. Upgrading a representative to a full CC member and key-holder requires a Community Council election. ## Review and removal of council members A council member can be requested to step down after prolonged inactivity, inability to sign transactions or inability to perform basic CC tasks. A review of a council member can be initiated by any community member on the forum. However, any decision will be based on the provided argumentation and will require 4 out of 6 council members to endorse the request. It should be noted that for such descission all facts and arguments will be taken in consideration. Other factors like a) the availability of community members to replace the council member b) optional representative and key-signing structure and c) other merits and contribution to governance such reviewing code or high quality input, will be taken into consideration.