-
Notifications
You must be signed in to change notification settings - Fork 78
updating the the steps for network upgrade for forte #1513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
vishalchangrani
merged 5 commits into
main
from
vishal/forte_upgrade_node_operator_steps
Oct 16, 2025
Merged
updating the the steps for network upgrade for forte #1513
vishalchangrani
merged 5 commits into
main
from
vishal/forte_upgrade_node_operator_steps
Oct 16, 2025
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
zhangchiqing
approved these changes
Oct 15, 2025
peterargue
approved these changes
Oct 16, 2025
|
|
||
| - `YOUR_NODE_TYPE` should be one of `collection`, `consensus`, `execution`, `verification`, `access` based on the node(s) that you are running. | ||
| - `YOUR_NODE_TYPE` should be one of `collection`, `consensus`, `execution`, `verification` based on the node(s) that you are running. | ||
| - For access nodes however, if you have execution data index enabled use the role `execution` otherwise use `access`. |
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe add a note about why
Suggested change
| - For access nodes however, if you have execution data index enabled use the role `execution` otherwise use `access`. | |
| - For access nodes however, if you have execution data index enabled use the role `execution` to ensure the execution state checkpoint is downloaded. Otherwise use `access`. |
Contributor
Author
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added explanation
Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com>
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.
No description provided.