Antioch_Council0_Report_20-04-2021.md 12 KB

Antioch - Council Election Round #0 - 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: #1
  • Start Block: #0
  • End Block: #86400
  • 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
@seainvestor 684 10
@blackmass 361 4
@l1dev 515 8
@anthony 129 0
@freakstatic_council 321 12
@nexusfallout 4 12
@cheomsk 552 12
@tomato 2 12
@technical 1058 8
@sparky 319 0
@manipal 355 0
@sasha 1015 11
Total Stake 0

1.4 - Council Roles

1.5 - Council Mint & Budget Status

  • Start minted: 0 tokens
  • End minted: 8898885 tokens
  • Total minted during council round: 8898885 tokens (+100% from start)

    • Minted from Spending proposals: tokens
    • Minted for CM payments: tokens
  • Budget proposal link: N/A

  • Budget forum link: N/A

(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

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

Proposal States

  • 7 Approved & executed proposals
    • Token value of spending proposals: 5982797 tokens
  • 2 Canceled proposals
  • 0 Rejected proposals
  • 0 Slashed proposals
  • 5 Expired proposals
  • 1 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

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

  • Total time for proposals to finalize: 958.31 hours

  • Average time for proposals to finalize: 79.85 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 1 - We need to hire new leaders

Proposal 2 - We need to hire new leaders

Proposal 3 - We need to hire new leaders

Proposal 4 - Storage Mint Initial Fill

Proposal 5 - Curator Mint Initial Fill

Proposal 6 - Resub: Com Repo Banner Competition Prop

Proposal 7 - Antioch - KPI 0.2 - Council Secretary

Proposal 8 - Resub: Hire for role: Bounty 10 Admin

Proposal 9 - Success Event 1 for Bounty 13

Proposal 10 - Success Event 1 for Bounty 13

Proposal 11 - Storage Mint Initial Fill - Resubmission

Proposal 12 - Sudo request to proceed to vote stage

Proposal 13 - Storage Lead Opening

Proposal 14 - Forum Rewards funding

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