Testnet4 Challenges release

challenge-OT4-B1/readme.md

@@ -0,0 +1,25 @@
+| Challenge | Title | GTU Reward | Seats | Start Date | Last Date for Submission  |
+| -         | -     |          -:| -     |-           | -                         |
+| OT4-B1    | Run a node for a month.           | 2500 GTU | 750 | 20-01-2021 23:00 PT | 03-03-2021 23:00 PT |
+##
+
+## Mission
+
+- Run a node for a month (30 full calender days).
+
+- The 30 days count starts from 21-01-2021 at 08:00 CET, even if you started to run your node before that. Hence, if you have uninterrupted uptime, the challenge can earliest be completed on 20-02-2021 at 08:00 CET.
+
+- If your node is down for some periods, you must add the lost time afterwards. The summary log accumulates the uptimes of the node. It must show a runtime of at least 720 hours when submitting.
+
+- This challenge can be run concurrently with either challenge OT4-B2, OT-B3 or OT4-B4 or as a stand-alone challenge. 
+
+
+## Submission
+
+- In submission.txt
+  - Add your node ID
+- Upload your summary log (see [Logs](/logs.md) for instructions & tooling)
+  - Runtime must show >= 720 hours.
+  - Do not temper with or change anything in the log. Otherwise, we cannot guarantee acceptance.
+
+Please follow the [submission instructions](/submission-process.md) thoroughly - your submission will not be accepted otherwise.

challenge-OT4-B1/submission.txt

@@ -0,0 +1 @@
+nodeid:<replace this text with the nodeid>

challenge-OT4-B2/readme.md

@@ -0,0 +1,49 @@
+| Challenge | Title | GTU Reward | Seats | Start Date | Last Date for Submission  |
+| -         | -     |          -:| -     |-           | -                         |
+| OT4-B2    | Run a baker for a month.         | 1000 GTU | 250 | 20-01-2021 23:00 PT | 03-03-2021 23:00 PT |
+##
+
+## Mission
+
+**1) Setup a node**
+
+- Run a node for a month (30 full calender days).
+
+- The 30 days count starts from 21-01-2021 at 08:00 CET, even if you started to run your node before that. Hence, if you have uninterrupted uptime, the challenge can earliest be completed on 20-02-2021 at 08:00 CET.
+
+- If your node is down for some periods, you must add the lost time afterwards. The summary log accumulates the uptimes of the node. It must show a runtime of at least 720 hours when submitting.
+
+- This challenge can be run concurrently with challenge OT4-B1 or as stand-alone challenge. It cannot be run concurrently with challenges OT4-B3 or OT4-B4.
+
+- When the node is running, move on to the next phase.
+
+**2) Baking (4 weeks)**
+
+- Create an identity and account in the mobile app. Request the GTU drop (You will receive 2000 GTUs, even though the drop says 100 GTU.
+
+- Register as baker in the concordium-client. Stake most or all of the total amount of your baker account.
+
+- Decide on if you want to restake earnings, check your current status and make changes to the restake flag accordingly.
+
+- Verify that your baker is included in the baker comitee.
+
+- Verify that your stake limit cannot be transferred.
+
+- Check your account regularly for baker rewards. 
+  - Note that with a 2000 GTU stake you might receive one baker reward per week but it is not guaranteed. Don't panic, receiving a baker reward is not mandatory for a successful submission.
+  - If you have received a baker reward, verify that it is added to the staked amount or to the amount at disposal, depending on the restake earnings status of your baker account.
+
+
+## Submission
+
+- In submission.txt
+  - Add your node ID
+  - Add your baker ID
+  - Add your baker account address
+  - Add the blockhash of the block with the add baker transaction in it
+
+- Upload your summary log (see [Logs](/logs.md) for instructions & tooling)
+  - Runtime must show >= 720 hours.
+  - Do not temper with or change anything in the log. Otherwise, we cannot guarantee acceptance.
+
+Please follow the [submission instructions](/submission-process.md) thoroughly - your submission will not be accepted otherwise.

challenge-OT4-B2/submission.txt

@@ -0,0 +1,4 @@
+nodeid:<replace this text with the nodeid>
+bakerid:<replace this text with the bakerid>
+accountaddress:<replace this text with the account address>
+blockhash_addbaker:<replace this text with the blockhash of the block with the add baker transaction in it>

challenge-OT4-B3/readme.md

@@ -0,0 +1,77 @@
+| Challenge | Title | GTU Reward | Seats | Start Date | Last Date for Submission  |
+| -         | -     |          -:| -     |-           | -                         |
+| OT4-B3    | Register and deregister as baker. | 2000 GTU | 250 | 20-01-2021 23:00 PT | 03-03-2021 23:00 PT |
+
+##
+
+
+## Mission
+
+**1) Setup a node**
+
+- Run a node for a month (30 full calender days).
+
+- The 30 days count starts from 21-01-2021 at 08:00 CET, even if you started to run your node before that. Hence, if you have uninterrupted uptime, the challenge can earliest be completed on 20-02-2021 at 08:00 CET.
+
+- If your node is down for some periods, you must add the lost time afterwards. The summary log accumulates the uptimes of the node. It must show a runtime of at least 720 hours when submitting.
+
+- This challenge can be run concurrently with challenge OT4-B1 or as stand-alone challenge. It cannot be run concurrently with challenges OT4-B2 or OT4-B4.
+
+- When the node is running, move on to the next phase.
+
+**2) Baking (3 weeks)**
+
+- Create an identity and account in the mobile app. Request the GTU drop (You will receive 2000 GTUs, even though the drop says 100 GTU.
+
+- Register as baker in the concordium-client. Stake most or all of the total amount of your baker account.
+
+- Decide on if you want to restake earnings, check your current status and make changes to the restake flag accordingly.
+
+- Verify that your baker is included in the baker comitee.
+
+- Verify that your stake limit cannot be transferred.
+
+- Check your account regularly for baker rewards. 
+  - Note that with a 2000 GTU stake you might receive one baker reward per week but it is not guaranteed. Don't panic, receiving a baker reward is not mandatory for a successful submission.
+  - If you have received a baker reward, verify that it is added to the staked amount or to the amount at disposal, depending on the restake earnings status of your baker account.
+
+- After 3 weeks, move on to the next phase.
+
+**3) Grace Period (1 week)**
+
+- Remove your baker.
+
+- Verify that your baker remains included in the baker comitee for a grace period of 1 week.
+
+- Verify that your stake limit cannot be transferred.
+
+- Check your account regularly for baker rewards. 
+  - Note that with a 2000 GTU stake you might receive one baker reward per week but it is not guaranteed. Don't panic, receiving a baker reward is not mandatory for a successful submission.
+  - If you have received a baker reward, verify that it is added to the staked amount or to the amount at disposal, depending on the restake earnings status of your baker account.
+
+- After a week, move on to the next phase.
+
+**4) Not Baking**
+
+- Verify that your node stops baking after the grace period.
+
+- Verify that your account does not receive rewards anymore.
+
+- Verify that your baker is not included in the baker comitee anymore.
+
+- Verify that your stake limit can be transferred now. Please note that there is a [known issue](https://github.com/Concordium/testnet-challenges-draft/issues/1) for the Android mobile app.
+
+## Submission
+
+- In submission.txt
+  - Add your node ID
+  - Add your baker ID
+  - Add your baker account address
+  - Add the blockhash of the block with the add baker transaction in it
+  - Add the blockhash of the block with the remove baker transaction in it
+
+- Upload your summary log (see [Logs](/logs.md) for instructions & tooling)
+  - Runtime must show >= 720 hours.
+  - Do not temper with or change anything in the log. Otherwise, we cannot guarantee acceptance.
+
+Please follow the [submission instructions](/submission-process.md) thoroughly - your submission will not be accepted otherwise.

challenge-OT4-B3/submission.txt

@@ -0,0 +1,5 @@
+nodeid:<replace this text with the nodeid>
+bakerid:<replace this text with the bakerid>
+accountaddress:<replace this text with the account address>
+blockhash_addbaker:<replace this text with the blockhash of the block with the add baker transaction in it>
+blockhash_removebaker:<replace this text with the blockhash of the block with the remove baker transaction in it>

challenge-OT4-B4/readme.md

@@ -0,0 +1,90 @@
+| Challenge | Title | GTU Reward | Seats | Start Date | Last Date for Submission  |
+| -         | -     |          -:| -     |-           | -                         |
+| OT4-B4    | Make baker updates.              | 3000 GTU | 250 | 20-01-2021 23:00 PT | 03-03-2021 23:00 PT |
+
+##
+
+
+## Mission
+
+**1) Setup a node**
+
+- Run a node for a month (30 full calender days).
+
+- The 30 days count starts from 21-01-2021 at 08:00 CET, even if you started to run your node before that. Hence, if you have uninterrupted uptime, the challenge can earliest be completed on 20-02-2021 at 08:00 CET.
+
+- If your node is down for some periods, you must add the lost time afterwards. The summary log accumulates the uptimes of the node. It must show a runtime of at least 720 hours when submitting.
+
+- This challenge can be run concurrently with challenge OT4-B1 or as stand-alone challenge. It cannot be run concurrently with challenges OT4-B2 or OT4-B3.
+
+- When the node is running, move on to the next phase.
+
+**2) Baking (1 week)**
+
+- Create an identity and account in the mobile app. Request the GTU drop (You will receive 2000 GTUs, even though the drop says 100 GTU.
+
+- Register as baker in the concordium-client. Stake 1000 GTU.
+
+- Decide on if you want to restake earnings, check your current status and make changes to the restake flag accordingly.
+
+- Verify that your baker is included in the baker comitee.
+
+- Verify that your stake limit cannot be transferred.
+
+- After 1 week, move on to the next phase.
+
+**3) Updating (3 weeks)**
+
+Make the following updates.
+
+u1) Update baker keys on the chain but use the current baker keys.
+  - Save the blockhash of the update transaction.
+  - Check the block explorer in the network dashboard via https://dashboard.testnet.concordium.com/chain/<blockhash> and verify that the transactions are shown correctly.
+
+u2) Update baker keys on the chain and use fresh baker keys.
+  - Save the blockhash of the update transaction.
+  - Check the block explorer in the network dashboard via https://dashboard.testnet.concordium.com/chain/<blockhash> and verify that the transactions are shown correctly.
+
+u3) Remove baker and then add baker again with the same keys for the same account. You will have to wait for a week until your changes take effect.
+  - Save the blockhash of the add baker transaction.
+  - Save the blockhash of the remove baker transaction.
+  - Check the block explorer in the network dashboard via https://dashboard.testnet.concordium.com/chain/<blockhash> and verify that the transactions are shown correctly.
+
+u4) Remove baker and then add baker again with fresh keys for the same account. You will have to wait for a week until your changes take effect.
+  - Save the blockhash of the add baker transaction.
+  - Save the blockhash of the remove baker transaction.
+  - Check the block explorer in the network dashboard via https://dashboard.testnet.concordium.com/chain/<blockhash> and verify that the transactions are shown correctly.
+
+u5) Remove baker and then add baker again with fresh keys for a new account. You will have to wait for a week until your changes take effect.
+  - Save the blockhash of the add baker transaction.
+  - Save the blockhash of the remove baker transaction.
+  - Check the block explorer in the network dashboard via https://dashboard.testnet.concordium.com/chain/<blockhash> and verify that the transactions are shown correctly.
+
+u6) Increase your stake to 2000 GTU. Verify that the new stake takes effect after 1 epoch.
+  - Save the blockhash of the stake transaction.
+  - Check the block explorer in the network dashboard via https://dashboard.testnet.concordium.com/chain/<blockhash> and verify that the transactions are shown correctly.
+
+## Submission
+
+- In submission.txt
+  - Add your node ID
+  - Add your first baker ID
+  - Add your second baker ID
+  - Add your first baker account address
+  - Add your second baker account address
+  - Add the blockhash of the block with the first add baker transaction in it
+  - Add the blockhash of the block with the update 1 transaction in it
+  - Add the blockhash of the block with the update 2 transaction in it
+  - Add the blockhash of the block with the add baker transaction of update 3 in it
+  - Add the blockhash of the block with the remove baker transaction of update 3 in it
+  - Add the blockhash of the block with the add baker transaction of update 4 in it
+  - Add the blockhash of the block with the remove baker transaction of update 4 in it
+  - Add the blockhash of the block with the add baker transaction of update 5 in it
+  - Add the blockhash of the block with the remove baker transaction of update 5 in it
+  - Add the blockhash of the block with the update 6 transaction in it
+
+- Upload your summary log (see [Logs](/logs.md) for instructions & tooling)
+  - Runtime must show >= 720 hours.
+  - Do not temper with or change anything in the log. Otherwise, we cannot guarantee acceptance.
+
+Please follow the [submission instructions](/submission-process.md) thoroughly - your submission will not be accepted otherwise.

challenge-OT4-B4/submission.txt

@@ -0,0 +1,15 @@
+nodeid:<replace this text with the nodeid>
+bakerid1:<replace this text with the first bakerid>
+bakerid2:<replace this text with the second bakerid>
+accountaddress1:<replace this text with the first account address>
+accountaddress2:<replace this text with the second account address>
+blockhash_addbaker:<replace this text with the blockhash of the block with the first add baker transaction in it>
+blockhash_u1:<replace this text with the blockhash of the block with the update 1 transaction in it>
+blockhash_u2:<replace this text with the blockhash of the block with the update 2 transaction in it>
+blockhash_u3_addbaker:<replace this text with the blockhash of the block with the add baker transaction of update 3 in it>
+blockhash_u3_removebaker:<replace this text with the blockhash of the block with the remove baker transaction of update 3 in it>
+blockhash_u4_addbaker:<replace this text with the blockhash of the block with the add baker transaction of update 4 in it>
+blockhash_u4_removebaker:<replace this text with the blockhash of the block with the remove baker transaction of update 4 in it>
+blockhash_u5_addbaker:<replace this text with the blockhash of the block with the add baker transaction of update 5 in it>
+blockhash_u5_removebaker:<replace this text with the blockhash of the block with the remove baker transaction of update 5 in it>
+blockhash_u6:<replace this text with the blockhash of the block with the update 6 transaction in it>

logs.md

@@ -0,0 +1,47 @@
+
+### Log submission
+
+For B1+B2/B3/B4 challenges, proof of runtime via logs is required.
+
+There is fairly verbose logging enabled by default for the node software in Testnets, so we've created a small tool `retrieve_minified_logs` to sample your full set of log files and output a summary that is acceptable for submission.
+
+- [Download retrieve_minified_logs for Linux](https://client-distribution-testnet.concordium.com/retrieve_minified_logs-linux-v1)
+- [Download retrieve_minified_logs for OS X](https://client-distribution-testnet.concordium.com/retrieve_minified_logs-macos-v1)
+- [Download retrieve_minified_logs for Windows](https://client-distribution-testnet.concordium.com/retrieve_minified_logs-windows-v1.exe)
+
+
+Simply run the relevant binary on your system where the Concordium Node has been running. The tool will output two files in the folder it is run.
+
+**⚠️ These files must be submitted without modifications. Tampering with the summary log will be detected and result in disqualification from all challenges.**
+
+
+
+### Log sizes & rotation
+
+After running the node for a significant time you may find that you are running out of disk space on your node.
+
+You can find your log file location by running:
+
+```
+docker inspect --format='{{.LogPath}}' <container_name_or_id>
+```
+
+Where the `<container_name_or_id>` is found by running `docker ps -a`.
+
+
+**⚠️ Make sure you generate log summaries for submission _before_ clearing any logs!**
+
+
+You can then clear out your current logs via the command line:
+
+```
+# On OSX / Linux
+truncate -s 0 <log_path>
+
+# On Windows
+echo.> <log_path>
+```
+
+Repeat this process if the log size gets too large again.
+
+Make sure to submit all your log summaries if you're doing any of the `B*` challenges.