Berachain’s network relies on validator nodes and RPC nodes. Each can be configured as a full node or archive node.
Each of these types of nodes is a pair of both an execution client and a consensus client. Berachain is a Layer 1 EVM Identical chain, which means that for the execution layer, it supports any EVM execution client paired with a consensus client and framework built by Berachain called BeaconKit.
RPC vs validator nodes
The main difference between an RPC node and a validator node is that a validator can propose blocks and receive block rewards.
An RPC node can become a validator node by joining the Active Set through interaction with the BeaconDeposit contract by meeting the $BERA stake requirements.
Active set
The active set is the set of validators that are currently participating in the consensus layer of the network.
The current limit of validators in the active set is 69.
Validators can choose to leave the active set voluntarily — learn how — or be ejected from the set if a validator with more stake joins.
Validator stake requirements
The minimum stake requirement depends on whether the active set is completely full.
If the active set is not full, the minimum stake requirement is 250,000 $BERA.
If the active set is full, the minimum stake requirement is 10,000 $BERA more than the amount staked by the last validator in the active set.
It can take up to 3 epochs (192 blocks per epoch) for deposits to be processed and for a validator to be included in the active set.
Direct staking
Berachain follows Proof-of-Stake (PoS) direct staking, which allows $BERA holders to directly stake their $BERA to a validator. However, note that if funds are withdrawn from a validator, currently all funds are returned to a single address: the validator’s Withdrawal Credentials Address.
This means that validators will have to communicate how they handle funds when a validator is removed from the active set.
Avoid staking to validators without knowing how they handle funds when a validator is removed from the active set.
Staking pools
Validators can also operate staking pools, which enable liquid staking services for their communities. Staking pools use smart contracts to manage deposits and withdrawals, allowing stakers to receive liquid shares (stBERA) that automatically grow in value as rewards accumulate. Staking pools provide validators with a way to build and monetize their own community of stakers while offering stakers lower barriers to entry and flexible withdrawals. For information about setting up and operating staking pools, see the Staking Pools documentation.
Removed from active set
If a validator is removed from the active set, all $BERA staked to that validator will be returned to the validator’s Withdrawal Credentials Address, which is set when the validator makes their first deposit.
A validator can decide to become a validator again but will need to generate new CometBFT validator keys and start the deposit process again as if they were a new validator.
Staking with a previously-used CometBFT identity — a validator that was removed from the active set — will result in the funds being returned to that validator’s withdrawal address at the end of the current epoch. The validator can never be re-activated.
Voluntary withdrawals
A Validator can withdraw all or part of their stake.
Validator block rewards and distribution
Block rewards are in the form of $BGT, with a base reward of 0.5 $BGT per block proposed.
The network does not distribute rewards automatically. You must distribute block rewards through the Distributor contract. Distribution must occur before 8,191 seconds have passed, or validators risk losing those rewards. 
