Add TestNet guidelines (#519)

* minor fix * added TestNet guidelines * TestNet guidelines link * June 29 updates
nearprotocol · Jun 26, 2020 · 8d8c8d0 · 8d8c8d0
1 parent 551c380
commit 8d8c8d0
Show file tree

Hide file tree

Showing 4 changed files with 34 additions and 5 deletions.
diff --git a/GUIDELINES.md b/GUIDELINES.md
@@ -8,9 +8,9 @@ This is not going to be easy: we will deploy hard forks constantly, we will test
 However, Stake Wars is not about doing things right or wrong. It is mostly about learning how smart contract-based delegation works, and get ready to run NEAR together.
 
 ## Rules
-There are no strict rules, rather guidelines and examples. Judges on NEAR side will rate your participation, and will update the [leaderboard](LEADERBOARD.md) every week with basic node information.
+There are no strict rules, rather guidelines and examples. Judges on NEAR side will rate your participation, and will update the [leaderboard](LEADERBOARD.md) every week.
 
-*If you are acting in good faith, you’re almost assuredly good. If you’re acting in bad faith, moderators will exclude you from the competition.*
+_If you are acting in good faith, you’re almost assuredly good. If you’re acting in bad faith, moderators will exclude you from the competition._
 
 Here are some examples and we will trust you to follow the spirit of the law:
 
@@ -39,3 +39,28 @@ We want...
 * To put the last year or so of hard work in front of our community to try it out
 * To find glaring flaws in our systems, designs and code
 * To learn what your needs are as part of the validator community
+
+## Additional guidelines to join TestNet
+We are happy to have as many professional validators and distinguished BetaNet node operators to TestNet as we can. However, TestNet network requires additional attention, as we have applications and developers actively using it - which means we can't afford to have nodes offline or not updated.
+
+Stake Wars organizers will reach out directly, proposing to shut down your BetaNet node, and receive delegated tokens on TestNet. There are no specific requirements, however the evaluation will be based on these factors (not in order of importance):
+* your staking pool uptime is in the 90th percentile of the [leaderboard](LEADERBOARD.md)
+* your pool was running for a substantial number of epochs
+* you successfully completed the Stake Wars challenges
+* you are active in the community channels (Discord and the [portal](https://portal.near.org))
+* you actively updated your node and successfully completed BetaNet migrations on Tuesdays
+* you are already a successful validator on other PoS networks
+* you contributed to `nearcore` and other NEAR repositories (submitting issues, finding bugs, improving docs...)
+
+In practical terms, to join TestNet you will have to:
+1. deploy your TestNet staking pool, using the staking pool factory [smart contract](https://explorer.testnet.near.org/accounts/stakingpool)
+2. build and run your TestNet node
+3. submit your information to [this form](https://nearprotocol1001.typeform.com/to/x4Bval). Specify both your BetaNet and TestNet pools, and don't forget to disclose your Github and Discord/Telegram IDs, so it's easier for us to contact you in case of issues
+
+The main differences with BetaNet will be:
+- less frequent updates
+- a different branch of nearcore: [stable](https://github.com/nearprotocol/nearcore/tree/stable)
+- longer epochs (43,200 blocks instead of 10,000)
+
+**Heads up:** TestNet is a permissionless network, so you can deploy your validator node and its staking pool today. However, Stake Wars organizers will delegate TestNet tokens to your pool only after reaching out and discussing your commitment in running the network.
+
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
 # Stake Wars Episode II: Return of the Validators
-June 22th 2020 update: New challenge added [here](/challenges/challenge004.md)!
+June 26th 2020 update: TestNet guidelines are live [here](GUIDELINES.md).
 
 Welcome to NEAR Stake Wars Episode II, Return of the Validators!
 

diff --git a/scenarios.md b/scenarios.md
@@ -6,7 +6,7 @@ Validators still have to properly run their nodes infrastructure, and get famili
 1. Professionally deploy and run the node
 2. Update the node software
 3. Deploy the Delegation smart contract
-4. Enroll your Validator on the Delegator App
+4. Enroll your Validator
 5. Update the Delegation smart contract
 
 ### 1.Professionally deploy and run the node
@@ -36,7 +36,7 @@ _Note: this part is still work in progress_
 - Stake delegating your BetaNet funds to the contract
 
 
-### 4. Enroll your Validator in the Delegator App
+### 4. Enroll your Validator
 Once your contract is ready, you can issue a pull request to the file [VALIDATORS.md](VALIDATORS.md), including your information at the bottom of the list. This file will automatically enroll your node in the Stake Wars 2.0, and will help users to find your staking pool.
 
 

diff --git a/updates.md b/updates.md
@@ -1,5 +1,9 @@
 # UPDATES
 
+## UPDATE June 29th
+
+* Added the guidelines to join TestNet! See them [here](GUIDELINES.md)
+
 ## UPDATE June 22nd
 
 * Added the Challenge 004, to learn how to dynamically adjust the stake of a pool: [Challenge004](/challenges/challenge004.md)