Etusivu Tutki Apua
Rekisteröidy Kirjaudu sisään
Operations
/
community-repo
3
0
Fork 0
Tiedostot Ongelmat 0 Pull-pyynnöt 0 Wiki
Haara: validator-logging-tool
Haarat Tagit
community-repo
/
council-reports
/
babylon
/
Babylon Council 10 Report - 17-02-2021.md

Babylon Council 10 Report - 17-02-2021.md 11 KB
Pysyvä linkki Historia Raaka

Council Election Round #10 - 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

  • Council Election Round: #10
  • Start Block: #1872001
  • End Block: #2073601
  • Forum thread for round feedback: (This was not completed this round)

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 8 8000000 0
@l1dev 515 12 2500000 8500000
@anthony 129 9 5000000 3000000
@supunssw 318 3 6000000 2000000
@freakstatic_council 321 14 17000000 4000000
@tomato 2 14 5000000 4000000
Total Stake 65000000

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

  • 15 Proposals Created
    • 6 Text Proposals
    • 4 Spending Proposals
    • 1 SetWorkingGroupLeaderReward Proposals
    • 2 SetWorkingGroupMintCapacity Proposals
    • 0 BeginReviewWorkingGroupLeaderApplication
    • 0 TerminateWorkingGroupLeaderRole
    • 0 FillWorkingGroupLeaderOpening
    • 1 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 1 SetElectionParameters

Proposal States

  • 13 Approved & executed proposals
    • Token value of spending proposals: 2,885,000 tokens
  • 1 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 0 Expired proposals
    • Token value: N/A tokens

Failed Proposals

  • 0 NotEnoughCapacity failures
    • Token value: 0 tokens

  • 0 ExecutionFailed

  • Total time for proposals to finalize: 291.92 hours

  • Average time for proposals to finalize: 22.45 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 119 - Refill Storage Working Group mint

Proposal 120 - KPI 10.3 - Appoint New Council Secretary

Proposal 121 - KPI 9.2 - Council 02 - Tokenomics Report

Proposal 122 - KPI 9.2 - Babylon Council 2 Report

Proposal 123 - Adjust Curator Lead Reward

Proposal 124 - Increase council size to 12

Proposal 125 - Increase Validator Count

Proposal 126 - Sticker Competition Report

Proposal 127 - Content Curators Mint

Proposal 128 - Proposed New Budget

Proposal 129 - KPI 10.6 - Sticker Competition Plan

Proposal 130 - KPI 10.4 - New Council Payment params

Proposal 131 - Replace offline storage provider

Proposal 132 - JoystreamStats development (weeks 4-6)

Proposal 133 - KPI 10.4 - New Validator Params

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

  • N/A

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