Skip to content

Rewrite staking pool installation for the hands-off operator CLI - #98

Open
camembera wants to merge 10 commits into
mainfrom
docs/staking-pool-install-cli
Open

Rewrite staking pool installation for the hands-off operator CLI#98
camembera wants to merge 10 commits into
mainfrom
docs/staking-pool-install-cli

Conversation

@camembera

Copy link
Copy Markdown
Collaborator

Rewrites the staking-pool installation walkthrough for the new single-command, two-mode CLI (companion to berachain/guides#441).

  • Replaces the six-subcommand, cast-required flow with one install command.
  • Documents hot-key (PRIVATE_KEY set, fully automatic) vs. cold-signing (no key, prints cast send for a separate signing machine) modes.
  • Documents the single up-front confirmation, concise default output vs. --verbose, and kill/resume safety.
  • set-min-balance, deploy, activate remain 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.md in the companion PR), which implements against this page as its UX contract.

…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant