From aede14216248ad8c8a2aeef4acdaeef3113a3e6f Mon Sep 17 00:00:00 2001 From: Mario Rogic Date: Wed, 20 Jan 2021 19:38:37 +0000 Subject: [PATCH] Testnet4 Challenges release --- LICENSE | 427 ++++++++++++++++++++++++++++++++ challenge-OT4-B1/readme.md | 25 ++ challenge-OT4-B1/submission.txt | 1 + challenge-OT4-B2/readme.md | 49 ++++ challenge-OT4-B2/submission.txt | 4 + challenge-OT4-B3/readme.md | 77 ++++++ challenge-OT4-B3/submission.txt | 5 + challenge-OT4-B4/readme.md | 90 +++++++ challenge-OT4-B4/submission.txt | 15 ++ logs.md | 47 ++++ readme.md | 91 +++++++ status.md | 28 +++ submission-process.md | 46 ++++ 13 files changed, 905 insertions(+) create mode 100644 LICENSE create mode 100644 challenge-OT4-B1/readme.md create mode 100644 challenge-OT4-B1/submission.txt create mode 100644 challenge-OT4-B2/readme.md create mode 100644 challenge-OT4-B2/submission.txt create mode 100644 challenge-OT4-B3/readme.md create mode 100644 challenge-OT4-B3/submission.txt create mode 100644 challenge-OT4-B4/readme.md create mode 100644 challenge-OT4-B4/submission.txt create mode 100644 logs.md create mode 100644 readme.md create mode 100644 status.md create mode 100644 submission-process.md diff --git a/LICENSE b/LICENSE new file mode 100644 index 000000000..3b7b82d0d --- /dev/null +++ b/LICENSE @@ -0,0 +1,427 @@ +Attribution-ShareAlike 4.0 International + +======================================================================= + +Creative Commons Corporation ("Creative Commons") is not a law firm and +does not provide legal services or legal advice. Distribution of +Creative Commons public licenses does not create a lawyer-client or +other relationship. Creative Commons makes its licenses and related +information available on an "as-is" basis. Creative Commons gives no +warranties regarding its licenses, any material licensed under their +terms and conditions, or any related information. Creative Commons +disclaims all liability for damages resulting from their use to the +fullest extent possible. + +Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and +conditions that creators and other rights holders may use to share +original works of authorship and other material subject to copyright +and certain other rights specified in the public license below. The +following considerations are for informational purposes only, are not +exhaustive, and do not form part of our licenses. + + Considerations for licensors: Our public licenses are + intended for use by those authorized to give the public + permission to use material in ways otherwise restricted by + copyright and certain other rights. Our licenses are + irrevocable. Licensors should read and understand the terms + and conditions of the license they choose before applying it. + Licensors should also secure all rights necessary before + applying our licenses so that the public can reuse the + material as expected. Licensors should clearly mark any + material not subject to the license. This includes other CC- + licensed material, or material used under an exception or + limitation to copyright. More considerations for licensors: + wiki.creativecommons.org/Considerations_for_licensors + + Considerations for the public: By using one of our public + licenses, a licensor grants the public permission to use the + licensed material under specified terms and conditions. If + the licensor's permission is not necessary for any reason--for + example, because of any applicable exception or limitation to + copyright--then that use is not regulated by the license. Our + licenses grant only permissions under copyright and certain + other rights that a licensor has authority to grant. Use of + the licensed material may still be restricted for other + reasons, including because others have copyright or other + rights in the material. A licensor may make special requests, + such as asking that all changes be marked or described. + Although not required by our licenses, you are encouraged to + respect those requests where reasonable. More_considerations + for the public: + wiki.creativecommons.org/Considerations_for_licensees + +======================================================================= + +Creative Commons Attribution-ShareAlike 4.0 International Public +License + +By exercising the Licensed Rights (defined below), You accept and agree +to be bound by the terms and conditions of this Creative Commons +Attribution-ShareAlike 4.0 International Public License ("Public +License"). To the extent this Public License may be interpreted as a +contract, You are granted the Licensed Rights in consideration of Your +acceptance of these terms and conditions, and the Licensor grants You +such rights in consideration of benefits the Licensor receives from +making the Licensed Material available under these terms and +conditions. + + +Section 1 -- Definitions. + + a. Adapted Material means material subject to Copyright and Similar + Rights that is derived from or based upon the Licensed Material + and in which the Licensed Material is translated, altered, + arranged, transformed, or otherwise modified in a manner requiring + permission under the Copyright and Similar Rights held by the + Licensor. For purposes of this Public License, where the Licensed + Material is a musical work, performance, or sound recording, + Adapted Material is always produced where the Licensed Material is + synched in timed relation with a moving image. + + b. Adapter's License means the license You apply to Your Copyright + and Similar Rights in Your contributions to Adapted Material in + accordance with the terms and conditions of this Public License. + + c. BY-SA Compatible License means a license listed at + creativecommons.org/compatiblelicenses, approved by Creative + Commons as essentially the equivalent of this Public License. + + d. Copyright and Similar Rights means copyright and/or similar rights + closely related to copyright including, without limitation, + performance, broadcast, sound recording, and Sui Generis Database + Rights, without regard to how the rights are labeled or + categorized. For purposes of this Public License, the rights + specified in Section 2(b)(1)-(2) are not Copyright and Similar + Rights. + + e. Effective Technological Measures means those measures that, in the + absence of proper authority, may not be circumvented under laws + fulfilling obligations under Article 11 of the WIPO Copyright + Treaty adopted on December 20, 1996, and/or similar international + agreements. + + f. Exceptions and Limitations means fair use, fair dealing, and/or + any other exception or limitation to Copyright and Similar Rights + that applies to Your use of the Licensed Material. + + g. License Elements means the license attributes listed in the name + of a Creative Commons Public License. The License Elements of this + Public License are Attribution and ShareAlike. + + h. Licensed Material means the artistic or literary work, database, + or other material to which the Licensor applied this Public + License. + + i. Licensed Rights means the rights granted to You subject to the + terms and conditions of this Public License, which are limited to + all Copyright and Similar Rights that apply to Your use of the + Licensed Material and that the Licensor has authority to license. + + j. Licensor means the individual(s) or entity(ies) granting rights + under this Public License. + + k. Share means to provide material to the public by any means or + process that requires permission under the Licensed Rights, such + as reproduction, public display, public performance, distribution, + dissemination, communication, or importation, and to make material + available to the public including in ways that members of the + public may access the material from a place and at a time + individually chosen by them. + + l. Sui Generis Database Rights means rights other than copyright + resulting from Directive 96/9/EC of the European Parliament and of + the Council of 11 March 1996 on the legal protection of databases, + as amended and/or succeeded, as well as other essentially + equivalent rights anywhere in the world. + + m. You means the individual or entity exercising the Licensed Rights + under this Public License. Your has a corresponding meaning. + + +Section 2 -- Scope. + + a. License grant. + + 1. Subject to the terms and conditions of this Public License, + the Licensor hereby grants You a worldwide, royalty-free, + non-sublicensable, non-exclusive, irrevocable license to + exercise the Licensed Rights in the Licensed Material to: + + a. reproduce and Share the Licensed Material, in whole or + in part; and + + b. produce, reproduce, and Share Adapted Material. + + 2. Exceptions and Limitations. For the avoidance of doubt, where + Exceptions and Limitations apply to Your use, this Public + License does not apply, and You do not need to comply with + its terms and conditions. + + 3. Term. The term of this Public License is specified in Section + 6(a). + + 4. Media and formats; technical modifications allowed. The + Licensor authorizes You to exercise the Licensed Rights in + all media and formats whether now known or hereafter created, + and to make technical modifications necessary to do so. The + Licensor waives and/or agrees not to assert any right or + authority to forbid You from making technical modifications + necessary to exercise the Licensed Rights, including + technical modifications necessary to circumvent Effective + Technological Measures. For purposes of this Public License, + simply making modifications authorized by this Section 2(a) + (4) never produces Adapted Material. + + 5. Downstream recipients. + + a. Offer from the Licensor -- Licensed Material. Every + recipient of the Licensed Material automatically + receives an offer from the Licensor to exercise the + Licensed Rights under the terms and conditions of this + Public License. + + b. Additional offer from the Licensor -- Adapted Material. + Every recipient of Adapted Material from You + automatically receives an offer from the Licensor to + exercise the Licensed Rights in the Adapted Material + under the conditions of the Adapter's License You apply. + + c. No downstream restrictions. You may not offer or impose + any additional or different terms or conditions on, or + apply any Effective Technological Measures to, the + Licensed Material if doing so restricts exercise of the + Licensed Rights by any recipient of the Licensed + Material. + + 6. No endorsement. Nothing in this Public License constitutes or + may be construed as permission to assert or imply that You + are, or that Your use of the Licensed Material is, connected + with, or sponsored, endorsed, or granted official status by, + the Licensor or others designated to receive attribution as + provided in Section 3(a)(1)(A)(i). + + b. Other rights. + + 1. Moral rights, such as the right of integrity, are not + licensed under this Public License, nor are publicity, + privacy, and/or other similar personality rights; however, to + the extent possible, the Licensor waives and/or agrees not to + assert any such rights held by the Licensor to the limited + extent necessary to allow You to exercise the Licensed + Rights, but not otherwise. + + 2. Patent and trademark rights are not licensed under this + Public License. + + 3. To the extent possible, the Licensor waives any right to + collect royalties from You for the exercise of the Licensed + Rights, whether directly or through a collecting society + under any voluntary or waivable statutory or compulsory + licensing scheme. In all other cases the Licensor expressly + reserves any right to collect such royalties. + + +Section 3 -- License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the +following conditions. + + a. Attribution. + + 1. If You Share the Licensed Material (including in modified + form), You must: + + a. retain the following if it is supplied by the Licensor + with the Licensed Material: + + i. identification of the creator(s) of the Licensed + Material and any others designated to receive + attribution, in any reasonable manner requested by + the Licensor (including by pseudonym if + designated); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of + warranties; + + v. a URI or hyperlink to the Licensed Material to the + extent reasonably practicable; + + b. indicate if You modified the Licensed Material and + retain an indication of any previous modifications; and + + c. indicate the Licensed Material is licensed under this + Public License, and include the text of, or the URI or + hyperlink to, this Public License. + + 2. You may satisfy the conditions in Section 3(a)(1) in any + reasonable manner based on the medium, means, and context in + which You Share the Licensed Material. For example, it may be + reasonable to satisfy the conditions by providing a URI or + hyperlink to a resource that includes the required + information. + + 3. If requested by the Licensor, You must remove any of the + information required by Section 3(a)(1)(A) to the extent + reasonably practicable. + + b. ShareAlike. + + In addition to the conditions in Section 3(a), if You Share + Adapted Material You produce, the following conditions also apply. + + 1. The Adapter's License You apply must be a Creative Commons + license with the same License Elements, this version or + later, or a BY-SA Compatible License. + + 2. You must include the text of, or the URI or hyperlink to, the + Adapter's License You apply. You may satisfy this condition + in any reasonable manner based on the medium, means, and + context in which You Share Adapted Material. + + 3. You may not offer or impose any additional or different terms + or conditions on, or apply any Effective Technological + Measures to, Adapted Material that restrict exercise of the + rights granted under the Adapter's License You apply. + + +Section 4 -- Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that +apply to Your use of the Licensed Material: + + a. for the avoidance of doubt, Section 2(a)(1) grants You the right + to extract, reuse, reproduce, and Share all or a substantial + portion of the contents of the database; + + b. if You include all or a substantial portion of the database + contents in a database in which You have Sui Generis Database + Rights, then the database in which You have Sui Generis Database + Rights (but not its individual contents) is Adapted Material, + + including for purposes of Section 3(b); and + c. You must comply with the conditions in Section 3(a) if You Share + all or a substantial portion of the contents of the database. + +For the avoidance of doubt, this Section 4 supplements and does not +replace Your obligations under this Public License where the Licensed +Rights include other Copyright and Similar Rights. + + +Section 5 -- Disclaimer of Warranties and Limitation of Liability. + + a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE + EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS + AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF + ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, + IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, + WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR + PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, + ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT + KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT + ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. + + b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE + TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, + NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, + INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, + COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR + USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN + ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR + DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR + IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + + c. The disclaimer of warranties and limitation of liability provided + above shall be interpreted in a manner that, to the extent + possible, most closely approximates an absolute disclaimer and + waiver of all liability. + + +Section 6 -- Term and Termination. + + a. This Public License applies for the term of the Copyright and + Similar Rights licensed here. However, if You fail to comply with + this Public License, then Your rights under this Public License + terminate automatically. + + b. Where Your right to use the Licensed Material has terminated under + Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided + it is cured within 30 days of Your discovery of the + violation; or + + 2. upon express reinstatement by the Licensor. + + For the avoidance of doubt, this Section 6(b) does not affect any + right the Licensor may have to seek remedies for Your violations + of this Public License. + + c. For the avoidance of doubt, the Licensor may also offer the + Licensed Material under separate terms or conditions or stop + distributing the Licensed Material at any time; however, doing so + will not terminate this Public License. + + d. Sections 1, 5, 6, 7, and 8 survive termination of this Public + License. + + +Section 7 -- Other Terms and Conditions. + + a. The Licensor shall not be bound by any additional or different + terms or conditions communicated by You unless expressly agreed. + + b. Any arrangements, understandings, or agreements regarding the + Licensed Material not stated herein are separate from and + independent of the terms and conditions of this Public License. + + +Section 8 -- Interpretation. + + a. For the avoidance of doubt, this Public License does not, and + shall not be interpreted to, reduce, limit, restrict, or impose + conditions on any use of the Licensed Material that could lawfully + be made without permission under this Public License. + + b. To the extent possible, if any provision of this Public License is + deemed unenforceable, it shall be automatically reformed to the + minimum extent necessary to make it enforceable. If the provision + cannot be reformed, it shall be severed from this Public License + without affecting the enforceability of the remaining terms and + conditions. + + c. No term or condition of this Public License will be waived and no + failure to comply consented to unless expressly agreed to by the + Licensor. + + d. Nothing in this Public License constitutes or may be interpreted + as a limitation upon, or waiver of, any privileges and immunities + that apply to the Licensor or You, including from the legal + processes of any jurisdiction or authority. + + +======================================================================= + +Creative Commons is not a party to its public +licenses. Notwithstanding, Creative Commons may elect to apply one of +its public licenses to material it publishes and in those instances +will be considered the “Licensor.” The text of the Creative Commons +public licenses is dedicated to the public domain under the CC0 Public +Domain Dedication. Except for the limited purpose of indicating that +material is shared under a Creative Commons public license or as +otherwise permitted by the Creative Commons policies published at +creativecommons.org/policies, Creative Commons does not authorize the +use of the trademark "Creative Commons" or any other trademark or logo +of Creative Commons without its prior written consent including, +without limitation, in connection with any unauthorized modifications +to any of its public licenses or any other arrangements, +understandings, or agreements concerning use of licensed material. For +the avoidance of doubt, this paragraph does not form part of the +public licenses. + +Creative Commons may be contacted at creativecommons.org. diff --git a/challenge-OT4-B1/readme.md b/challenge-OT4-B1/readme.md new file mode 100644 index 000000000..e6375b14d --- /dev/null +++ b/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. diff --git a/challenge-OT4-B1/submission.txt b/challenge-OT4-B1/submission.txt new file mode 100644 index 000000000..d84474f47 --- /dev/null +++ b/challenge-OT4-B1/submission.txt @@ -0,0 +1 @@ +nodeid: diff --git a/challenge-OT4-B2/readme.md b/challenge-OT4-B2/readme.md new file mode 100644 index 000000000..88c131a15 --- /dev/null +++ b/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. diff --git a/challenge-OT4-B2/submission.txt b/challenge-OT4-B2/submission.txt new file mode 100644 index 000000000..b6c1144b5 --- /dev/null +++ b/challenge-OT4-B2/submission.txt @@ -0,0 +1,4 @@ +nodeid: +bakerid: +accountaddress: +blockhash_addbaker: \ No newline at end of file diff --git a/challenge-OT4-B3/readme.md b/challenge-OT4-B3/readme.md new file mode 100644 index 000000000..307912311 --- /dev/null +++ b/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. diff --git a/challenge-OT4-B3/submission.txt b/challenge-OT4-B3/submission.txt new file mode 100644 index 000000000..b3a29f5d7 --- /dev/null +++ b/challenge-OT4-B3/submission.txt @@ -0,0 +1,5 @@ +nodeid: +bakerid: +accountaddress: +blockhash_addbaker: +blockhash_removebaker: \ No newline at end of file diff --git a/challenge-OT4-B4/readme.md b/challenge-OT4-B4/readme.md new file mode 100644 index 000000000..11208e45e --- /dev/null +++ b/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/ 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/ 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/ 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/ 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/ 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/ 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. diff --git a/challenge-OT4-B4/submission.txt b/challenge-OT4-B4/submission.txt new file mode 100644 index 000000000..248cc15b8 --- /dev/null +++ b/challenge-OT4-B4/submission.txt @@ -0,0 +1,15 @@ +nodeid: +bakerid1: +bakerid2: +accountaddress1: +accountaddress2: +blockhash_addbaker: +blockhash_u1: +blockhash_u2: +blockhash_u3_addbaker: +blockhash_u3_removebaker: +blockhash_u4_addbaker: +blockhash_u4_removebaker: +blockhash_u5_addbaker: +blockhash_u5_removebaker: +blockhash_u6: \ No newline at end of file diff --git a/logs.md b/logs.md new file mode 100644 index 000000000..2116013b6 --- /dev/null +++ b/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}}' +``` + +Where the `` 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 + +# On Windows +echo.> +``` + +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. diff --git a/readme.md b/readme.md new file mode 100644 index 000000000..d7d79935c --- /dev/null +++ b/readme.md @@ -0,0 +1,91 @@ + +# Testnet 4 Challenges + +We are really glad to invite you to join our Incentivized Testnet 4! + +Concordium Testnet 4 was released January 13, 2021. + +Concoridum Testnet 4 Incentivized challenges start January 20, 2021 at 23:00 PT and will end 6 weeks later. + +During this period, smart contract developers, businesses, node operators, and community members can, collectively, receive rewards up to 0,15% of the mainnet supply, (up to 15,000,000 GTU) for helping secure, sustain, and grow Concordium Network and the ecosystem. Rewards will be transferred in GTU after the Mainnet goes live. + +Concordium Testnet 4 is a collaborative era intended to stress-test the network, encourage participation from all over the world, and help testers, developers, and users get ready to participate in Concordium. + + +## Status + +See [Status](/status.md). + + +## Missions and Challenges + +Each challenge has its own subfolder under `challenge-OT4-*` with a `readme.md` that specifies the challenge. + +| Challenge | Title | GTU Reward | Seats | Start Date | Last Date for Submission | +| - | - | -:| - |- | - | +| OT4-B1 | [Run a node for a month.](challenge-OT4-B1) | 2500 GTU | 750 | 20-01-2021 23:00 PT | 03-03-2021 23:00 PT | +| OT4-B2 | [Run a baker for a month.](challenge-OT4-B2) | 1000 GTU | 250 | 20-01-2021 23:00 PT | 03-03-2021 23:00 PT | +| OT4-B3 | [Register and deregister as baker.](challenge-OT4-B3) | 2000 GTU | 250 | 20-01-2021 23:00 PT | 03-03-2021 23:00 PT | +| OT4-B4 | [Make baker updates.](challenge-OT4-B4) | 3000 GTU | 250 | 20-01-2021 23:00 PT | 03-03-2021 23:00 PT | + +Each of the baker challenge OT4-B* takes 4 weeks to complete. OT4-B1 can be run as a stand-alone challenge or concurrently with either challenge OT4-B2, OT-B3, or OT4-B4. OT4-B2, OT4-B3, and OT4-B4 **cannot** be combined with each other. + +The challenges intentionally only provide a minimum description of the tasks. For detailed step-to-step guides and troubleshooting, we expect contributors to consult [Documentation and Help](#documentation-and-help) or our [Discord channel](https://discord.com/invite/xWmQ5tp). + + +## Rules of Engagement + +- A contributor, who wants to submit a challenge result in this repository, must be a registered user on GitHub. +- Concordium accepts one approved submission per challenge per contributor, unless the challenges exclude one another, see [Missions and Challenges](#missions-and-challenges). +- The GitHub user name should not be changed until the rewards are paid out on mainnet. +- Each challenge has a GTU amount tag, which is rewarded, if Concordium accepts the submission. +- Each challenge has a total number of seats for which rewards can be paid out. +- All submissions must stricely follow our [Submission Process](/submission-process.md), otherwise they will be rejected. + + +Note: all GTU activity on the Testnet is non-transferrable to Mainnet, the Testnet is just that: a test network. + + +## Submission Process + +See [Submission Process](/submission-process.md). + + +## Review process + +See [Submission Process](/submission-process.md). + + + +## Bugs and Improvements + +If you encounter a problem, please check under [Status](status.md), already [Reported Issues and FAQs](/projects/1) and [Troubleshooting](https://developers.concordium.com/en/testnet4/testnet/see-also/troubleshooting.html). + +If you cannot find an answer, ask on [Telegram](https://t.me/concordium_official) or [Discord](https://discord.com/invite/xWmQ5tp). If unresolved, you can submit a new issue under [Issues](/issues) and provide a short description, steps to reproduce, platform and OS, logs, expected result and actual result. + +## Documentation and Help + +- [Concordium Documentation](https://developers.concordium.com/en/testnet4/testnet/index.html) +- [Github.com Documentation](https://docs.github.com/en/github) + +## Contact + +- Discuss with the Concordium Core Team and Testers on [Telegram](https://t.me/concordium_official) and on [Discord](https://discord.com/invite/xWmQ5tp). +- Get informed about Concordium Testnets on [Twitter](https://twitter.com/concordiumnet) and subscribe to the [Concordium Community Newsletter](https://concordium.substack.com). + +## Disclaimer + +By participating in this Testnet, you agree to the Concordium Testnet [Terms and Conditions](https://github.com/Concordium/Testnet3-Challenges/blob/main/Concordium_Incentivized_Testnet_Program_Terms_and_Conditions.pdf). + +## License + +[![CC BY-SA 4.0][cc-by-sa-shield]][cc-by-sa] + +This work is licensed under a +[Creative Commons Attribution-ShareAlike 4.0 International License][cc-by-sa]. + +[![CC BY-SA 4.0][cc-by-sa-image]][cc-by-sa] + +[cc-by-sa]: http://creativecommons.org/licenses/by-sa/4.0/ +[cc-by-sa-image]: https://licensebuttons.net/l/by-sa/4.0/88x31.png +[cc-by-sa-shield]: https://img.shields.io/badge/License-CC%20BY--SA%204.0-lightgrey.svg diff --git a/status.md b/status.md new file mode 100644 index 000000000..5ff4063d6 --- /dev/null +++ b/status.md @@ -0,0 +1,28 @@ +# Testnet 4 Status + +## Rationale + +The purpose of this document is to provide real-time information when it comes to the Concordium Test Network, including known issues, downtime and any specific event that could alter the participation in the program. + +## Known issues, limitations and schedule events + +### ✅ Test Network + +* No known issues +* No limitations +* No scheduled downtime + +### ✅ Identity Issuer Notabene + + * No known issues + +### ✅ Challenges & Supporting Tooling + +* No known issues + +### FAQs and Troubleshooting + +* [Reported Issues and FAQs](https://github.com/Concordium/testnet-challenges-draft/projects/1) +* [Concordium Troubleshooting](https://developers.concordium.com/en/testnet4/testnet/see-also/troubleshooting.html) + +## Past Updates diff --git a/submission-process.md b/submission-process.md new file mode 100644 index 000000000..ae3346eed --- /dev/null +++ b/submission-process.md @@ -0,0 +1,46 @@ + +## Submission Process + +1. Fork the Tesnet4-Challenges repo. ([howto](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo)) +2. Each challenge has it's own folder, with a `readme.md` and `submission.txt` files. + - Submissions must adhere to the `readme.md` instructions exactly or they will be automatically disqualified. + - Submissions must fill out the `submission.txt` details or they will be automatically disqualified. +3. Create or upload your submission content in the correct challenge folder **only when you have completed it**. ([howto](https://docs.github.com/en/github/managing-files-in-a-repository/managing-files-on-github)) +4. Make a signed commit. ([howto](https://docs.github.com/en/github/authenticating-to-github/managing-commit-signature-verification)) +5. Create a pull request. ([howto](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)) + +⚠️ Please make only **one PR for all submissions*** ⚠️ + +Repeat steps 3+4 for every additional challenge when completed. You can keep adding more commits to the same pull request. + +Only make a challenge submission when it is completed. Do not submit placeholders or "reserve my spot" attempts - these will be ignored and may penalise your entire submission. + +*Yes, this is different from our advice in OT3. + + +## Disqualified Submissions + +- Closed pull requests will not be evaluated. If you close your PR that means you're not participating and don't want to be reviewed. +- If a user has more than 1 pull request open, only the earliest will be evaluated and all others closed +- If a user is detected to create multiple Github accounts and make multiple submissions, all their submssions on all accounts will be disqualified. + +Any behaviour indicating users acting in bad faith may result in disqualification at the Concordium teams' sole discretion. + +## Submission Ordering + +- If there are more submissions that seats for any particular challenge, we will evaluate ordering based on submission time for the submission.txt related to each specific challenge. +- Do not make dummy commits to "reserve your place", this will result in disqualification. +- Tampering with git commit times or git history in submissions will result in disqualification. + + + + +## Review process + +- Once all challenges have completed, Concordium will start labelling PRs according to detected submissions, and reviewing them. +- PRs will receive a comment that either confirms or rejects the submission. +- When all challenges are reviewed, a summary table of all reviews, usernames and total rewards will be posted. +- There will be 7 days for any feedback/issue resolution. +- After this time the final rewards will be posted with no further appeal. + +If we leave a comment asking for more information, or reject a submission, you can give us more info by commenting on the PR. There is no need to contact us or let us know outside of Github, we get notifications already.