Key Performance Indicators (KPIs) define success metrics for the overall testnet system, and determine how much value is added to the reward pool.
With the introduction of our new proposal system come KPIs - metrics we are using to evaluate the success of the testnet and its participants (particularly council members).
At any given time, there is a set of key performance indicators (KPI) which define success metrics for the overall system, and how much value should be added to the reward pool if these are achieved. The "achievement" of these objectives is evaulated by Jsgenesis. Definitions of terms used in the KPIs are defined here.
Current KPIs
For Round 17 of Constantinople, the KPIs are largely unchanged from Round 16. Note that this will (hopefully) be the final set of KPIs for Constantinople, and the final under the current scheme.
KPI 17.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 13.09.2020 ~00:00 UTC - #2565211 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block#2565211 and block #2665593must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 20.09.2020 - 07:00 UTC |
| Grading #1 | true |
| Payout | USD 50 |
KPI 17.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in a reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 13.09.2020 ~00:00 UTC - #2565211 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 20.09.2020 - 07:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 17.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 13.09.2020 ~00:00 UTC - #2565211 |
| Measurement period | 7 days |
| Success #1 | The 15th Council on Constantinople (#2464411-#2565210) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The 15th Council on Constantinople (#2464411-#2565210) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 20.09.2020 - 07:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | false |
| Grading #4 | false |
| Payout | USD 100 |
KPI 17.4 - Appoint New Council Secretary
In preparation for some changes to the KPI system, the Council must appoint one of their own as the Council Secretary, responsible for adding Council Reports (17.3) and representing the Council in the community repo (with some enhanced repo maintenance privileges).
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 13.09.2020 ~00:00 UTC - #2565211 |
| Measurement period | 7 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 with a higher permission level on the community repo. |
| Annihilation | No Council Secretary is appointed. |
| Graded | 20.09.2020 - 07:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 17.5 - Council Approves New Rewards, KPI system and Chain Parameters for Alexandria
With the new testnet (on a new chain) Alexandria fast approaching, some changes will be made. Jsgenesis will make a Text Proposal listing each proposed change (quantitative and qualitative). This proposal will be created before 00:00 UTC on Tuesday.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 15.09.2020 ~00:00 UTC - #2594011 |
| Measurement period | 5 days |
| Success #1 | The Council opens up a forum post, to discuss with the community, and evaluates the changes proposed |
| Success #2 | The Council Secretary makes a Proposal that presents a summary of the discussions, addressing each item in the Proposal. Finally, it contains a conclusion, with their rationale for agreeing, or disagreeing with each individual value |
| Success #3 | The Councils Proposal is approved |
| Annihilation | The approved Proposal fails to include arguments against their conclusion |
| Graded | 20.09.2020 - 07:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | true |
| Payout | USD 200 |
Pool Top Ups
| Date | Reason | 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 |
| 08.06.20 | KPI#2b |
$3177.58 | +$120 | $3297.58 | #1181755 | 110344193 |
| 13.06.20 | Recurring#3 | $3282.90 | +$200 | $3482.90 | #1249547 | 113215555 |
| 13.06.20 | KPI#3 | $3482.90 | +$170 | $3652.90 | #1249547 | 113215555 |
| 21.06.20 | Recurring#4 | $3501.50 | +$200 | $3701.50 | #1365602 | 119281477 |
| 21.06.20 | KPI#4 | $3701.50 | +$310 | $4011.50 | #1365602 | 119281477 |
| 28.06.20 | Recurring#5 | $3811.02 | +$200 | $4011.02 | #1466844 | 118985279 |
| 28.06.20 | KPI#5 | $4011.02 | +$150 | $4161.02 | #1466844 | 118985279 |
| 05.07.20 | Recurring#6 | $4057.66 | +$200 | $4257.66 | #1565000 | 122380927 |
| 05.07.20 | KPI#6 | $4257.66 | +$70 | $4327.66 | #1565000 | 122380927 |
| 12.07.20 | Recurring#7 | $4221.69 | +$200 | $4421.69 | #1666117 | 126463043 |
| 12.07.20 | KPI#7 | $4421.69 | +$70 | $4491.69 | #1666117 | 126463043 |
| 19.07.20 | Recurring#8 | $4386.69 | +$150 | $4536.69 | #1767176 | 129506757 |
| 19.07.20 | KPI#8 | $4536.69 | +$100 | $4636.69 | #1767176 | 129506757 |
| 26.07.20 | Recurring#9 | $4636.85 | +$150 | $4786.85 | #1868826 | 135610701 |
| 26.07.20 | KPI#9 | $4786.85 | +$250 | $5036.85 | #1868826 | 135610701 |
| 29.07.20 | Bonus* |
$4886.37 | +$250 | $5136.37 | #1914251 | 134271451 |
| 02.08.20 | Recurring#10 | $5136.37 | +$150 | $5286.37 | #1968360 | 134749211 |
| 02.08.20 | KPI#10 | $5286.37 | +$205 | $5491.37 | #1968360 | 134749211 |
| 09.08.20 | Recurring#11 | $5389.51 | +$150 | $5539.51 | #2067865 | 134289683 |
| 09.08.20 | KPI#11a |
$5539.51 | +$180 | $5719.51 | #2067865 | 134289683 |
| 12.08.20 | KPI#11b |
$5593.18 | +350 | $5943.18 | #2111168 | 139917608 |
| 17.08.20 | Bonus** |
$5566.31 | +$175 | $5741.31 | #2189723 | 134411555 |
| 20.08.20 | Recurring#12 | $5225.69 | +$150 | $5375.69 | #2232120 | 133493587 |
| 20.08.20 | KPI#12 | $5375.69 | +$175 | $5550.69 | #2232120 | 133493587 |
| 24.08.20 | Recurring#13 | $5550.69 | +$150 | $5700.69 | #2285717 | 136177990 |
| 24.08.20 | KPI#13 | $5700.69 | +$221 | $5921.69 | #2285717 | 136177990 |
| 30.08.20 | Recurring#14 | $5629.48 | +$150 | $5779.48 | #2369301 | 138200244 |
| 30.08.20 | KPI#14 | $5779.48 | +$300 | $6079.48 | #2369301 | 138200244 |
| 06.09.20 | Recurring#15 | $5994.45 | +$150 | $6144.45 | #2469656 | 142036846 |
| 06.09.20 | KPI#15 | $6144.45 | +$200 | $6344.45 | #2469656 | 142036846 |
| 14.09.20 | Recurring#16 | $6344.45 | +$150 | $6494.45 | #2586836 | 145956813 |
| 14.09.20 | KPI#16 | $6494.45 | +$200 | $6944.45 | #2586836 | 145956813 |
| 20.09.20 | Recurring#17 | $6944.45 | +$150 | $7094.45 | #2669841 | 154289594 |
| 20.09.20 | KPI#17 | $7094.45 | +$200 | $7544.45 | #2669841 | 154289594 |
- Bonus
*- See proposal 40 - Bonus
**- Bonus mint for telegram bots at #2189739
Status at 02.08.20:
- Initial: $2,500
- Total Recurring Rewards: $1,950
- Total KPI: $1,725
- Bonus: 250
- SUM: $6,425
Previous KPIs
The graded KPIs are found below.
Round 1
KPI 1.1 - Average block time < 6.025s & maintain 10 validators
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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 20:05:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success#1 | The difference between timestamps of block 910367 andblock 1010749 must be less than 604,710,000 milliseconds |
| Success#2 | Maintain a total of least 10 validators throughout the Measurement period |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Grading#1 | 605,010,030>604,710,000 -> false |
| Grading#2 | true |
| Payout | USD 50 |
KPI 1.2 - All proposals are cleared before they expire AND at no continuous 24h period are there 5 proposal in the active stage
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 120 |
| Active from | 20:05:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success#1 | No proposals expire due to missing votes |
| Success#2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Success#3 | For each new proposal, a forum post is opened for discussion between the council and other interested parties |
| Annihilation | No malicious or unreasonable proposals are approved |
| Grading#1 | true |
| Grading#2 | true |
| Grading#3 | true |
| Payout | USD 120 |
Round 2
KPI 2.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 29:05:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success#1 | The difference between timestamps of block 1039361 and block1139743 must be less than 604,710,000 milliseconds |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Grading | 06:06:2020 - 16:00 GMT |
| Grading#1 | 603,924,000>604,710,000 -> true |
| Payout | USD 50 |
KPI 2.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 90 |
| Active from | 29:05:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success#1 | No proposals expire due to missing votes |
| Success#2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Success#3 | For each new proposal, a forum post is opened for discussion between the council and other interested parties |
| Annihilation | No malicious or unreasonable proposals are approved |
| Grading | 06:06:2020 - 16:00 GMT |
| Grading#1 | true |
| Grading#2 | true |
| Grading#3 | false (proposal #8) |
| Payout | USD 60 |
KPI 2.3 - Content Creation
To improve the current state of available videos, we will incentivize it. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 120 |
| Active from | 29:05:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success#1 | At least 50 new curated videos added to the media page |
| Success#2 | Total runtime of videos exceeds 3h |
| Success#3 | An instructional video that guides a new user through all the steps for uploading and editing a video on the platform |
| Annihilation | A video not in line with the platform ToS remains available for more than 24h |
| Grading | 06:06:2020 - 16:00 GMT |
| Grading#1 | true |
| Grading#2 | true |
| Grading#3 | true |
| Payout | USD 120 |
KPI 2.4 - State of The Network Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reports would help the users make informed votes.
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 28:05:2020 - 16:00 GMT |
| Measurement period | 3 days |
| Success#1 | The Council produces a report on the state of the network tokenomics, and it's accounts |
| Success#2 | The Council produces a report on the Councils own performance |
| Annihilation | The report contains incorrect data. |
| Grading | 01:06:2020 - 16:00 GMT |
| Grading#1 | false |
| Grading#2 | false |
| Payout | USD 0 |
Round 3
For the Council active between 05.06.20-12.06.20 (blocks #1139611 and #1240271).
KPI 3.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 05:06:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | The difference between the timestamps of: block 1139889 and block 1240271 must be less than 604,710,000 milliseconds |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 13:06:2020 - 08:00 GMT |
| Grading#1 | false |
| Payout | USD 0 |
KPI 3.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 60 |
| Active from | 05:06:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Success #3 | For each new proposal, a forum post is opened for discussion between the council and other interested parties |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 13:06:2020 - 08:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | true |
| Payout | USD 60 |
KPI 3.3 - Content Curation
Content Curation is an important part of the platform, and needs improvement. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 120 |
| Active from | 05:06:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | The Curators publishes a 'Curation Policy' in the forum. |
| Success #2 | A Curator responds to all requests made on the forum within 24h. |
| Success #3 | All (video) entities with unplayable content are located and listed on the forum. All channel owners are assisted to replace media file. |
| Success #4 | All (video) entities containing playable content are curated and displayed. |
| Success #5 | All channels that warrants so get 'Verified' |
| Success #6 | All files in the 'dataDirectory' not linked to an entity are located and listed on the forum for removal. |
| Annihilation | A video not in line with the platform ToS remains available for more than 24h |
| Graded | 13:06:2020 - 08:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | false |
| Grading #4 | false |
| Grading #5 | false |
| Grading #6 | true |
| Payout | USD 60 |
KPI 3.4 - State of The Network Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reports would help the users make informed votes.
| Key | Value |
|---|---|
| Reward | USD 60 |
| Active from | 05:06:2020 - 16:00 GMT |
| Measurement period | 5 days |
| Success #1 | Constantinople Council #0 produces a text report covering its own workflow, challenges, thinking and performance. |
| Success #2 | Constantinople Council #1 produces a text report covering its own workflow, challenges, thinking and performance. |
| Annihilation | The report contains incorrect data. |
| Graded | 13:06:2020 - 08:00 GMT |
| Grading #1 | false* |
| Grading #2 | false |
| Payout | USD 0 |
Success Event #2 graded as false as the report was created to late.
KPI 3.5 - Tokenomics Network Reporting: Template & Tools
The Council did not manage to complete the previous KPI for State of the Network Reporting. This is important enough to fund.
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 05:06:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | A first version template is created. It includes the relevant data, and a format for presenting them. |
| Success #2 | A user-friendly script is created, that only takes blockheights as inputs, and returns the data needed in #1. |
| Annihilation | The report contains incorrect data. |
| Graded | 13:06:2020 - 08:00 GMT |
| Grading #1 | true |
| Grading #2 | false |
| Payout | USD 50 |
Round 4
KPI 4.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 12.06.2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | The difference between the timestamps of: block 1240411 and block 1340793 must be less than 604,710,000 milliseconds |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 21:06:2020 - 09:30 GMT |
| Grading #1 | true |
| Payout | USD 50 |
KPI 4.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 60 |
| Active from | 12.06.2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Success #3 | After the runtime upgrade at block #1279512, the proposal discussion system is used for all new proposals |
| Success #4 | All forum posts discussing old proposals are added to the their respective proposal discussion with metadata |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 21:06:2020 - 09:30 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | false |
| Grading #4 | false |
| Payout | USD 30 |
KPI 4.3 - Content Curation
Content Curation is an important part of the platform, and needs improvement. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 80 |
| Active from | 12.06.2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | All videos with unplayable content are moderated. |
| Success #2 | All (video) entities containing playable content are curated and displayed. |
| Success #3 | All channels that warrants so get 'Verified' |
| Success #4 | The featuered videos are updated twice |
| Annihilation | A video not in line with the platform ToS remains available for more than 24h |
| Graded | 21:06:2020 - 09:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | true |
| Grading #4 | true |
| Payout | USD 80 |
KPI 4.4 - Council Performance Review and Minutes
There needs to be some level of accountability and transparency for the Council. Weekly reports would help the users make informed votes.
| Key | Value |
|---|---|
| Reward | USD 60 |
| Active from | 12.06.2020 - 16:00 GMT |
| Measurement period | 3 days |
| Success #1 | The second Council on Constantinople (#1139611-#1240411) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Annihilation | The report contains incorrect information. |
| Graded | 21:06:2020 - 09:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 60 |
KPI 4.5 - Tokenomics and State of the Network Reporting
In addition to the above, there needs to be bookeeping/accounting of the platform's spending, and some general network data.
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 12.06.2020 - 16:00 GMT |
| Measurement period | 3 days |
| Success #1 | The second Council on Constantinople (#1139611-#1240411) produces a report based on the newest template. |
| Success #2 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 21:06:2020 - 09:00 GMT |
| Grading #1 | false |
| Grading #2 | false |
| Payout | USD 0 |
KPI 4.6 - Forum Sudo
As the usage of the forum has increased significantly, it's time to have proper maintenance, moderation and support.
| Key | Value |
|---|---|
| Reward | USD 60 |
| Active from | 12.06.2020 - 16:00 GMT |
| Measurement period | 3 days |
| Success #1 | The Council selects one (or more that shares a key) users to act as the forum sudo. |
| Success #2 | The forum sudo cleans up the forum, and creates new categories and subcategories in a way agreed upon. |
| Success #3 | All reports are added in the new, appropriate categories, with links to relevant information. |
| Annihilation | The forum sudo goes rogue. |
| Graded | 21:06:2020 - 09:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | false |
| Payout | USD 40 |
KPI 4.7 - Storage Providers Stay Up After the Runtime Upgrade
Due to the runtime upgrade at block #1279512, the Storage Providers need to upgrade and restart their nodes.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 15.06.2020 ~ 10:00 GMT |
| Measurement period | 1/2 day |
| Success #1 | Within 100 blocks of the upgrade, half of the Storage Providers are up and working. |
| Success #2 | Within 7200 blocks of the upgrade, all the Storage Providers are up and working. |
| Annihilation | All Storage Providers are fired before the upgrade |
| Graded | 21:06:2020 - 09:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
Round 5
KPI 5.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 19.06.2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | The difference between the timestamps of: block 1341211 and block 1441593 must be less than 604,710,000 milliseconds |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 28.06.2020 - 11:00 GMT |
| Grading #1 | 604,248,000 -> true |
| Payout | USD 50 |
KPI 5.2 - Validator Stake
To ensure no foul play by Validators, the incentives must be strong enough to keep them honest.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 19.06.2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | Have the Validators earn >20% of the max, on average over the last 72,000 blocks (5 days) |
| Success #2 | Have the Validators earn >30% of the max, on average over the last 57,600 blocks (4 days) |
| Success #3 | Have the Validators earn >40% of the max, on average over the last 43,200 blocks (3 days) |
| Success #4 | Have the Validators earn >50% of the max, on average over the last 28,800 blocks (2 days) |
| Annihilation | N/A |
| Graded | 28.06.2020 - 11:00 GMT |
| Grading #1 | Range: #1369597-#1441309Rewards,Remaining: 54704,440684Result: 11.0% -> false |
| Grading #2 | Range: #1383991-#1441309Rewards,Remaining: 43022,352731Result: 10.8% -> false |
| Grading #3 | Range: #1398324-#1441309Rewards,Remaining: 31367,266359Result: 10.5% -> false |
| Grading #4 | Range: #1412691-#1441309Rewards,Remaining: 19761,177867Result: 10.0% -> false |
| Payout | USD 0 |
KPI 5.3 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 60 |
| Active from | 19.06.2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Success #3 | All forum posts discussing old proposals are added to the their respective proposal discussion with metadata |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 28.06.2020 - 11:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | false |
| Payout | USD 40 |
KPI 5.4 - Council Performance Review and Minutes
There needs to be some level of accountability and transparency for the Council. Weekly reports would help the users make informed votes.
| Key | Value |
|---|---|
| Reward | USD 60 |
| Active from | 19.06.2020 - 16:00 GMT |
| Measurement period | 3 days |
| Success #1 | The fourth Council on Constantinople (#1240411-#1341211) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Annihilation | The report contains incorrect information. |
| Graded | 28.06.2020 - 11:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 60 |
KPI 5.5 - Tokenomics and State of the Network Reporting
In addition to the above, there needs to be bookeeping/accounting of the platform's spending, and some general network data.
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 19.06.2020 - 16:00 GMT |
| Measurement period | 3 days |
| Success #1 | The fourth Council on Constantinople (#1240411-#1341211) produces a report based on the newest template |
| Success #2 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 28.06.2020 - 11:00 GMT |
| Grading #1 | false |
| Grading #2 | false |
| Payout | USD 0 |
Round 6
KPI 6.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 20 |
| Active from | 26:06:2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | The difference between the timestamps of: block 1442011 and block 1542393 must be less than 604,710,000 milliseconds |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 05.07.2020 - 08:00 GMT |
| Grading #1 | true |
| Payout | USD 20 |
KPI 6.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 26.06.2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 05.07.2020 - 08:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 6.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users make informed votes.
| Key | Value |
|---|---|
| Reward | USD 120 |
| Active from | 26.06.2020 - 16:00 GMT |
| Measurement period | 3 days |
| Success #1 | The fifth Council on Constantinople (#1341211-#1442010) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | he fifth Council on Constantinople (#1341211-#1442010) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 05.07.2020 - 08:00 GMT |
| Grading #1-4 | false |
| Payout | USD 0 |
KPI 6.4 - Telegram Bots
Some Telegram bots have already been created, but they need some improvements and to be presented in the main channel. Details can be found in the blog.
| Key | Value |
|---|---|
| Reward | USD 400 |
| Active from | 26.06.2020 - 16:00 GMT |
| Measurement period | 7 days |
| Success #1 | Validators: At the end of each era, reports the status of the Validator set. Also report slashings. |
| Success #2 | Storage Providers: Reports 'expired', 'down' and 'offline' Storage Providers. |
| Success #3 | Proposals: Reports all 'Proposal Status' changes. |
| Success #4 | Council: Reports all 'Council' and 'Council Election' status changes. |
| Success #5 | Forum: Reports all new 'posts', 'threads' and 'categories' made. |
| Success #6 | Curators: Reports all new 'Openings' and status changes of openings. |
| Success #7 | Channels: Reports all new 'Channels' made. |
| Success #8 | Content: Reports 'Entity properties' changed in the 'Video Class'. |
| Annihilation | Bots contain malicious code |
| Graded | 05.07.2020 - 08:00 GMT |
| Grading #1-8 | false |
| Payout | USD 0 |
Round 7
KPI 7.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 20 |
| Active from | 03.07.2020 ~17:00 GMT - #1542811 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block#1542811 and block #1643193 must be less than 604,710,000milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 12.07.2020 - 08:00 GMT |
| Grading #1 | true |
| Payout | USD 20 |
KPI 7.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 03.07.2020 ~17:00 GMT - #1542811 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 12.07.2020 - 08:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 7.3 - Improve Community Repo
For the community to submit KPI deliverables, contribute code and maintain publish ideas, the community GitHub repo needs improvements.
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 03.07.2020 ~17:00 GMT - #1542811 |
| Measurement period | 7 days |
| Success #1 | Agree on a concept, based on the information outlined here. |
| Success #2 | A PR to the community, based on what was agreed in 1, is opened. |
| Success #3 | A proposal to merge the PR is made and approved. |
| Annihilation | A PR is approved despite not being in line with the concepts in 1and 2. |
| Graded | 12.07.2020 - 08:00 GMT |
| Grading #1 | false |
| Grading #2 | false |
| Grading #3 | false |
| Payout | USD 0 |
KPI 7.4 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users make informed votes.
| Key | Value |
|---|---|
| Reward | USD 120 |
| Active from | 03.07.2020 ~17:00 GMT - #1542811 |
| Measurement period | 3 days |
| Success #1 | The fifth Council on Constantinople (#1442010-#1542810) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | he fifth Council on Constantinople (#1442010-#1542810) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 12.07.2020 - 08:00 GMT |
| Grading #1 | false |
| Grading #2 | false |
| Grading #3 | false |
| Grading #4 | false |
| Payout | USD 0 |
KPI 7.5 - Telegram Bots
On account of the increased technical complexity and coordination required for this task, we have decided to extend the deadline a further two weeks.
Some Telegram bots have already been created, but they need some improvements and to be presented in the main channel. Details can be found in the blog.
| Key | Value |
|---|---|
| Reward | USD 400 |
| Active from | 03:07:2020 ~17:00 GMT - #1542811 |
| Measurement period | 14 days |
| Success #1 | Validators: At the end of each era, reports the status of the Validator set. Also report slashings. |
| Success #2 | Storage Providers: Reports 'expired', 'down' and 'offline' Storage Providers. |
| Success #3 | Proposals: Reports all 'Proposal Status' changes. |
| Success #4 | Council: Reports all 'Council' and 'Council Election' status changes. |
| Success #5 | Forum: Reports all new 'posts', 'threads' and 'categories' made. |
| Success #6 | Curators: Reports all new 'Openings' and status changes of openings. |
| Success #7 | Channels: Reports all new 'Channels' made. |
| Success #8 | Content: Reports 'Entity properties' changed in the 'Video Class'. |
| Annihilation | Bots contain malicious code |
| Grading | 19.07.2020 - 16:00 GMT |
Round 8
KPI 8.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 10.07.2020 ~17:30 GMT - #1643611 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block #1643611 and block#1743993 must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 19.07.2020 - 09:00 GMT |
| Grading #1 | true |
| Payout | USD 50 |
KPI 8.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 10.07.2020 ~17:30 GMT - #1643611 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 19.07.2020 - 09:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 8.3 - Improve Community Repo
For the community to submit KPI deliverables, contribute code and maintain publish ideas, the community GitHub repo needs improvements.
| Key | Value |
|---|---|
| Reward | USD 150 |
| Active from | 10.07.2020 ~17:30 GMT - #1643611 |
| Measurement period | 7 days |
| Success #1 | Agree on a concept, based on the information outlined here. |
| Success #2 | A PR to the community, based on what was agreed in 1, is opened. |
| Success #3 | A proposal to merge the PR is made and approved. |
| Annihilation | A PR is approved despite not being in line with the concepts in 1and 2. |
| Graded | 19.07.2020 - 09:00 GMT |
| Grading #1 | false |
| Grading #2 | false |
| Grading #3 | false |
| Payout | USD 0 |
KPI 8.4 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 10.07.2020 ~17:30 GMT - #1643611 |
| Measurement period | 3 days |
| Success #1 | The sixth Council on Constantinople (#1542811-#1643610) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The sixth Council on Constantinople (#1542811-#1643610) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 19.07.2020 - 09:00 GMT |
| Grading #1-4 | false |
| Payout | USD 0 |
KPI 8.5 - Telegram Bots
KPI 7.5 from last round had a 14 day measurement period. This update increases the reward from $400 to $600.
Some Telegram bots have already been created, but they need some improvements and to be presented in the main channel. Details can be found in the blog.
| Key | Value |
|---|---|
| Reward | USD 600 |
| Active from | 03.07.2020 ~17:00 GMT - #1542811 |
| Measurement period | 14 days |
| Success #1 | Validators: At the end of each era, reports the status of the Validator set. Also report slashings. |
| Success #2 | Storage Providers: Reports 'expired', 'down' and 'offline' Storage Providers. |
| Success #3 | Proposals: Reports all 'Proposal Status' changes. |
| Success #4 | Council: Reports all 'Council' and 'Council Election' status changes. |
| Success #5 | Forum: Reports all new 'posts', 'threads' and 'categories' made. |
| Success #6 | Curators: Reports all new 'Openings' and status changes of openings. |
| Success #7 | Channels: Reports all new 'Channels' made. |
| Success #8 | Content: Reports 'Entity properties' changed in the 'Video Class'. |
| Annihilation | Bots contain malicious code |
| Graded | 19.07.2020 - 09:00 GMT |
| Grading #1-8 | false |
| Payout | USD 0 |
Round 9
KPI 9.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 17.07.2020 ~17:30 GMT - #1744411 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block #1744411 and block#1844793 must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 26.07.2020 - 10:00 GMT |
| Grading #1 | true - 603,756,001 |
| Payout | USD 50 |
KPI 9.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 17.07.2020 ~17:30 GMT - #1744411 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 26.07.2020 - 10:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 9.3 - Improve Community Repo
For the community to submit KPI deliverables, contribute code and maintain publish ideas, the community GitHub repo needs improvements.
| Key | Value |
|---|---|
| Reward | USD 150 |
| Active from | 17.07.2020 ~17:30 GMT - #1744411 |
| Measurement period | 7 days |
| Success #1 | Agree on a concept, based on the information outlined here. |
| Success #2 | A PR to the community, based on what was agreed in 1, is opened. |
| Success #3 | A proposal to merge the PR is made and approved. |
| Annihilation | A PR is approved despite not being in line with the concepts in 1and 2. |
| Graded | 26.07.2020 - 10:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 150 |
KPI 9.4 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 17.07.2020 ~17:30 GMT - #1744411 |
| Measurement period | 3 days |
| Success #1 | The seventh Council on Constantinople (#1643611-#1744410) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The seventh Council on Constantinople (#1643611-#1744410) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 26.07.2020 - 10:00 GMT |
| Grading #1-4 | false |
| Payout | USD 0 |
KPI 9.5 - Telegram Bots
KPI 8.5 from last round had a 14 day measurement period. This update increases the reward from $600 to $800.
Some Telegram bots have already been created, but they need some improvements and to be presented in the main channel. Details can be found in the blog.
| Key | Value |
|---|---|
| Reward | USD 800 |
| Active from | 03.07.2020 ~17:00 GMT - #1542811 |
| Measurement period | 21 days |
| Success #1 | Validators: At the end of each era, reports the status of the Validator set. Also report slashings. |
| Success #2 | Storage Providers: Reports 'expired', 'down' and 'offline' Storage Providers. |
| Success #3 | Proposals: Reports all 'Proposal Status' changes. |
| Success #4 | Council: Reports all 'Council' and 'Council Election' status changes. |
| Success #5 | Forum: Reports all new 'posts', 'threads' and 'categories' made. |
| Success #6 | Curators: Reports all new 'Openings' and status changes of openings. |
| Success #7 | Channels: Reports all new 'Channels' made. |
| Success #8 | Content: Reports 'Entity properties' changed in the 'Video Class'. |
| Annihilation | Bots contain malicious code |
| Grading | 09.08.2020 - 16:00 GMT |
Round 10
KPI 10.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 24.07.2020 ~17:30 GMT - #1845211 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block #1845211 and block#1945593 must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 02.08.2020 - 09:00 GMT |
| Grading #1 | true - 603,738,000 |
| Payout | USD 50 |
KPI 10.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in a reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 24.07.2020 ~17:30 GMT - #1845211 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 02.08.2020 - 09:00 GMT |
| Grading #1 | false |
| Grading #2 | true |
| Payout | USD 25 |
KPI 10.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 24.07.2020 ~17:30 GMT - #1845211 |
| Measurement period | 7 days |
| Success #1 | The eighth Council on Constantinople (#1744411-#1845210) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The eighth Council on Constantinople (#1744411-#1845210) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 02.08.2020 - 09:00 GMT |
| Grading #1-4 | false |
| Payout | USD 0 |
KPI 10.4 - Storage Provider Post Runtime Upgrade
After the runtime upgrade, scheduled at approx. block #1916000, the platform needs to restore the storage system.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 24.07.2020 ~17:30 GMT - #1845211 |
| Measurement period | 7 days |
| Success #1 | Create an opening for a storage lead. |
| Success #2 | Open it for applications. |
| Success #3 | Choose a new storage lead. |
| Success #4 | Fund the storage provider mint. |
| Success #5 | Ensure at least 4 storage nodes are up and running. |
| Annihilation | The storage lead fails to run a storage node. |
| Graded | 02.08.2020 - 09:00 GMT |
| Grading #1-2 | true |
| Grading #3-5 | false |
| Payout | USD 80 |
KPI 10.5 - Telegram Bots
Some Telegram bots have already been created, but they need some improvements and to be presented in the main channel. Details can be found in the blog.
| Key | Value |
|---|---|
| Reward | USD 800 |
| Active from | 03.07.2020 ~17:00 GMT - #1542811 |
| Measurement period | 21 days |
| Success #1 | Validators: At the end of each era, reports the status of the Validator set. Also report slashings. |
| Success #2 | Storage Providers: Reports 'expired', 'down' and 'offline' Storage Providers. |
| Success #3 | Proposals: Reports all 'Proposal Status' changes. |
| Success #4 | Council: Reports all 'Council' and 'Council Election' status changes. |
| Success #5 | Forum: Reports all new 'posts', 'threads' and 'categories' made. |
| Success #6 | Curators: Reports all new 'Openings' and status changes of openings. |
| Success #7 | Channels: Reports all new 'Channels' made. |
| Success #8 | Content: Reports 'Entity properties' changed in the 'Video Class'. |
| Annihilation | Bots contain malicious code |
| Grading | 09.08.2020 - 16:00 GMT |
Round 11
KPI 11.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 31.07.2020 ~18:00 GMT - #1946011 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block #1946011 and block#2046393 must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 09.08.2020 - 09:00 GMT |
| Grading #1 | true - 603,342,000 |
| Payout | USD 50 |
KPI 11.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in a reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 31.07.2020 ~18:00 GMT - #1946011 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 09.08.2020 - 09:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 11.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 31.07.2020 ~18:00 GMT - #1946011 |
| Measurement period | 7 days |
| Success #1 | The ninth Council on Constantinople (#1845211-#1946010) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The ninth Council on Constantinople (#1845211-#1946010) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 09.08.2020 - 09:00 GMT |
| Grading #1-4 | false |
| Payout | USD 0 |
KPI 11.4 - Storage Provider Post Runtime Upgrade
After the runtime upgrade at block #1914789, the platform needs to restore the storage system.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 31.07.2020 ~18:00 GMT - #1946011 |
| Measurement period | 7 days |
| Success #1 | Discuss, and decide on the rewards for the Lead. |
| Success #2 | Start the review process, and discuss candidates. |
| Success #3 | Choose a new Storage Lead. |
| Success #4 | Set a budget for the Storage Working Group, |
| and fund the Storage Provider Mint. | |
| Success #5 | Ensure at least 4 storage-nodes are up and running. |
| Annihilation | The Storage Lead fails to run a storage node. |
| Graded | 09.08.2020 - 09:00 GMT |
| Grading #1-2 | true |
| Grading #3-5 | false |
| Payout | USD 80 |
KPI 11.5 - Telegram Bots
Some Telegram bots have already been created, but they need some improvements and to be presented in the main channel.
| Key | Value |
|---|---|
| Reward | USD 800 |
| Active from | 03.07.2020 ~17:00 GMT - #1542811 |
| Measurement period | 21 days |
| Success #1 | Validators: At the end of each era, reports the status of the Validator set. Also report slashings. |
| Success #2 | Storage Providers: Reports 'expired', 'down' and 'offline' Storage Providers. |
| Success #3 | Proposals: Reports all 'Proposal Status' changes. |
| Success #4 | Council: Reports all 'Council' and 'Council Election' status changes. |
| Success #5 | Forum: Reports all new 'posts', 'threads' and 'categories' made. |
| Success #6 | Curators: Reports all new 'Openings' and status changes of openings. |
| Success #7 | Channels: Reports all new 'Channels' made. |
| Success #8 | Content: Reports 'Entity properties' changed in the 'Video Class'. |
| Annihilation | Bots contain malicious code |
| Graded | 12.08.2020 - 11:00 GMT |
| Grading #1 | false |
| Grading #2 | false |
| Grading #3 | partial- Not fully featured |
| Grading #4 | true |
| Grading #5 | true |
| Grading #6 | false |
| Grading #7 | true |
| Grading #8 | false |
| Grading #3-5 | false |
| Payout | USD 350 |
Round 12
KPI 12.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 07.08.2020 ~18:00 GMT - #2046811 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block #2046811 and block#2147193 must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 17.08.2020 - 18:00 GMT |
| Grading #1 | true |
| Payout | USD 50 |
KPI 12.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in a reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 07.08.2020 ~18:00 GMT - #2046811 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 17.08.2020 - 18:00 GMT |
| Grading #1 | true |
| Grading #2 | false |
| Payout | USD 25 |
KPI 12.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 07.08.2020 ~18:00 GMT - #2046811 |
| Measurement period | 7 days |
| Success #1 | The tenth Council on Constantinople (#1946011-#2046810) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The tenth Council on Constantinople (#1946011-#2046810) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 17.08.2020 - 19:45 GMT |
| Grading #1-4 | false |
| Payout | USD 0 |
KPI 12.4 - Storage Provider Post Runtime Upgrade
After the runtime upgrade at block #1914789, the platform needs to restore the storage system.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 07.08.2020 ~18:00 GMT - #2046811 |
| Measurement period | 7 days |
| Success #1 | Choose a new Storage Lead. |
| Success #2 | Set a budget for the Storage Working Group, and fund the Storage Provider Mint. |
| Success #3 | Ensure at least 4 storage-nodes are fully synced, and up and running. |
| Success #4 | Once Success event 3 is achieved fully sycned, the storage node with Worker ID 1 is fired. |
| Annihilation | No new fully synced storage-nodes running at end of the measurement period. |
| Graded | 17.08.2020 - 18:00 GMT |
| Grading #1 | true |
| Grading #2 | false |
| Grading #3 | false |
| Grading #4 | false |
| Payout | USD 0 (Annihilation triggered) |
KPI 12.5 - Determine New KPI Structure
The KPI system has not worked as intended. An improved system will be proposed as a Text Proposal before block #2086850.
| Key | Value |
|---|---|
| Reward | USD 500 |
| Active from | 07.08.2020 ~18:00 GMT - #2046811 |
| Measurement period | 7 days |
| Success #1 | The proposed system is evaluated by the Council, and opinions are contributed by >8 CMs in the proposal discussion. |
| Success #2 | Other community members, with a total balance+stake >5% of issuance, provide feedback on the forum. |
| Success #3 | Based on the feedback given, the Council creates a list of questions and suggested changes in the form of an approved Text Proposal. |
| Success #4 | If a new design is agreed upon by Jsgenesis and the community, a PR documenting the system in full is opened in the Community Repo. |
| Success #5 | The group or person that created this PR, receives the tJOY equivalent of at least $100USD through a Spending Proposal. |
| Annihilation | Not applicable. |
| Graded | 17.08.2020 - 20:00 GMT |
| Grading #1 | true |
| Grading #2 | false |
| Grading #3 | false |
| Grading #4 | false |
| Grading #5 | false |
| Payout | USD 100 |
Round 13
KPI 13.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 14.08.2020 ~18:00 GMT - #2147611 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of blocks #2147611 and #2247993 must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 23.08.2020 - 17:00 GMT |
| Grading #1 | true |
| Payout | USD 50 |
KPI 13.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in a reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 14.08.2020 ~18:00 GMT - #2147611 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 24.08.2020 - 11:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 13.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 14.08.2020 ~18:00 GMT - #2147611 |
| Measurement period | 7 days |
| Success #1 | The eleventh Council on Constantinople (#2046811-#2147610) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The eleventh Council on Constantinople (##2046811-#2147610) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 24.08.2020 - 11:00 GMT |
| Grading #1 | false |
| Grading #2 | false |
| Grading #3 | false |
| Grading #4 | false |
| Payout | USD 0 |
KPI 13.4 - Storage Provider Post Runtime Upgrade
After the runtime upgrade at block #1914789, the platform needs to restore the storage system.
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 14.08.2020 ~18:00 GMT - #2147611 |
| Measurement period | 7 days |
| Success #1 | Set a budget for the Storage Working Group, and fund the Storage Provider Mint. |
| Success #2 | Ensure at least 4 storage-nodes are fully synced, and up and running. |
| Success #3 | Once Success event 2 is achieved fully sycned, the storage node with Worker ID 1 is fired. |
| Annihilation | No new fully synced storage-nodes running at end of the measurement period. |
| Graded | 24.08.2020 - 11:00 GMT |
| Grading #1 | true |
| Grading #2 | false |
| Grading #3 | false |
| Payout | USD 33 |
KPI 13.5 - Appoint Council Secretary
In preparation for some changes to the KPI system, the Council must appoint one of their own as the Council Secretary, responsible for adding Council Reports (13.3) and representing the Council in the community repo (with some enhanced repo maintenance privileges).
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 14.08.2020 ~18:00 GMT - #2147611 |
| Measurement period | 7 days |
| Success #1 | The Council informally appoints a Council Secretary through a spending proposal and pays them an appropriate rate for their responsibilities (below). |
| Success #2 | The spending proposal must provide a link to the Council Secretary's GitHub account so we can provide them with a higher permission level on the community repo. |
| Annihilation | No Council Secretary is appointed. |
| Graded | 24.08.2020 - 11:00 GMT |
| Grading #1 | true |
| Grading #2 | false |
| Payout | USD 50 |
KPI 13.6 - Council Secretary Adds Council Reports
Past Council Reports have not been included in the community repo. These need to be added for purposes of accountability and transparency.
| Key | Value |
|---|---|
| Reward | USD 150 |
| Active from | 14.08.2020 ~18:00 GMT - #2147611 |
| Measurement period | 7 days |
| Success #1 | The Council Secretary adds all previous Council reports to the community repo (via Pull Request). |
| Annihilation | No Council Reports are added to the repo. |
| Graded | 24.08.2020 - 11:00 GMT |
| Grading #1 | partial (3/12) |
| Payout | USD 38 |
KPI 13.7 - Council Secretary Adds Tokenomics Reports
Past Tokemomics & State of the Network reports have not been included in the community repo. These need to be added to help participants better understand how our testnets operate.
| Key | Value |
|---|---|
| Reward | USD 150 |
| Active from | 14.08.2020 ~18:00 GMT - #2147611 |
| Measurement period | 7 days |
| Success #1 | The Council Secretary adds all previous Tokemomics & State of the Network reports to the community repo (via Pull Request) |
| Annihilation | No Tokenomics Reports are added to the repo. |
| Graded | 24.08.2020 - 11:00 GMT |
| Grading #1 | false |
| Payout | USD 0 |
Round 14
KPI 14.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 21.08.2020 ~18:00 GMT - #2248411 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block #2248411 and block#2348793 must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 30.08.2020 - 10:00 GMT |
| Grading #1 | true |
| Payout | USD 50 |
KPI 14.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in a reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 21.08.2020 ~18:00 GMT - #2248411 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 30.08.2020 - 10:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 14.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 21.08.2020 ~18:00 GMT - #2248411 |
| Measurement period | 7 days |
| Success #1 | The twelfth Council on Constantinople (#2147611-#2248410) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The twelfth Council on Constantinople (#2147611-#2248410) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 30.08.2020 - 10:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | false |
| Grading #4 | false |
| Payout | USD 100 |
KPI 14.4 - Appoint New Council Secretary
In preparation for some changes to the KPI system, the Council must appoint one of their own as the Council Secretary, responsible for adding Council Reports (14.3) and representing the Council in the community repo (with some enhanced repo maintenance privileges).
| Key | Value |
|---|---|
| Reward | USD 100 |
| Active from | 21.08.2020 ~18:00 GMT - #2248411 |
| Measurement period | 7 days |
| Success #1 | The Council informally appoints a Council Secretary through a spending proposal and pays them an appropriate rate for their responsibilities (below). |
| Success #2 | The spending proposal must provide a link to the Council Secretary's GitHub account so we can provide them with a higher permission level on the community repo. |
| Annihilation | No Council Secretary is appointed. |
| Graded | 30.08.2020 - 10:00 GMT |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 100 |
KPI 14.5 - Council Secretary Adds Council Reports
Past Council Reports have not been included in the community repo. These need to be added for purposes of accountability and transparency.
| Key | Value |
|---|---|
| Reward | USD 150 |
| Active from | 21.08.2020 ~18:00 GMT - #2248411 |
| Measurement period | 7 days |
| Success #1 | The Council Secretary adds all previous Council reports to the community repo (via Pull Request). |
| Annihilation | No Council Reports are added to the repo. |
| Graded | 30.08.2020 - 10:00 GMT |
| Grading #1 | false |
| Payout | USD 0 |
KPI 14.6 - Council Secretary Adds Tokenomics Reports
Past Tokemomics & State of the Network reports have not been included in the community repo. These need to be added to help participants better understand how our testnets operate.
| Key | Value |
|---|---|
| Reward | USD 150 |
| Active from | 21.08.2020 ~18:00 GMT - #2248411 |
| Measurement period | 7 days |
| Success #1 | The Council Secretary adds all previous Tokemomics & State of the Network reports to the community repo (via Pull Request) |
| Annihilation | No Tokenomics Reports are added to the repo. |
| Graded | 30.08.2020 - 10:00 GMT |
| Grading #1 | false |
| Payout | USD 0 |
Round 15
KPI 15.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 29.08.2020 ~23:00 UTC - #2363611 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block #2363611 and block#2463993 must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 06.09.2020 - 09:00 UTC |
| Grading #1 | false |
| Payout | USD 0 |
KPI 15.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in a reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 29.08.2020 ~18:00 UTC - #2363611 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 06.09.2020 - 09:00 UTC |
| Grading #1 | false (73) |
| Grading #2 | true |
| Payout | USD 50 |
KPI 15.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 29.08.2020 ~18:00 UTC - #2363611 |
| Measurement period | 7 days |
| Success #1 | The thirteenth Council on Constantinople (#2248411-#2363610) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The thirteenth Council on Constantinople (#2248411-#2363610) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 06.09.2020 - 09:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | false |
| Grading #4 | false |
| Payout | USD 100 |
KPI 15.4 - Appoint New Council Secretary
In preparation for some changes to the KPI system, the Council must appoint one of their own as the Council Secretary, responsible for adding Council Reports (15.3) and representing the Council in the community repo (with some enhanced repo maintenance privileges).
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 29.08.2020 ~23:00 UTC - #2363611 |
| Measurement period | 7 days |
| Success #1 | The Council informally appoints a Council Secretary through a spending proposal and pays them an appropriate rate for their responsibilities (below). |
| Success #2 | The spending proposal must provide a link to the Council Secretary's GitHub account so we can provide them with a higher permission level on the community repo. |
| Annihilation | No Council Secretary is appointed. |
| Graded | 06.09.2020 - 09:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 15.5 - Council Evaluates the Working Groups
The Council Evaluates the performance of the Storage Provider and Curator Working Groups over the last month.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 31.08.2020 ~23:00 UTC - #2392411 |
| Measurement period | 5 days |
| Success #1 | The Council approves a Text or Spending Proposal, containing a review of the performance and resource allocation of the Curator Working Group from block #1949025 to the final block of August 2020 (UTC). |
| Success #2 | The Council approves a Text or Spending Proposal, that reviews the performance and resource allocation of the Storage Provider Working Group, from block #1949025 to the final block of August 2020 (UTC). |
| Annihilation | The reports contains objectively false data. |
| Graded | 06.09.2020 - 09:00 UTC |
| Grading #1 | false |
| Grading #2 | false |
| Payout | USD 0 |
Round 16
KPI 16.1 - 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 (divided by 1000). Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 06.09.2020 ~00:00 UTC - #2464411 |
| Measurement period | 7 days |
| Success #1 | The difference between timestamps of block#2464411 and block #2463993must be less than 604,710,000 milliseconds. |
| Annihilation | Block finalization lags more than 600 blocks behind head at any point throughout the Measurement period |
| Graded | 14.09.2020 - 13:00 UTC |
| Grading #1 | true |
| Payout | USD 50 |
KPI 16.2 - Proposal Clearance
For the governance process to work, all proposals must be dealt with professionally, and in a reasonable time frame to avoiding blocking new proposals coming in. Definition of terms can be found here.
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 06.09.2020 ~00:00 UTC - #2464411 |
| Measurement period | 7 days |
| Success #1 | No proposals expire due to missing votes |
| Success #2 | At no point will the number of active proposal stay at 5 for longer than 14,400 blocks (~24h) |
| Annihilation | No malicious or unreasonable proposals are approved |
| Graded | 14.09.2020 - 13:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 16.3 - Council Reporting
There needs to be some level of accountability and transparency for the Council. Weekly reporting of workflow and Tokenomics will allow users to make informed votes.
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 06.09.2020 ~00:00 UTC - #2464411 |
| Measurement period | 7 days |
| Success #1 | The 14th Council on Constantinople (#2363611-#2464410) produces a log of events, with all of the Council's actions, challenges and tasks. |
| Success #2 | This is accompanied by a report covering its own workflow, challenges, thinking and performance. |
| Success #3 | The 14th Council on Constantinople (#2363611-#2464410) produces a report based on the newest template. |
| Success #4 | The script (in typescript) that produces the output is made available alongside the report. |
| Annihilation | The report contains incorrect information. |
| Graded | 14.09.2020 - 13:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Grading #3 | false |
| Grading #4 | false |
| Payout | USD 100 |
KPI 16.4 - Appoint New Council Secretary
In preparation for some changes to the KPI system, the Council must appoint one of their own as the Council Secretary, responsible for adding Council Reports (16.3) and representing the Council in the community repo (with some enhanced repo maintenance privileges).
| Key | Value |
|---|---|
| Reward | USD 50 |
| Active from | 06.09.2020 ~00:00 UTC - #2464411 |
| Measurement period | 7 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 with a higher permission level on the community repo. |
| Annihilation | No Council Secretary is appointed. |
| Graded | 14.09.2020 - 13:00 UTC |
| Grading #1 | true |
| Grading #2 | true |
| Payout | USD 50 |
KPI 16.5 - Council Approves New Rewards, KPI system and Chain Parameters for Alexandria
With the new testnet (on a new chain) Alexandria fast approaching, some changes will be made. Jsgenesis will make a Text Proposal listing each proposed change (quantitative and qualitative).
| Key | Value |
|---|---|
| Reward | USD 200 |
| Active from | 08.09.2020 ~00:00 UTC - #2493211 |
| Measurement period | 5 days |
| Success #1 | The Council opens up a forum post, to discuss with the community, and evaluates the changes proposed |
| Success #2 | The Council Secretary makes a Proposal that presents a summary of the discussions, addressing each item in the Proposal. Finally, it contains a conclusion, with their rationale for agreeing, or disagreeing with each individual value |
| Success #3 | The Councils Proposal is approved |
| Annihilation | The approved Proposal fails to include arguments against their conclusion |
| Graded | 14.09.2020 - 13:00 UTC |
| Grading #1 | true* |
| Grading #2 | true* |
| Grading #3 | true* |
| Payout | USD 200 |
*Jsgenesis failed to deliver on time...
Definition of Terms
Curated
A curated item in the content directory means that it's tagged with appropriate and well researched metadata, such as:
- All available fields are populated if appropriate and available
- Thumbnails, descriptions and links are in the correct format, informative, and not copied without permission
- Licenses and attributions are correct, thus avoiding making content that would otherwise be within the Platforms ToS, fall out of this category
- Content of high quality and importance should be "promoted", as featured content
Terms of Service (ToS)
By using any of Our Software, you agree to not state, write, link to, download, distribute, share or encourage other users to state, write, link to, download, distribute, share or encourage anything that:
- breach or infringe any copyright or intellectual property of any third party.
- is abusive, malicious, threatening or unlawful in any way.
Company has not reviewed all content of this website, and is not responsible for content submitted or provided by individuals or groups not directly tied to them.
Timestamp
Each block produced contains a timestamp. This can be found in the explorer or through a chain state query. This timestamp will be the reference for grading when applicable.
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.