Skip to main content

Documentation Index

Fetch the complete documentation index at: https://berachain-422fce37-feat-nodes-section-reno.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Berachain Node (beacond) Reference

beacond, is an EVM consensus client implementation used as a basic beacon node for Berachain. See BeaconKit Consensus Layer for more details.

Global Flags

These flags apply to all commands:
FlagDescription
--home stringDirectory for config and data (default: ~/.beacond)

Basic Commands

init

Initialize validator and node configuration files.
beacond init <moniker> [flags]

Flags

FlagDescription
--chain-id stringGenesis file chain-id (randomly created if blank)
--beacon-kit.chain-specWhich chain to generate configurations for. This value is also placed in the generated app.toml. mainnet or testnet or file
--beacon-kit.chain-spec-fileIf chain-spec=file, which file to use. Should be toml format. This value is also placed in the generated app.toml.
--default-denom stringGenesis file default denomination (default: “stake”)
--initial-height intInitial block height at genesis (default: 1)
-o, --overwriteOverwrite the genesis.json file
--recoverRecover existing key using seed phrase instead of creating new one

start

Run the node application with CometBFT in process.
beacond start [flags]

Flags

The start command has numerous configuration flags for networking, consensus, pruning, and more. Key flags include:
FlagDescription
--abci stringABCI transport (socket or grpc) (default: “socket”)
--address stringListen address (default: “tcp://127.0.0.1:26658”)
--db_backend stringDatabase backend (default: “pebbledb”)
--moniker stringNode name
--p2p.laddr stringNode listen address (default: “tcp://0.0.0.0:26656”)
--p2p.persistent_peers stringComma-delimited ID@host:port persistent peers
--p2p.seeds stringComma-delimited ID@host:port seed nodes
--pruning stringPruning strategy (default|nothing|everything|custom)
--rpc.laddr stringRPC listen address (default: “tcp://127.0.0.1:26657”)
Additional flags are available for detailed engine configuration, beacon-kit settings, and consensus parameters.

status

Query remote node for status information.
beacond status [flags]

Flags

FlagDescription
-n, --node stringNode to connect to (default: “tcp://localhost:26657”)
-o, --output stringOutput format (text|json) (default: “json”)

version

Print the application binary version information.
beacond version [flags]

Flags

FlagDescription
--longPrint long version information
-o, --output stringOutput format (text|json) (default: “text”)

rollback

Recover from an incorrect application state transition by rolling back one height.
beacond rollback [flags]

Flags

FlagDescription
--hardRemove last block as well as state

CometBFT Commands (comet)

Commands for managing the CometBFT consensus engine.

comet bootstrap-state

Bootstrap CometBFT state at an arbitrary block height using a light client.
beacond comet bootstrap-state [flags]

Flags

FlagDescription
--height intBlock height to bootstrap state at (uses latest block height in app state if not provided)

comet reset-state

Remove all data and WAL (Write-Ahead Log).
beacond comet reset-state [flags]

comet show-address

Show this node’s CometBFT validator consensus address.
beacond comet show-address [flags]

comet show-node-id

Show this node’s ID.
beacond comet show-node-id [flags]

comet show-validator

Show this node’s CometBFT validator info.
beacond comet show-validator [flags]

comet unsafe-reset-all

Remove all data and WAL, reset this node’s validator to genesis state (unsafe).
beacond comet unsafe-reset-all [flags]

Flags

FlagDescription
--keep-addr-bookKeep the address book intact
-k, --key-type stringPrivate key type (ed25519|secp256k1|bls12_381) (default: “ed25519”)

comet version

Print protocols’ and libraries’ version numbers this app was compiled against.
beacond comet version [flags]

Deposit Commands (deposit)

Commands for managing validator deposits.

deposit create-validator

Create a validator deposit with necessary credentials.
beacond deposit create-validator [withdrawal-address] [amount] ?[beacond/genesis.json] [flags]

Flags

FlagDescription
-g, --genesis-validator-root stringUse provided genesis validator root (if not set, beacond genesis file must be provided)
-o, --override-node-keyOverride the node private key

deposit validate

Validate a deposit message for creating a new validator.
beacond deposit validate [pubkey] [withdrawal-credentials] [amount] [signature] ?[beacond/genesis.json] [flags]

Flags

FlagDescription
-g, --genesis-validator-root stringUse provided genesis validator root (if not set, beacond genesis file must be provided)

deposit validator-keys

Output validator public key in various formats.
beacond deposit validator-keys [flags]
Displays the validator key as Comet address, Comet pubkey, and Eth/Beacon pubkey formats.

Genesis Commands (genesis)

Commands for genesis file management. These are largely only of interest to those of us maintaining Berachain, so we have stuck to the generally useful ones.

genesis validator-root

Get and return the genesis validator root hash.
beacond genesis validator-root [beacond/genesis.json] [flags]

JWT Commands (jwt)

Commands for managing JWT authentication.

jwt generate

Generate a new JWT authentication secret.
beacond jwt generate [flags]

Flags

FlagDescription
-o, --output-path stringOptional output file path for the JWT secret (default: ”./jwt.hex”)

jwt validate

Validate a JWT secret by checking if it’s formatted properly.
beacond jwt validate [flags]

Flags

FlagDescription
-i, --input-path stringOptional input file path for the JWT secret (default: ”./jwt.hex”)