Update split keys quickstart to match charon behavior#164
Open
pinebit wants to merge 2 commits into
Open
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Update the "Migrate an Existing Validator" (split keys) quickstart and the CLI reference to match actual charon behavior:
--cluster-dir=/opt/charon/clusterto the example docker command; without it the cluster is created in./node*, contradicting the page's./clustertree and the zip step.deposit-data-*.jsonfiles ARE re-created in split mode, signed with the existing validator keys using the provided withdrawal addresses, and add a warning not to submit them for already-activated validators. The page previously omitted these files entirely.Created charon cluster, cluster dir path, deposit-data files).--split-existing-keysflag description in the CLI reference.Note: the fee-recipient ordering note and the updated flag description correspond to ObolNetwork/charon#4577 and apply from the charon release containing it; the deposit data documentation is accurate for current releases as well.
🤖 Generated with Claude Code