Etusivu Tutki Apua
Rekisteröidy Kirjaudu sisään
Operations
/
community-repo
3
0
Fork 0
Tiedostot Ongelmat 0 Pull-pyynnöt 0 Wiki
Puu: d30828390f
Haarat Tagit
community-repo
/
council
/
reports
/
archived
/
alexandria-testnet
/
Alexandria_Council3_report_05-11-2020.md

Alexandria_Council3_report_05-11-2020.md 11 KB
Historia Raaka

Council Election Round #3 - 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
@hoangptsc 495 11 2000 2050000
@anthony 129 6 5000000 110000
@freakstatic_council 321 10 5000000 1525000
@nexusfallout 4 5 5000000 1515000
@tomato 2 11 4500000 1650000
@sparky 319 4 5000000 20000
Total Stake 31372000

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

  • 13 Proposals Created

    • 6 Text Proposals
    • 4 Spending Proposals
    • 2 SetWorkingGroupLeaderReward Proposals
    • 0 SetWorkingGroupMintCapacity Proposals
    • 1 SetContentWorkingGroupMintCapacity Proposals

  • 11 Approved & executed proposals

    • Token value: 8150000 tokens

  • 2 Canceled proposals

  • 0 Rejected proposals

  • 0 Slashed proposals

  • 0 Expired proposals

    • Token value: N/A tokens

  • 0 NotEnoughCapacity failures

  • Total time for proposals to finalize: 241.86

  • Average time for proposals to finalize: 18.60 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 29 - Council 02 - Tokenomics Report

Proposal 30 - Council #2 report

Proposal 31 - KPI 03.3 - Appoint New Council Secretary

Proposal 32 - Telegram Bot Update

Proposal 33 - Storage Provider Spot Check

Proposal 34 - Content Curator Role Spot Check

Proposal 35 - Proposed budget adjustment

Proposal 36 - Proposed budget adjustment

Proposal 37 - Storage Lead Reward Adjustment

Proposal 38 - KPI 03.6 - Suggested community bounties

Proposal 39 - Storage Lead Reward Adjustment

Proposal 40 - Replenishing the mint tor ContentCurator

Proposal 41 - Replenishing the mint tor ContentCurator

2.4 - Select threads & events

2.5 - Working Group Spotchecks

3 - Review

3.1 - Workflow, Performance, Challenged & Thinking

  • @tomato
    • I think this council session went pretty well. The budgets are becoming more critical to deal with, and because validators are much more stable and with higher rewards there are a lot more changes with it.
    • We also completed our first community bounty for the Telegram bot. Unfortunately it has a few small bugs still but it is at least running once again.
    • Overall we're making good progress with the KPIs, not perfect, but it seems we're starting to achieve most of them
    • Since the new KPI system we haven't had any proposals expire due to lack of votes and most proposals get voted on within a reasonable timeframe, this has been a big help in making more frequent progress.

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

  • There are no outstanding bounties at this time.

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