validator-manage

To join a GenLayer validator, you use the GenLayer CLI to add new validator accounts to your chosen testnet. The process enforces prerequisites like having the CLI installed, the correct active network selected, and existing owner and operator accounts before adding the validator.

Funding a GenLayer operator account requires supplying staking tokens to the operator wallet via the GenLayer CLI. The Skill checks for an existing operator account on the active testnet before transferring the staking tokens needed to secure the network.

Yes, you can assign or update validator identities and monikers per network using the GenLayer CLI. This identity management ensures your validator is correctly recognized across the specific testnet you are operating on.

Managing GenLayer validators across multiple testnets requires the GenLayer CLI to be installed and configured. You must treat each testnet separately with distinct staking contracts, ensuring the correct active network and corresponding owner and operator accounts are set.

You can view current validators and manage their associations by listing them through the GenLayer CLI. This allows you to organize accounts per network and owner, providing checks for network, account, and validator status across isolated testnets.

Validator management fails if prerequisites are unmet, such as the genlayer CLI not being installed, the incorrect active network being selected, or missing owner and operator accounts. The Skill provides checks for network, account, and validator status to prevent these errors.