Full-Node Requirements
Full nodes share all the features of the basic nodes and additionally facilitate Cross-Chain Communication. To do that, they must keep access to external blockchains and off-chain data feed for price oracles. Full node rewards consist of:
- Self-staking rewards which accrue in proportion to the number of staked tokens
- Transaction fees
- Fees from cross-chain transactions
- A portion of nominators' staking rewards (optional)
For Native Hardware
For AWS Instances
Hardware | Minimum requirement |
|---|---|
CPU | - x86-64 compatible
- Intel Ice Lake, or newer (Xeon or Core series); AMD Zen3, or newer (EPYC)
- Simultaneous multithreading disabled (Hyper-Threading on Intel, SMT on AMD)
- Prefer single-threaded performance over a higher cores count |
Storage | An NVMe SSD of 1 TB (As it should be reasonably sized to deal with blockchain growth) |
RAM | 32GB DDR4 |
Hardware | Minimum requirement |
|---|---|
EC2 | m5zn.2xlarge |
VCPU | 8 |
RAM | 32GB |
EBS | 1TB (gp2) |
Operating system requirements (Ubuntu 18.04 ~ 22.04 Recommended)
- Linux Kernel 5.16 or later
- Amazon Linux 2: 5.10.130-118.517.amzn2.x86_64 or later
Testnet
Mainnet
Requirements | Amount |
|---|---|
Minimum self-bond | 100,000 BFC |
Minimum voting power (self-bond + total nominated BFC) | 100,000 BFC |
Requirements | Amount |
|---|---|
Minimum self-bond | 400,000 BFC |
Minimum voting power (self-bond + total nominated BFC) | 4,000,000 BFC |
Validators should securely manage three accounts, Stash, Controller, and Relayer 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 operations.
- Relayer account: An EVM account for cross-chain action participation. It should have enough balance for transaction fees used in 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
Full nodes should set up Web3 providers to all the external blockchains supported by the Bifrost Network via reusing their blockchain RPC nodes or employing external services (e.g. Infura or NodeReal).
The full-node validators collect on-chain and off-chain data for price oracles.
- On-chain price feed: ChainLink
- Off-chain API: CoinGecko, Upbit, Binance, Gate.io, Kucoin
Last modified 1mo ago