Clarify - do not use bonsai + archive node #1582
Merged
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
Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@non-fungible-nelson can you review? Do we want to soften the wording a bit given we're currently working on supporting Bonsai + Archive |
|
LGTM --> I am happy to reword these later on. Right now, these changes are all accurate. |
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.
Clarify syncing and data storage format pages that you shouldn't run an archive node with bonsai. Clarify the definitions of full and archive nodes.
Fixes #1524
Preview: