Skip to main content
This guide shows validator operators how to use delegated capital to stand up and run a staking pool. It builds on the Installation guide and reuses the same helper scripts. It does not cover delegator actions; coordinate with your capital provider as needed. See Installation first. At minimum, set up env.sh in install-helpers/.
All helper scripts write cast commands to files; review and run them yourself. Transactions are never sent automatically. Signing defaults to Ledger; set PRIVATE_KEY in env.sh if you prefer a local key.

​
Assumptions

  • You completed the validator Installation steps (env configured, node synced).
  • The Berachain Foundation has prepared a DelegationHandler and delegated funds for your validator pubkey.

​
1. Check readiness

Confirm the chain, validator pubkey, and whether a delegated pool/handler is detected: 
./status.sh
If a handler exists, the script displays delegated amounts and whether a pool already exists for your pubkey.

​
2. Create the pool with delegated funds (first 10,000 BERA)

If the pool is not yet created, use the delegated creation script. It consumes the first 10,000 BERA from the handler to register the validator and writes a ready-to-run command file. This step is the delegated equivalent of the self-funded flow’s register.sh (it performs the 10,000 BERA deposit and deploys the pool contracts). 
./delegated-create-pool.sh
This will create a script with deployment commands. Review it. Then run it to submit the transaction, then wait for confirmation.

​
3. Wait for validator registration

After deploying the contracts, wait for your validator to be registered on the beacon chain. You can check registration status with: 
./status.sh
The validator must appear on the beacon chain before you can activate the pool.

​
4. Activate the pool

Activation mirrors the Installation flow. Once the validator is recognised as registered on the beacon chain, run activate.sh: 
./activate.sh
activate.sh is a permissionless call keyed on your validator pubkey and no longer takes --sr or --op. It preflights the activation locally (pool deployed, pool not already active, operator and withdrawal-credentials match, proofs verify against a single pinned slot) and writes generated/activation-command.sh for you to review and execute. Proofs are contract-checked against MAX_TIMESTAMP_AGE = 10 minutes; if you delay broadcasting beyond that window, re-run activate.sh to regenerate.

​
5. Deposit remaining delegated funds

After activation, deposit the remaining delegated funds to reach your target balance (for example, 250,000 BERA on Bepolia). The script writes a command file for you to execute. 
./delegated-deposit.sh --amount 240000

​
6. Verify status

./status.sh
You should see contract addresses, the operator match on the beacon deposit contract, and the pool marked ACTIVE. The script also reports delegated amounts when a handler is present.

​
7. Withdraw yield (operator)

Operators can withdraw earned yield independently of principal. The helper script writes two commands (request, then complete after cooldown): 
./delegated-withdraw-yield.sh --pubkey 0xYOUR_VALIDATOR_PUBKEY
Follow the prompts to execute the generated request and completion scripts after the cooldown. Principal withdrawals are controlled by the delegator and are out of scope here. Once you have attracted additional depositors, the foundation can redeem its stake without causing your validator to exit.
If you are self-funded, use stake.sh from the Installation guide instead of the delegated deposit flow.

​
Where to next