added tutorial for multikey #918
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@iulianpascalau please review |
|
|
||
| Make sure that all operations from step 6 are made as quickly as possible. In case this step takes a long time, the backup multikey group should take over. | ||
|
|
||
| :::caution | ||
| Always attempt this process while closely monitor your nodes. If done correctly, your nodes might experience a brief rating drop (until the backup group takes over - if necessary) | ||
| ::: | ||
|
|
||
| ### Setup a multikey node |
There was a problem hiding this comment.
I think this is better to go before L316 (Migration guide from single-key operation to multikey)
| @@ -332,6 +326,12 @@ Whenever deciding to switch from single-key operation to multikey, the following | |||
|
|
|||
| Make sure that all operations from step 6 are made as quickly as possible. In case this step takes a long time, the backup multikey group should take over. | |||
|
|
|||
| :::warning | |||
There was a problem hiding this comment.
why this change? I think the warning should be put before the script
|
|
||
| Make sure that all operations from step 6 are made as quickly as possible. In case this step takes a long time, the backup multikey group should take over. | ||
|
|
||
| :::caution | ||
| Always attempt this process while closely monitor your nodes. If done correctly, your nodes might experience a brief rating drop (until the backup group takes over - if necessary) | ||
| ::: | ||
|
|
||
| ### Setup a multikey node |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the pull request (what is new / what has changed)
Did you test the changes locally ?
Which category (categories) does this pull request belong to?