Start Operator

Setup Checklist

Before starting the Operator Service, confirm that everything is in place:

I've created my Vault I've fully synced my execution client I've fully synced my consensus client I've configured MEV-Boost I've installed the Operator Service I've generated validator keys and uploaded them into my validator client I've set the fee recipient address in my validator client I've set up the Validators Manager

Start Operator Service

Run the Operator Service using the start command with your Vault address and node endpoints. Choose the format matching your installation method:

Binary

./operator start \
  --vault=0x834F27bC8670491b75af512d943f01D5383F87Cf \
  --consensus-endpoints=https://consensus-node \
  --execution-endpoints=https://execution-node

Docker

For Docker, you first need to mount the folder containing validator keystores and include the --data-dir flag alongside the start command:

docker run --restart on-failure:10 \
-u $(id -u):$(id -g) \
-v ~/.stakewise/:/data \
europe-west4-docker.pkg.dev/stakewiselabs/public/v3-operator:v4.1.10 \
src/main.py start \
--vault=0x834F27bC8670491b75af512d943f01D5383F87Cf \
--data-dir=/data \
--consensus-endpoints=http://localhost:5052 \
--execution-endpoints=http://localhost:8545

Source Files

PYTHONPATH=. poetry run python src/main.py start \
--vault=0x834F27bC8670491b75af512d943f01D5383F87Cf \
--consensus-endpoints=http://localhost:5052 \
--execution-endpoints=http://localhost:8545

Optional Flags

Flag	Description
--keystores-dir	Directory with validator keys in EIP-2335 ↗ format. Must contain a single password.txt or per-keystore password files (e.g., keystore1.json, keystore1.txt)
--keystores-password-file	Path to the password file for decrypting keystores
--wallet-file	Path to the wallet file. Default: file generated by create-wallet
--wallet-password-file	Path to the wallet password file. Default: file generated by create-wallet
--harvest-vault	Keeps your Vault synced by calling updateState every 12 hours, reducing gas costs for users. The Vault state is also updated whenever users interact with it (deposits, withdrawals, etc.)
--claim-fee-splitter	Periodically claims fees to shareholder addresses. See Fee Claiming →
--run-nodes	Starts and manages local Reth (execution), Lighthouse (consensus), and validator nodes alongside the Operator Service. Requires node-install first. See Automated Node Setup →
--validator-type	Register 0x01 instead of default 0x02 validators
--min-deposit-amount-gwei	Minimum Vault balance to trigger registration or top-up. Minimum allowed: 1 ETH/GNO. Default: 10 ETH/GNO
--vault-min-balance-gwei	ETH to keep in the Vault and not stake. Default: 0
--max-validator-balance-gwei	Maximum validator balance for top-ups. Default: 1945 ETH (Ethereum), 1800 GNO (Gnosis)
--min-deposit-delay	Minimum delay between registration or top-up transactions. Default: 3600 seconds (1 hour)
--max-withdrawal-request-fee-gwei	Maximum fee per withdrawal request. Default: 1000 Gwei
--disable-withdrawals	Disables submitting partial and full withdrawals. This reduces gas costs but increases withdrawal times for users. Oracles will instead handle exits using signatures from registration
--max-fee-per-gas-gwei	Maximum gas fee per transaction. Default: 10 Gwei (Ethereum), 2 Gwei (Gnosis)
--concurrency	Number of processes in a pool. For optimal performance, set to half your CPU cores (e.g., --concurrency=4 for 8-core systems) to prevent overloading during keystore operations
--disable-validators-registration	Disables registering new validators
--disable-validators-funding	Disables topping up existing 0x02 validators
--verbose	Enable debug mode, prints full output on error
--log-level	Set logging level: ERROR, WARNING, INFO, DEBUG