Home Explore Help
Register Sign In
Operations
/
community-repo
3
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Branch: master
Branches Tags
community-repo
/
council-reports
/
antioch-reports
/
Antioch Council 1 Report - 28-04-2021.md

Antioch Council 1 Report - 28-04-2021.md 18 KB
Permalink History Raw

Antioch - Council Election Round #1 - 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: #118800
  • End Block: #277200
  • 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 16 1000 5135500
@blackmass 361 3 3000000 2000000
@l1dev 515 9 1000000 5000200
@supunssw 318 6 2000000 1000000
@doppelganger23 2039 20 2000 2560000
@freakstatic_council 321 26 1000000 5100100
@leet_joy 957 22 299500 6000000
@fierydev 439 20 10000000 0
@leopold 1295 13 1156 2515000
@nexusfallout 4 23 9900000 0
@cheomsk 552 26 2000 2650600
@tomato 2 26 525000 5100000
@2themoon 1989 20 1000 2510000
@sparky 319 0 3000000 0
@lopegor 1369 25 420000 6167300
@manipal 355 0 1231200 5000000
Total Stake 83121556

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

  • 27 Proposals Created
    • 8 Text Proposals
    • 9 Spending Proposals
    • 0 SetWorkingGroupLeaderReward Proposals
    • 1 SetWorkingGroupMintCapacity Proposals
    • 1 BeginReviewWorkingGroupLeaderApplication
    • 2 TerminateWorkingGroupLeaderRole
    • 5 FillWorkingGroupLeaderOpening
    • 0 SetValidatorCount
    • 1 AddWorkingGroupLeaderOpening
    • 0 SetElectionParameters
    • 0 RuntimeUpgrade

Proposal States

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

  • 2 ExecutionFailed

  • Total time for proposals to finalize: 555.97 hours

  • Average time for proposals to finalize: 23.16 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 19 - KPI 00.1 - Tokenomics Report

Proposal 20 - Storage Lead Opening

Proposal 21 - Antioch KPI 1.7

Proposal 22 - Antioch - KPI 1.2 - Council Secretary

Proposal 23 - Resub: Forum Rewards funding

Proposal 24 - Resub: Forum Rewards funding

Proposal 25 - Antioch KPI 1.7

Proposal 26 - Fire the placeholder curator lead

Proposal 27 - Bounty #13: Example Discord Bot

Proposal 28 - Builders Group

Proposal 29 - Resub: Hire Curator Lead

Proposal 30 - Antioch KPI 00.1 - Council Report

Proposal 31 - Fire the placeholder storage lead

Proposal 32 - Bounty Discussion - Proposal Bot

Proposal 33 - Begin review of storage lead apps

Proposal 34 - Bounty 14: Submission 1

Proposal 35 - Bounty 14: Submission 2

Proposal 36 - Sudo request to proceed to vote stage

Proposal 37 - Bounty 14: Submissions 3-7

Proposal 38 - Fire for role: Bounty 10 admin

Proposal 39 - Select Storage Lead

Proposal 40 - Bounty 14: Submission 8-13

Proposal 41 - Bounty 14: Submission 14

Proposal 42 - Hiring Storage Lead

Proposal 43 - Antioch KPI 1.8 - Antioch WG Budget 1

Proposal 44 - Storage Lead

Proposal 45 - Fill Working Group Mint Capacity

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