Fuel-core is a Rust implementation of a full node for the Fuel v2 blockchain protocol. The repository serves as the primary client software for participating in Fuel networks, with current deployments running version 0.48.1 across Fuel Ignition, Testnet, and Devnet networks. The codebase is actively maintained and classified across multiple blockchain infrastructure domains including smart contracts, virtual machines, transaction processing, consensus mechanisms, peer-to-peer networking, cryptography, and scalability solutions with a modular architecture.
The repository provides comprehensive tooling for both node operators and developers. Node operators can run Fuel nodes either from pre-compiled binaries or by building from source, with detailed documentation provided for participating in the Ignition network. The software supports multiple deployment configurations, including local network setups for development purposes. The node implementation includes a GraphQL service endpoint at /v1/graphql that allows interaction with the blockchain through GraphQL queries, enabling transaction submission and other client operations. The transaction executor performs instant block production with changes persisted to RocksDB by default.
Development infrastructure is well-established within the repository. Contributors are expected to follow guidelines documented in CONTRIBUTING.md and run ci_checks.sh before submitting changes. The build system uses xtask for development compilation, which handles cargo builds and custom processes such as GraphQL schema regeneration. Testing is facilitated through the ci_checks.sh script that runs all CI checks. The repository supports multiple operating systems with specific system requirements documented for macOS, Debian, and Arch Linux, including requirements for clang and the wasm32-unknown-unknown Rust target.
Activity data shows sustained engagement from the development team.
The repository includes extensive operational documentation covering system requirements, compilation procedures, testing frameworks, and troubleshooting guidance. Notable operational considerations include file descriptor limits on macOS that can cause RocksDB failures, database management through the ~/.fuel/db directory, and configurable logging through the RUST_LOG environment variable. The software supports in-memory database modes for development and allows disabling block production through configuration flags. Automatic crate publishing is handled through the publish-crates GitHub action, with local troubleshooting possible via the act tool. The modular architecture enables flexible deployment scenarios from local development networks to production Ignition network participation.
