Flare Mainnet Entity Operations
Flare is an EVM-compatible Layer 1 with enshrined data protocols. A production Flare operator normally runs a validator node and a Flare Entity stack so the same entity can validate the network and participate in the Flare Systems Protocol (FSP), including FTSOv2 and FDC.
Architecture
| Layer | Component | Purpose |
|---|---|---|
| Validator | go-flare node | Flare P-Chain validation, C-Chain execution, staking identity |
| FSP | Flare System Client | Contract interactions, voter registration, protocol submissions, signing policy tasks, finalization |
| FSP | C-Chain Indexer | Indexes FSP contract events and transactions used by protocol clients |
| FTSO | FTSO Client | Anchor feed commit/reveal data for FTSOv2 Scaling |
| FTSO | Fast Updates Client | Block-latency feed updates, backed by sortition key and fast-update accounts |
| FTSO | Feed Value Provider | Operator-provided price/data source API consumed by FTSO clients |
| FDC | FDC Client | Consumes verifier APIs and submits FDC voting data through FSP |
| FDC | FDC Suite | Chain nodes, indexers, verifiers, and optional Web2 verifier used by the FDC client |
Checked Versions
Values below were checked from official Flare docs and repositories on 2026-05-11.
| Item | Version / Commit | Source |
|---|---|---|
go-flare | v1.13.0 | Latest GitHub release and Docker Hub versioned tag checked on 2026-05-11 |
flare-systems-deployment | 0fa4ac7 | Main branch commit checked on 2026-05-11 |
flare-system-client | v1.0.12 | Image tag in flare-systems-deployment/docker-compose.yaml |
flare-system-c-chain-indexer | v1.1.2 | Image tag in flare-systems-deployment/docker-compose.yaml |
ftso-scaling | v1.0.9 | Image tag in flare-systems-deployment/docker-compose.yaml |
fdc-client | v1.2.9 | Image tag in flare-systems-deployment/docker-compose.yaml |
fast-updates/go-client | v1.0.2 | Image tag in flare-systems-deployment/docker-compose.yaml |
fdc-suite-deployment | 5cb3644 | Main branch commit checked on 2026-05-11 |
The FDC suite release notes currently include v1.2.4-rc.1, which requires XRP reindexing and BTC/DOGE/XRP PostgreSQL migration or reindex. Do not upgrade FDC suite repositories blindly; read RELEASES.md and plan downtime or a parallel deployment.
Hardware
| Deployment | CPU | RAM | Disk |
|---|---|---|---|
| Flare validator node only | 4 cores | 16 GB | 1 TB SSD pruned, 5.7 TB SSD archival |
| Full Flare Entity on one host | 16 cores | 64 GB | 4 TB SSD |
| Full FDC suite on one host | 16-32 cores/threads | 64 GB | 4 TB NVMe |
| Web2 verifier standalone | 4 cores | 8 GB | Minimal local disk |
Splitting FSP, FDC, and the value provider across multiple servers is supported and often easier to operate at scale. Keep latency low between the System Client, FDC Client, FTSO Client, and their upstream APIs.
Network Ports
| Port | Scope | Purpose |
|---|---|---|
9651/tcp | Public | Flare P2P / staking port, must be reachable |
9650/tcp | Local or trusted network only | go-flare HTTP API |
3101/tcp | Internal trusted network | Feed Value Provider example/default API |
9800/tcp | Internal trusted network | EVM verifier API default |
| FDC verifier ports | Internal trusted network | BTC/DOGE/XRP/Web2 verifier APIs, based on compose files |
Never expose 9650 or verifier APIs publicly without authentication, filtering, and a clear reason. Validator nodes should not serve public RPC traffic.
Operating Directories
| Directory | Contents |
|---|---|
/data/flare/node | go-flare Docker Compose, database mount, config, logs, staking keys |
/data/flare/fdc-suite-deployment | FDC blockchain node, indexer, verifier deployment repository and generated configs |
/data/flare/flare-systems-deployment | FSP/FTSO/FDC client deployment repository and generated configs |
/data/flare/value-provider | Operator-owned FTSO Feed Value Provider deployment |