Council Duties Upgrade


#1

Swarm Council Duties Upgrade

Description of the proposed change to the Swarm Network Constitution

This GAP proposes the following changes to the Swarm Network Constitution, to be adopted with a “YES” or rejected with a “NO” vote:

To Update the Swarm Network Constitution section “VIII. Swarm Council A. Duties” from the Original List of Duties to the New List of Duties, both available below for comparison.


Here is the (*)ORIGINAL LIST of Duties as displayed on the web and on the Swarm Network Constitution: https://docs.swarmnetwork.org/the-swarm-network/the-swarm-council / https://docs.swarm.fund/SNC-2019.02.pdf

(*)VIII. Swarm Council A. Duties.

  1. Initiate sensible GAPs.
  2. Ensure that all GABs are compliant with the Purposes.
  3. Administer funding for Governance Actions.
  4. Help prevent use of the Platform for illicit purposes.

Here is the (**)PROPOSED LIST of Duties:

(**)VIII. Swarm Council A. Duties.

  1. Initiate sensible GAPs.
  2. Ensure that all GABs are compliant with the Purposes.
  3. Administer funding for Governance Actions.
  4. Help prevent use of the Platform for illicit purposes.
  5. To commit and contribute in setting up monthly meetings for the Swarm Council.
  6. To attempt attending and contributing to all official (online) meetings that will be organized by the Swarm Council on a monthly basis.
  7. Within 24 hours of a Swarm Council meeting, the Council should release a post to the community forum to be archived and dated, and containing the following information:
    – Agenda items covered during the meeting;
    – Council members present during the meeting;
    – Actions decided upon to be finalized or postponed;
  8. To represent in good faith, the vision, adoption, interests, improvements and value of the Swarm Network and its staking functionalities.
  9. To engage in organizing and coordinating ‘community work groups’, where members are volunteer work of various nature, pitch and develop ideas, and dedicate time towards the adoption and development of the Swarm Network.
  10. To publish all wallet addresses that have access to the multi-signature contract controlling the Swarm Treasury. It is the Swarm Council’s duty to keep an up-to-date identity record of the respective owners of those wallets.
  11. To publish, describe and update on the Swarm Network’s website, a list of all the tools officially developed or being developed by the Swarm Network, their current completion status as well as up-to-date informative material.
  12. To record, archive and make available any invoice, contract, grant or payment being authorized, or paid by the Swarm Network through its Treasury.
  13. To record and preserve details of all future SWM tokens, exchanged by the Swarm Network, for any other units of value as a way of re-balancing its Treasury after a community GAB. To provide details of such exchanges to the community no later than 30 days later.
  14. To commit, to the best of its abilities, in actively researching, evaluating and developing strategies towards the long-term vision and adoption of the Swarm Network, its long-term funding and the utility of its SWM token.
  15. To demonstrate availability to the community, developers and users adopting the Swarm Network.

Purpose and rationale for the constitutional change and its intended outcomes

Many Swarm Network members feel a lack of structure and community engagement at the Swarm Network. Therefore, we believe that the duties of the SNC have come to require an upgrade and to be described in greater detail.

Identify the specific uses for which any Swarm Treasury funds may be expended to support the Governance Action;

This proposal has no request for funds associated with it.

Additional information for Governance Actions requiring the expenditure of Swarm Treasury funds

N/A

Approval

Per SNC-2019-02 Sec X.C “a ballot for a referendum on an amendment to the Swarm Network Constitution is approved when the votes for “Adopt” (“yes”) outnumber the votes for “Reject " (“no”) at the end of the Voting Period.”


#2

Should this not say ‘make’ available?


#3

Yes, likely. I will change it in this post but it’s too late to change in the ballot. It is on the blockchain now.


#4

Maintain as in “keep available”, but whatever is fine.