Basic node operators stake BFC to verify and create blocks. Validators should expect staking rewards if they stake in the network for at least three months. The longer the staking period, the higher the rewards. The rewards consist of:
Self-staking rewards which accrue in proportion to the number of staked tokens
Transaction fees
A portion of nominators' staking rewards (optional)
CPU
4 cores
8+ cores
RAM
8 GB
16+ GB
Disk
500 GB
1+ TB
CPU
4 cores
8+ cores
RAM
16 GB
32+ GB
Disk
1.5+ TB
2+ TB
Minimum self-bond
50,000 BFC
Minimum voting power (self-bond + total nominated BFC)
50,000 BFC
Minimum self-bond
400,000 BFC
Minimum voting power (self-bond + total nominated BFC)
2,000,000 BFC
To guarantee network stability and fast finality, all node operators are required to meet the published hardware specifications.
Effective immediately, Validator-Nodes must be capable of consistently performing block creation within a 3-second timeframe (the target block time). Validators who fail to maintain this performance standard due to inadequate hardware will be subject to monitoring and have a possibility of being penalized (slashed).
To avoid penalties and ensure optimal block creation performance, your setup must meet or exceed the requirements above.
Validators should securely manage two accounts, Stash and Controller accounts, for self-bonding deposit and consensus participation, respectively.
Stash account: An EVM account for the self-bonding deposit.
Controller account: An EVM account for consensus participation. It should have enough balance for transaction fees used in certain operations.
Validators require three types of keys as follows:
AURA key for block production
GRANDPA key for block finalization
“Imonline” key to check the node availability
Last updated
