Home Explore Help
Register Sign In
Operations
/
community-repo
3
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 682e0a1d2a
Branches Tags
community-repo
/
council
/
reports
/
antioch-reports
/
Antioch_Council3_Report_14-05-2021.md

Antioch_Council3_Report_14-05-2021.md 15 KB
History Raw

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

  • Council Election Round: #6
  • Council Term: 3
  • Start Block: #378000
  • End Block: #478800
  • Forum thread for round feedback: N/A

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
@julysake 2124 7 3914300 0
@blackmass 361 4 5000000 0
@anthony 129 7 6000000 0
@xandrell 867 15 10000 3000000
@nkhlghbl 1962 14 50000 3000000
@doppelganger23 2039 8 6000000 3000000
@freakstatic_council 321 14 1000000 6330000
@leet_joy 957 13 2000000 3000000
@fierydev 439 14 6666666 0
@wasabi 1497 13 10000 3100000
@nexusfallout 4 14 7000000 100
@cheomsk 552 10 1000 6000100
@tomato 2 13 1000000 6330100
@masteel 2109 10 60000 3102000
@lopegor 1369 9 1000 1135200
@manipal 355 0 6000000 0
Total Stake 82710466

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

  • 21 Proposals Created
    • 10 Text Proposals
    • 6 Spending Proposals
    • 4 SetWorkingGroupLeaderReward Proposals
    • 1 SetWorkingGroupMintCapacity Proposals
    • 0 BeginReviewWorkingGroupLeaderApplication
    • 0 TerminateWorkingGroupLeaderRole
    • 0 FillWorkingGroupLeaderOpening
    • 0 SetValidatorCount
    • 0 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 0 RuntimeUpgrade

Proposal States

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

  • 2 NotEnoughCapacity failures
    • Token value: 23688100 tokens

  • 0 ExecutionFailed

  • Total time for proposals to finalize: 278.62 hours

  • Average time for proposals to finalize: 17.41 hours

    • This average is calculated from all proposals, including expired proposals but excluding canceled 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 59 - Content Curator opening

Proposal 60 - Community Bounty #4: Telegram Bot

Proposal 61 - Bounty 14: Submission 15-17

Proposal 62 - Antioch - KPI 3.2 - Council Secretary

Proposal 63 - Update Storage Lead reward for Budget 1

Proposal 64 - Update Curator Lead reward for Budget 1

Proposal 65 - Update Curator Lead reward for Budget 1

Proposal 66 - Update Storage Lead reward for Budget 1

Proposal 67 - Update Curator Lead reward for Budget 1

Proposal 68 - Resub: Bounty 14: Submission 15-17

Proposal 69 - KPI 2.5 - Tokenomics report

Proposal 70 - Antioch - KPI 2.5 - Council Minutes

Proposal 71 - Fill Working Group Mint Capacity

Proposal 72 - Antioch KPI 3.x - Antioch WG Budget 2

Proposal 73 - Prize pot for bounty 10 II

Proposal 74 - Re: Community Bounty #4: Telegram Bot

Proposal 75 - Bounty #12: Endpoints May/2021

Proposal 76 - Update Storage Lead reward for Budget 1

Proposal 77 - Update Curator Lead reward for Budget 1

Proposal 78 - Antioch - Storage WG Reporting Reqs 1

Proposal 79 - Antioch - Curator WG Reporting Reqs 1

2.4 - Select threads & events

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

  • 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