BIFROST Network
  • Introduction
  • Bifrost Network Architecture
    • Consensus
    • Cross-Chain Communication Protocol (CCCP)
    • Oracle Service
  • Running a Node
    • Basic-Node Requirements
    • Full-Node Requirements
    • Validator Account Management
    • Guide for Operators
      • Setting up an Endpoint Node
        • Using Docker
        • Using Systemd
      • Setting up a Validator Node
        • Using Docker
        • Using Systemd
      • Setting up a Relayer
        • bifrost-relayer.rs
        • bifrost-relayer.py (Deprecated)
      • Chain Data Snapshots
      • Trouble Shooting
        • Testnet Chain Sync Issue
    • System Monitoring
      • Prometheus and Grafana
      • Sentry
  • Nominators
  • Developer Documentations
    • Ethereum API
      • Ethereum Precompiled Contracts
      • Libraries
      • Developer Environments
    • Bifrost Precompiled Contracts
      • Staking
      • Governance
      • RelayManager
    • Pallet Interfaces
      • BfcStaking
      • BfcUtility
      • BfcOffences
      • RelayManager
    • Client API
      • JSON-RPC API
        • author
        • chain
        • childstate
        • debug
        • eth
        • grandpa
        • net
        • offchain
        • payment
        • rpc
        • state
        • system
        • trace
        • txpool
        • web3
      • Explorer API
      • Runtime API
    • Cross-Chain Transaction and Oracle API
      • Price Oracle Contract API
      • Socket Contract API
    • Testnet Faucet
  • Governance
  • Security
  • Tokens & Assets
    • Unified Token
    • Inflation Model
  • Add Network
    • Pockie
    • MetaMask
  • Bridge
    • Bridge Guide
      • Depositing to the Bifrost Network
      • Withdrawing to another network
    • Glossary
  • Staking
    • Staking Guide
      • Stake BFC
      • Unstake BFC
    • Glossary
      • All Validators
      • My Staking Status
  • Language
    • 바이프로스트 네트워크 가이드
Powered by GitBook
On this page
  • Technical Requirements
  • Bonding Requirements
  • Operating Requirements
  • Account Management
  • Required Credentials
  • External Source Access
  1. Running a Node

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)

Technical Requirements

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.5TB (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

1.5TB (gp3)

Operating system requirements (Ubuntu 18.04 ~ 24.04 Recommended)

  • Linux Kernel 5.16 or later

  • Amazon Linux 2: 5.10.130-118.517.amzn2.x86_64 or later

Bonding Requirements

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

Operating Requirements

Account Management

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.

Required Credentials

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

External Source Access

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).

Price Feed

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

PreviousBasic-Node RequirementsNextValidator Account Management

Last updated 2 months ago