šŸ“‘Testnet Rules

This page contains formal criteria and certain expectations of testnet participants

For efficient testnet running we established testnet rules that have following main sections:

Basic requirements for testers performance and operation

The minimal formal criteria for not being disqualified for inactivity:

  • Maintaining uptime for the running Node software;

  • Executing software update within 72 hours from the official update announcement

    • OR provision of a cause for inability to do so;

  • Maintaining correct operation of the software without frequent downtimes/slashing (which are not related to the issues in the software or are not accompanied by a proper bug report)

Violation of these rules will result in notifications and following disqualification from the testnet with rewards rescindment.

Formal criteria for testers to stay in the testnet based on the leaderboard score

Twice a week the leaderboard will be posted in the testnet telegram channel.

The keepers (a mapping keeper_id -> score) will be sorted by the scores in a descending order.

The algorithm for the scores is the following:

  1. Divide the time in 24-hour time frames;

  2. Calculate the number of executions of each keeper in these time frames;

  3. Calculate the final score:

We settle on the 5-day time frame-based leaderboard:

According to this leaderboard, testers, whose keepers with the highest score have scored less than a predefined , will be excluded from further participation in the testnet.

The threshold is to be announced.

Additional requirements for being in top of leaderboard and get more rewards

Performing these additional activities may result (but does not guarantee) an increased incentivization:

Tester's guidelines

Our goal is to assemble a community of enthusiastic and interested people, ready to help push the future of decentralization and automation in the blockchain. Current testers - experienced and with deep understanding of the protocol - will become the basis of the PowerAgent network of keepers, once we go live.

The following list hints what it means to be a GOOD tester and a BAD tester.

A Good Tester:

  • Is seeking knowledge in the field of web3 automation;

  • Acts in the interest of the project and the community;

  • Has up-to-date knowledge about the project state;

  • Is versed in the technical specification of the project: understands what it is and how it works;

  • Is an attentive and thoughtful person;

  • Updates his software regularly;

  • Can execute minor software maintenance (restart/reinstallation) on their own;

  • Is interested in employing automation in their own Web3 journey.

Example of a Good Tester:

Example of a Bad Tester:

On the basis of the leaderboard scores as formal criteria or subjective evaluation of performance, the Team reserves the right to suspend any person from participation in the testnet without further explanation.

Last updated