Rewrite staking pool installation for the hands-off operator CLI - #98
Open
camembera wants to merge 10 commits into
Open
Rewrite staking pool installation for the hands-off operator CLI#98camembera wants to merge 10 commits into
camembera wants to merge 10 commits into
Conversation
…tor CLI. Thin the per-step behavior lists in the operator flow now that the command reference covers each flag and the underlying call sequence.
…lout. The 5-slot cushion should not run out in normal operation, so the example session no longer walks through the block-not-found error as an expected step.
Draft for Lead review/markup: single `install` entry point, hot-key vs cold-signing mode selection, one confirmation, concise default output with --verbose, resume-safe, set-min-balance/delegated pools out of the automatic flow. deploy/activate/set-min-balance stay available as standalone commands for advanced/manual use.
installation.mdx described a signing-preference prompt (Ledger vs private key) that the CLI never actually reads a key for either way; clarify it defaults to --ledger and is a flag/env override only.
--finalize with no id now finalizes every ready withdrawal request in one batch transaction; --finalize <id> still finalizes just that one.
status/activate/set-min-balance/stake/unstake now read install's scenario file so BEACOND_HOME isn't needed to run them afterward on a remote validator; deploy is the one exception and is unaffected.
Drop env.sh.template copy-and-edit and the deleted standalone verbs.
Replace S-labels and CLI_CHAIN with EL/CL env vars, Plan naming, generated files section, role-address prompts, and compact status expectations.
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.
Rewrites the staking-pool installation walkthrough for the new single-command, two-mode CLI (companion to berachain/guides#441).
installcommand.PRIVATE_KEYset, fully automatic) vs. cold-signing (no key, printscast sendfor a separate signing machine) modes.--verbose, and kill/resume safety.set-min-balance,deploy,activateremain available as standalone commands for advanced/manual use, called out explicitly rather than left ambiguous.Approved directly by the Lead ahead of the implementation brief (
project/briefs/staking-pools-operator-cli-redesign.mdin the companion PR), which implements against this page as its UX contract.