Key Performance Indicators (KPIs) define success metrics for the overall testnet system, and will act as an incentive for the Council to do a good job.

Table of Content

Overview

During the Constantinople testnet, we realized that the KPI system wasn't working as intended. Instead of KPIs just being added to the "Fiat Pool", and shared across all tJOY holders, Council KPIs will now only reward the Council Members and their Voters.

Historical KPI information (from the previous testnet) can be found here.

New KPIs will be released for every new Council Term.  The "achievement" of these objectives is evaluated by Jsgenesis.

Current KPIs

For the Third Council on Alexandria, the Council KPIs are as follows:

3.1 - Proposal Clearance

For the governance process to function properly, all proposals must be processed effectively, and in a reasonable time frame to avoiding blocking new proposals coming in.

As this is considered as one the main components of the Councils responsibilities, there are no rewards associated with this. However, failure will trigger an annihilation of all (potential) KPI rewards, and trigger a new election.

Key Value
Reward NA
Active from 23.10.2020 ~23:20 UTC - #460801
Measurement period 14 days (Full Council Term)
Success #1 At no point will the number of active proposal stay at 5 for longer
than 14,400 blocks (~24h).
Success #2 No malicious or unreasonable proposals are approved.
Annihilation Failure will result in the loss of ALL KPI rewards, and a new Council
Election will be started immediately
Grade date 09.11.2020 - 12:00 UTC

3.2 - Council Reporting

There needs to be some level of accountability and transparency for the Council. For each Term the Council must produce a report of 'events' and 'Tokenomics' to allow users make informed votes. This must be submitted as a PR to the Community Repo.

Key Value
Reward NA
Active from 23.10.2020 ~23:20 UTC - #460801
Measurement period 16 days
Success #1 The Third Council on Alexandria (#460801-#662401) produces a
report based on the 'Council Reporting Template' and the
'Tokenomics' script.
Annihilation Unlike other 'annihilations', failure for this KPI will result in
the loss of ALL KPI rewards.
Grade date 09.11.2020 - 12:00 UTC

3.3 - Appoint New Council Secretary

The Council must appoint one of their own as the Council Secretary, responsible for adding Council Reports and representing the Council in the Community Repo, and given triage access.

Key Value
Reward 50 USD
Active from 23.10.2020 ~23:20 UTC - #460801
Measurement period 5 days
Success #1 The Council informally appoints a
Council Secretary through a spending proposal and pays them an
appropriate rate for their responsibilities.
Success #2 The spending proposal must provide a link to the Council Secretary's
GitHub account so we can provide them 'triage' permissions on the
community repo.
Annihilation No Council Secretary is appointed.
Grade date 09.11.2020 - 12:00 UTC

3.4 - Block Production

In order to have a reliable network, a KPI focusing on block production and validator stability is required. Timestamp of each block can be found using the block explorer.

Key Value
Reward 150 USD
Active from 23.10.2020 ~23:20 UTC - #460801
Measurement period 14 days (Full Council Term)
Success #1 The difference between the timestamp of blocks #460801 and #662401 must be less than 1213632000.
Success #2 The total Validator+Nominator stake averages over 15% of total
issuance.
Success #3 The total Validator+Nominator stake averages over 20% of total
issuance.
Annihilation The difference between the timestamp of blocks #460801 and #662401 is over 1219680000, or the total Validator+Nominator stake averages under 10% of total issuance.
Grade date 09.11.2020 - 12:00 UTC

3.5 - Managing the Working Groups

Ensuring a high quality of service delivered by the Working Groups is a key part of the Council's workload.

Key Value
Reward 100 USD
Active from 23.10.2020 ~23:20 UTC - #460801
Measurement period 14 days
Success #1 New budgets are set for each group, taking the 'Recurring
Replenishment', platform inflation and the costs for each role into account.
Success #2 The Council perform spotchecks of working groups' performance, and reports the results.
Annihilation Fewer than two Curators and three Storage Providers (Leads
included) are operating at the end of the measurement period.
Grade date 09.11.2020 - 12:00 UTC

3.6 - Managing Community Bounties

Managing Community Bounties will be a growing part of the Council's workload. Establishing good workflows for this will be iterative and situational.

Key Value
Reward 250 USD
Active from 23.10.2020 ~23:20 UTC - #460801
Measurement period 14 days (Full Council Term)
Success #1 An overview and explanation of the the Community Bounty system
is produced for the Community Repo.
Success #2 Community Bounty #1 - 'Update Telegram Bot', is submitted within
the Council Term.
Success #3 Community Bounty #2 - 'Research and Testing of
polkadot-js extension, is submitted within the Council Term.
Success #4 Community Bounty #3 - 'Improve Telegram Bot(s), is assigned
within the Council Term.
Success #5 The Council presents a list of potential Bounties they think would
be of value for the project
Annihilation Unlike standard annihilations, any rewards paid for a Bounty that
exceeds what Jsgenesis pays will be deducted from the Council's
KPI rewards.
Grade date 09.11.2020 - 12:00 UTC

Results and Rewards

Date Round Payout Change New Block Issuance
28.05.20 Recurring#1 $2499.95 +$250 $2749.95 #1020520 101922341
28.05.20 KPI#1 $2749.95 +$170 $2919.95 #1020520 101922341
05.06.20 Recurring#2 $2861.11 +$250 $3111.11 #1138912 107876699
06.06.20 KPI#2a $3082.32 +$110 $3192.32 #1152762 107473160
Date Round Previous Change New Block Issuance
28.05.20 Recurring#1 $2499.95 +$250 $2749.95 #1020520 101922341
28.05.20 KPI#1 $2749.95 +$170 $2919.95 #1020520 101922341
05.06.20 Recurring#2 $2861.11 +$250 $3111.11 #1138912 107876699
06.06.20 KPI#2a $3082.32 +$110 $3192.32 #1152762 107473160

Previous KPIs

Term 1

1.1 - Proposal Clearance

For the governance process to function properly, all proposals must be processed professionally, and in a reasonable time frame to avoiding blocking new proposals coming in.

As this is considered as one the main components of the Councils responsibilities, there are no rewards associated with this. However, failure will trigger an annihilation of all (potential) KPI rewards, and trigger a new election.

Key Value
Reward NA
Active from 25.09.2020 ~10:00 UTC - #157601
Measurement period 14 days (Full Council Term)
Success #1 At no point will the number of active proposal stay at 5 for longer
than 14,400 blocks (~24h).
Success #2 No malicious or unreasonable proposals are approved.
Annihilation Failure will result on the loss ALL KPI rewards, and a new Council
Election will be started immediately
Grade date 12.10.2020 - 12:00 UTC
Graded 12.10.2020 - 12:00 UTC
Grading event #1 true
Grading event #2 true
Payout NA

1.2 - Council Reporting

There needs to be some level of accountability and transparency for the Council. For each Term the Council must produce a report of 'events' and 'Tokenomics' to allow users make informed votes. This must be submitted as a PR to the Community Repo.

Key Value
Reward NA
Active from 25.09.2020 ~10:00 UTC - #157601
Measurement period 16 days
Success #1 The First Council on Alexandria (#157601-#359201) produces a
report based on the 'Council Reporting Template' and the
'Tokenomics' script. (see 1.4)
Annihilation Unlike other 'annihilations', failure for this KPI will result on
the loss ALL KPI rewards.
Grade date 12.10.2020 - 12:00 UTC
Graded 12.10.2020 - 12:00 UTC
Grading event #1 true
Grading event #2 true
Payout NA

1.3 - Appoint New Council Secretary

With the changes to the KPI system, the Council must appoint one of their own as the Council Secretary, responsible for adding Council Reports and representing the Council in the Community Repo, and given triage access.

Key Value
Reward 50 USD
Active from 25.09.2020 ~10:00 UTC - #157601
Measurement period 3 days
Success #1 The Council informally appoints a
Council Secretary through a spending proposal and pays them an
appropriate rate for their responsibilities.
Success #2 The spending proposal must provide a link to the Council Secretary's
GitHub account so we can provide them 'triage' permissions on the
community repo.
Annihilation No Council Secretary is appointed.
Grade date 12.10.2020 - 12:00 UTC
Graded 12.10.2020 - 12:00 UTC
Grading event #1 true
Payout 50 USD

1.4 - Block Production

In order to have a reliable network, a KPI focusing on block production and validator stability is required. Timestamp of each block can be found using the block explorer.

Key Value
Reward 50 USD
Active from 25.09.2020 ~10:00 UTC - #57601
Measurement period 14 days (Full Council Term)
Success #1 The difference between the timestamp of blocks #57601
and #259201 must be less than 1213632000.
Success #2 No era starts with less than 10 Validators.
Success #3 The total Validator+Nominator stake averages over 15% of total
issuance.
Annihilation Block finalization lags more than 3600 blocks behind best at
any point throughout the measurement period.
Grade date 12.10.2020 - 12:00 UTC
Graded 12.10.2020 - 12:00 UTC
Grading event #1 false
Grading event #2 true
Grading event #3 true
Payout 33 USD

1.5 - Managing the Community Repo

The Community Repo needs a cleanup and to be re-organized for the new network. Note that for PR to 'count' the Council Secretary must request a review by Jsgenesis (@blrhc and @bwhm) and include a link to an approved Proposal for said PR.

Key Value
Reward 200 USD
Active from 25.09.2020 ~10:00 UTC - #157601
Measurement period 14 days (Full Council Term)
Success #1 The Council Secretary requests a review by Jsgenesis for all open
PRs that should be merged.
Success #2 A new PR, that re-organizes the repo is opened.
Success #3 A new Council Reporting Template is made, and a PR is opened.
Success #4 A 'tokenomics' script (in typescript), is produced, and a PR is
opened.
Annihilation The Council Secretary fails to follow the workflow.
Grade date 12.10.2020 - 12:00 UTC
Graded 12.10.2020 - 12:00 UTC
Grading event #1 false
Grading event #2 false
Grading event #3 false
Grading event #4 true
Payout 50 USD

1.6 - Establishing new Working Groups

New Leads for the Storage and Curator working groups are needed for Alexandria.

Key Value
Reward 50 USD
Active from 25.09.2020 ~10:00 UTC - #157601
Measurement period 7 days
Success #1 The Council hires Leads for each group.
Success #2 Reasonable budgets are set for each group, taking the 'Recurring
Replenishment', platform inflation and the costs for each role into
account.
Annihilation Fewer than two Curators and three Storage Providers (Leads
included) are operating at the end of the measurement period.
Grade date 12.10.2020 - 12:00 UTC
Graded 12.10.2020 - 12:00 UTC
Grading event #1 true
Grading event #2 true
Payout 0 USD (Annihilation)

1.7 - Managing Community Bounties

Managing Community Bounties will be a growing part of the Councils workload. Establishing good workflows for this will be iterative and situational.

Key Value
Reward 250 USD
Active from 25.09.2020 ~10:00 UTC - #157601
Measurement period 14 days (Full Council Term)
Success #1 An overview and explanation of the the Community Bounty system
is produced for the Community Repo.
Success #2 Categories and Subcategories for Community Bounties are made
for the Forum.
Success #3 Community Bounty #1 - 'Update Telegram Bot', is submitted within
the Council Term.
Success #4 Other Community Bounties are managed satisfactory in accordance
with Jsgenesis' and the Councils own process.
Annihilation Unlike standard annihilations, any rewards paid for a Bounty
that exceeds what Jsgenesis pays will be deducted from
the Council's KPI rewards.
Grade date 12.10.2020 - 12:00 UTC
Graded 12.10.2020 - 12:00 UTC
Grading event #1 false
Grading event #2 true
Grading event #3 false
Grading event #4 false
Payout 62.5 USD

Term 2

2.1 - Proposal Clearance

For the governance process to function properly, all proposals must be processed professionally, and in a reasonable time frame to avoiding blocking new proposals coming in.

As this is considered as one the main components of the Councils responsibilities, there are no rewards associated with this. However, failure will trigger an annihilation of all (potential) KPI rewards, and trigger a new election.

Key Value
Reward NA
Active from 09.10.2020 ~18:25 UTC - #259201
Measurement period 14 days (Full Council Term)
Success #1 At no point will the number of active proposal stay at 5 for longer
than 14,400 blocks (~24h).
Success #2 No malicious or unreasonable proposals are approved.
Annihilation Failure will result on the loss ALL KPI rewards, and a new Council
Election will be started immediately
Grade date 26.10.2020 - 12:00 UTC
Graded 26.10.2020 - 12:00 UTC
Grading event #1 true
Grading event #2 true
Payout NA

2.2 - Council Reporting

There needs to be some level of accountability and transparency for the Council. For each Term the Council must produce a report of 'events' and 'Tokenomics' to allow users make informed votes. This must be submitted as a PR to the Community Repo.

Key Value
Reward NA
Active from 09.10.2020 ~18:25 UTC - #259201
Measurement period 16 days
Success #1 The Second Council on Alexandria (#259201-#460801) produces a
report based on the 'Council Reporting Template' and the
'Tokenomics' script. (see 1.4)
Annihilation Unlike other 'annihilations', failure for this KPI will result on
the loss ALL KPI rewards.
Grade date 26.10.2020 - 12:00 UTC
Graded 26.10.2020 - 12:00 UTC
Grading event #1 true
Payout NA

2.3 - Appoint New Council Secretary

The Council must appoint one of their own as the Council Secretary, responsible for adding Council Reports and representing the Council in the Community Repo, and given triage access.

Key Value
Reward 50 USD
Active from 09.10.2020 ~18:25 UTC - #259201
Measurement period 5 days
Success #1 The Council informally appoints a
Council Secretary through a spending proposal and pays them an
appropriate rate for their responsibilities.
Success #2 The spending proposal must provide a link to the Council Secretary's
GitHub account so we can provide them 'triage' permissions on the
community repo.
Annihilation No Council Secretary is appointed.
Grade date 26.10.2020 - 12:00 UTC
Graded 26.10.2020 - 12:00 UTC
Grading event #1 true
Payout 50 USD

2.4 - Block Production

In order to have a reliable network, a KPI focusing on block production and validator stability is required. Timestamp of each block can be found using the block explorer.

Key Value
Reward 150 USD
Active from 09.10.2020 ~18:25 UTC - #259201
Measurement period 14 days (Full Council Term)
Success #1 The difference between the timestamp of blocks #259201
and #460801 must be less than 1213632000.
Success #2 The total Validator+Nominator stake averages over 15% of total
issuance.
Success #3 The total Validator+Nominator stake averages over 20% of total
issuance.
Annihilation Block finalization lags more than 3600 blocks behind best at
any point throughout the measurement period.
Grade date 26.10.2020 - 12:00 UTC
Graded 26.10.2020 - 12:00 UTC
Grading event #1 false (1226580000)
Grading event #2 false (14.1%)
Grading event #3 false (14.1%)
Payout 0 USD

2.5 - Managing the Working Groups

Ensuring a high quality of service delivered by the Working Groups is a key part of the Council's workload.

Key Value
Reward 150 USD
Active from 09.10.2020 ~18:25 UTC - #259201
Measurement period 14 days
Success #1 New budgets are set for each group, taking the 'Recurring
Replenishment', platform inflation and the costs for each role into account.
Success #2 The Council perform spotchecks, and reports the results.
Annihilation Fewer than two Curators and three Storage Providers (Leads
included) are operating at the end of the measurement period.
Grade date 26.10.2020 - 12:00 UTC
Graded 26.10.2020 - 15:00 UTC
Grading event #1 true
Grading event #2 true
Payout 150 USD

2.6 - Managing Community Bounties

Managing Community Bounties will be a growing part of the Councils workload. Establishing good workflows for this will be iterative and situational.

Key Value
Reward 250 USD
Active from 09.10.2020 ~18:25 UTC - #259201
Measurement period 14 days (Full Council Term)
Success #1 An overview and explanation of the the Community Bounty system
is produced for the Community Repo.
Success #2 Community Bounty #1 - 'Update Telegram Bot', is submitted within
the Council Term.
Success #3 Community Bounty #2 - 'Research and Testing of
polkadot-js extension, is submitted within the Council Term.
Success #4 Community Bounty #3 - 'Improve Telegram Bot(s), is assigned
within the Council Term.
Success #5 The Council presents a list of potential Bounties they think would
be of value for the project
Annihilation Unlike standard annihilations, any rewards paid for a Bounty that
exceeds what Jsgenesis pays will be deducted from the Council's
KPI rewards.
Grade date 26.10.2020 - 12:00 UTC
Graded 26.10.2020 - 15:00 UTC
Grading event #1 true
Grading event #2 false
Grading event #3 false
Grading event #4 false
Grading event #5 true
Payout 100 USD

Disclaimer

All forward looking statements, estimates and commitments found in this blog post should be understood to be highly uncertain, not binding and for which no guarantees of accuracy or reliability can be provided. To the fullest extent permitted by law, in no event shall Joystream, Jsgenesis or our affiliates, or any of our directors, employees, contractors,  service providers or agents have any liability whatsoever to any person  for any direct or indirect loss, liability, cost, claim, expense or  damage of any kind, whether in contract or in tort, including negligence, or otherwise, arising out of or related to the use of all or  part of this post, or any links to third party websites.