fuellabs/fuel-core
Rust full node implementation of the Fuel v2 protocol.
How fuel-core is put together
fuel-core is the Rust implementation of the Fuel blockchain full node (v0.48.2, BUSL-1.1). It is a large Cargo workspace whose binary (`bin/fuel-core`) orchestrates services: a GraphQL API (async-graphql on axum at /v1/graphql), transaction pool, block producer, consensus modules (PoA and BFT), block importer that commits state to RocksDB, P2P sync, an Ethereum relayer built on the alloy stack, gas-price service, and compression service. Transactions enter via a `submit` GraphQL mutation, are executed by the executor (with parallel and upgradable WASM variants), and blocks are imported and queryable through GraphQL. Supporting binaries include a GraphQL CLI client, e2e test client, chaos-test harness (which spawns Redis for leader leases), and keygen.
Languages
Frameworks
Datastores
Infrastructure
Major components
GraphQL API service
Serves the public Fuel client API at /v1/graphql including submit, dry-run, estimate-predicates, and chain queries; schema is generated to crates/client/assets/schema.sdl.
Executor (crates/services/executor, parallel-executor, upgradable-executor/wasm-executor)
Executes transactions against the Fuel VM, with a parallel variant and a WASM-packaged upgradable executor for forkless upgrades.
Consensus modules (consensus_module/poa, bft)
Implements proof-of-authority instant block production and BFT consensus, using Redis-backed leader leasing for multi-node coordination.
Importer (crates/services/importer)
Validates and commits produced/synced blocks and their state transitions into the persistent database, emitting committed-block streams.
TxPool v2 + TxStatusManager
Admits, orders, and tracks transactions pending inclusion and propagates their status updates to subscribers.
P2P & Sync (crates/services/p2p, sync)
Peer-to-peer gossip of blocks/transactions and catch-up synchronization of chain state from peers.
Relayer (crates/services/relayer)
Bridges Ethereum L1 events into Fuel state using the alloy provider/RPC stack.
Storage & Database (crates/storage, crates/database, crates/fuel-core/src/database.rs, combined_database.rs)
Defines storage abstractions, column families, and the combined RocksDB (+Redis) persistence layer behind feature flags like rocksdb-production.
A single internal cleanup improved how the proof-of-authority system sends updates, making it faster and more efficient.
2 weeksWeek of 2026-08-24
Recent work on fuel-core focused on improving network reliability and infrastructure hygiene. The team made the blockchain's peer-to-peer layer smarter about which computers to trust for data, and cleaned up internal plumbing in the proof-of-authority component. Supporting changes also made the automated testing pipeline more reliable by reducing dependence on live external services.
Week by week
2026-08-24A single internal cleanup improved how the proof-of-authority system sends updates, making it faster and more efficient.latest1 change
Refactor
Faster, cleaner update publishing in PoA
The proof-of-authority component now publishes its announcements through Redis using a modern async approach with cached connections, cutting overhead and reorganizing where that logic lives.
2026-08-10This week hardened the peer-to-peer network against unreliable participants and fixed several automated testing pipelines.3 changes
Fix
Smarter handling of unreliable network peers
Peers that repeatedly fail to answer requests are now penalized, and the node prefers trusted 'reserved' peers when fetching new blocks, making block syncing more dependable.
Fix
Testing no longer touches the real AWS account
The continuous integration tests now simulate Amazon's key-management service locally instead of calling the company's live AWS account, avoiding cost and risk.
Chore
Repaired broken CI security and compatibility checks
Two automated checks—one scanning dependencies for known vulnerabilities and one verifying version compatibility—were fixed so they run correctly again.
Dependencies and code review
Dependency advisories
Security Watch
No known advisories across 0 scanned dependencies.
No known advisories in the scanned dependencies.
Code review
38 files reviewed; 0 of 1 claimed findings confirmed after verification.
Get this report every week for your repos.
GitZoid learns each repo, reports what changed, and flags what needs attention. One flat price for the whole team.
$19 a month, flat · First 10 outputs free · No card required