Manually Exit Validators
Manual exits should only be used in specific scenarios: emergency, maintenance, or testing.
Validators Manager Required
The wallet executing this command must be set as the Validators Manager in the Vault settings. If the Validators Manager is set to the wallet address of the Relayer, you have to add the --relayer-endpoint parameter.
./operator exit-validators
Example Output
Enter the comma separated list of API endpoints for execution nodes: https://execution-node
Enter the comma separated list of API endpoints for consensus nodes: https://consensus-node
Enter your vault address: 0x3320ad928c20187602a2b2c04eeaa813fa899468
Fetching vault validators...
Are you sure you want to exit 3 validators with indexes: 513571, 513572, 513861? [y/N]: y
Exits for validators with index(es) 513571, 513572, 513861 are successfully initiated
exit-validators flags
| Flag | Description |
|---|---|
--indexes | Comma-separated list of validator indexes to exit. Cannot be used with --count |
--count | Number of validators to exit (default: all active). Cannot be used with --indexes |
--relayer-endpoint | Relayer endpoint URL for API mode operations |
--no-confirm | Skips confirmation prompts |
--max-withdrawal-request-fee-gwei | Maximum fee per withdrawal request. Default: 1000 Gwei |
--vault-first-block | Block the Vault was created at. Speeds up event fetching considerably on long-lived Vaults |
--network | Network of the Vault. Default: the network chosen during init |
--data-dir | Path where keystores and config data are placed. Default: ~/.stakewise |
-v, --verbose | Enable debug mode, prints full output on error |
--log-level | Set logging level: ERROR, WARNING, INFO, DEBUG. Default: INFO |