├── .gitignore ├── CNAME ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── _config.yml ├── assets ├── CasperNetwork │ └── casper-signer-logo.jpg ├── Connect-a-Wallet │ ├── 00-CSPR-Live-Casper-Signer-Option.png │ ├── 01-Casper-Signer-Connect-to-Site-01.png │ ├── 02-Casper-Signer-Approve-Connection.png │ ├── 03-Casper-Signer-Hamburger-Menu-with-Multi-Account.png │ └── 04-CSPR-Live-View-account.png ├── Generate-Keys │ └── 00-CSPR-Live-Create-Account.png ├── SignerGuide │ ├── 01-First-Home.png │ ├── 02-Main-Menu.png │ ├── 03-Key-Management.png │ ├── 04-Connected-Sites.png │ ├── 05-Casper-Signer-Unlock-Vault.png │ └── Archived │ │ ├── 00-Casper-Signer-First-Login.png │ │ ├── 01-Casper-Signer-Create-Account.png │ │ ├── 02-Casper-Signer-Hamburger-Menu.png │ │ ├── 03-Casper-Signer-Key-Management.png │ │ ├── 05-Casper-Signer-New-Vault.png │ │ ├── 06-Casper-Signer-Connected-Sites.png │ │ └── 07-Casper-Signer-Import-Account-Filled.png └── Transfer-CSPR │ └── 00-CSPR-Live-Wallet-Menu-Transfer-CSPR.png ├── build.sh ├── docs ├── aws │ └── setup-testnet-validator-from-scratch.md ├── faq-user.md ├── faq-validator.md ├── testnet-rewards.md ├── testnet.md ├── testnet │ ├── testnet-upgrades.md │ ├── upgrade-1_1_0.md │ ├── upgrade-1_1_2.md │ ├── upgrade-1_2_0.md │ ├── upgrade-1_2_1.md │ ├── upgrade-1_3_1.md │ ├── upgrade-1_3_2.md │ ├── upgrade-1_3_4.md │ ├── upgrade-1_4_1.md │ ├── upgrade-1_4_10.md │ ├── upgrade-1_4_13.md │ ├── upgrade-1_4_15.md │ ├── upgrade-1_4_2.md │ ├── upgrade-1_4_3.md │ ├── upgrade-1_4_4.md │ ├── upgrade-1_4_5.md │ ├── upgrade-1_4_6.md │ ├── upgrade-1_4_7.md │ ├── upgrade-1_4_8.md │ ├── upgrade-1_5_2.md │ ├── upgrade-1_5_3.md │ ├── upgrade-1_5_5.md │ ├── upgrade-1_5_6.md │ ├── upgrade-1_5_7.md │ ├── upgrade-1_5_8.md │ └── upgrade-2_0_1.md └── ubuntu │ └── setup-testnet-validator-from-scratch.md └── src ├── aws └── setup-testnet-validator-from-scratch.md ├── casper-client ├── bond.md ├── check-auction-info.md ├── check-balance.md └── check-transaction-status.md ├── disclaimer.md ├── faq-user.md ├── faq-validator.md ├── testnet-rewards.md ├── testnet.md ├── testnet ├── create-testnet-account.md ├── fund-testnet-account.md ├── testnet-upgrades.md ├── testnet-warning.md ├── upgrade-1_1_0.md ├── upgrade-1_1_2.md ├── upgrade-1_2_0.md ├── upgrade-1_2_1.md ├── upgrade-1_3_1.md ├── upgrade-1_3_2.md ├── upgrade-1_3_4.md ├── upgrade-1_4_1.md ├── upgrade-1_4_10.md ├── upgrade-1_4_13.md ├── upgrade-1_4_15.md ├── upgrade-1_4_2.md ├── upgrade-1_4_3.md ├── upgrade-1_4_4.md ├── upgrade-1_4_5.md ├── upgrade-1_4_6.md ├── upgrade-1_4_7.md ├── upgrade-1_4_8.md ├── upgrade-1_5_2.md ├── upgrade-1_5_3.md ├── upgrade-1_5_5.md ├── upgrade-1_5_6.md ├── upgrade-1_5_7.md ├── upgrade-1_5_8.md └── upgrade-2_0_1.md └── ubuntu ├── bond.md ├── build-the-contracts.md ├── casper-client ├── bond.md ├── check-auction-info.md ├── check-balance.md └── check-transaction-status.md ├── checkout-release-branch-testnet.md ├── configure-node.md ├── generate-keys.md ├── install-casper-node.md ├── monitor-node-status.md ├── open-files-limit.md ├── open-ports.md ├── remove-casper-node.md ├── setup-testnet-validator-from-scratch.md ├── setup-validator-from-scratch.md ├── start-node.md └── sudo-notice.md /.gitignore: -------------------------------------------------------------------------------- 1 | .idea 2 | -------------------------------------------------------------------------------- /CNAME: -------------------------------------------------------------------------------- 1 | docs.cspr.community -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | community@make.services. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to Casper Network - Information and How-To Guides 2 | :+1::tada: First off, thanks for taking the time to contribute! :tada::+1: 3 | 4 | The following is a set of rules and guidelines for contributing to this repo. Please feel free to propose changes to this document in a pull request. 5 | 6 | ## Submitting issues 7 | 8 | If you have questions about how to install and use Signer on [CSPR.Live](https://cspr.live) or about how to install and operate a validator node on the Casper Network, please direct these to the related [discord channels](https://discord.gg/caspernetwork): `#validators-general`, `#node-tech-support`, `#casperdotlive` 9 | 10 | ### Guidelines 11 | * Please search the existing issues first, it's likely that your issue was already reported or even fixed. 12 | - Go to the main page of the repository, click "issues" and type any word in the top search/command bar. 13 | - You can also filter by appending e. g. "state:open" to the search string. 14 | - More info on [search syntax within github](https://help.github.com/articles/searching-issues) 15 | 16 | ## Contributing to the Documentation 17 | 18 | Thanks for wanting to contribute to Casper Network - Information and How-To Guides. You rock! 19 | 20 | ### Workflow for contributions: 21 | * [Fork](https://github.com/make-software/how-to-casper-network/fork) the main repo 22 | * Make your changes 23 | * Create a new pull request 24 | 25 | ### Notes: 26 | * Typo corrections and new articles are welcome contributions. 27 | * The documentation is served on GitHub pages with Jekyll. 28 | * Make your changes in the `src` directory, then run the `build.sh` script to publish them to the docs directory. 29 | * Use markdown syntax for documentation. 30 | * Try to use includes as much as possible to avoid content duplication. 31 | * Respect the [license](https://github.com/make-software/how-to-casper-network/blob/master/LICENSE) terms of the repo 32 | 33 | ### Testing your changes: 34 | - You can have your clone deployed to GH Pages to see the results. This is what most people prefer to avoid installing dependencies locally, and adding extra config for local run. 35 | 36 | **OR** 37 | 38 | - You can; 39 | - Add a `Gemfile` to your local clone with the content 40 | ``` 41 | source "https://rubygems.org" 42 | gem "github-pages", group: :jekyll_plugins 43 | gem "webrick", "~> 1.7" 44 | ``` 45 | - Then run these commands in the given order: 46 | ``` 47 | bundle config set --local path 'vendor/bundle' 48 | bundle install 49 | bundle exec jekyll serve 50 | ``` 51 | * Please note that the first two commands are meant to be run only once unless you delete the downloaded dependencies inside your clone dir. 52 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Casper Network - Information and How-To Guides 2 | 3 | ## For Users 4 | 5 | This documentation aims to help with onboarding the new end users of the Casper Network by providing guides on basic setup and operations. 6 | - Casper Signer [Migrating to Casper Wallet from Signer](https://www.casperwallet.io/user-guide/signer-user-start-here) 7 | - 👛 [Connecting to Dapps](https://www.casperwallet.io/user-guide/connecting-to-dapps) 8 | - 💸 [Transfer CSPR](https://www.casperwallet.io/user-guide/transfer-cspr-between-accounts) 9 | - 🥩 [Delegating CSPR Stake](https://www.casperwallet.io/user-guide/delegating-and-undelegating-cspr) 10 | - 🥙 [Undelegating CSPR Stake](https://www.casperwallet.io/user-guide/delegating-and-undelegating-cspr) 11 | 12 | - ❓ [User FAQ](/docs/faq-user.md) 13 | 14 | ## For Node Operators 15 | 16 | This documentation is aimed to help prospective node-operators set up and configure their Casper Network validator nodes. 17 | 18 | ### MainNet Guides 19 | - [Set up MainNet validator node](https://github.com/casper-network/casper-node/wiki/Mainnet-Node-Installation-Instructions) 20 | 21 | ### TestNet Guides 22 | - [Set up TestNet validator node from scratch on AWS](/docs/aws/setup-testnet-validator-from-scratch.md) 23 | - [Set up TestNet validator node from scratch on Ubuntu](/docs/ubuntu/setup-testnet-validator-from-scratch.md) 24 | 25 | ### TestNet Information 26 | - [TestNet Code of Conduct and Incentive Requirements](/docs/testnet.md) 27 | - [TestNet Rewards](/docs/testnet-rewards.md) 28 | - [TestNet Upgrades](/docs/testnet/testnet-upgrades.md) 29 | 30 | ### Miscellaneous 31 | - [Validator FAQ](/docs/faq-validator.md) 32 | 33 | ### Do you have any questions? 34 | 35 | - [Discord Community](https://discord.gg/caspernetwork) 36 | - [Telegram Community](https://t.me/casperblockchain) 37 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | theme: jekyll-theme-cayman 2 | title: Casper How-To Guides 3 | google_analytics: UA-194946916-1 4 | -------------------------------------------------------------------------------- /assets/CasperNetwork/casper-signer-logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/CasperNetwork/casper-signer-logo.jpg -------------------------------------------------------------------------------- /assets/Connect-a-Wallet/00-CSPR-Live-Casper-Signer-Option.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/Connect-a-Wallet/00-CSPR-Live-Casper-Signer-Option.png -------------------------------------------------------------------------------- /assets/Connect-a-Wallet/01-Casper-Signer-Connect-to-Site-01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/Connect-a-Wallet/01-Casper-Signer-Connect-to-Site-01.png -------------------------------------------------------------------------------- /assets/Connect-a-Wallet/02-Casper-Signer-Approve-Connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/Connect-a-Wallet/02-Casper-Signer-Approve-Connection.png -------------------------------------------------------------------------------- /assets/Connect-a-Wallet/03-Casper-Signer-Hamburger-Menu-with-Multi-Account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/Connect-a-Wallet/03-Casper-Signer-Hamburger-Menu-with-Multi-Account.png -------------------------------------------------------------------------------- /assets/Connect-a-Wallet/04-CSPR-Live-View-account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/Connect-a-Wallet/04-CSPR-Live-View-account.png -------------------------------------------------------------------------------- /assets/Generate-Keys/00-CSPR-Live-Create-Account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/Generate-Keys/00-CSPR-Live-Create-Account.png -------------------------------------------------------------------------------- /assets/SignerGuide/01-First-Home.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/01-First-Home.png -------------------------------------------------------------------------------- /assets/SignerGuide/02-Main-Menu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/02-Main-Menu.png -------------------------------------------------------------------------------- /assets/SignerGuide/03-Key-Management.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/03-Key-Management.png -------------------------------------------------------------------------------- /assets/SignerGuide/04-Connected-Sites.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/04-Connected-Sites.png -------------------------------------------------------------------------------- /assets/SignerGuide/05-Casper-Signer-Unlock-Vault.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/05-Casper-Signer-Unlock-Vault.png -------------------------------------------------------------------------------- /assets/SignerGuide/Archived/00-Casper-Signer-First-Login.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/Archived/00-Casper-Signer-First-Login.png -------------------------------------------------------------------------------- /assets/SignerGuide/Archived/01-Casper-Signer-Create-Account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/Archived/01-Casper-Signer-Create-Account.png -------------------------------------------------------------------------------- /assets/SignerGuide/Archived/02-Casper-Signer-Hamburger-Menu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/Archived/02-Casper-Signer-Hamburger-Menu.png -------------------------------------------------------------------------------- /assets/SignerGuide/Archived/03-Casper-Signer-Key-Management.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/Archived/03-Casper-Signer-Key-Management.png -------------------------------------------------------------------------------- /assets/SignerGuide/Archived/05-Casper-Signer-New-Vault.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/Archived/05-Casper-Signer-New-Vault.png -------------------------------------------------------------------------------- /assets/SignerGuide/Archived/06-Casper-Signer-Connected-Sites.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/Archived/06-Casper-Signer-Connected-Sites.png -------------------------------------------------------------------------------- /assets/SignerGuide/Archived/07-Casper-Signer-Import-Account-Filled.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/SignerGuide/Archived/07-Casper-Signer-Import-Account-Filled.png -------------------------------------------------------------------------------- /assets/Transfer-CSPR/00-CSPR-Live-Wallet-Menu-Transfer-CSPR.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/make-software/how-to-casper-network/bbc2a100f47581c4dde9cfa8f9e5499d8e2077a1/assets/Transfer-CSPR/00-CSPR-Live-Wallet-Menu-Transfer-CSPR.png -------------------------------------------------------------------------------- /build.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | function readAndResolveIncludes() { 4 | while IFS= read -r line 5 | do 6 | if [[ "$line" =~ ^\[include.*\]$ ]] 7 | then 8 | include_file=(`echo "${line#[include}"`) 9 | include_file=(`echo "${1%/*}/${include_file%]}"`) 10 | readAndResolveIncludes "$include_file" 11 | else 12 | echo "$line" 13 | fi 14 | done < $1 15 | } 16 | 17 | rm -rf docs/* 18 | 19 | #files=($(find src -type f -name '*.md')) 20 | files=( 21 | src/aws/setup-testnet-validator-from-scratch.md 22 | src/ubuntu/setup-testnet-validator-from-scratch.md 23 | src/faq-user.md 24 | src/faq-validator.md 25 | src/testnet.md 26 | src/testnet-rewards.md 27 | src/testnet/testnet-upgrades.md 28 | src/testnet/upgrade-1_1_0.md 29 | src/testnet/upgrade-1_1_2.md 30 | src/testnet/upgrade-1_2_0.md 31 | src/testnet/upgrade-1_2_1.md 32 | src/testnet/upgrade-1_3_1.md 33 | src/testnet/upgrade-1_3_2.md 34 | src/testnet/upgrade-1_3_4.md 35 | src/testnet/upgrade-1_4_1.md 36 | src/testnet/upgrade-1_4_2.md 37 | src/testnet/upgrade-1_4_3.md 38 | src/testnet/upgrade-1_4_4.md 39 | src/testnet/upgrade-1_4_5.md 40 | src/testnet/upgrade-1_4_6.md 41 | src/testnet/upgrade-1_4_7.md 42 | src/testnet/upgrade-1_4_8.md 43 | src/testnet/upgrade-1_4_10.md 44 | src/testnet/upgrade-1_4_13.md 45 | src/testnet/upgrade-1_4_15.md 46 | src/testnet/upgrade-1_5_2.md 47 | src/testnet/upgrade-1_5_3.md 48 | src/testnet/upgrade-1_5_5.md 49 | src/testnet/upgrade-1_5_6.md 50 | src/testnet/upgrade-1_5_7.md 51 | src/testnet/upgrade-1_5_8.md 52 | src/testnet/upgrade-2_0_1.md 53 | ) 54 | 55 | for file in ${files[*]} 56 | do 57 | outfile="docs/${file#src/}" 58 | outdir=${outfile%/*} 59 | 60 | mkdir -p "${outdir}" 61 | touch "${outfile}" 62 | 63 | printf " %s > %s\n" $file $outfile 64 | 65 | readAndResolveIncludes "$file" > $outfile 66 | done 67 | -------------------------------------------------------------------------------- /docs/faq-user.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions (FAQ) for the Users of CSPR.Live 2 | 3 | ## What is delegation? 4 | 5 | Delegation allocates your CSPR tokens to a chosen validator on the network who is participating in the Casper Network's Consensus Protocol. As a proof of stake network, node operators 'stake' their tokens to earn the eligibility to propose new blocks for the network and approve blocks proposed by other validators, but require constant uptime and monitoring of a server connected the Casper Network, instead of 'mining' like other tokens. 6 | 7 | Instead of having to operate and maintain a Casper node (server that stores a copy of the blockchain), you can instead delegate your tokens to someone on the network who has indicated they intend to operate a server on the network. These server operators are called Validators, and they keep a certain percentage of rewards generated from your staked tokens, similar to a commission. Validators set their own fee, as well as earn rewards for their own staked tokens. By participating in the protocol this way, you help to improve decentralization and security of the network, and earn rewards in return. 8 | 9 | ## How frequently the staking rewards are paid? 10 | 11 | Staking rewards are paid to your account on a per-Era basis. One Era is currently set to 2 hours, and each block is set for 16 seconds. For the first reward to appear after delegation/staking, it may take up to 2 Eras (~4 hours). 12 | 13 | ## I've delegated my tokens but the rewards don't arrive at my wallet? 14 | 15 | The rewards are automatically added to your current stake on the corresponding validator. You may observe them under the Rewards tab on your account details page on cspr.live. For the first reward to appear after delegation/staking, it may take up to 2 Eras (~4 hours). 16 | 17 | ## Is there a cool-down/lock period after delegation? 18 | 19 | While there is a delay before you can access your previously delegated tokens, there is no cool-down or lock period after you delegate tokens. You can undelegate any amount of tokens at any time. Upon undelegating tokens from a validator, the network puts funds on hold for 7 Eras, approximately 14 hours and then automatically returns the CSPR tokens to your account. 20 | 21 | ## Is there slashing? Can I lose my delegated tokens? 22 | 23 | Currently, slashing is not enabled on the Casper Mainnet, and there are no plans to enable it in the near future. If a validator behaves poorly on the network, they may be evicted from the auction, and you will not earn rewards during the period that the validator is evicted. If slashing is ever enabled in the future—which would require approval through a governance vote—tokens could be removed as a penalty for poor or malicious behavior on the network. In that case, you could lose tokens delegated to that validator. 24 | 25 | ## What is the cost of delegation and undelegation? 26 | 27 | Both the delegation and the undelegation processes have a cost of 2.5 CSPR. So make sure you have extra CSPR in your account apart from the amount you are delegating. For example, if you are going to delegate 1000 CSPR, you should have at least 1005 CSPR in your wallet, 2.5 CSPR for the delegation and another 2.5 CSPR to cover the undelegation later. In other words, you should keep at least 2.5 CSPR in your wallet after delegation to be able to undelegate. 28 | 29 | ## What is the yearly reward rate for the delegated tokens? 30 | 31 | The base annual reward rate is 8% of the total supply, resulting in a current APY of approximately 15% on the Mainnet (because only a portion of the total supply is currently staked and participating in the reward distribution). The APY might decrease over time as more tokens get staked on the network. 32 | 33 | ## I see some validators with big stake producing blocks, and some smaller ones not. Does that mean only the bigger ones are getting rewards? 34 | 35 | No. On Casper Mainnet, everyone gets seigniorage according to their stake, regardless of whether you've produced blocks or not. The only thing a block proposer gets, is to keep the transaction fees associated with transfers and deploys in the block they proposed. As you may know, transfers cost only 100000000 motes (0.1 CSPR), so these fees are not substantial on a transfer-by-transfer basis. 36 | 37 | The block proposer is chosen also based on odds relative to stake, so if you have 0.1% of stake on the network, the odds that you'll get chosen as the block proposer are very small. This has nothing to do with seigniorage. 38 | 39 | As per the new design of validator rewards on Casper 2.0, some volatility in rewards is expected in the short run. However, all validator rewards should average to an amount proportional to their total stake in the long run. 40 | 41 | ## Some top validators have a commission rate of 100%. What does that mean? 42 | 43 | Validators with Delegation rate of 100 are ones that either don't want to or are restricted from acting as a staking service. You will earn nothing from them. 44 | 45 | ## How can I delegate my tokens? 46 | 47 | An easy, web-based staking UI is available on [CSPR.Live](https://cspr.live/delegate-stake). You may follow these steps to delegate your tokens: 48 | 49 | 1. [Install Casper Wallet](https://www.casperwallet.io/download) 50 | 2. Transfer funds to your wallet on the Casper Wallet app 51 | 3. [Delegate your CSPR stake](https://www.casperwallet.io/user-guide/delegating-and-undelegating-cspr) 52 | -------------------------------------------------------------------------------- /docs/faq-validator.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions (FAQ) 2 | 3 | ## My node is running but is not visible by peers 4 | 5 | Check that you opened the 35000 port in your firewall settings and the node listens to it: 6 | 7 | ``` 8 | sudo ss -lntp 9 | ``` 10 | 11 | ## I receive {"code":32003,"message":"state query failed: ValueNotFound(\"Failed to find base key at path: Key::Account(...)\")"} when checking the balance 12 | 13 | Make sure that you are using the hex representation of the correct public key, and that the key is funded. 14 | 15 | ## I receive "ApiError::Transfer [14]" in my bid transaction status 16 | 17 | Make sure you bid less than you have in your account. In case you bid all you have then you didn't leave anything to pay for the transaction execution, make sure to leave fund to pay for transaction. 18 | 19 | ## I do not see my bid in the auction info 20 | 21 | Make sure that: 22 | - you sent your bid to the correct chain (```--chain-name``` argument) 23 | 24 | If the request was correct, check the transaction status to ensure it went through. 25 | Sending a transaction to the network does not mean that the transaction processed successfully. It’s important to check to see that the contract executed properly: 26 | 27 | ``` 28 | casper-client get-deploy --node-address http://:7777 | jq .result.execution_results 29 | ``` 30 | 31 | Replace `````` with the deploy hash of the transaction you want to check. 32 | 33 | ## How do I estimate execution cost? 34 | 35 | The ```chainspec.toml``` file lists operation costs, but manual estimation is complex. 36 | 37 | A better approach is to test contracts on the Testnet or use the [speculative execution endpoint](https://docs.casper.network/developers/dapps/speculative-exec), which simulates contract execution without changing state and returns detailed gas usage. The Casper team also benchmarks key contracts, with results published in the documentation. 38 | 39 | ## The setup instructions have `CASPER_VERSION=1_0_0` but the current version on the test net is different (i.e. `1.2.0`). Should I change this value to reflect the latest version and directly install that version? 40 | No. Do the normal installation for version `1.0.0` up to the `start your node` step, then stage the upgrades in order, one by one, let your node catch up with the network, then do the bonding. (Instructions already cover all of these steps.) 41 | 42 | ## I did the bonding request as instructed, but it failed with the status of "Out of gas error". 43 | Increase the value of the `--payment-amount` parameter in the bonding request. As of version `1.2.0`, bids and delegations cost ~3 CSPR. 44 | 45 | ## Can I move my node to a different machine/location/IP-address? 46 | Yes. You may follow these steps: 47 | * Backup the contents of the `/etc/casper/validator_keys` directory from your old node. 48 | * Do an install from scratch at the new location/machine by following the usual instructions until the point of validator key creation. 49 | * Copy the contents of the `/etc/casper/validator_keys` directory from the old node to the new node at the same location. 50 | * Stop the old node: `sudo systemctl stop casper-node-launcher` (You can now shutdown the old node completely.) 51 | * Continue following the usual instructions until the point of bonding for the new node. 52 | * Wait for the new node to catch up with the network. 53 | * Make sure its status is active on cspr.live 54 | * If you find that you're no longer in the list of Validators but expected to be, you may have been `evicted` because your validator node was not participating in consensus for an era. If you want to rejoin, you need to "reactivate your bid" using the following commands: 55 | 56 | `CHAIN_NAME=$(curl -s http://127.0.0.1:8888/status | jq -r '.chainspec_name')` 57 | 58 | `sudo -u casper casper-client put-deploy --secret-key /etc/casper/validator_keys/secret_key.pem --chain-name "$CHAIN_NAME" --session-path ~/casper-node/target/wasm32-unknown-unknown/release/activate_bid.wasm --payment-amount 300000000 --session-arg "validator_public_key:public_key='$(cat /etc/casper/validator_keys/public_key_hex)'"` 59 | 60 | ## Is this an incentivised Testnet? If so, what are the rules for the reward calculation? 61 | All information about the reward program is here: [https://docs.cspr.community/docs/testnet-rewards.html](https://docs.cspr.community/docs/testnet-rewards.html) 62 | 63 | ## Where is the faucet to get Testnet tokens? 64 | [https://testnet.cspr.live/tools/faucet](https://testnet.cspr.live/tools/faucet) 65 | 66 | ## I see that some nodes have much more tokens bonded/delegated than what I have on my node. Does it mean they will get more rewards? 67 | No. Number of tokens on your node or being in top-100 based on the number of tokens on your node doesn’t mean anything for reward calculation. Primary criteria for successful participation is the uptime. See here for more information: [https://docs.cspr.community/docs/testnet-rewards.html](https://docs.cspr.community/docs/testnet-rewards.html) 68 | 69 | ## How can I make sure my node is perceived as up & running for reward calculation? 70 | * Go to this address in a browser and take note of the `height` value at the bottom of the page: `http://IP-ADDRESS-OF-YOUR-NODE:8888/status` 71 | * Now go to this address: `https://testnet.cspr.live/validator/PUBLIC-HASH-OF-YOUR-NODE` 72 | * Make sure that you see the `ACTIVE` (green) label on your node’s page on testnet.cspr.live, and the `LATEST BLOCK HEIGHT` value at the top of the page is the same as the height value from your node’s status output (you took note of that at the first step). (+-3 difference between these values is okay.) 73 | 74 | -------------------------------------------------------------------------------- /docs/testnet-rewards.md: -------------------------------------------------------------------------------- 1 | 2 | **⚠️ NOTICE: The previous Testnet Rewards Program has officially ended as of September 30, 2024. For details on the upcoming phase of the Testnet Program, please visit the [Casper Network forum](https://forum.casper.network/).** 3 | 4 | # Casper Testnet Rewards 5 | 6 | ## Introduction 7 | 8 | Thank you for participating in the Casper Testnet program. Your voluntary participation in this Testnet is enabling 9 | stakeholders across the Casper eco-system, including core node developers, validators, dApp developers and tool developers, 10 | to test their software in a non-production environment, and to preview upcoming software changes. 11 | As announced at the onset of the Testnet program, it is planned to award rewards to Testnet participants, contingent 12 | upon their adherence to the [Code of Conduct](testnet.md), based on an algorithmically calculated score that incorporates 13 | certain performance criteria (see below), and subject to certain limits and final approval. 14 | 15 | ## Reward Calculation 16 | 17 | ### Principles 18 | 19 | * Rewards are calculated on a weekly basis, beginning with the first full week after Testnet Genesis, i.e. the week starting 20 | Monday April 12th, 2021. 21 | * Weeks begin on Monday at 0:00:00 UTC, and end on Sunday at 23:59:59 UTC. 22 | * Rewards are awarded to the top-ranked `n` of Testnet participants in a given week: 23 | * `n` is subject to a future decision 24 | * the ranking each week is calculated as explained below 25 | * all participants tied for the last reward-eligible position will be awarded 26 | * Rewards are accrued and paid at a later date, subject to Casper token lock-up periods and Casper Association's workflow and grant specifics 27 | * The total reward amount available to the program is subject to a change as needed with a prior announcement 28 | * Reward participation is contingent upon completing a KYC/AML process, details for which will be announced at a later date. 29 | * One KYC'd person can only be tied to one node, for reward purposes. 30 | 31 | ### Weekly Reward Calculation 32 | 33 | The basic scoring algorithm is: 34 | 35 | ```shell 36 | 100 * uptime_percentage 37 | ``` 38 | where `uptime_percentage` is defined as your node running within 4 blocks from the "tip" of the blockchain, with an active bid. Your node is regularly scanned 39 | on port `8888` to check your block height, so if your port `8888` is closed, you are not considered "up". `uptime_percentage` 40 | is calculated on a 24-hour basis, during each UTC day. 41 | 42 | #### Longevity Score 43 | 44 | The longevity score is the cumulative daily score of a node since the last fault. Any day with a score below 90 is considered a fault, which will also cause your longevity score to be reset to zero. 45 | 46 | Network longevity at 100% will be used as a factor to break ties (longer longevity=higher ranking among tied performance metrics) and where a tie causes the rewardee list to exceed 100 rewardees, the list will either be shortened to exclude all tied rewardees, or extended up to 110 rewardees, whichever results in fewer rewardee additions/removals. 47 | 48 | #### Deductions 49 | 50 | Your cumulative weekly score can be reduced if any of the following events occur: 51 | 52 | ##### Network Weight 53 | 54 | If your node at any time during the weekly calculation period has a network weight of 6% or more, your score for that 55 | week will be reduced by 10%. 56 | 57 | ##### Validator Bid 58 | 59 | If your node does not have an active bid on the network, it will be considered down, and will not be eligible for rewards. If you follow the installation instructions completely, you will have an active bid. Please see the [Validator FAQ](https://docs.cspr.community/docs/faq-validator.html) for more details on how to monitor your node's bid status, and how to reactivate your bid if it gets deactivated. 60 | 61 | ##### Node Software Version 62 | 63 | If your node is not running the expected casper-node software version by the `era` following the `era` that a software 64 | upgrade is slated to take effect, your score for that week will be reduced by 10%. As an example, if a software upgrade is 65 | slated for `era 234` and your node is still not upgraded at the beginning of `era 235`, you will lose 10% of your score. 66 | 67 | 68 | _Please note that the Casper Testnet program is implemented by providing rewards 69 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 70 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 71 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 72 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 73 | -------------------------------------------------------------------------------- /docs/testnet.md: -------------------------------------------------------------------------------- 1 | 2 | **⚠️ NOTICE: The previous Testnet Rewards Program has officially ended as of September 30, 2024. For details on the upcoming phase of the Testnet Program, please visit the [Casper Network forum](https://forum.casper.network/).** 3 | 4 | # Casper Testnet 5 | 6 | ## Introduction 7 | A Casper Testnet has been bootstrapped with the following objectives: 8 | * having a permissionless test environment that ecosystem participants can join and use in order to develop, test and tune their tools and 9 | applications that eventually target the Casper Mainnet, without the need for Mainnet tokens. 10 | 11 | * providing the ability for the validator community to install and try out new versions of Casper node software, as well as 12 | alternative configurations of their nodes and node software, all in an environment where things "are allowed to break". 13 | 14 | * testing and providing access to upcoming protocol and eco-system tool changes, in order to ensure compatibility with existing 15 | applications once said changes deploy to the Casper Mainnet. 16 | 17 | ## Incentivized Participation 18 | Casper Association is inviting interested parties to participate in the Testnet and will offer incentive rewards to Testnet participants. The following 19 | will apply to incentivized participation: 20 | 1. It is intended that rewards will be distributed on the Testnet for a period of time. This will be ratified soon after Testnet is up. 21 | Everyone will have a *chance* to earn, but not everyone is *guaranteed* (nor is anyone entitled) to earn rewards. 22 | 23 | 2. Early and solid participation and node operation, as well as adherence to the Code of Conduct below, is the best way to ensure a chance at rewards. 24 | 25 | 3. Testnet Validators will be scored using an algorithm that takes **uptime** and **liveness** into account, among other factors. 26 | **BEING IN THE TOP RANKS OF VALIDATORS BY STAKE WEIGHT WILL NOT BE A CRITERIA FOR EARNING REWARDS!** 27 | 28 | 4. Anyone wishing to earn rewards will need to pass AML/KYC and register their Public Key as part of their participation. 29 | 30 | ## Testnet Code of Conduct 31 | It is mandatory that all participants adhere to the Testnet Code of Conduct below. Adherence is taken into consideration for reward calculation. 32 | 1. Join the [Testnet Participants Telegram Group](https://t.me/CasperTestNet), and be responsive to Admin announcements. 33 | 2. Make sure your port 8888 is open to the public. It will be monitored for reward calculation purposes. 34 | 3. Once there are 50 or more participants on the network, maintain a stake that is below 6% of the network. There is no benefit to accumulating stake. 35 | It is not a reward criteria, and Testnet Tokens have no express or implied value whatsoever. 36 | 4. Stage and participate in node software updates before they are slated to take effect. This requires being attentive for and responsive to notifications 37 | in the Telegram channel. 38 | 5. If you have to take your node offline, unbond your stake first. 39 | 6. Follow the minimum [Recommended Hardware Specifications](https://docs.casper.network/operators/setup/hardware/) 40 | 7. Participation is entirely at your own risk and you agree to hold Casper Association, and their employees, officers, directors, paid consultants 41 | and agents, harmless from any and all liability. 42 | 43 | 44 | _Please note that the Casper Testnet program is implemented by providing rewards 45 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 46 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 47 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 48 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 49 | -------------------------------------------------------------------------------- /docs/testnet/testnet-upgrades.md: -------------------------------------------------------------------------------- 1 | # Casper TestNet Upgrades 2 | 3 | - [TestNet Upgrade to casper-node v1.1.0](upgrade-1_1_0.md) 4 | - [TestNet Upgrade to casper-node v1.1.2](upgrade-1_1_2.md) 5 | - [TestNet Upgrade to casper-node v1.2.0](upgrade-1_2_0.md) 6 | - [TestNet Upgrade to casper-node v1.2.1](upgrade-1_2_1.md) 7 | - [TestNet Upgrade to casper-node v1.3.1](upgrade-1_3_1.md) 8 | - [TestNet Upgrade to casper-node v1.3.2](upgrade-1_3_2.md) 9 | - [TestNet Upgrade to casper-node v1.3.4](upgrade-1_3_4.md) 10 | - [TestNet Upgrade to casper-node v1.4.1](upgrade-1_4_1.md) 11 | - [TestNet Upgrade to casper-node v1.4.2](upgrade-1_4_2.md) 12 | - [TestNet Upgrade to casper-node v1.4.3](upgrade-1_4_3.md) 13 | - [TestNet Upgrade to casper-node v1.4.4](upgrade-1_4_4.md) 14 | - [TestNet Upgrade to casper-node v1.4.5](upgrade-1_4_5.md) 15 | - [TestNet Upgrade to casper-node v1.4.6](upgrade-1_4_6.md) 16 | - [TestNet Upgrade to casper-node v1.4.7](upgrade-1_4_7.md) 17 | - [TestNet Upgrade to casper-node v1.4.8](upgrade-1_4_8.md) 18 | - [TestNet Upgrade to casper-node v1.4.10](upgrade-1_4_10.md) 19 | - [TestNet Upgrade to casper-node v1.4.13](upgrade-1_4_13.md) 20 | - [TestNet Upgrade to casper-node v1.4.15](upgrade-1_4_15.md) 21 | - [TestNet Upgrade to casper-node v1.5.2](upgrade-1_5_2.md) 22 | - [TestNet Upgrade to casper-node v1.5.3](upgrade-1_5_3.md) 23 | - [TestNet Upgrade to casper-node v1.5.5](upgrade-1_5_5.md) 24 | - [TestNet Upgrade to casper-node v1.5.6](upgrade-1_5_6.md) 25 | - [TestNet Upgrade to casper-node v1.5.7](upgrade-1_5_7.md) 26 | - [TestNet Upgrade to casper-node v1.5.8](upgrade-1_5_8.md) 27 | - [TestNet Upgrade to casper-node v2.0.1](upgrade-2_0_1.md) 28 | 29 | 30 | _Please note that the Casper Testnet program is implemented by providing rewards 31 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 32 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 33 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 34 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 35 | 36 | 37 | 38 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_1_0.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.1.0 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.1.0`, the activation point is `Era 166`, which will be approximately around: 9 | * Thursday April 22, 2021 at 15:00 UTC 10 | * Thursday April 22, 2021 at 17:00 CET 11 | * Thursday April 22, 2021 at 11AM EDT 12 | * Thursday April 22, 2021 at 8AM PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_1_0 24 | sudo -u casper /etc/casper/config_from_example.sh 1_1_0 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 166, 42 | "protocol_version": "1.1.0" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_1_2.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.1.2 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.1.2`, the activation point is `Era 388`, which will be approximately around: 9 | * Tuesday May 11, 2021 at 13:00 UTC 10 | * Tuesday May 11, 2021 at 15:00 CET 11 | * Tuesday May 11, 2021 at 9AM EDT 12 | * Tuesday May 11, 2021 at 6AM PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_1_2 24 | sudo -u casper /etc/casper/config_from_example.sh 1_1_2 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 388, 42 | "protocol_version": "1.1.2" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_2_0.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.2.0 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.2.0`, the activation point is `Era 490`, which will be approximately around: 9 | * Wednesday May 19, 2021 at 16:32 UTC 10 | * Wednesday May 19, 2021 at 18:32 CET 11 | * Wednesday May 19, 2021 at 12:32 EDT 12 | * Wednesday May 19, 2021 at 09:32 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_2_0 24 | sudo -u casper /etc/casper/config_from_example.sh 1_2_0 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 490, 42 | "protocol_version": "1.2.0" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_2_1.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.2.1 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.2.1`, the activation point is `Era 1143`, which will be approximately around: 9 | * Tuesday July 13, 2021 at 13:27 UTC 10 | * Tuesday July 13, 2021 at 15:27 CET 11 | * Tuesday July 13, 2021 at 9:27 AM EDT 12 | * Tuesday July 13, 2021 at 6:27 AM PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_2_1 24 | sudo -u casper /etc/casper/config_from_example.sh 1_2_1 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 1143, 42 | "protocol_version": "1.2.1" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_3_1.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.3.1 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.3.1`, the activation point is `Era 1346`, which will be approximately around: 9 | * Friday July 30, 2021 at 12:01 UTC 10 | * Friday July 30, 2021 at 14:01 CET 11 | * Friday July 30, 2021 at 08:01 EDT 12 | * Friday July 30, 2021 at 05:01 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_3_1 24 | sudo -u casper /etc/casper/config_from_example.sh 1_3_1 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 1346, 42 | "protocol_version": "1.3.1" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_3_2.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.3.2 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.3.2`, the activation point is `Era 1418`, which will be approximately around: 9 | * Thursday August 05, 2021 at 12:12 UTC 10 | * Thursday August 05, 2021 at 14:12 CET 11 | * Thursday August 05, 2021 at 08:12 EDT 12 | * Thursday August 05, 2021 at 05:12 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_3_2 24 | sudo -u casper /etc/casper/config_from_example.sh 1_3_2 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 1418, 42 | "protocol_version": "1.3.2" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_3_4.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.3.4 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.3.4`, the activation point is `Era 2005`, which will be approximately around: 9 | * Thursday September 23, 2021 at 12:24 UTC 10 | * Thursday September 23, 2021 at 14:24 CET 11 | * Thursday September 23, 2021 at 08:24 EDT 12 | * Thursday September 23, 2021 at 05:24 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_3_4 24 | sudo -u casper /etc/casper/config_from_example.sh 1_3_4 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 2005, 42 | "protocol_version": "1.3.4" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_1.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.1 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.1`, the activation point is `Era 2400`, which will be approximately around: 9 | * Tuesday October 26, 2021 at 12:15 UTC 10 | * Tuesday October 26, 2021 at 14:15 CET 11 | * Tuesday October 26, 2021 at 08:15 EDT 12 | * Tuesday October 26, 2021 at 05:15 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_1 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_1 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 2400, 42 | "protocol_version": "1.4.1" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_10.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.10 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.10`, the activation point is `Era 7098`, which will be approximately around: 9 | * Tuesday November 22, 2022 at 12:09 UTC 10 | * Tuesday November 22, 2022 at 13:09 CET 11 | * Tuesday November 22, 2022 at 07:09 EST 12 | * Tuesday November 22, 2022 at 04:09 PST 13 | * Tuesday November 22, 2022 at 20:09 HKST 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_10 25 | sudo -u casper /etc/casper/config_from_example.sh 1_4_10 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 7098, 43 | "protocol_version": "1.4.10" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | 50 | _Please note that the Casper Testnet program is implemented by providing rewards 51 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 52 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 53 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 54 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 55 | 56 | 57 | 58 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_13.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.13 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.13`, the activation point is `Era 8154`, which will be approximately around: 9 | * Tuesday February 21, 2023 at 15:47 UTC 10 | * Tuesday February 21, 2023 at 16:47 CET 11 | * Tuesday February 21, 2023 at 10:47 EST 12 | * Tuesday February 21, 2023 at 07:47 PST 13 | * Tuesday February 21, 2023 at 23:47 HKST 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_13 25 | sudo -u casper /etc/casper/config_from_example.sh 1_4_13 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 8154, 43 | "protocol_version": "1.4.13" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | 50 | _Please note that the Casper Testnet program is implemented by providing rewards 51 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 52 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 53 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 54 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 55 | 56 | 57 | 58 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_15.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.15 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.15`, the activation point is `Era 9015`, which will be approximately around: 9 | * Thursday May 04, 2023 at 12:02 UTC 10 | * Thursday May 04, 2023 at 14:02 CET 11 | * Thursday May 04, 2023 at 08:02 EST 12 | * Thursday May 04, 2023 at 05:02 PST 13 | * Thursday May 04, 2023 at 20:02 HKST 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_15 25 | sudo -u casper /etc/casper/config_from_example.sh 1_4_15 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 9015, 43 | "protocol_version": "1.4.15" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | 50 | _Please note that the Casper Testnet program is implemented by providing rewards 51 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 52 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 53 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 54 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 55 | 56 | 57 | 58 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_2.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.2 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.2`, the activation point is `Era 2736`, which will be approximately around: 9 | * Tuesday November 23, 2021 at 13:13 UTC 10 | * Tuesday November 23, 2021 at 15:13 CET 11 | * Tuesday November 23, 2021 at 09:13 EDT 12 | * Tuesday November 23, 2021 at 06:13 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_2 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_2 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 2736, 42 | "protocol_version": "1.4.2" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_3.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.3 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.3`, the activation point is `Era 2940`, which will be approximately around: 9 | * Friday December 10, 2021 at 13:45 UTC 10 | * Friday December 10, 2021 at 14:45 CET 11 | * Friday December 10, 2021 at 08:45 EST 12 | * Friday December 10, 2021 at 05:45 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_3 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_3 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 2940, 42 | "protocol_version": "1.4.3" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_4.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.4 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.4`, the activation point is `Era 3264`, which will be approximately around: 9 | * Thursday January 06, 2022 at 14:33 UTC 10 | * Thursday January 06, 2022 at 15:33 CET 11 | * Thursday January 06, 2022 at 09:33 EST 12 | * Thursday January 06, 2022 at 06:33 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_4 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_4 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 3264, 42 | "protocol_version": "1.4.4" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_5.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.5 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.5`, the activation point is `Era 4102`, which will be approximately around: 9 | * Thursday March 17, 2022 at 12:39 UTC 10 | * Thursday March 17, 2022 at 13:39 CET 11 | * Thursday March 17, 2022 at 08:39 EST 12 | * Thursday March 17, 2022 at 05:39 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_5 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_5 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 4102, 42 | "protocol_version": "1.4.5" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_6.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.6 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.6`, the activation point is `Era 4785`, which will be approximately around: 9 | * Friday May 13, 2022 at 12:23 UTC 10 | * Friday May 13, 2022 at 13:23 CET 11 | * Friday May 13, 2022 at 08:23 EST 12 | * Friday May 13, 2022 at 05:23 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_6 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_6 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 4785, 42 | "protocol_version": "1.4.6" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_7.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.7 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.7`, the activation point is `Era 5828`, which will be approximately around: 9 | * Monday August 08, 2022 at 12:59 UTC 10 | * Monday August 08, 2022 at 13:59 CET 11 | * Monday August 08, 2022 at 08:59 EST 12 | * Monday August 08, 2022 at 05:59 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_7 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_7 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 5828, 42 | "protocol_version": "1.4.7" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_4_8.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.8 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.8`, the activation point is `Era 5948`, which will be approximately around: 9 | * Thursday August 18, 2022 at 13:16 UTC 10 | * Thursday August 18, 2022 at 15:16 CET 11 | * Thursday August 18, 2022 at 09:16 EST 12 | * Thursday August 18, 2022 at 06:16 PST 13 | * Thursday August 18, 2022 at 21:16 HKST 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_8 25 | sudo -u casper /etc/casper/config_from_example.sh 1_4_8 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 5948, 43 | "protocol_version": "1.4.8" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | 50 | _Please note that the Casper Testnet program is implemented by providing rewards 51 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 52 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 53 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 54 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 55 | 56 | 57 | 58 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_5_2.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.2 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.2`, the activation point is `Era 9904`, which will be approximately around: 9 | * Monday July 17, 2023 at 16:16 UTC 10 | * Monday July 17, 2023 at 09:16 Pacific 11 | * Monday July 17, 2023 at 12:16 Eastern 12 | * Monday July 17, 2023 at 18:16 Zurich 13 | * Monday July 18, 2023 at 00:16 Hong_Kong 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_5_2 25 | sudo -u casper /etc/casper/config_from_example.sh 1_5_2 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 9904, 43 | "protocol_version": "1.5.2" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | 50 | _Please note that the Casper Testnet program is implemented by providing rewards 51 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 52 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 53 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 54 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 55 | 56 | 57 | 58 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_5_3.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.3 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.3`, the activation point is `Era 10827`, which will be approximately around: 9 | * Monday October 02, 2023 at 14:28 UTC 10 | * Monday October 02, 2023 at 10:28 EST 11 | * Monday October 02, 2023 at 07:28 PST 12 | * Monday October 02, 2023 at 16:28 EU/Zurich 13 | * Monday October 02, 2023 at 22:28 HK 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 10827, 42 | "protocol_version": "1.5.3" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_5_5.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.5 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.5`, the activation point is `Era 11751`, which will be approximately around: 9 | * Monday December 18, 2023 at 14:51 UTC 10 | * Monday December 18, 2023 at 06:51 US/Pacific 11 | * Monday December 18, 2023 at 09:51 US/Eastern 12 | * Monday December 18, 2023 at 15:51 Europe/Zurich 13 | * Monday December 18, 2023 at 22:51 Asia/Hong_Kong 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 11751, 42 | "protocol_version": "1.5.5" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_5_6.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.6 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.6`, the activation point is `Era 12268`, which will be approximately around: 9 | * Monday January 30, 2024 at 16:09 UTC 10 | * Monday January 30, 2024 at 08:09 US/Pacific 11 | * Monday January 30, 2024 at 11:09 US/Eastern 12 | * Monday January 30, 2024 at 17:09 Europe/Zurich 13 | * Monday January 31, 2024 at 00:09 Asia/Hong_Kong 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 12268, 42 | "protocol_version": "1.5.6" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | 49 | _Please note that the Casper Testnet program is implemented by providing rewards 50 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 51 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 52 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 53 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 54 | 55 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_5_7.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.7 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.7`, the activation point is `Era 14473`, which will be approximately around Thursday, August 01, 2024 at 14:38 UTC. 9 | 10 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 11 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 12 | 13 | ## Upgrade Staging Instructions 14 | 15 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 16 | one by one: 17 | 18 | ```shell 19 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 20 | ``` 21 | 22 | ## Verifying Successful Staging 23 | 24 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 25 | upgrade by taking a look at your `status` end-point, as follows: 26 | 27 | ```shell 28 | curl -s http://127.0.0.1:8888/status | jq -r 29 | ``` 30 | 31 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 32 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 33 | 34 | ```json 35 | "next_upgrade": { 36 | "activation_point": 14473, 37 | "protocol_version": "1.5.7" 38 | }, 39 | ``` 40 | 41 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 42 | 43 | 44 | _Please note that the Casper Testnet program is implemented by providing rewards 45 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 46 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 47 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 48 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 49 | 50 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-1_5_8.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.8 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.8`, the activation point is `Era 14570`, which will be approximately around Friday, August 09, 2024 at 13:53 UTC. 9 | 10 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 11 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 12 | 13 | ## Upgrade Staging Instructions 14 | 15 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 16 | one by one: 17 | 18 | ```shell 19 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 20 | ``` 21 | 22 | ## Verifying Successful Staging 23 | 24 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 25 | upgrade by taking a look at your `status` end-point, as follows: 26 | 27 | ```shell 28 | curl -s http://127.0.0.1:8888/status | jq -r 29 | ``` 30 | 31 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 32 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 33 | 34 | ```json 35 | "next_upgrade": { 36 | "activation_point": 14570, 37 | "protocol_version": "1.5.8" 38 | }, 39 | ``` 40 | 41 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 42 | 43 | 44 | _Please note that the Casper Testnet program is implemented by providing rewards 45 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 46 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 47 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 48 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 49 | 50 | -------------------------------------------------------------------------------- /docs/testnet/upgrade-2_0_1.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v2.0.1 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v2.0.1`, the activation point is `Era 17497`, which will be approximately around Thursday, April 10, 2025 at 14:46 UTC. 9 | 10 | Please make sure you have properly staged the upgrade well ahead of the activation point, so that your node will be upgraded on time. 11 | 12 | ## Upgrade Staging Instructions 13 | 14 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following command: 15 | 16 | ```shell 17 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 18 | ``` 19 | 20 | ## Verifying Successful Staging 21 | 22 | After you have successfully executed the above command, you can verify that your node is correctly staged with the 23 | upgrade by taking a look at the output of the following command to make sure it has the 24 | `Next Upgrade: {'activation_point': 17497, 'protocol_version': '2.0.1'}` `status` line: 25 | 26 | ```shell 27 | /etc/casper/node_util.py watch 28 | ``` 29 | 30 | If you don't see the `Next Upgrade` line here, then your upgrade staging was not executed successfully. 31 | 32 | 33 | _Please note that the Casper Testnet program is implemented by providing rewards 34 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 35 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 36 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 37 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 38 | 39 | -------------------------------------------------------------------------------- /src/aws/setup-testnet-validator-from-scratch.md: -------------------------------------------------------------------------------- 1 | # Setup Test Net validator node from scratch on Ubuntu 20.04 on AWS 2 | 3 | [include ../testnet/testnet-warning.md] 4 | 5 | ## Create security group 6 | 7 | Create ```casper-validator``` security group that exposes the following ports to public: 8 | 9 | - ```7777``` - rpc port 10 | - ```8888``` - status port 11 | - ```9999``` - event stream port 12 | - ```35000``` - gossip port 13 | 14 | ## Launch instance 15 | 16 | Launch an appropriately powered instance using Ubuntu Server 20.04 LTS AMI and at least a 2TB EBS volume, and attach the ```casper-validator``` security group to it. 17 | 18 | ## Create elastic IP 19 | 20 | Create elastic IP and assign it to the instance 21 | 22 | [include ../ubuntu/setup-testnet-validator-from-scratch.md] 23 | 24 | -------------------------------------------------------------------------------- /src/casper-client/bond.md: -------------------------------------------------------------------------------- 1 | To bond to the network as a validator you need to submit your bid using ```casper-client```: 2 | 3 | ``` 4 | sudo -u casper casper-client put-transaction add-bid \ 5 | --chain-name "" \ 6 | --delegation-rate $(( RANDOM % 11 )) \ 7 | --public-key $(cat /etc/casper/validator_keys/public_key_hex) \ 8 | --transaction-amount 10000000000000 \ 9 | --secret-key /etc/casper/validator_keys/secret_key.pem \ 10 | --standard-payment true \ 11 | --payment-amount 2500000000 \ 12 | --gas-price-tolerance 1 13 | ``` 14 | 15 | Where: 16 | - ```transaction-amount``` - This is the amount that is being bid. If the bid wins, this will be the validator’s initial bond amount. The minimum bid amount is ```10000 CSPR``` or ```10000000000000 motes``` as an argument to the ```ad-bid``` transaction. 17 | - ```delegation-rate``` - The percentage of rewards that the validator retains from delegators that delegate their tokens to the node. The example above sets a random value between 0 (meaning 0%) and 10 (meaning 10%). 18 | - ```payment-amount``` - The fee in motes (1 CSPR = 10^9 motes) to cover the contract execution cost. It's ```2.5 CSPR``` or ```2500000000 motes``` on the command above. 19 | 20 | Replace: 21 | - `````` with the chain name you are joining 22 | 23 | Note down the ```transaction_hash``` returned in the response to query its status later. 24 | -------------------------------------------------------------------------------- /src/casper-client/check-auction-info.md: -------------------------------------------------------------------------------- 1 | To determine if the bid was accepted, execute the following command: 2 | 3 | ``` 4 | casper-client get-auction-info --node-address http://:7777 5 | ``` 6 | 7 | The bid should appear among the returned ```bids```. If the public key associated with a bid appears in the ```validator_weights``` structure for an era, then the account is bonded in that era. 8 | -------------------------------------------------------------------------------- /src/casper-client/check-balance.md: -------------------------------------------------------------------------------- 1 | To get the balance we need to perform the following three query commands: 2 | 3 | 1. Get the state root hash (has to be performed for each balance check because the hash changes with time): 4 | 5 | ``` 6 | casper-client get-state-root-hash --node-address http://127.0.0.1:7777 | jq -r 7 | ``` 8 | 2. Get the main purse associated with your account: 9 | 10 | ``` 11 | sudo -u casper casper-client query-state --node-address http://127.0.0.1:7777 --key --state-root-hash | jq -r 12 | ``` 13 | 14 | 3. Get the main purse balance: 15 | 16 | ``` 17 | casper-client get-balance --node-address http://127.0.0.1:7777 --purse-uref --state-root-hash | jq -r 18 | ``` 19 | -------------------------------------------------------------------------------- /src/casper-client/check-transaction-status.md: -------------------------------------------------------------------------------- 1 | Sending a transaction to the network does not mean that the transaction processed successfully. It’s important to check to see that the contract executed properly: 2 | 3 | ``` 4 | casper-client get-deploy --node-address http://:7777 | jq .result.execution_results 5 | ``` 6 | 7 | Replace `````` with the deploy hash of the transaction you want to check. 8 | -------------------------------------------------------------------------------- /src/disclaimer.md: -------------------------------------------------------------------------------- 1 | 2 | _Please note that the Casper Testnet program is implemented by providing rewards 3 | through the [Casper Association](https://casper.network) (CA), a not-for-profit, Switzerland-domiciled organization 4 | responsible for overseeing the Casper network and supporting its organic evolution and continued decentralization. 5 | MAKE Technology LLC is not affiliated with the Casper Association, and has no control over the program sponsorship or the incentivized 6 | reward program, and is hosting these guides and documents as a service to the Casper community only._ 7 | -------------------------------------------------------------------------------- /src/faq-user.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions (FAQ) for the Users of CSPR.Live 2 | 3 | ## What is delegation? 4 | 5 | Delegation allocates your CSPR tokens to a chosen validator on the network who is participating in the Casper Network's Consensus Protocol. As a proof of stake network, node operators 'stake' their tokens to earn the eligibility to propose new blocks for the network and approve blocks proposed by other validators, but require constant uptime and monitoring of a server connected the Casper Network, instead of 'mining' like other tokens. 6 | 7 | Instead of having to operate and maintain a Casper node (server that stores a copy of the blockchain), you can instead delegate your tokens to someone on the network who has indicated they intend to operate a server on the network. These server operators are called Validators, and they keep a certain percentage of rewards generated from your staked tokens, similar to a commission. Validators set their own fee, as well as earn rewards for their own staked tokens. By participating in the protocol this way, you help to improve decentralization and security of the network, and earn rewards in return. 8 | 9 | ## How frequently the staking rewards are paid? 10 | 11 | Staking rewards are paid to your account on a per-Era basis. One Era is currently set to 2 hours, and each block is set for 16 seconds. For the first reward to appear after delegation/staking, it may take up to 2 Eras (~4 hours). 12 | 13 | ## I've delegated my tokens but the rewards don't arrive at my wallet? 14 | 15 | The rewards are automatically added to your current stake on the corresponding validator. You may observe them under the Rewards tab on your account details page on cspr.live. For the first reward to appear after delegation/staking, it may take up to 2 Eras (~4 hours). 16 | 17 | ## Is there a cool-down/lock period after delegation? 18 | 19 | While there is a delay before you can access your previously delegated tokens, there is no cool-down or lock period after you delegate tokens. You can undelegate any amount of tokens at any time. Upon undelegating tokens from a validator, the network puts funds on hold for 7 Eras, approximately 14 hours and then automatically returns the CSPR tokens to your account. 20 | 21 | ## Is there slashing? Can I lose my delegated tokens? 22 | 23 | Currently, slashing is not enabled on the Casper Mainnet, and there are no plans to enable it in the near future. If a validator behaves poorly on the network, they may be evicted from the auction, and you will not earn rewards during the period that the validator is evicted. If slashing is ever enabled in the future—which would require approval through a governance vote—tokens could be removed as a penalty for poor or malicious behavior on the network. In that case, you could lose tokens delegated to that validator. 24 | 25 | ## What is the cost of delegation and undelegation? 26 | 27 | Both the delegation and the undelegation processes have a cost of 2.5 CSPR. So make sure you have extra CSPR in your account apart from the amount you are delegating. For example, if you are going to delegate 1000 CSPR, you should have at least 1005 CSPR in your wallet, 2.5 CSPR for the delegation and another 2.5 CSPR to cover the undelegation later. In other words, you should keep at least 2.5 CSPR in your wallet after delegation to be able to undelegate. 28 | 29 | ## What is the yearly reward rate for the delegated tokens? 30 | 31 | The base annual reward rate is 8% of the total supply, resulting in a current APY of approximately 15% on the Mainnet (because only a portion of the total supply is currently staked and participating in the reward distribution). The APY might decrease over time as more tokens get staked on the network. 32 | 33 | ## I see some validators with big stake producing blocks, and some smaller ones not. Does that mean only the bigger ones are getting rewards? 34 | 35 | No. On Casper Mainnet, everyone gets seigniorage according to their stake, regardless of whether you've produced blocks or not. The only thing a block proposer gets, is to keep the transaction fees associated with transfers and deploys in the block they proposed. As you may know, transfers cost only 100000000 motes (0.1 CSPR), so these fees are not substantial on a transfer-by-transfer basis. 36 | 37 | The block proposer is chosen also based on odds relative to stake, so if you have 0.1% of stake on the network, the odds that you'll get chosen as the block proposer are very small. This has nothing to do with seigniorage. 38 | 39 | As per the new design of validator rewards on Casper 2.0, some volatility in rewards is expected in the short run. However, all validator rewards should average to an amount proportional to their total stake in the long run. 40 | 41 | ## Some top validators have a commission rate of 100%. What does that mean? 42 | 43 | Validators with Delegation rate of 100 are ones that either don't want to or are restricted from acting as a staking service. You will earn nothing from them. 44 | 45 | ## How can I delegate my tokens? 46 | 47 | An easy, web-based staking UI is available on [CSPR.Live](https://cspr.live/delegate-stake). You may follow these steps to delegate your tokens: 48 | 49 | 1. [Install Casper Wallet](https://www.casperwallet.io/download) 50 | 2. Transfer funds to your wallet on the Casper Wallet app 51 | 3. [Delegate your CSPR stake](https://www.casperwallet.io/user-guide/delegating-and-undelegating-cspr) 52 | -------------------------------------------------------------------------------- /src/faq-validator.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions (FAQ) 2 | 3 | ## My node is running but is not visible by peers 4 | 5 | Check that you opened the 35000 port in your firewall settings and the node listens to it: 6 | 7 | ``` 8 | sudo ss -lntp 9 | ``` 10 | 11 | ## I receive {"code":32003,"message":"state query failed: ValueNotFound(\"Failed to find base key at path: Key::Account(...)\")"} when checking the balance 12 | 13 | Make sure that you are using the hex representation of the correct public key, and that the key is funded. 14 | 15 | ## I receive "ApiError::Transfer [14]" in my bid transaction status 16 | 17 | Make sure you bid less than you have in your account. In case you bid all you have then you didn't leave anything to pay for the transaction execution, make sure to leave fund to pay for transaction. 18 | 19 | ## I do not see my bid in the auction info 20 | 21 | Make sure that: 22 | - you sent your bid to the correct chain (```--chain-name``` argument) 23 | 24 | If the request was correct, check the transaction status to ensure it went through. 25 | [include casper-client/check-transaction-status.md] 26 | 27 | ## How do I estimate execution cost? 28 | 29 | The ```chainspec.toml``` file lists operation costs, but manual estimation is complex. 30 | 31 | A better approach is to test contracts on the Testnet or use the [speculative execution endpoint](https://docs.casper.network/developers/dapps/speculative-exec), which simulates contract execution without changing state and returns detailed gas usage. The Casper team also benchmarks key contracts, with results published in the documentation. 32 | 33 | ## The setup instructions have `CASPER_VERSION=1_0_0` but the current version on the test net is different (i.e. `1.2.0`). Should I change this value to reflect the latest version and directly install that version? 34 | No. Do the normal installation for version `1.0.0` up to the `start your node` step, then stage the upgrades in order, one by one, let your node catch up with the network, then do the bonding. (Instructions already cover all of these steps.) 35 | 36 | ## I did the bonding request as instructed, but it failed with the status of "Out of gas error". 37 | Increase the value of the `--payment-amount` parameter in the bonding request. As of version `1.2.0`, bids and delegations cost ~3 CSPR. 38 | 39 | ## Can I move my node to a different machine/location/IP-address? 40 | Yes. You may follow these steps: 41 | * Backup the contents of the `/etc/casper/validator_keys` directory from your old node. 42 | * Do an install from scratch at the new location/machine by following the usual instructions until the point of validator key creation. 43 | * Copy the contents of the `/etc/casper/validator_keys` directory from the old node to the new node at the same location. 44 | * Stop the old node: `sudo systemctl stop casper-node-launcher` (You can now shutdown the old node completely.) 45 | * Continue following the usual instructions until the point of bonding for the new node. 46 | * Wait for the new node to catch up with the network. 47 | * Make sure its status is active on cspr.live 48 | * If you find that you're no longer in the list of Validators but expected to be, you may have been `evicted` because your validator node was not participating in consensus for an era. If you want to rejoin, you need to "reactivate your bid" using the following commands: 49 | 50 | `CHAIN_NAME=$(curl -s http://127.0.0.1:8888/status | jq -r '.chainspec_name')` 51 | 52 | `sudo -u casper casper-client put-deploy --secret-key /etc/casper/validator_keys/secret_key.pem --chain-name "$CHAIN_NAME" --session-path ~/casper-node/target/wasm32-unknown-unknown/release/activate_bid.wasm --payment-amount 300000000 --session-arg "validator_public_key:public_key='$(cat /etc/casper/validator_keys/public_key_hex)'"` 53 | 54 | ## Is this an incentivised Testnet? If so, what are the rules for the reward calculation? 55 | All information about the reward program is here: [https://docs.cspr.community/docs/testnet-rewards.html](https://docs.cspr.community/docs/testnet-rewards.html) 56 | 57 | ## Where is the faucet to get Testnet tokens? 58 | [https://testnet.cspr.live/tools/faucet](https://testnet.cspr.live/tools/faucet) 59 | 60 | ## I see that some nodes have much more tokens bonded/delegated than what I have on my node. Does it mean they will get more rewards? 61 | No. Number of tokens on your node or being in top-100 based on the number of tokens on your node doesn’t mean anything for reward calculation. Primary criteria for successful participation is the uptime. See here for more information: [https://docs.cspr.community/docs/testnet-rewards.html](https://docs.cspr.community/docs/testnet-rewards.html) 62 | 63 | ## How can I make sure my node is perceived as up & running for reward calculation? 64 | * Go to this address in a browser and take note of the `height` value at the bottom of the page: `http://IP-ADDRESS-OF-YOUR-NODE:8888/status` 65 | * Now go to this address: `https://testnet.cspr.live/validator/PUBLIC-HASH-OF-YOUR-NODE` 66 | * Make sure that you see the `ACTIVE` (green) label on your node’s page on testnet.cspr.live, and the `LATEST BLOCK HEIGHT` value at the top of the page is the same as the height value from your node’s status output (you took note of that at the first step). (+-3 difference between these values is okay.) 67 | 68 | -------------------------------------------------------------------------------- /src/testnet-rewards.md: -------------------------------------------------------------------------------- 1 | 2 | **⚠️ NOTICE: The previous Testnet Rewards Program has officially ended as of September 30, 2024. For details on the upcoming phase of the Testnet Program, please visit the [Casper Network forum](https://forum.casper.network/).** 3 | 4 | # Casper Testnet Rewards 5 | 6 | ## Introduction 7 | 8 | Thank you for participating in the Casper Testnet program. Your voluntary participation in this Testnet is enabling 9 | stakeholders across the Casper eco-system, including core node developers, validators, dApp developers and tool developers, 10 | to test their software in a non-production environment, and to preview upcoming software changes. 11 | As announced at the onset of the Testnet program, it is planned to award rewards to Testnet participants, contingent 12 | upon their adherence to the [Code of Conduct](testnet.md), based on an algorithmically calculated score that incorporates 13 | certain performance criteria (see below), and subject to certain limits and final approval. 14 | 15 | ## Reward Calculation 16 | 17 | ### Principles 18 | 19 | * Rewards are calculated on a weekly basis, beginning with the first full week after Testnet Genesis, i.e. the week starting 20 | Monday April 12th, 2021. 21 | * Weeks begin on Monday at 0:00:00 UTC, and end on Sunday at 23:59:59 UTC. 22 | * Rewards are awarded to the top-ranked `n` of Testnet participants in a given week: 23 | * `n` is subject to a future decision 24 | * the ranking each week is calculated as explained below 25 | * all participants tied for the last reward-eligible position will be awarded 26 | * Rewards are accrued and paid at a later date, subject to Casper token lock-up periods and Casper Association's workflow and grant specifics 27 | * The total reward amount available to the program is subject to a change as needed with a prior announcement 28 | * Reward participation is contingent upon completing a KYC/AML process, details for which will be announced at a later date. 29 | * One KYC'd person can only be tied to one node, for reward purposes. 30 | 31 | ### Weekly Reward Calculation 32 | 33 | The basic scoring algorithm is: 34 | 35 | ```shell 36 | 100 * uptime_percentage 37 | ``` 38 | where `uptime_percentage` is defined as your node running within 4 blocks from the "tip" of the blockchain, with an active bid. Your node is regularly scanned 39 | on port `8888` to check your block height, so if your port `8888` is closed, you are not considered "up". `uptime_percentage` 40 | is calculated on a 24-hour basis, during each UTC day. 41 | 42 | #### Longevity Score 43 | 44 | The longevity score is the cumulative daily score of a node since the last fault. Any day with a score below 90 is considered a fault, which will also cause your longevity score to be reset to zero. 45 | 46 | Network longevity at 100% will be used as a factor to break ties (longer longevity=higher ranking among tied performance metrics) and where a tie causes the rewardee list to exceed 100 rewardees, the list will either be shortened to exclude all tied rewardees, or extended up to 110 rewardees, whichever results in fewer rewardee additions/removals. 47 | 48 | #### Deductions 49 | 50 | Your cumulative weekly score can be reduced if any of the following events occur: 51 | 52 | ##### Network Weight 53 | 54 | If your node at any time during the weekly calculation period has a network weight of 6% or more, your score for that 55 | week will be reduced by 10%. 56 | 57 | ##### Validator Bid 58 | 59 | If your node does not have an active bid on the network, it will be considered down, and will not be eligible for rewards. If you follow the installation instructions completely, you will have an active bid. Please see the [Validator FAQ](https://docs.cspr.community/docs/faq-validator.html) for more details on how to monitor your node's bid status, and how to reactivate your bid if it gets deactivated. 60 | 61 | ##### Node Software Version 62 | 63 | If your node is not running the expected casper-node software version by the `era` following the `era` that a software 64 | upgrade is slated to take effect, your score for that week will be reduced by 10%. As an example, if a software upgrade is 65 | slated for `era 234` and your node is still not upgraded at the beginning of `era 235`, you will lose 10% of your score. 66 | 67 | [include disclaimer.md] 68 | -------------------------------------------------------------------------------- /src/testnet.md: -------------------------------------------------------------------------------- 1 | 2 | **⚠️ NOTICE: The previous Testnet Rewards Program has officially ended as of September 30, 2024. For details on the upcoming phase of the Testnet Program, please visit the [Casper Network forum](https://forum.casper.network/).** 3 | 4 | # Casper Testnet 5 | 6 | ## Introduction 7 | A Casper Testnet has been bootstrapped with the following objectives: 8 | * having a permissionless test environment that ecosystem participants can join and use in order to develop, test and tune their tools and 9 | applications that eventually target the Casper Mainnet, without the need for Mainnet tokens. 10 | 11 | * providing the ability for the validator community to install and try out new versions of Casper node software, as well as 12 | alternative configurations of their nodes and node software, all in an environment where things "are allowed to break". 13 | 14 | * testing and providing access to upcoming protocol and eco-system tool changes, in order to ensure compatibility with existing 15 | applications once said changes deploy to the Casper Mainnet. 16 | 17 | ## Incentivized Participation 18 | Casper Association is inviting interested parties to participate in the Testnet and will offer incentive rewards to Testnet participants. The following 19 | will apply to incentivized participation: 20 | 1. It is intended that rewards will be distributed on the Testnet for a period of time. This will be ratified soon after Testnet is up. 21 | Everyone will have a *chance* to earn, but not everyone is *guaranteed* (nor is anyone entitled) to earn rewards. 22 | 23 | 2. Early and solid participation and node operation, as well as adherence to the Code of Conduct below, is the best way to ensure a chance at rewards. 24 | 25 | 3. Testnet Validators will be scored using an algorithm that takes **uptime** and **liveness** into account, among other factors. 26 | **BEING IN THE TOP RANKS OF VALIDATORS BY STAKE WEIGHT WILL NOT BE A CRITERIA FOR EARNING REWARDS!** 27 | 28 | 4. Anyone wishing to earn rewards will need to pass AML/KYC and register their Public Key as part of their participation. 29 | 30 | ## Testnet Code of Conduct 31 | It is mandatory that all participants adhere to the Testnet Code of Conduct below. Adherence is taken into consideration for reward calculation. 32 | 1. Join the [Testnet Participants Telegram Group](https://t.me/CasperTestNet), and be responsive to Admin announcements. 33 | 2. Make sure your port 8888 is open to the public. It will be monitored for reward calculation purposes. 34 | 3. Once there are 50 or more participants on the network, maintain a stake that is below 6% of the network. There is no benefit to accumulating stake. 35 | It is not a reward criteria, and Testnet Tokens have no express or implied value whatsoever. 36 | 4. Stage and participate in node software updates before they are slated to take effect. This requires being attentive for and responsive to notifications 37 | in the Telegram channel. 38 | 5. If you have to take your node offline, unbond your stake first. 39 | 6. Follow the minimum [Recommended Hardware Specifications](https://docs.casper.network/operators/setup/hardware/) 40 | 7. Participation is entirely at your own risk and you agree to hold Casper Association, and their employees, officers, directors, paid consultants 41 | and agents, harmless from any and all liability. 42 | 43 | [include disclaimer.md] 44 | -------------------------------------------------------------------------------- /src/testnet/create-testnet-account.md: -------------------------------------------------------------------------------- 1 | Install [Casper Wallet](https://www.casperwallet.io), and import your `secret_key.pem` file following the steps described under the `Import keys into Casper Wallet` section of the [Migrating to Casper Wallet from Signer](https://www.casperwallet.io/user-guide/signer-user-start-here) guide. 2 | -------------------------------------------------------------------------------- /src/testnet/fund-testnet-account.md: -------------------------------------------------------------------------------- 1 | Go to [Testnet CSPR.Live](https://testnet.cspr.live/), and [connect](https://www.casperwallet.io/user-guide/connecting-to-dapps) with the account you want to fund. Click `Tools` from the top navigation menu, then click `Faucet`. Wait for the faucet page to load, and click the `Request tokens` button. Wait until the request transaction succeeds. 2 | 3 | > **Note:** If you need more Testnet tokens than provided by the faucet, you can make a request by sending an email to `casper-testnet@make.services` explaining the details of your need. 4 | -------------------------------------------------------------------------------- /src/testnet/testnet-upgrades.md: -------------------------------------------------------------------------------- 1 | # Casper TestNet Upgrades 2 | 3 | - [TestNet Upgrade to casper-node v1.1.0](upgrade-1_1_0.md) 4 | - [TestNet Upgrade to casper-node v1.1.2](upgrade-1_1_2.md) 5 | - [TestNet Upgrade to casper-node v1.2.0](upgrade-1_2_0.md) 6 | - [TestNet Upgrade to casper-node v1.2.1](upgrade-1_2_1.md) 7 | - [TestNet Upgrade to casper-node v1.3.1](upgrade-1_3_1.md) 8 | - [TestNet Upgrade to casper-node v1.3.2](upgrade-1_3_2.md) 9 | - [TestNet Upgrade to casper-node v1.3.4](upgrade-1_3_4.md) 10 | - [TestNet Upgrade to casper-node v1.4.1](upgrade-1_4_1.md) 11 | - [TestNet Upgrade to casper-node v1.4.2](upgrade-1_4_2.md) 12 | - [TestNet Upgrade to casper-node v1.4.3](upgrade-1_4_3.md) 13 | - [TestNet Upgrade to casper-node v1.4.4](upgrade-1_4_4.md) 14 | - [TestNet Upgrade to casper-node v1.4.5](upgrade-1_4_5.md) 15 | - [TestNet Upgrade to casper-node v1.4.6](upgrade-1_4_6.md) 16 | - [TestNet Upgrade to casper-node v1.4.7](upgrade-1_4_7.md) 17 | - [TestNet Upgrade to casper-node v1.4.8](upgrade-1_4_8.md) 18 | - [TestNet Upgrade to casper-node v1.4.10](upgrade-1_4_10.md) 19 | - [TestNet Upgrade to casper-node v1.4.13](upgrade-1_4_13.md) 20 | - [TestNet Upgrade to casper-node v1.4.15](upgrade-1_4_15.md) 21 | - [TestNet Upgrade to casper-node v1.5.2](upgrade-1_5_2.md) 22 | - [TestNet Upgrade to casper-node v1.5.3](upgrade-1_5_3.md) 23 | - [TestNet Upgrade to casper-node v1.5.5](upgrade-1_5_5.md) 24 | - [TestNet Upgrade to casper-node v1.5.6](upgrade-1_5_6.md) 25 | - [TestNet Upgrade to casper-node v1.5.7](upgrade-1_5_7.md) 26 | - [TestNet Upgrade to casper-node v1.5.8](upgrade-1_5_8.md) 27 | - [TestNet Upgrade to casper-node v2.0.1](upgrade-2_0_1.md) 28 | 29 | [include ../disclaimer.md] 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /src/testnet/testnet-warning.md: -------------------------------------------------------------------------------- 1 | > ## **IMPORTANT** 2 | > By choosing to participate in the Casper Test Net, you acknowledge that you have reviewed and will abide by 3 | > the [Test Net Code of Conduct and Incentive Requirements](../testnet.md). Failure to do so may reduce or fully 4 | > disqualify any Test Net incentive participation. 5 | > 6 | > Before you set up your node, make sure it conforms to the minimum [Recommended Hardware Specifications](https://docs.casper.network/operators/setup/hardware/) 7 | 8 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_1_0.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.1.0 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.1.0`, the activation point is `Era 166`, which will be approximately around: 9 | * Thursday April 22, 2021 at 15:00 UTC 10 | * Thursday April 22, 2021 at 17:00 CET 11 | * Thursday April 22, 2021 at 11AM EDT 12 | * Thursday April 22, 2021 at 8AM PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_1_0 24 | sudo -u casper /etc/casper/config_from_example.sh 1_1_0 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 166, 42 | "protocol_version": "1.1.0" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_1_2.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.1.2 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.1.2`, the activation point is `Era 388`, which will be approximately around: 9 | * Tuesday May 11, 2021 at 13:00 UTC 10 | * Tuesday May 11, 2021 at 15:00 CET 11 | * Tuesday May 11, 2021 at 9AM EDT 12 | * Tuesday May 11, 2021 at 6AM PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_1_2 24 | sudo -u casper /etc/casper/config_from_example.sh 1_1_2 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 388, 42 | "protocol_version": "1.1.2" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_2_0.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.2.0 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.2.0`, the activation point is `Era 490`, which will be approximately around: 9 | * Wednesday May 19, 2021 at 16:32 UTC 10 | * Wednesday May 19, 2021 at 18:32 CET 11 | * Wednesday May 19, 2021 at 12:32 EDT 12 | * Wednesday May 19, 2021 at 09:32 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_2_0 24 | sudo -u casper /etc/casper/config_from_example.sh 1_2_0 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 490, 42 | "protocol_version": "1.2.0" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_2_1.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.2.1 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.2.1`, the activation point is `Era 1143`, which will be approximately around: 9 | * Tuesday July 13, 2021 at 13:27 UTC 10 | * Tuesday July 13, 2021 at 15:27 CET 11 | * Tuesday July 13, 2021 at 9:27 AM EDT 12 | * Tuesday July 13, 2021 at 6:27 AM PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_2_1 24 | sudo -u casper /etc/casper/config_from_example.sh 1_2_1 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 1143, 42 | "protocol_version": "1.2.1" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_3_1.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.3.1 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.3.1`, the activation point is `Era 1346`, which will be approximately around: 9 | * Friday July 30, 2021 at 12:01 UTC 10 | * Friday July 30, 2021 at 14:01 CET 11 | * Friday July 30, 2021 at 08:01 EDT 12 | * Friday July 30, 2021 at 05:01 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_3_1 24 | sudo -u casper /etc/casper/config_from_example.sh 1_3_1 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 1346, 42 | "protocol_version": "1.3.1" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_3_2.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.3.2 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.3.2`, the activation point is `Era 1418`, which will be approximately around: 9 | * Thursday August 05, 2021 at 12:12 UTC 10 | * Thursday August 05, 2021 at 14:12 CET 11 | * Thursday August 05, 2021 at 08:12 EDT 12 | * Thursday August 05, 2021 at 05:12 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_3_2 24 | sudo -u casper /etc/casper/config_from_example.sh 1_3_2 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 1418, 42 | "protocol_version": "1.3.2" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_3_4.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.3.4 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.3.4`, the activation point is `Era 2005`, which will be approximately around: 9 | * Thursday September 23, 2021 at 12:24 UTC 10 | * Thursday September 23, 2021 at 14:24 CET 11 | * Thursday September 23, 2021 at 08:24 EDT 12 | * Thursday September 23, 2021 at 05:24 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_3_4 24 | sudo -u casper /etc/casper/config_from_example.sh 1_3_4 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 2005, 42 | "protocol_version": "1.3.4" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_1.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.1 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.1`, the activation point is `Era 2400`, which will be approximately around: 9 | * Tuesday October 26, 2021 at 12:15 UTC 10 | * Tuesday October 26, 2021 at 14:15 CET 11 | * Tuesday October 26, 2021 at 08:15 EDT 12 | * Tuesday October 26, 2021 at 05:15 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_1 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_1 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 2400, 42 | "protocol_version": "1.4.1" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_10.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.10 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.10`, the activation point is `Era 7098`, which will be approximately around: 9 | * Tuesday November 22, 2022 at 12:09 UTC 10 | * Tuesday November 22, 2022 at 13:09 CET 11 | * Tuesday November 22, 2022 at 07:09 EST 12 | * Tuesday November 22, 2022 at 04:09 PST 13 | * Tuesday November 22, 2022 at 20:09 HKST 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_10 25 | sudo -u casper /etc/casper/config_from_example.sh 1_4_10 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 7098, 43 | "protocol_version": "1.4.10" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | [include ../disclaimer.md] 50 | 51 | 52 | 53 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_13.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.13 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.13`, the activation point is `Era 8154`, which will be approximately around: 9 | * Tuesday February 21, 2023 at 15:47 UTC 10 | * Tuesday February 21, 2023 at 16:47 CET 11 | * Tuesday February 21, 2023 at 10:47 EST 12 | * Tuesday February 21, 2023 at 07:47 PST 13 | * Tuesday February 21, 2023 at 23:47 HKST 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_13 25 | sudo -u casper /etc/casper/config_from_example.sh 1_4_13 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 8154, 43 | "protocol_version": "1.4.13" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | [include ../disclaimer.md] 50 | 51 | 52 | 53 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_15.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.15 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.15`, the activation point is `Era 9015`, which will be approximately around: 9 | * Thursday May 04, 2023 at 12:02 UTC 10 | * Thursday May 04, 2023 at 14:02 CET 11 | * Thursday May 04, 2023 at 08:02 EST 12 | * Thursday May 04, 2023 at 05:02 PST 13 | * Thursday May 04, 2023 at 20:02 HKST 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_15 25 | sudo -u casper /etc/casper/config_from_example.sh 1_4_15 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 9015, 43 | "protocol_version": "1.4.15" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | [include ../disclaimer.md] 50 | 51 | 52 | 53 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_2.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.2 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.2`, the activation point is `Era 2736`, which will be approximately around: 9 | * Tuesday November 23, 2021 at 13:13 UTC 10 | * Tuesday November 23, 2021 at 15:13 CET 11 | * Tuesday November 23, 2021 at 09:13 EDT 12 | * Tuesday November 23, 2021 at 06:13 PDT 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_2 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_2 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 2736, 42 | "protocol_version": "1.4.2" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_3.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.3 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.3`, the activation point is `Era 2940`, which will be approximately around: 9 | * Friday December 10, 2021 at 13:45 UTC 10 | * Friday December 10, 2021 at 14:45 CET 11 | * Friday December 10, 2021 at 08:45 EST 12 | * Friday December 10, 2021 at 05:45 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_3 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_3 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 2940, 42 | "protocol_version": "1.4.3" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_4.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.4 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.4`, the activation point is `Era 3264`, which will be approximately around: 9 | * Thursday January 06, 2022 at 14:33 UTC 10 | * Thursday January 06, 2022 at 15:33 CET 11 | * Thursday January 06, 2022 at 09:33 EST 12 | * Thursday January 06, 2022 at 06:33 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_4 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_4 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 3264, 42 | "protocol_version": "1.4.4" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_5.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.5 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.5`, the activation point is `Era 4102`, which will be approximately around: 9 | * Thursday March 17, 2022 at 12:39 UTC 10 | * Thursday March 17, 2022 at 13:39 CET 11 | * Thursday March 17, 2022 at 08:39 EST 12 | * Thursday March 17, 2022 at 05:39 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_5 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_5 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 4102, 42 | "protocol_version": "1.4.5" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_6.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.6 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.6`, the activation point is `Era 4785`, which will be approximately around: 9 | * Friday May 13, 2022 at 12:23 UTC 10 | * Friday May 13, 2022 at 13:23 CET 11 | * Friday May 13, 2022 at 08:23 EST 12 | * Friday May 13, 2022 at 05:23 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_6 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_6 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 4785, 42 | "protocol_version": "1.4.6" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_7.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.7 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.7`, the activation point is `Era 5828`, which will be approximately around: 9 | * Monday August 08, 2022 at 12:59 UTC 10 | * Monday August 08, 2022 at 13:59 CET 11 | * Monday August 08, 2022 at 08:59 EST 12 | * Monday August 08, 2022 at 05:59 PST 13 | 14 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 15 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 16 | 17 | ## Upgrade Staging Instructions 18 | 19 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 20 | one by one: 21 | 22 | ```shell 23 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_7 24 | sudo -u casper /etc/casper/config_from_example.sh 1_4_7 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 5828, 42 | "protocol_version": "1.4.7" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | 51 | 52 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_4_8.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.4.8 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.4.8`, the activation point is `Era 5948`, which will be approximately around: 9 | * Thursday August 18, 2022 at 13:16 UTC 10 | * Thursday August 18, 2022 at 15:16 CET 11 | * Thursday August 18, 2022 at 09:16 EST 12 | * Thursday August 18, 2022 at 06:16 PST 13 | * Thursday August 18, 2022 at 21:16 HKST 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_4_8 25 | sudo -u casper /etc/casper/config_from_example.sh 1_4_8 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 5948, 43 | "protocol_version": "1.4.8" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | [include ../disclaimer.md] 50 | 51 | 52 | 53 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_5_2.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.2 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.2`, the activation point is `Era 9904`, which will be approximately around: 9 | * Monday July 17, 2023 at 16:16 UTC 10 | * Monday July 17, 2023 at 09:16 Pacific 11 | * Monday July 17, 2023 at 12:16 Eastern 12 | * Monday July 17, 2023 at 18:16 Zurich 13 | * Monday July 18, 2023 at 00:16 Hong_Kong 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/pull_casper_node_version.sh casper-test.conf 1_5_2 25 | sudo -u casper /etc/casper/config_from_example.sh 1_5_2 26 | ``` 27 | 28 | ## Verifying Successful Staging 29 | 30 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 31 | upgrade by taking a look at your `status` end-point, as follows: 32 | 33 | ```shell 34 | curl -s http://127.0.0.1:8888/status | jq -r 35 | ``` 36 | 37 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 38 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 39 | 40 | ```json 41 | "next_upgrade": { 42 | "activation_point": 9904, 43 | "protocol_version": "1.5.2" 44 | }, 45 | ``` 46 | 47 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 48 | 49 | [include ../disclaimer.md] 50 | 51 | 52 | 53 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_5_3.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.3 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.3`, the activation point is `Era 10827`, which will be approximately around: 9 | * Monday October 02, 2023 at 14:28 UTC 10 | * Monday October 02, 2023 at 10:28 EST 11 | * Monday October 02, 2023 at 07:28 PST 12 | * Monday October 02, 2023 at 16:28 EU/Zurich 13 | * Monday October 02, 2023 at 22:28 HK 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 10827, 42 | "protocol_version": "1.5.3" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_5_5.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.5 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.5`, the activation point is `Era 11751`, which will be approximately around: 9 | * Monday December 18, 2023 at 14:51 UTC 10 | * Monday December 18, 2023 at 06:51 US/Pacific 11 | * Monday December 18, 2023 at 09:51 US/Eastern 12 | * Monday December 18, 2023 at 15:51 Europe/Zurich 13 | * Monday December 18, 2023 at 22:51 Asia/Hong_Kong 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 11751, 42 | "protocol_version": "1.5.5" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_5_6.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.6 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.6`, the activation point is `Era 12268`, which will be approximately around: 9 | * Monday January 30, 2024 at 16:09 UTC 10 | * Monday January 30, 2024 at 08:09 US/Pacific 11 | * Monday January 30, 2024 at 11:09 US/Eastern 12 | * Monday January 30, 2024 at 17:09 Europe/Zurich 13 | * Monday January 31, 2024 at 00:09 Asia/Hong_Kong 14 | 15 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 16 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 17 | 18 | ## Upgrade Staging Instructions 19 | 20 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 21 | one by one: 22 | 23 | ```shell 24 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 25 | ``` 26 | 27 | ## Verifying Successful Staging 28 | 29 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 30 | upgrade by taking a look at your `status` end-point, as follows: 31 | 32 | ```shell 33 | curl -s http://127.0.0.1:8888/status | jq -r 34 | ``` 35 | 36 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 37 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 38 | 39 | ```json 40 | "next_upgrade": { 41 | "activation_point": 12268, 42 | "protocol_version": "1.5.6" 43 | }, 44 | ``` 45 | 46 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 47 | 48 | [include ../disclaimer.md] 49 | 50 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_5_7.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.7 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.7`, the activation point is `Era 14473`, which will be approximately around Thursday, August 01, 2024 at 14:38 UTC. 9 | 10 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 11 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 12 | 13 | ## Upgrade Staging Instructions 14 | 15 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 16 | one by one: 17 | 18 | ```shell 19 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 20 | ``` 21 | 22 | ## Verifying Successful Staging 23 | 24 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 25 | upgrade by taking a look at your `status` end-point, as follows: 26 | 27 | ```shell 28 | curl -s http://127.0.0.1:8888/status | jq -r 29 | ``` 30 | 31 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 32 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 33 | 34 | ```json 35 | "next_upgrade": { 36 | "activation_point": 14473, 37 | "protocol_version": "1.5.7" 38 | }, 39 | ``` 40 | 41 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 42 | 43 | [include ../disclaimer.md] 44 | 45 | -------------------------------------------------------------------------------- /src/testnet/upgrade-1_5_8.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v1.5.8 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v1.5.8`, the activation point is `Era 14570`, which will be approximately around Friday, August 09, 2024 at 13:53 UTC. 9 | 10 | In order to not have points deducted for your Testnet reward score, you have to make sure you have properly staged the 11 | upgrade well ahead of the activation point, so that your node will be upgraded on time. 12 | 13 | ## Upgrade Staging Instructions 14 | 15 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following two commands, 16 | one by one: 17 | 18 | ```shell 19 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 20 | ``` 21 | 22 | ## Verifying Successful Staging 23 | 24 | After you have successfully executed the above commands, you can verify that your node is correctly staged with the 25 | upgrade by taking a look at your `status` end-point, as follows: 26 | 27 | ```shell 28 | curl -s http://127.0.0.1:8888/status | jq -r 29 | ``` 30 | 31 | This will print the status of your node to your terminal. Towards the end of the JSON output, you will find an object 32 | called `next_upgrade`, which if you successfully staged your upgrade, will have the following structure and values: 33 | 34 | ```json 35 | "next_upgrade": { 36 | "activation_point": 14570, 37 | "protocol_version": "1.5.8" 38 | }, 39 | ``` 40 | 41 | If you see another value here, for example `null`, then your upgrade staging was not executed successfully. 42 | 43 | [include ../disclaimer.md] 44 | 45 | -------------------------------------------------------------------------------- /src/testnet/upgrade-2_0_1.md: -------------------------------------------------------------------------------- 1 | # Upgrade to casper-node v2.0.1 2 | 3 | ## Introduction and Timing 4 | We are requesting that all Casper Testnet participants stage the upgrade of their nodes to a new version of `casper_node` 5 | immediately, using the instructions below. "Staging an upgrade" is a process in which you tell your node to download 6 | the upgrade files and prepare them, so that they can automatically be applied at the pre-defined activation point. 7 | 8 | For this upgrade, to `casper-node v2.0.1`, the activation point is `Era 17497`, which will be approximately around Thursday, April 10, 2025 at 14:46 UTC. 9 | 10 | Please make sure you have properly staged the upgrade well ahead of the activation point, so that your node will be upgraded on time. 11 | 12 | ## Upgrade Staging Instructions 13 | 14 | The process to upgrade your node is very straightforward. Log in to your node, and execute the following command: 15 | 16 | ```shell 17 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 18 | ``` 19 | 20 | ## Verifying Successful Staging 21 | 22 | After you have successfully executed the above command, you can verify that your node is correctly staged with the 23 | upgrade by taking a look at the output of the following command to make sure it has the 24 | `Next Upgrade: {'activation_point': 17497, 'protocol_version': '2.0.1'}` `status` line: 25 | 26 | ```shell 27 | /etc/casper/node_util.py watch 28 | ``` 29 | 30 | If you don't see the `Next Upgrade` line here, then your upgrade staging was not executed successfully. 31 | 32 | [include ../disclaimer.md] 33 | 34 | -------------------------------------------------------------------------------- /src/ubuntu/bond.md: -------------------------------------------------------------------------------- 1 | ## Bond to the network 2 | 3 | Once you ensure that your node is running correctly and is visible by other proceed to bonding. 4 | 5 | ### Check your balance 6 | 7 | Check your balance to ensure you have funds to bond: 8 | 9 | [comment]: <> ([include ../casper-client/check-balance.md]) 10 | 11 | [include casper-client/check-balance.md] 12 | 13 | ### Make bonding request 14 | 15 | [comment]: <> ([include ../casper-client/bond.md]) 16 | 17 | [include casper-client/bond.md] 18 | 19 | ### Check that your bonding request worked 20 | 21 | [include casper-client/check-transaction-status.md] 22 | 23 | ### Query the auction info and look for your bid 24 | 25 | [include casper-client/check-auction-info.md] 26 | -------------------------------------------------------------------------------- /src/ubuntu/build-the-contracts.md: -------------------------------------------------------------------------------- 1 | #### Build the contracts 2 | 3 | ``` 4 | make setup-rs 5 | make build-client-contracts -j 6 | ``` 7 | -------------------------------------------------------------------------------- /src/ubuntu/casper-client/bond.md: -------------------------------------------------------------------------------- 1 | If you followed the installation steps from this document you can run the following script to bond. 2 | It substitutes the public key hex value for you and sends recommended argument values: 3 | 4 | ``` 5 | CHAIN_NAME=$(curl -s http://127.0.0.1:8888/status | jq -r '.chainspec_name') 6 | 7 | sudo -u casper casper-client put-transaction add-bid \ 8 | --chain-name "$CHAIN_NAME" \ 9 | --delegation-rate $(( RANDOM % 11 )) \ 10 | --public-key $(cat /etc/casper/validator_keys/public_key_hex) \ 11 | --transaction-amount 10000000000000 \ 12 | --secret-key /etc/casper/validator_keys/secret_key.pem \ 13 | --standard-payment true \ 14 | --payment-amount 2500000000 \ 15 | --gas-price-tolerance 1 16 | ``` 17 | 18 | #### Argument Explanation 19 | - ```transaction-amount``` - This is the amount that is being bid. If the bid wins, this will be the validator’s initial bond amount. The minimum bid amount is ```10000 CSPR``` or ```10000000000000 motes``` as an argument to the ```ad-bid``` transaction. 20 | - ```delegation-rate``` - The percentage of rewards that the validator retains from delegators that delegate their tokens to the node. The example above sets a random value between 0 (meaning 0%) and 10 (meaning 10%). 21 | - ```payment-amount``` - The fee in motes (1 CSPR = 10^9 motes) to cover the contract execution cost. It's ```2.5 CSPR``` or ```2500000000 motes``` on the command above. 22 | 23 | Remember the ```transaction_hash``` returned in the response to query its status later. 24 | -------------------------------------------------------------------------------- /src/ubuntu/casper-client/check-auction-info.md: -------------------------------------------------------------------------------- 1 | To determine if the bid was accepted, execute the following command: 2 | 3 | ``` 4 | casper-client get-auction-info --node-address http://127.0.0.1:7777 5 | ``` 6 | 7 | The bid should appear among the returned ```bids```. If the public key associated with a bid appears in the ```validator_weights``` structure for an era, then the account is bonded in that era. 8 | -------------------------------------------------------------------------------- /src/ubuntu/casper-client/check-balance.md: -------------------------------------------------------------------------------- 1 | If you followed the installation steps from this document you can run the following script to check the balance: 2 | 3 | ``` 4 | PUBLIC_KEY_HEX=$(sudo -u casper cat /etc/casper/validator_keys/public_key_hex) 5 | STATE_ROOT_HASH=$(casper-client get-state-root-hash --node-address http://127.0.0.1:7777 | jq -r '.result | .state_root_hash') 6 | PURSE_UREF=$(sudo -u casper casper-client query-state --node-address http://127.0.0.1:7777 --key "$PUBLIC_KEY_HEX" --state-root-hash "$STATE_ROOT_HASH" | jq -r '.result | .stored_value | .Account | .main_purse') 7 | casper-client get-balance --node-address http://127.0.0.1:7777 --purse-uref "$PURSE_UREF" --state-root-hash "$STATE_ROOT_HASH" | jq -r '.result | .balance_value' 8 | ``` 9 | -------------------------------------------------------------------------------- /src/ubuntu/casper-client/check-transaction-status.md: -------------------------------------------------------------------------------- 1 | Sending a transaction to the network does not mean that the transaction processed successfully. It’s important to check to see that the contract executed properly: 2 | 3 | ``` 4 | casper-client get-deploy --node-address http://127.0.0.1:7777 | jq .result.execution_results 5 | ``` 6 | 7 | Replace `````` with the deploy hash of the transaction you want to check. 8 | -------------------------------------------------------------------------------- /src/ubuntu/checkout-release-branch-testnet.md: -------------------------------------------------------------------------------- 1 | #### Checkout the release branch 2 | 3 | > **Note** 4 | > Verify that the version of your contracts matches the version of the casper-node software you have 5 | > installed. 6 | 7 | ``` 8 | git checkout release-1.5.8 9 | ``` 10 | -------------------------------------------------------------------------------- /src/ubuntu/configure-node.md: -------------------------------------------------------------------------------- 1 | ## Configure and Run the Node 2 | 3 | ### Configure the node's firewall 4 | In order to secure your node somewhat from unauthorized/excessive connections/requests, you can configure the firewall of the node using a template ```ufw``` setup: 5 | 6 | ``` 7 | cd ~; curl -JLO https://genesis.casper.network/firewall_only_node_to_node.sh 8 | chmod +x ./firewall.sh 9 | 10 | # Look at this and make sure you understand what it does and want to run it on your server. 11 | # You will need to provide `y` to reset and enable steps. 12 | cat ./firewall.sh 13 | 14 | # Install firewall 15 | sudo ./firewall.sh 16 | ``` 17 | 18 | ### Stage all protocol upgrades 19 | 20 | ``` 21 | sudo -u casper /etc/casper/node_util.py stage_protocols casper-test.conf 22 | ``` 23 | 24 | The above command will download and stage all available node upgrades to your machine so they are prepped when the node is turned on, and will automatically execute the upgrade and the required time. 25 | 26 | ### Set trusted hash 27 | 28 | Set the `trusted_hash` to the hash value of the latest block on Casper TestNet: 29 | 30 | ``` 31 | NODE_ADDR=https://node.testnet.casper.network/rpc 32 | PROTOCOL=2_0_1 33 | sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node-address $NODE_ADDR | jq -r .result.block_with_signatures.block.Version2.hash | tr -d '\n')'" /etc/casper/$PROTOCOL/config.toml 34 | ``` 35 | 36 | The command above will set the trusted hash on the config file of the `2.0.1` protocol version. Please note that the protocol version should be set to the largest available protocol version you see in `ls /etc/casper`. 37 | -------------------------------------------------------------------------------- /src/ubuntu/generate-keys.md: -------------------------------------------------------------------------------- 1 | Navigate to the default key directory: 2 | ``` 3 | cd /etc/casper/validator_keys 4 | ``` 5 | 6 | And execute the following command to generate the keys: 7 | ``` 8 | sudo -u casper casper-client keygen . 9 | ``` 10 | 11 | It will create three files in the ```/etc/casper/validator_keys``` directory: 12 | 13 | - ```secret_key.pem``` - your private key; never share it with anyone 14 | - ```public_key.pem``` - your public key 15 | - ```public_key_hex``` - hex representation of your public key; copy it to your machine to create an account 16 | 17 | Save your keys to a safe place. The public key hex file is used to identify your account when delegators stake their tokens with you or if you are transferring CSPR to this account. 18 | -------------------------------------------------------------------------------- /src/ubuntu/install-casper-node.md: -------------------------------------------------------------------------------- 1 | #### Add Casper repository 2 | 3 | Execute the following in order to add the Casper repository to `apt` in Ubuntu. 4 | ```shell 5 | sudo mkdir -m 0755 -p /etc/apt/keyrings/ 6 | sudo curl https://repo.casper.network/casper-repo-pubkey.gpg --output /etc/apt/keyrings/casper-repo-pubkey.gpg 7 | echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/casper-repo-pubkey.gpg] https://repo.casper.network/releases focal main" | sudo tee -a /etc/apt/sources.list.d/casper.list 8 | sudo apt update 9 | ``` 10 | 11 | #### Install the Casper node software 12 | 13 | ``` 14 | sudo apt install -y casper-node-launcher casper-client casper-sidecar 15 | ``` 16 | -------------------------------------------------------------------------------- /src/ubuntu/monitor-node-status.md: -------------------------------------------------------------------------------- 1 | ### Monitor the node status 2 | 3 | #### Check the node log 4 | 5 | Please note that it is expected to see a lot of connection messages flooding your screen when you check the logs. Don't be scared by the `request timed out` and `outgoing connection failed` messages as long as they are all `INFO` level messages, and as long as you also see a lot of `linear chain block stored` messages, which means that your node is successfully fetching and storing existing blocks from other/older peers on the network. 6 | 7 | ``` 8 | sudo tail -fn100 /var/log/casper/casper-node.log /var/log/casper/casper-node.stderr.log 9 | ``` 10 | 11 | #### Check the node status 12 | 13 | ``` 14 | curl -s http://127.0.0.1:8888/status | jq 15 | ``` 16 | 17 | #### Monitor the node's sync progres 18 | You can monitor the node's synchronization progress by using the ```node_util.py``` utility script: 19 | 20 | ``` 21 | /etc/casper/node_util.py watch 22 | ``` 23 | 24 | When you run the watch command, expect to see something like this: 25 | ``` 26 | Every 5.0s: /etc/casper/node_util.py node_status ; /etc/casper/node_util.py systemd_status 27 | 28 | Last Block: 2035316 (Era: 10565) 29 | Peer Count: 214 30 | Uptime: 1day 20h 31m 7s 504ms 31 | Build: 1.5.2-86b7013 32 | Key: 0173a3611a3730d6d1a71e91c15a046b3278f6ae9291df6963067958d87035e1fc 33 | Next Upgrade: None 34 | 35 | Reactor State: KeepUp 36 | Available Block Range - Low: 2028872 High: 2035316 37 | 38 | ● casper-node-launcher.service - Casper Node Launcher 39 | Loaded: loaded (/lib/systemd/system/casper-node-launcher.service; enabled; vendor preset: enabled) 40 | Active: active (running) since Fri 2023-09-08 22:15:57 UTC; 1 day 20h ago 41 | Docs: https://docs.casper.network 42 | Main PID: 2775 (casper-node-lau) 43 | Tasks: 11 (limit: 38291) 44 | Memory: 29.3G 45 | CGroup: /system.slice/casper-node-launcher.service 46 | ├─2775 /usr/bin/casper-node-launcher 47 | └─2789 /var/lib/casper/bin/1_5_2/casper-node validator /etc/casper/1_5_2/config.toml 48 | ``` 49 | 50 | If your Reactor State is in "CatchUp" you will need to wait for the node to gather more blocks before it will become "KeepUp" and subsequently show an "Available Block Range". 51 | 52 | If your casper-node-launcher status is not active (running) with increasing time, you are either not running or restarting. 53 | 54 | The watch command also allows an `--ip` argument to use with a node on the same network that is in sync. This will show how far behind your node currently is. 55 | 56 | #### Wait for node to catch up 57 | Before you do anything, such as trying to bond as a validator or perform any RPC calls, make sure your node has fully 58 | caught up with the network. You can recognize this by log entries that tell you that joining has finished, and that the 59 | RPC and REST servers have started: 60 | 61 | ``` 62 | {"timestamp":"Feb 09 02:28:35.577","level":"INFO","fields":{"message":"finished joining"},"target":"casper_node::cli"} 63 | {"timestamp":"Feb 09 02:28:35.578","level":"INFO","fields":{"message":"started JSON-RPC server","address":"0.0.0.0:7777"},"target":"casper_node::components::rpc_server::http_server"} 64 | {"timestamp":"Feb 09 02:28:35.578","level":"INFO","fields":{"message":"started REST server","address":"0.0.0.0:8888"},"target":"casper_node::components::rest_server::http_server"} 65 | ``` 66 | 67 | While Monitoring the node’s synchronization progress using the node_util.py utility script: 68 | ``` 69 | /etc/casper/node_util.py watch 70 | ``` 71 | Make sure the Node is in KeepUp and has synced enough blocks for the current TTL (2 hours / 16.384 = 450 blocks) before continuing with the next steps. 72 | ``` -------------------------------------------------------------------------------- /src/ubuntu/open-files-limit.md: -------------------------------------------------------------------------------- 1 | ## Update Open Files Limit 2 | 3 | Before beginning, update the maximum open files limit for your system. Specifically, update the node's `/etc/security/limits.conf` file as described below, to ensure proper node operation. 4 | 5 | Add the following row to the bottom of the `/etc/security/limits.conf` file: 6 | 7 | ``` 8 | casper hard nofile 64000 9 | ``` 10 | 11 | And make sure the bottom part of the file contents looks similar to what is seen below: 12 | 13 | ``` 14 | #* soft core 0 15 | #root hard core 100000 16 | #* hard rss 10000 17 | #@student hard nproc 20 18 | #@faculty soft nproc 20 19 | #@faculty hard nproc 50 20 | #ftp hard nproc 0 21 | #ftp - chroot /ftp 22 | #@student - maxlogins 4 23 | casper hard nofile 64000 24 | 25 | # End of file 26 | ``` 27 | -------------------------------------------------------------------------------- /src/ubuntu/open-ports.md: -------------------------------------------------------------------------------- 1 | ## Open Firewall Ports 2 | 3 | In your firewall set-up, make sure you expose the following ports to public and that they're routed to your node: 4 | 5 | - ```7777``` - rpc port 6 | - ```8888``` - status port 7 | - ```9999``` - event stream port 8 | - ```35000``` - gossip port 9 | -------------------------------------------------------------------------------- /src/ubuntu/remove-casper-node.md: -------------------------------------------------------------------------------- 1 | ``` 2 | sudo systemctl stop casper-node-launcher.service 3 | sudo apt purge -y casper-client 4 | sudo apt purge -y casper-node-launcher 5 | sudo rm -rf /etc/casper 6 | sudo rm -rf /var/lib/casper 7 | ``` 8 | -------------------------------------------------------------------------------- /src/ubuntu/setup-testnet-validator-from-scratch.md: -------------------------------------------------------------------------------- 1 | # Setup Test Net validator node from scratch on Ubuntu 20.04 2 | 3 | [include ../testnet/testnet-warning.md] 4 | 5 | [include sudo-notice.md] 6 | 7 | [include open-ports.md] 8 | 9 | [include open-files-limit.md] 10 | 11 | [include setup-validator-from-scratch.md] 12 | 13 | ## Generate keys and fund your account 14 | 15 | ### Generate node keys 16 | 17 | [include generate-keys.md] 18 | 19 | ### Create account 20 | 21 | [include ../testnet/create-testnet-account.md] 22 | 23 | ### Fund account 24 | 25 | [include ../testnet/fund-testnet-account.md] 26 | 27 | [include configure-node.md] 28 | 29 | [include start-node.md] 30 | 31 | [include monitor-node-status.md] 32 | 33 | [include bond.md] 34 | 35 | [include ../disclaimer.md] 36 | -------------------------------------------------------------------------------- /src/ubuntu/setup-validator-from-scratch.md: -------------------------------------------------------------------------------- 1 | ## Install software 2 | 3 | ### Update package repositories 4 | 5 | ``` 6 | sudo apt update 7 | ``` 8 | 9 | ### Install pre-requisites 10 | 11 | ``` 12 | sudo apt install -y dnsutils software-properties-common git 13 | ``` 14 | 15 | The node uses ```dig``` to get external IP for autoconfig during the installation process 16 | 17 | ### Install helpers 18 | 19 | ``` 20 | sudo apt install jq -y 21 | ``` 22 | 23 | We will use ```jq``` to process JSON responses from API later in the process 24 | 25 | ### Remove Previous Versions 26 | 27 | If you were running previous versions of the casper-node on this machine, first stop and remove the old versions: 28 | 29 | [include remove-casper-node.md] 30 | 31 | ### Install Casper node 32 | 33 | [include install-casper-node.md] 34 | -------------------------------------------------------------------------------- /src/ubuntu/start-node.md: -------------------------------------------------------------------------------- 1 | ### Start the node 2 | 3 | ``` 4 | sudo logrotate -f /etc/logrotate.d/casper-node 5 | sudo systemctl start casper-node-launcher; sleep 2 6 | systemctl status casper-node-launcher 7 | ``` 8 | -------------------------------------------------------------------------------- /src/ubuntu/sudo-notice.md: -------------------------------------------------------------------------------- 1 | > ### Note 2 | > Do not execute all the commands below as `root`. `sudo` is included where it is required. 3 | > 4 | > Do not create or use the username `casper`. It will be automatically created during the installation, and is meant to be used by the node software as a no-login user. 5 | > 6 | > Expect that initial setup of a node will take about 15-20 minutes, and you will need to wait for a few hours for the node to sync before bonding it to the network. 7 | --------------------------------------------------------------------------------