Giza_Council45_Report.md 13 KB

Giza - Council Election Round #47 - Performance Review and Minutes

1 - Basic Information

1.1 - Introduction

The council is expected to produce reports during each round and provide feedback in the form of workflow, challenges, thinking and performance as well as minutes covering important events during the council session.

Usernames referenced are Joystream usernames. All times are calculated based on 6.02 second blocktimes and not actual blocktimes. The Council Round number is taken from the chain, the KPI rounds have an offset number.

1.2 - Council Round Overview

  • Council Election Round: #47
  • Council Term: 45
  • Start Block: #4597200
  • End Block: #4697999

1.3 - Council members & vote participation

  • All usernames are listed in the order given by activeCouncil from chain state.
  • Votes cast includes all types of vote (Approve, Reject, Abstain & Slash)
  • In the event a proposal is not finalized within the current council, it will be indicated and current council votes will not be recorded due to system limitations
Username Member ID Prop. Votes Cast CM Own Stake CM Voter Stake
@adovrn 2502 16 1000 45000000
@lkskrn 644 4 40000100 0
@xfactorus 635 11 28810000 10000000
@freakstatic_council 321 7 50000000 1111
@leet_joy 957 16 1000 55000000
@oxygen 3029 16 1000 55000000
@chiffah 2462 9 1000 56500000
@tomato 2 9 30000000 12000000
@maxlevush 2130 11 5600000 47000000
@jen4ph 3234 14 1000 57000000
@isonar 2182 3 37000000 0
@marat_mu 2154 12 40000000 15000000
Subtotal: 231415100 352501111
Total: 583916211

1.4 - Council Roles

  • Council Secretary
    • None
  • Council Deputy Secretary
    • None

1.5 - Council Mint & Budget Status

(Note: The council budget is now based on the rewards for roles, council payments and validator payments. Jsgenesis decides how much to set the mint to.)

2 - Minutes

2.1 - Proposal Overview

Proposal Types

  • 21 Proposals Created
    • 7 Text Proposals
    • 7 Spending Proposals
    • 0 SetWorkingGroupLeaderReward Proposals
    • 7 SetWorkingGroupMintCapacity Proposals
    • 0 BeginReviewWorkingGroupLeaderApplication Proposals
    • 0 TerminateWorkingGroupLeaderRole
    • 0 FillWorkingGroupLeaderOpening
    • 0 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 0 RuntimeUpgrade

Proposal States

  • 15 Approved & executed proposals
  • 0 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 0 Expired proposals
  • 5 proposals passed to next council
    • These proposals didn't gather enough quorum in the current council term, so the votes are reset and passed to the next council.

Failed Proposals

  • 0 NotEnoughCapacity failures
  • 1 ExecutionFailed

  • Total time for proposals to finalize: 324.30 hours

  • Average time for proposals to finalize: 20.27 hours

    • This average is calculated from all proposals, including expired proposals but excluding canceled proposals.

2.2 - Proposal Breakdown

Proposal 1202 - Distribution mint refill

Proposal 1203 - Builders mint refill

Proposal 1204 - Builders Report 44

Proposal 1205 - Re: Payment for community tools

Proposal 1206 - operations Beta mint refill

Proposal 1207 - KPI 44.I-4 - Council Minutes

Proposal 1208 - curators WG refill

Proposal 1209 - Payments for Bounty #24 (22th Week)

Proposal 1210 - Bounty 18. Payments. 27-th week.

Proposal 1211 - Refill Storage WG mint

Proposal 1212 - Weekly Beta operations WG Report 2

Proposal 1213 - Weekly Storage WG Report 38

Proposal 1214 - Weekly CWG Report 45

Proposal 1215 - CWG OKR rewards

Proposal 1216 - Curator Lead OKR

Proposal 1217 - add to Atlas

Proposal 1218 - Refill CWG mint

Proposal 1219 - Refill DWG mint

Proposal 1220 - Re: Re: Payment for community tools

Proposal 1221 - Beta Operations WG spending request

Proposal 1222 - Memo: Appointing Kate_fm - Beta Deputy

4 - Obligations

Council obligations are payments or items that carry through council sessions. These are noted so that future councils can easily see what items they should be aware of. Items can be removed from here once they have been resolved or become outdated.

4.1 Current Documents / Processes

  • Council Report
    • Each council should produce a report which highlights important events, council participation, mint spending and other important facts surrounding the council term
  • Council Budget
    • This is a proposal which tries to guide how many tokens the current council may have available to it during a term. This is a non binding proposal, so is mainly used as a guide for now.

4.2 Regular Payments / Proposals

  • Council Mint
    • The council mint needs to be checked on a regular basis and in the event it is near depletion, a council member should notify a member of Jsgenesis in order for it to be refilled.
    • The council mint is set at a value decided by Jsgenesis.
  • Council Roles
    • Council Secretary
      • This role was introduced in Council Round #18 and the payments are now managed by KPI rewards.
  • Content Curator Mint
    • The Content Curator Mint currently has a maximum value of 5 million tokens.
    • The Content Curator Mint has to be filled periodically and the agreed amount was discussed earlier. The amount may change in the future, but the rewards for this role are dependent on the council passing these proposals in a timely fashion.
    • The Content Curator Lead role is expected to keep track of their mint level and any member of the Joystream platform can create a proposal to refill this mint.
  • Storage Mint
    • The Storage Mint currently has a maximum value of 5 million tokens.
    • This mint has be refilled periodically
    • The Storage Lead role is expected to keep track of their mint level and any member of the Joystream platform can create a proposal to refill this mint.

4.2 Bounties

5 - Report changelog

  • October, November 2021

    • proposals refactor, show amount for spending proposals
    • merge council report script into tokenomics generator (PR #485)
  • 04.11.2020

    • added working group review section
  • 22.10.2020

    • updated budget section to reflect nature of new budget system
    • updated events to be threads & events
  • 14.09.2020

    • removed member addresses and replaced with member IDs since they take less space
    • added realized and unrealized spending