Babylon Council 9 Report - 01-02-2021.md 10 KB

Council Election Round #8 - 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 @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 Backers CM Own Stake CM Voter Stake
@blackmass 361 2 8000000 1810000
@anthony 129 1 8500000 500000
@supunssw 318 0 8000000 0
@freakstatic_council 321 6 9000000 2518100
@fierydev 439 1 5348000 500000
@sparky 319 0 8000000 0
Total Stake 5328100

1.4 - Council Roles

1.5 - Council Mint & Budget Status

  • Start minted: 82964380 tokens
  • End minted: 107567276 tokens
  • Total minted during council round: 24602896 tokens (+29.65% from start)

2 - Minutes

2.1 - Proposal Overview

Proposal Types

  • 14 Proposals Created
    • 4 Text Proposals
    • 9 Spending Proposals
    • 0 SetWorkingGroupLeaderReward Proposals
    • 0 SetWorkingGroupMintCapacity Proposals
    • 0 SetContentWorkingGroupMintCapacity Proposals
    • 0 BeginReviewWorkingGroupLeaderApplication
    • 0 TerminateWorkingGroupLeaderRole
    • 0 FillWorkingGroupLeaderOpening
    • 1 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening

Proposal States

  • 13 Approved & executed proposals
  • 0 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 0 Expired proposals

Failed Proposals

  • 0 NotEnoughCapacity failures
    • Token value: 0 tokens
  • 0 ExecutionFailed

2.2 - Proposal Breakdown

Proposal 105 - Correction of proposal 101

Proposal 106 - KPI 8.1 - Council 01 - Tokenomics Report

Proposal 107 - Babylon Council 1 Report

Proposal 108 - Telegram Sticker Competition Submission

Proposal 109 - Telegram Competition Sticker

Proposal 110 - KPI 09.6 - Joystream Sprocket

Proposal 111 - Increase validator count

Proposal 112 - Add "community ideas" folder to repo

Proposal 113 - Refund: Improvements for Stats Website

Proposal 114 - Reversal of Proposal 101

Proposal 115 - KPI 9.3 - Appoint New Council Secretary

Proposal 116 - Community Bounty #6

Proposal 117 - Upload 90 Movies

Proposal 118 - Refund for missed payments

2.4 - Select threads & events

2.5 - Working Group Spotchecks

  • No Storage Role Spot Check was done

3 - Review

3.1 - Workflow, Performance, Challenged & Thinking

The council has able to avoid expired proposals

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 Documents WIP

  • Tokenomics Reports
    • This is a periodic report which should be produced after each council round has concluded. It should serve as a tool to see the overall economics of the platform.
  • Working Group Evaluations
    • This was introduced in KPI 15.5 and should serve as a way of evaluting the working groups, so far it hasn't been produced fully.

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 1 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