Skip to main content
install.sh deploys and activates one staking pool from guides/apps/staking-pools/install-helpers/. You configure the environment, run the script, and execute the commands it asks you to. The script uses Foundation-delegated funds when a DelegationHandler has been provisioned for your validator. Otherwise it spends 10,000 BERA plus gas from your funding wallet.

What you need before you run install.sh

You need a synced validator, helper tools, and live endpoints:
  • A synced Berachain validator
  • bash, Foundry (cast), jq, and curl
  • Reachable execution-layer JSON-RPC and consensus-layer Node API endpoints. Enable the Node API. The Node API can run on any node; it doesn’t have to be on the validator.
You also need one funding path:
  • Self-funded: at least 10,000 BERA plus gas in the funding wallet
  • Delegated: a DelegationHandler already formed and funded for your validator, plus gas for activation
The Berachain Foundation forms the DelegationHandler when they issue a delegation. That setup is internal; operators run install.sh once the handler exists.

Clone install-helpers

Clone the guides repo and enter the helper directory:

Set environment variables

Copy env.sh.template to env.sh in that directory, then edit the copy. install.sh sources env.sh when the file is present.

Run install.sh

Use ./install.sh --help for usage.
If a DelegationHandler with delegated funds exists for your validator’s pubkey, the script uses the delegated path. Otherwise it uses the self-funded path. The script will walk you through obtaining the necessary information, verifying the signatures, and activating the validator. Upon completion, receipts are written to staking-pool-receipts.jsonl.

What’s next

The Operator guide covers day-two work. The example frontend is a sample UI for end users. Continue with: