Эхлэл Бүгдийг харах Тусламж
Бүртгүүлэх Нэвтрэх
Operations
/
community-repo
3
0
Салаа 0
Файлууд Асуудлууд 0 Хуулах хүсэлтүүд 0 Мэдлэгийн сан
Мод: 2622b037e7
Салаанууд Тагууд
community-repo
/
council
/
reports
/
giza
/
Giza_Council47_Report.md

Giza_Council47_Report.md 11 KB
Түүх Анхны өгөгдөл

Giza - Council Election Round #49 - 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.01 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: #49
  • Council Term: 47
  • Start Block: #4798800
  • End Block: #4899599

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
@ilich 2194 14 1000 40000000
@ars44 2593 14 14000000 5000000
@lkskrn 644 3 40000999 0
@l1dev 515 10 50000000 0
@0x2bc 2098 9 40000000 0
@xfactorus 635 11 29470000 0
@freakstatic_council 321 9 45000000 0
@oxygen 3029 9 1000 35000000
@maxlevush 2130 14 17000000 10000000
@igrex 1048 13 1000 45000000
@isonar 2182 1 40000000 0
@marat_mu 2154 5 40000000 10000000
Subtotal: 315473999 145000000
Total: 460473999

1.4 - Council Roles

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

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

Proposal States

  • 14 Approved & executed proposals
  • 0 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 0 Expired proposals
  • 0 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

  • 0 ExecutionFailed

  • Total time for proposals to finalize: 333.06 hours

  • Average time for proposals to finalize: 23.79 hours

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

2.2 - Proposal Breakdown

Proposal 1235 - Refill Distribution WG

Proposal 1236 - Weekly Storage WG Report 39

Proposal 1237 - KPI 47.I-2 - Council Secretary

Proposal 1238 - 47.I-3 - Deputy Council Secretary

Proposal 1239 - Bounty 18. Payments. 29-th week.

Proposal 1240 - Council Minutes 46 + Builders Report

Proposal 1241 - Payments for Bounty #24 (24rd Week)

Proposal 1242 - Weekly Beta operations WG Report 4

Proposal 1243 - operations Beta mint refill

Proposal 1244 - Weekly CWG Report 47

Proposal 1245 - Weekly Storage WG Report 40

Proposal 1246 - CWG OKR rewards

Proposal 1247 - Curator Lead OKR rewards

Proposal 1248 - Refill CWG mint

2.4 - Selected Threads & Events

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