Icon HelpCircleForumIcon Link

⌘K

Icon HelpCircleForumIcon Link
Icon AlertTriangle

Mainnet docs are version-pinned. Check each section's exact version in the sidebar; it can lag the newest upstream release.

Docs /
Node Operator /
Fuel Sequencer

Icon LinkRunning a Fuel Sequencer Node or Validator

Below is a summary of key information to help you get started with running a node for the Fuel Sequencer blockchain.

For more details, please refer to the deployment repository Icon Link.

Icon LinkHardware Requirements

HardwareMinimumRecommended
Processor4 Cores8 Cores
Memory8 GB16 GB
Storage200 GB1 TB

Icon LinkPort Configuration

Unless otherwise configured, the following ports should be available:

  • Sequencer: 26656, 26657, 9090, 1317
  • Sidecar: 8080
  • Ethereum: 8545, 8546

These components interact with each other, so any changes to the port configuration must be reflected in the corresponding components. Specifically:

  • Changes to Sequencer ports must be updated in the Sidecar's runtime flags.
  • Changes to the Sidecar port must be updated in the Sequencer's app config.
  • Changes to Ethereum ports must be updated in the Sidecar's runtime flags.

Icon LinkGetting Started

Depending on your needs, you can choose one of the following setups:

  1. Running a Mainnet Fuel Sequencer Node : Your local node will connect to and sync with the mainnet Fuel Sequencer network.
  2. Running a Mainnet Fuel Sequencer Validator : Your local node will connect to, sync with, and validate transactions on the mainnet Fuel Sequencer network.
  3. Running a Testnet Fuel Sequencer Node : Your local node will connect to and sync with the testnet Fuel Sequencer network.
  4. Running a Testnet Fuel Sequencer Validator : Your local node will connect to, sync with, and validate transactions on the testnet Fuel Sequencer network.