ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-20 03:35:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Edit validator keys note per review

Browse Source
This commit is contained in:
Rome Reginelli
2020-07-31 10:10:36 -07:00
committed by GitHub
parent cc45a55f43
commit b1e2aca835
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md
View File

@@ -72,7 +72,7 @@ In a location **not** on your validator:
This file should be stored securely and not shared.
**Warning:** Store the generated `validator-keys.json` key file in a secure, offline, and recoverable location, such as an encrypted USB flash drive. Do not store keys on the validator where you intend to use the keys. If your `secret_key` is compromised, [revoke the key](https://github.com/ripple/validator-keys-tool/blob/master/doc/validator-keys-tool-guide.md#key-revocation) immediately. Do not modify the contents of `validator-keys.json`, except to increment the `token _sequence` after generating a new validation token using a copy of the file. For example, if you copy your secure, backed up `validation-keys.json` to your validator to generate a new token, generating the token will increase the `token_sequence` field. If you do not update the `token_sequence` field in your secure backup, then the next token you generate will have the same or lower sequence number as the token you are currently using. The network will ignore validations that have a sequence number that is less than the previously highest observed number. Alternately, simply copy `validator-keys.json` to your backup location every time you generate a new validation token, so your backup version has the correct `token_sequence`.
**Warning:** Store the generated `validator-keys.json` key file in a secure, offline, and recoverable location, such as an encrypted USB flash drive. Do not store keys on the validator where you intend to use the keys. If your `secret_key` is compromised, [revoke the key](https://github.com/ripple/validator-keys-tool/blob/master/doc/validator-keys-tool-guide.md#key-revocation) immediately. Do not modify the contents of `validator-keys.json`, except to update the backup after generating a new token. If you generate more than one token from the same backup without updating, the network ignores the later tokens because they use the same `token_sequence` number.
For more information about the `validator-keys` tool and the key pairs it generates, see the [Validator Keys Tool Guide](https://github.com/ripple/validator-keys-tool/blob/master/doc/validator-keys-tool-guide.md).