Domovská stránka Prehľadávať Pomoc
Registrovať Prihlásiť sa
Operations
/
community-repo
3
0
Fork 0
Súbory Issues 0 Pull requesty 0 Wiki
Branch: validator-logging-tool
Branche Tagy
community-repo
/
council-reports
/
babylon
/
Babylon Council 12 Report - 18-03-2021.md

Babylon Council 12 Report - 18-03-2021.md 19 KB
Permanentný odkaz História Raw

Council Election Round #12 - 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 second blocktimes and not actual blocktimes. The Council Round number is taken from the chain, the KPI rounds have an offset number.

This report was compiled by @tomato with assistance from @freakstatic

1.2 - Council Round Overview

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
@blackmass 361 17 14300000 0
@l1dev 515 25 500000 1001000
@anthony 129 14 12000000 1200000
@supunssw 318 7 10000000 0
@freakstatic_council 321 28 500000 1000000
@fierydev 439 22 9000000 100
@nexusfallout 4 18 7056000 0
@cheomsk 552 28 55000 1402000
@tomato 2 26 750000 1201000
@sparky 319 0 17000000 0
@manipal 355 0 500000 3000000
@sasha 1015 17 1100000 510000
Total Stake 82075100

1.4 - Council Roles

1.5 - Council Mint & Budget Status

  • Start minted: 133482776 tokens
  • End minted: 162825566 tokens

  • Total minted during council round: 29342790 tokens (+21.98% from start)

    • Minted from Spending proposals: tokens
    • Minted for CM payments: tokens

  • Budget proposal link: N/A

  • Budget forum link: https://testnet.joystream.org/#/forum/threads/321

(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

  • 29 Proposals Created
    • 9 Text Proposals
    • 17 Spending Proposals
    • 2 SetWorkingGroupLeaderReward Proposals
    • 0 SetWorkingGroupMintCapacity Proposals
    • 0 BeginReviewWorkingGroupLeaderApplication
    • 0 TerminateWorkingGroupLeaderRole
    • 0 FillWorkingGroupLeaderOpening
    • 0 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 1 RuntimeUpgrade

Proposal States

  • 21 Approved & executed proposals
    • Token value of spending proposals: 9600000 tokens
  • 1 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 3 Expired proposals
    • Token value: 4720000 tokens
  • 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

  • 1 NotEnoughCapacity failures
    • Token value: 5000000 tokens

  • 0 ExecutionFailed

  • Total time for proposals to finalize: 882.1 hours

  • Average time for proposals to finalize: 38.35 hours

    • This average is calculated from all proposals, including canceled and expired proposals.
    • Proposals which are not successfully voted by the current council are considered finalized at the final blockheight of the current council. So if the current council has 50 hours to vote on proposal, but does not fully vote and the proposal is passed onto the next council, this 50 hours is included in the average time to finalize.

2.2 - Proposal Breakdown

Proposal 178 - Exclusive stickers for telegram

Proposal 179 - KPI 11.2 - Tokenomics Report

Proposal 180 - KPI 11.2 - Council Report

Proposal 181 - Competition 1 - Amendment to rules

Proposal 182 - KPI 12.5: Managing the Working Groups

Proposal 183 - Refill Storage Working Group mint

Proposal 184 - JoystreamStats APIv1 (weeks 8+9/21)

Proposal 185 - Curators Working Group MINT

Proposal 186 - PR: API examples and Curator tools

Proposal 187 - KPI 12.3 - Appoint New Council Secretary

Proposal 188 - KPI 11.4 - Late Report

Proposal 189 - KPI 12.5 - WG Report + Tasks

Proposal 190 - Refill Content Working Group Mint

Proposal 191 - Informal Role Hiring: Bounty 10 Admin

Proposal 192 - KPI 12.7 - Weekly Bounty Report A

Proposal 193 - Bounty #12: Deploy Reliable Endpoints

Proposal 194 - FM launch questionnaire - KPI 12.4

Proposal 195 - KPI 12.4 - FM launch questionnaire

Proposal 196 - Stickers

Proposal 197 - Re: JoystreamStats APIv1 (weeks 8+9/21)

Proposal 198 - Request for refund of missed payments

Proposal 199 - Faucet bot was updated

Proposal 200 - Application for the sticker contest

Proposal 201 - Draw Joystream

Proposal 202 - Joy stream flight to the moon)

Proposal 203 - Runtime Upgrade Proposal

Proposal 204 - Bounty 9 - Payout A

Proposal 205 - Bounty #12: Deploy Reliable Endpoints

Proposal 206 - KPI 12.7 - Weekly Bounty Report B

2.4 - Select threads & events

  • N/A

2.5 - Working Group Spotchecks

  • Storage Role Spot Check: (this wasn't performed during the council session)
  • Curator Role Spot Check: (this wasn't performed during the council session)

3 - Review

3.1 - Workflow, Performance, Challenged & Thinking

  • @tomato
    • The increased council size doesn't seem to have affected how long proposals take to pass. I was expecting that proposals might be quicker to be voted on but this isn't the case. It does look as if many proposals sit in a period of waiting for one final vote to finalize, this may just be down to the current council.
    • The concurrent proposal limit has been a severe restriction on many things. Even though its being addressed soon it does highlight the importance of having tools for CMs to know which proposals are active and require votes. It also highlights that it isn't viable to try and rush through proposals since the time for quorum remains about the same. It seems as though anyone submitting a proposal for "platform purposes" (such as refilling a WG mint or submitting a report) should submit these knowing they take about 34 hours and while it is possible to ask for things to be voted in sooner, it isn't reliable to do so.
    • The council processes are still developing and its clear that over time they will improve. For now incorporating all of these processes and making things fair for all participants on the platform (ex. ensuring people get a say about bounties before they are published) take a serious amount of time. The time required for these things isn't easy to define but its obviously something to take into consideration when trying to adjust things or to create a new bounty.
    • I've started creating calendars for each council session which paint a clearer picture of not only KPI deadlines but what areas of the council need more attention (such as reports). There is also a spending proposal overview that I'll be trying to issue after each council term which goes a long way in helping to understand what the council mints tokens for. These two documents as well as the council report, tokenomics report and eventually some other documents look as if they will become core components in communicating well what it is that the council does.
    • Towards the end of the term, it appears the council voting slowed down quite a bit
    • Creative proposals being submitted seems to cause people to not want to vote. This can be better managed by creating more competitions with managers in the future.
    • We're still facing some issues with inactive council members, there were 2 CMs who didn't vote on any proposals this term (https://joystreamstats.live/councils)

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 current payment is 2 million tokens per council round
  • 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

  • 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