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 Contents
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 current Council on Babylon, the Council KPIs are as follows:
13.1 - Proposal Clearance
For the governance process to function properly, all proposals must be processed effectively, and in a reasonable time frame to avoid blocking new proposals coming in.
As this is considered as one the main components of the Council's 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 | 17.03.2021 ~23:00 UTC - #2476801 |
| 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 | 04.04.2021 - 18:00 UTC |
13.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 | 17.03.2021 ~23:00 UTC - #2476801 |
| Measurement period | 16 days |
| Success #1 | The Council on Babylon (#2476801-#2678401) 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 | 04.04.2021 - 18:00 UTC |
13.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 | 150 USD |
| Active from | 17.03.2021 ~23:00 UTC - #2476801 |
| 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 Council Secretary will also be responsible for managing the Bounties, even if they choose to 'hire' someone else for as the Bounty Manager for some/all individual bounties. |
| Success #3 | 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 | 04.04.2021 - 18:00 UTC |
13.4 - Founding Member Program - Further Feedback
After a 'difficult' launch, and lots of feedback (both in the questionnaire, and other forms), it seems the program needs improvements. Jsgenesis will make a proposal with our ideas for improvements (22.03.2021).
| Key | Value |
|---|---|
| Reward | 150 USD |
| Active from | 22.03.2021 |
| Measurement period | 10 days |
| Success #1 | Review the proposal, and gather feedback from the community in a similar way as the questionnaire (KPI 12.4) |
| Annihilation | Spoofing replies and results. |
| Grade date | 04.04.2021 - 18:00 UTC |
13.5 - Follow up the Working Groups
With the new scope of work having been implemented in the previous term, and the inflow of new users, the pressure on the working groups increases.
| Key | Value |
|---|---|
| Reward | 200 USD |
| Active from | 17.03.2021 ~23:00 UTC - #2476801 |
| Measurement period | 5 days |
| Success #1 | Produce a brief report on whether the Curators are managing their new workflow. |
| Success #2 | Regardless of the outcome of said report, consider the need for more Curators, and whether more tools must be developed to perform their duties. |
| Annihilation | No task list is presented. |
| Grade date | 04.04.2021 - 18:00 UTC |
13.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 | 500 USD |
| Active from | 17.03.2021 ~23:00 UTC - #2476801 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | Familiarize themselves, then follow the new and improved guidelines for the Council role in Bounty Management (helpdesk) |
| Success #2 | Update/fix/maintain the Community Repo's new bounties-overview files (json, table issue) |
| Success #3 | Follow the instructions for each bounty, create the forum posts, follow up and, if required, create budgets, request funding and hire/assign Bounty Managers. |
| Success #4 | Submit a weekly bounty report, outlining the status and progress for each bounty. |
| Success #5 | Create a list of proposed bounties to easy the (ongoing) transation from Telegram to Discord |
| Success #6 | Create a list of proposed bounties to improve the Founding Member Program (eg. tasks, submitting scores, rules, etc.) |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 04.04.2021 - 18:00 UTC |
Results and Rewards
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 atany 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 Bountythat 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 atany 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 ofpolkadot-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 thatexceeds 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 |
Term 3
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 |
| Graded | 09.11.2020 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | NA |
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 |
| Graded | 09.11.2020 - 12:00 UTC |
| Grading event #1 | true |
| Payout | NA |
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 |
| Graded | 09.11.2020 - 12:00 UTC |
| Grading event #1 | true |
| Payout | USD 50 |
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 |
| Graded | 09.11.2020 - 12:00 UTC |
| Grading event #1 | false (1245336000) |
| Grading event #2 | true (17.0%) |
| Grading event #3 | false (17.0%) |
| Payout | 100 USD |
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 |
| Graded | 09.11.2020 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | 100 USD |
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 ofpolkadot-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 thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 09.11.2020 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Grading event #3 | false |
| Grading event #4 | false |
| Grading event #5 | true |
| Payout | 150 USD |
Term 4
4.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 | 07.11.2020 ~09:15 UTC - #662401 |
| 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 | 23.11.2020 - 12:00 UTC |
| Graded | 23.11.2020 - 13:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | NA |
4.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 | 07.11.2020 ~09:15 UTC - #662401 |
| Measurement period | 16 days |
| Success #1 | The Fourth 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 | 23.11.2020 - 12:00 UTC |
| Graded | 23.11.2020 - 13:00 UTC |
| Grading event #1 | true |
| Payout | NA |
4.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 | 07.11.2020 ~09:15 UTC - #662401 |
| 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 | 23.11.2020 - 12:00 UTC |
| Graded | 23.11.2020 - 13:00 UTC |
| Grading event #1 | false (not in time) |
| Grading event #2 | false (not in time) |
| Payout | 0 USD |
4.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 | 07.11.2020 ~09:15 UTC - #662401 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | The difference between the timestamp of blocks #662401 and #864001 must be less than 1229760000 (avg 6.1s/block) |
| Success #2 | The total Validator+Nominator stake averages over 17.5% of total issuance. |
| Success #3 | The total Validator+Nominator stake averages over 22.5% of total issuance. |
| Annihilation | The difference between the timestamp of blocks #662401 and #864001 is over 1249920000 (avg 6.2s/block), or the total Validator+Nominator stake averages under 10% of total issuance. |
| Grade date | 23.11.2020 - 12:00 UTC |
| Graded | 23.11.2020 - 13:00 UTC |
| Grading event #1 | false (1230594000) |
| Grading event #2 | true (18.4%) |
| Grading event #3 | false (18.4%) |
| Payout | 50 USD |
4.5 - Managing the Working Groups
Ensuring a high quality of service is delivered by the Working Groups is a key part of the Council's workload.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 07.11.2020 ~09:15 UTC - #662401 |
| Measurement period | 14 days |
| Success #1 | New budgets are set for each group, taking the: -'Recurring Replenishment' -platform inflation -the costs for each role into account. |
| Success #2 | The Council perform spotchecks of working groups' performance, and reports the results. |
| Annihilation | Council and/or Jsgenesis spotchecks shows less than 3 SPs up and running at any point during the Term. |
| Grade date | 23.11.2020 - 12:00 UTC |
| Graded | 23.11.2020 - 13:00 UTC |
| Grading event #1 | false |
| Grading event #2 | false |
| Payout | 0 USD |
4.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 | 07.11.2020 ~09:15 UTC - #662401 |
| 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 #2 - 'Research and Testing ofpolkadot-js extension, is submitted within the Council Term. |
| Success #3 | Success events 1-3 of Community Bounty #3 'Improve Telegram Bot(s)' are submitted within the Council Term. |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 23.11.2020 - 12:00 UTC |
| Graded | 23.11.2020 - 13:00 UTC |
| Grading event #1 | true |
| Grading event #2 | false |
| Grading event #3 | false (not complete, but partial) |
| Payout | 120 USD |
Term 5
5.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 Council's 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 | 21.11.2020 ~14:45 UTC - #864001 |
| 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 | 07.12.2020 - 18:00 UTC |
| Graded | 07.12.2020 - 16:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | NA |
5.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 | 21.11.2020 ~14:45 UTC - #864001 |
| Measurement period | 16 days |
| Success #1 | The Fifth Council on Alexandria (#864001-#1065601) 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 | 07.12.2020 - 18:00 UTC |
| Graded | 07.12.2020 - 16:00 UTC |
| Grading event #1 | true |
| Payout | NA |
5.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 | 21.11.2020 ~14:45 UTC - #864001 |
| 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 | 07.12.2020 - 18:00 UTC |
| Graded | 07.12.2020 - 16:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 50 |
5.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 | 75 USD |
| Active from | 21.11.2020 ~14:45 UTC - #864001 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | The difference between the timestamp of blocks #864001 and #1065601 must be less than 1229760000 (avg 6.1s/block) |
| Success #2 | The total Validator+Nominator stake averages over 17.5% of total issuance. |
| Success #3 | The total Validator+Nominator stake averages over 22.5% of total issuance. |
| Annihilation | The difference between the timestamp of blocks #864001 and #1065601 is over 1249920000 (avg 6.2s/block), or the total Validator+Nominator stake averages under 10% of total issuance. |
| Grade date | 07.12.2020 - 18:00 UTC |
| Graded | 07.12.2020 - 16:00 UTC |
| Grading event #1 | true (1220262000) |
| Grading event #2 | true (22.4%) |
| Grading event #2 | false (22.4%) |
| Payout | USD 50 |
5.5 - Managing the Working Groups
Ensuring a high quality of service is delivered by the Working Groups is a key part of the Council's workload.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 21.11.2020 ~14:45 UTC - #864001 |
| 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 | Council and/or Jsgenesis spotchecks shows less than 3 SPs up and running at any point during the Term. |
| Grade date | 07.12.2020 - 18:00 UTC |
| Graded | 07.12.2020 - 16:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 0 (annihilation triggered) |
5.6 - Council Report
The new KPI system has now been running for 4 full terms. It's time to evaluate.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 21.11.2020 ~14:45 UTC - #864001 |
| Measurement period | 14 days |
| Success #1 | The Council produces a report covering terms 1-4. Details can be found in Community Repo, issue 45. |
| Annihilation | The report contains false information. |
| Grade date | 07.12.2020 - 18:00 UTC |
| Graded | 07.12.2020 - 16:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 100 |
5.7 - Content Migration
With the next release, Babylon (early/mid December), the content directory will be overhauled. This means some content may need to be migrated manually.
| Key | Value |
|---|---|
| Reward | 75 USD |
| Active from | 21.11.2020 ~14:45 UTC - #864001 |
| Measurement period | 14 days |
| Success #1 | The Council produces a list of Content to be migrated. Details can be found in the Community Repo, issue 46 |
| Annihilation | NA. |
| Grade date | 07.12.2020 - 18:00 UTC |
| Graded | 07.12.2020 - 16:00 UTC |
| Grading event #1 | true |
| Payout | USD 75 |
5.8 - 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 | 200 USD |
| Active from | 21.11.2020 ~14:45 UTC - #864001 |
| 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 #2 - 'Research and Testing ofpolkadot-js extension, is submitted within the Council Term. |
| Success #3 | Success events 1-3 of Community Bounty #3 - 'Improve Telegram Bot(s)' are submitted within the Council Term. |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 07.12.2020 - 18:00 UTC |
| Graded | 07.12.2020 - 16:00 UTC |
| Grading event #1 | true |
| Grading event #2 | false |
| Grading event #3 | true |
| Payout | USD 133 |
Note: Bounty #3 was graded/rewarded $25, whereas the Council spent $225. Thus, $200 will be deducted from the Council KPI reward.
Term 6
6.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 Council's 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 | 05.12.2020 ~18:00 UTC - #1065601 |
| 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 | 21.12.2020 - 18:00 UTC |
| Graded | 22.12.2020 - 15:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | NA |
6.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 | 05.12.2020 ~18:00 UTC - #1065601 |
| Measurement period | 16 days |
| Success #1 | The Sixth Council on Alexandria (#1065601-#1267201) 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 | 21.12.2020 - 18:00 UTC |
| Graded | 22.12.2020 - 15:00 UTC |
| Grading event #1 | true |
| Payout | NA |
| Graded | 22.12.2020 - 15:00 UTC |
| Grading event #1 | true |
| Payout | NA |
6.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 | 05.12.2020 ~18:00 UTC - #1065601 |
| 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 | 21.12.2020 - 18:00 UTC |
| Graded | 22.12.2020 - 15:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 50 |
6.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 | 05.12.2020 ~18:00 UTC - #1065601 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | The difference between the timestamp of blocks #1065601 and #1267201 must be less than 1229760000 (avg 6.1s/block). |
| Success #2 | The total Validator+Nominator stake averages between 20% and 30% of total issuance. |
| Annihilation | The difference between the timestamp of blocks #1065601 and #1267201 is over 1260000000 (avg 6.25s/block), or the total Validator+Nominator stake averages under 10% of total issuance. |
| Grade date | 21.12.2020 - 18:00 UTC |
| Graded | 22.12.2020 - 15:00 UTC |
| Grading event #1 | true (1220436000) |
| Grading event #2 | true (24.6%) |
| Payout | USD 50 |
6.5 - Managing the Working Groups
Ensuring a high quality of service is delivered by the Working Groups is a key part of the Council's workload.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 05.12.2020 ~18:00 UTC - #1065601 |
| 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 | Council and/or Jsgenesis spotchecks shows less than 3 SPs up and running at any point during the Term. |
| Grade date | 21.12.2020 - 18:00 UTC |
| Graded | 22.12.2020 - 15:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 100 |
6.6 - Quality Content Sourcing
With the new consumer app fast approaching, new quality content is desired. The Council needs to find a way to source more quality content for the platform.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 05.12.2020 ~18:00 UTC - #1065601 |
| Measurement period | 14 days |
| Success #1 | The Council delivers a report, outlining how the Joystream can populate the content directory with quality content under sufficiently permissive licenses. Details in Community Repo issue 53. |
| Annihilation | The report contains false information. |
| Grade date | 21.12.2020 - 18:00 UTC |
| Graded | 22.12.2020 - 15:00 UTC |
| Grading event #1 | true |
| Payout | USD 100 |
6.7 - 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 | 300 USD |
| Active from | 05.12.2020 ~18:00 UTC - #1065601 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | Community Bounty #2 - 'Research and Testing of polkadot-js extension', is submitted within the Council Term. |
| Success #2 | Success events 1-3 of Community Bounty #4 - 'Improve Telegram Bot(s)' (#3 re-issued) are submitted within the Council Term. |
| Success #3 | Council fulfills their scope of work for opening Community Bounty #5. |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 21.12.2020 - 18:00 UTC |
| Graded | 22.12.2020 - 15:00 UTC |
| Grading event #1 | false |
| Grading event #2 | false |
| Grading event #3 | true |
| Payout | USD 100 |
Term 7
7.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 Council's 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 | 19.12.2020 ~21:00 UTC - #1267201 |
| 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 | 05.01.2021 - 18:00 UTC |
| Graded | 05.01.2021 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | NA |
7.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 | 19.12.2020 ~21:00 UTC - #1267201 |
| Measurement period | 16 days |
| Success #1 | The Seventh Council on Alexandria (#1267201-#1468801) 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 | 05.01.2021 - 18:00 UTC |
| Graded | 05.01.2021 - 12:00 UTC |
| Grading event #1 | true |
| Payout | NA |
7.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 | 19.12.2020 ~21:00 UTC - #1267201 |
| 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 | 05.01.2021 - 18:00 UTC |
| Graded | 05.01.2021 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 50 |
7.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 | 19.12.2020 ~21:00 UTC - #1267201 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | The difference between the timestamp of blocks #1267201 and #1468801 must be less than 1229760000 (avg 6.1s/block). |
| Success #2 | The total Validator+Nominator stake averages between 20% and 30% of total issuance. |
| Annihilation | The difference between the timestamp of blocks #1267201 and #1468801 is over 1260000000 (avg 6.25s/block), or the total Validator+Nominator stake averages under 10% of total issuance. |
| Grade date | 05.01.2021 - 18:00 UTC |
| Graded | 05.01.2021 - 12:00 UTC |
| Grading event #1 | true 1227126000 |
| Grading event #2 | true 24.1% |
| Payout | USD 50 |
7.5 - Managing the Working Groups
In addition to the regular tasks, the runtime upgrade will require extra work in terms of management. In particular as the Curator Working Group module will be changed.
| Key | Value |
|---|---|
| Reward | 200 USD |
| Active from | 19.12.2020 ~21:00 UTC - #1267201 |
| Measurement period | 7 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 | As the 'old' Curators will still be paid (assuming there are tokens in the mint), the Council must ensure that the mint is empty before block #1290000 |
| Success #3 | In addition, remove 'old' Curators from their job. This cannot by done through the Proposal system AFTER the upgrade. |
| Success #4 | After the upgrade, the Storage Providers must upgrade their storage nodes in order to still function. |
| Success #5 | Hire a new Curator Lead. |
| Annihilation | There are Storage Providers that haven't upgraded after block #1368001 |
| Grade date | 05.01.2021 - 18:00 UTC |
| Graded | 05.01.2021 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | false |
| Grading event #3 | true |
| Grading event #4 | true |
| Grading event #5 | false* |
| Payout | USD 180 |
- * Partial payout as it was attempted
7.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 | 300 USD |
| Active from | 19.12.2020 ~21:00 UTC - #1267201 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | Community Bounty #2 - 'Research and Testing of polkadot-js extension', is submitted within the Council Term. |
| Success #2 | Success events 1-3 of Community Bounty #4 - 'Improve Telegram Bot(s)' (#3 re-issued) are submitted within the Council Term. |
| Success #3 | Community Bounty #5 - 'Joystream Telegram Sticker pack', in line with the approved scheme outlined in proposal #69, has recieved at least one approved entry. |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 05.01.2021 - 18:00 UTC |
| Graded | 05.01.2021 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | false |
| Grading event #3 | true |
| Payout | USD 200 |
Term 8
8.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 Council's 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 | 03.01.2021 ~02:00 UTC - #1468801 |
| 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 | 19.01.2021 - 18:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | NA |
8.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 | 03.01.2021 ~02:00 UTC - #1468801 |
| Measurement period | 16 days |
| Success #1 | The Second Council on Babylon (#1468801-#1670401) 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 | 19.01.2021 - 18:00 UTC |
| Graded | 19.01.2021 - 10:00 UTC |
| Grading event #1 | true |
| Payout | NA |
8.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 | 03.01.2021 ~02:00 UTC - #1468801 |
| 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 | 19.01.2021 - 18:00 UTC |
| Graded | 19.01.2021 - 10:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 50 |
8.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 | 03.01.2021 ~02:00 UTC - #1468801 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | The difference between the timestamp of blocks #1468801 and #1670401 must be less than 1229760000 (avg 6.1s/block). |
| Success #2 | The total Validator+Nominator stake averages between 20% and 30% of total issuance. |
| Annihilation | The difference between the timestamp of blocks #1468801 and #1670401 is over 1260000000 (avg 6.25s/block), or the total Validator+Nominator stake averages under 10% of total issuance. |
| Grade date | 19.01.2021 - 18:00 UTC |
| Graded | 19.01.2021 - 10:00 UTC |
| Grading event #1 | false (1245552000) |
| Grading event #2 | true (23.7%) |
| Payout | USD 25 |
8.5 - Managing the Working Groups
In addition to the regular tasks, the runtime upgrade will require extra work in terms of management. In particular as the Curator Working Group module will be changed.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 03.01.2021 ~02:00 UTC - #1468801 |
| Measurement period | 7 days |
| Success #1 | "New budgets are set for each group, taking the 'Recurring Replenishment', platform inflation and the costs and platform needs for each role into account.", |
| Success #2 | Hire a new Curator Lead. |
| Annihilation | There are Storage Providers that haven't upgraded after block #1368001 |
| Grade date | 19.01.2021 - 18:00 UTC |
| Graded | 19.01.2021 - 10:00 UTC |
| Grading event #1 | false |
| Grading event #2 | true |
| Payout | USD 50 |
8.6 - Joystream Sprocket
Start the Joystream Sprocket based on issue #1966 in the 'joystream' repo. At least $200 of funding will be made available by Jsgenesis.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 03.01.2021 ~02:00 UTC - #1468801 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | A complete plan for starting the first Joystream Sprocket is created. |
| Success #2 | A list of achievable wants and needs (technical or other) to start it up is submitted. Some of this may be a new bounty (see KPI 8.7-2). |
| Annihilation | N/A |
| Grade date | 19.01.2021 - 18:00 UTC |
| Graded | 19.01.2021 - 10:00 UTC |
| Grading event #1 | false |
| Grading event #2 | false |
| Payout | USD 0 |
8.7 - 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 | 300 USD |
| Active from | 03.01.2021 ~02:00 UTC - #1468801 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | Community Bounty #5 - 'Joystream Telegram Sticker pack', in line with the approved scheme outlined in proposal #69, has recieved at least one approved entry. |
| Success #2 | Based on KPI 8.6-2, create the bounty/bounties needed. |
| Success #3 | Create one (complete) new bounty, based Community feedback and wishes, and present the full 'issue' text as a PR. |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 19.01.2021 - 18:00 UTC |
| Graded | 19.01.2021 - 10:00 UTC |
| Grading event #1 | true |
| Grading event #2 | false |
| Grading event #2 | false |
| Payout | USD 100 |
Term 9
9.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 Council's 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 | 17.01.2021 ~12:00 UTC - #1670401 |
| 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 | 01.02.2021 - 18:00 UTC |
| Graded | 02.02.2021 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | NA |
9.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 | 17.01.2021 ~12:00 UTC - #1670401 |
| Measurement period | 16 days |
| Success #1 | The Third Council on Babylon (#1670401-#1872001) 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 | 01.02.2021 - 18:00 UTC |
| Graded | 02.02.2021 - 12:00 UTC |
| Grading event #1 | true |
| Payout | NA |
9.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 | 17.01.2021 ~12:00 UTC - #1670401" |
| 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 | 01.02.2021 - 18:00 UTC |
| Graded | 02.02.2021 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 50 |
9.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 | 17.01.2021 ~12:00 UTC - #1670401 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | The difference between the timestamp of blocks #1670401 and #1872001 must be less than 1229760000 (avg 6.1s/block). |
| Success #2 | The total Validator+Nominator stake averages between 20% and 30% of total issuance. |
| Annihilation | The difference between the timestamp of blocks #1670401 and #1872001 is over 1260000000 (avg 6.25s/block), or the total Validator+Nominator stake averages under 10% of total issuance. |
| Grade date | 01.02.2021 - 18:00 UTC |
| Graded | 02.02.2021 - 12:00 UTC |
| Grading event #1 | false (1253418000) |
| Grading event #2 | true (24.9%) |
| Payout | USD 25 |
9.5 - Managing the Working Groups
In addition to the regular tasks, the runtime upgrade will require extra work in terms of management. In particular as the Curator Working Group module will be changed.
| Key | Value |
|---|---|
| Reward | 50 USD |
| Active from | 17.01.2021 ~12:00 UTC - #1670401 |
| Measurement period | 7 days |
| Success #1 | "New budgets are set for each group, taking the 'Recurring Replenishment', platform inflation and the costs and platform needs for each role into account.", |
| Annihilation | N/A |
| Grade date | 01.02.2021 - 18:00 UTC |
| Graded | 02.02.2021 - 12:00 UTC |
| Grading event #1 | false |
| Payout | USD 0 |
9.6 - Joystream Sprocket
Start the Joystream Sprocket based on issue #1966 in the 'joystream' repo. At least $200 of funding will be made available by Jsgenesis.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 17.01.2021 ~12:00 UTC - #1670401 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | A complete plan for starting the first Joystream Sprocket is created. |
| Success #2 | A list of achievable wants and needs (technical or other) to start it up is submitted. Some of this may be a new bounty (see KPI 8.7-2). |
| Annihilation | N/A |
| Grade date | 01.02.2021 - 18:00 UTC |
| Graded | 02.02.2021 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Notes | Although attempted, it seems incomplete. |
| Payout | USD 75 |
9.7 - 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 | 300 USD |
| Active from | 17.01.2021 ~12:00 UTC - #1670401 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | Community Bounty #5 - 'Joystream Telegram Sticker pack', in line with the approved scheme outlined in proposal #69, has recieved at least one approved entry. |
| Success #2 | Based on KPI 8.6-2, create the bounty/bounties needed. |
| Success #3 | Create one (complete) new bounty, based Community feedback and wishes, and present the full 'issue' text as a PR. |
| Success #4 | Community Bounty #5 - 'Increase Validator Set Research', is submitted within the Council Term. |
| Success #5 | All new bounties gets a thread, and followed up in the Forum". |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 01.02.2021 - 18:00 UTC |
| Graded | 02.02.2021 - 12:00 UTC |
| Grading event #1 | true |
| Grading event #2 | false |
| Grading event #3 | false |
| Grading event #4 | true |
| Grading event #5 | true |
| Payout | USD 180 |
Term 10
10.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 Council's 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 | 31.01.2021 ~23:00 UTC - #1872001 |
| 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 | 16.02.2021 - 18:00 UTC |
| Graded | 17.10.2020 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | NA |
10.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 | 31.01.2021 ~23:00 UTC - #1872001 |
| Measurement period | 16 days |
| Success #1 | The Fourth Council on Babylon (#1872001-#2073601) 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 | 16.02.2021 - 18:00 UTC |
| Graded | 17.10.2020 - 13:30 UTC |
| Grading event #1 | true |
| Payout | NA |
10.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 | 31.01.2021 ~23:00 UTC - #1872001 |
| 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 | 16.02.2021 - 18:00 UTC |
| Graded | 17.10.2020 - 13:30 UTC |
| Grading event #1 | true |
| Payout | USD 50 |
10.4 - Increase the Opportunities on the Platform
Due to a new incentives program we are in the process of rolling out, we want to open up for more participation on the platform. As a consequence, the platform's budget will be increased to USD 1000/council term.
| Key | Value |
|---|---|
| Reward | 250 USD |
| Active from | 31.01.2021 ~23:00 UTC - #1872001 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | Increase the number of validator slots to 80 from approx #1771201. Expect to further increase this number in the future. |
| Success #2 | Based on the results from Bounty #6, and further discussion, request changes to related parameters. |
| Success #3 | Increase the number of spots on the Council to 12, and change the other parameters where appropriate. Request a new recurring reward scheme based on this. |
| Success #4 | The workload for the Curator group will go up with the new scheme (as new bounties will be rolled out). Ensure the group is both properly manned, and trained for this development. |
| Success #5 | Set up a new budget for the platform, revising both the number of positions for each role, and their rewards. |
| Annihilation | N/A |
| Grade date | 16.02.2021 - 18:00 UTC |
| Graded | 17.10.2020 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | false |
| Grading event #3 | true |
| Grading event #4 | false |
| Grading event #5 | true |
| Payout | USD 150 |
10.5 - 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 | 31.01.2021 ~23:00 UTC - #1872001 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | The difference between the timestamp of blocks #1872001 and #2073601 must be less than 1229760000 (avg 6.1s/block). |
| Success #2 | The total Validator+Nominator stake averages between 20% and 30% of total issuance. |
| Annihilation | The difference between the timestamp of blocks #1872001 and #2073601 is over 1260000000 (avg 6.25s/block), or the total Validator+Nominator stake averages under 10% of total issuance. |
| Grade date | 16.02.2021 - 18:00 UTC |
| Graded | 17.10.2020 - 13:30 UTC |
| Grading event #1 | false |
| Grading event #1 | true |
| Payout | USD 25 |
| Notes | Annihilation not enforced due to large validator set |
10.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 | 200 USD |
| Active from | 31.01.2021 ~23:00 UTC - #1872001 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | #5 - 'Joystream Telegram Sticker pack': Submit a report of the current status, covering both the results and the cost, and present a plan going forward. |
| Success #2 | As new bounties will be rolled out in the term, perform the Council's tasks as required. |
| Success #3 | For the bounties that requires 'Admins', create budgets and hire/assign members for the tasks. |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 16.02.2021 - 18:00 UTC |
| Graded | 17.10.2020 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Grading event #3 | NA |
| Payout | USD 200 |
| Notes | Event #3 not possible |
Term 11
11.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 Council's 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 | 16.02.2021 ~03:30 UTC - #2073601 |
| 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 | 06.03.2021 - 18:00 UTC |
| Graded | 05.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 0 |
11.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 | 16.02.2021 ~03:30 UTC - #2073601 |
| Measurement period | 16 days |
| Success #1 | The Fourth Council on Babylon (#2073601-#2275201) 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 | 06.03.2021 - 18:00 UTC |
| Graded | 05.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Payout | USD 0 |
11.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 | 16.02.2021 ~03:30 UTC - #2073601 |
| 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 | 06.03.2021 - 18:00 UTC |
| Graded | 05.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 50 |
11.4 - Research Max Validator Change
After the validator set was increased last week, there was some unexpected behaviour. Produce a report answering the following questions.
| Key | Value |
|---|---|
| Reward | 250 USD |
| Active from | 16.02.2021 ~03:30 UTC - #2073601 |
| Measurement period | 14 days |
| Success #1 | After the proposal was executed (#1937365), how quickly did the new validators show up? |
| Success #2 | Was there any clear patterns for the new validators? |
| Success #3 | Did the number of network nodes increase 'proportionally'? (Might be hard to figure out, unless you've configured your node to accept >80 peers.) |
| Success #4 | What happened to the rewards in tJOY and USD terms? |
| Success #5 | Was there a spike in tokens staked, or were they just shifted? |
| Success #6 | What happened to the average block time, and blocks per era and session/epoch? |
| Success #7 | Anything else that was noteworthy? |
| Annihilation | N/A |
| Grade date | 06.03.2021 - 18:00 UTC |
| Graded | 05.03.2021 - 13:30 UTC |
| Grading event #1-7 | false |
| Payout | USD 0 |
11.5 - 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 | 300 USD |
| Active from | 16.02.2021 ~03:30 UTC - #2073601 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | Update/fix/maintain the Community Repo's new bounties-overview files (json, table issue) |
| Success #2 | Follow the instructions for each bounty, create the forum posts, follow up and, if required, create budgets, request funding and hire/assign members as managers. |
| Success #3 | Submit a weekly bounty report, outlining the status and progress for each bounty. |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 06.03.2021 - 18:00 UTC |
| Graded | 05.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | false |
| Grading event #3 | false |
| Payout | USD 100 |
Term 12
12.1 - Proposal Clearance
For the governance process to function properly, all proposals must be processed effectively, and in a reasonable time frame to avoid blocking new proposals coming in.
As this is considered as one the main components of the Council's 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 | 03.03.2021 ~08:15 UTC - #2275201 |
| 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 | 21.03.2021 - 18:00 UTC |
| Graded | 20.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 0 |
12.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 | 03.03.2021 ~08:15 UTC - #2275201 |
| Measurement period | 16 days |
| Success #1 | The Fourth Council on Babylon (#2073601-#2275201) 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 | 21.03.2021 - 18:00 UTC |
| Graded | 20.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Payout | USD 0 |
12.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 | 150 USD |
| Active from | 03.03.2021 ~08:15 UTC - #2275201 |
| 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 Council Secretary will also be responsible for managing the Bounties, even if they choose to 'hire' someone else for as the Bounty Manager for some/all individual bounties. |
| Success #3 | 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 | 21.03.2021 - 18:00 UTC |
| Graded | 20.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Grading event #3 | true |
| Payout | USD 150 |
12.4 - Founding Member Program Feedback
With the first Scoring Period of the Founding Member, we need to get some feedback from the Community. Some questions can be found in issue 113 of the Community Repo.
| Key | Value |
|---|---|
| Reward | 200 USD |
| Active from | 03.03.2021 ~08:15 UTC - #2275201 |
| Measurement period | 10 days |
| Success #1 | Make a questionnaire, and get feedback from at least 100 platform users (less will simply mean partial credit). |
| Success #2 | Parse the feedback, and present the key findings in a PR to Community Repo. |
| Annihilation | Spoofing replies and results. |
| Grade date | 21.03.2021 - 18:00 UTC |
| Graded | 20.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 200 |
12.5 - Managing the Working Groups
With the inflow of new users, both the Storage and the Content Curator Working Groups are seeing an increased workload. Are they performing their tasks?
| Key | Value |
|---|---|
| Reward | 150 USD |
| Active from | 03.03.2021 ~08:15 UTC - #2275201 |
| Measurement period | 5 days |
| Success #1 | Revise the workload for the groups, and if required, set new budgets for the Working Groups. |
| Success #2 | Create high level, yet specific, list of tasks for the Working Groups. |
| Success #3 | Publish a report on the state of both Working Groups, as it stands at the start of the Term. |
| Annihilation | No task list is presented. |
| Grade date | 21.03.2021 - 18:00 UTC |
| Graded | 20.03.2021 - 13:30 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Grading event #3 | true |
| Payout | USD 150 |
12.6 - Follow up the Working Groups
Follow up the Working Group performance with regards to their tasks.
| Key | Value |
|---|---|
| Reward | 100 USD |
| Active from | 16.03.2021 ~#2448001 |
| Measurement period | 3 days |
| Success #1 | Publish a report on the state of both Working Groups, as it stands at the end of the Term. |
| Success #2 | Include some notes for the next Council, regarding the budgets and whether new/more/fewer workers are needed. |
| Annihilation | No report is made |
| Grade date | 21.03.2021 - 18:00 UTC |
| Grading event #1 | true |
| Grading event #2 | true |
| Payout | USD 100 |
12.7 - 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 | 300 USD |
| Active from | 03.03.2021 ~08:15 UTC - #2275201 |
| Measurement period | 14 days (Full Council Term) |
| Success #1 | Familiarize themselves, then follow the new and improved guidelines for the Council role in Bounty Management (helpdesk) |
| Success #2 | Update/fix/maintain the Community Repo's new bounties-overview files (json, table issue) |
| Success #3 | Follow the instructions for each bounty, create the forum posts, follow up and, if required, create budgets, request funding and hire/assign Bounty Managers. |
| Success #4 | Submit a weekly bounty report, outlining the status and progress for each bounty. |
| Annihilation | Unlike standard annihilations, any rewards paid for a Bounty thatexceeds what Jsgenesis pays will be deducted from the Council's KPI rewards. |
| Grade date | 21.03.2021 - 18:00 UTC |
| Grading event #1 | false |
| Grading event #2 | true |
| Grading event #3 | false |
| Grading event #4 | true |
| Payout | USD 150 |
All KPI rewards paid.
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.