Skip to main content

Network

Flare has four networks, each serving different purposes. All networks are permissionless and EVM compatible:

  • Flare Mainnet. The production network where all the action happens. Transactions cost real money here.
  • Flare Testnet Coston2. Test your applications without spending real money. This should be your first choice when developing applications.
  • Songbird Canary-Network. Experimental proving ground for Flare.
  • Songbird Testnet Coston. The testnet for Songbird Canary-Network.

The most common development tracks are:

  1. Application Development (Recommended track for dApp developers):
    • Flare Testnet Coston2 → Flare Mainnet
  2. Protocol Development (Required track for all protocol level changes):
    • Songbird Testnet Coston → Songbird Canary-Network → Flare Testnet Coston2 → Flare Mainnet

Configuration

Specific configuration details for connecting to each Flare network, including public RPC endpoints, chain identifiers, blockchain explorers, and testnet faucets.

Network nameFlare Mainnet
Public RPCs (HTTPS)https://flare-api.flare.network/ext/C/rpc
https://stylish-light-theorem.flare-mainnet.quiknode.pro/ext/bc/C/rpc
Public RPCs (WSS)wss://flare-api.flare.network/ext/C/ws
wss://stylish-light-theorem.flare-mainnet.quiknode.pro/ext/bc/C/ws
Chain ID14
Native currencyFLR (18 decimals)
Routescan Explorerhttps://flarescan.com
Blockscout Explorerhttps://flare-explorer.flare.network
Faucet-
Bootstrapping nodeshttps://flare-bootstrap.flare.network
https://flare-bootstrap-1.staking.production.figment.io
https://flare.senseinode.com
{Safe}Wallethttps://multisig.flare.network
RPC Connection code snippet
curl https://flare-api.flare.network/ext/C/rpc -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Supported wallets

A variety of wallets across desktop, browser extension, and mobile platforms support Flare. Discover suitable options for your needs on the Flare Wallets page.

Transaction format

  • Address space: Matches Ethereum, 20-byte addresses using ECDSA.

  • Transaction format: Matches Ethereum, complies with EIP-2718, encoded with RLP.

  • Transaction fees:

    • Type0 (Legacy) - Fee is calculated as gasUsed * gasPrice.

    • Type2 (EIP-1559) - Fee is calculated as (baseFee + priorityFee) * gas. Both the base and priority fees are burned.

Smart contracts

  • Compatibility: Fully EVM-compatible. Contracts written in Solidity, Vyper, or other EVM languages can be deployed directly.

  • RPC-API: Ethereum RPC API

  • Supported opcodes: Supports all EVM opcodes up to and including the London hard fork.

Consensus mechanism

  • Consensus Protocol: Snowman++ (from Avalanche) provides a high-throughput, totally ordered consensus with fast finality. Learn more on the Consensus page.

  • Sybil resistance mechanism: Proof-of-Stake (PoS)

  • Delegation: In-protocol

  • Block time: ≈1.8 seconds

  • Finality: Single-slot finality. Once a block is accepted through the consensus process (gossip), it's considered final.

  • Transaction ordering: Determined by the block proposer (leader), the default behavior is priority gas auction.

  • Participants (Validators):

    • Nodes must meet a minimum self-bond requirement (defined by governance) to become validators.
    • Validators participate in consensus voting and are randomly selected as leaders to propose new blocks, weighted by their total stake (self-bond + delegated stake).
    • The network currently features around 90 validators (median stake ≈0.7%, max stake ≈3.3%).
  • Enshrined protocols: In addition to consensus, Flare validators are also data providers for FTSO and FDC.

Block verification

Adding Flare (FLR) to your exchange

Integrating Flare is similar to integrating Ethereum or other EVM chains. To add it to your exchange set up an RPC node and use the appropriate network configuration for Flare Mainnet.

Additional resources: Flare Brand assets, go-flare Source Code

Watch the video