Fuel Development
Index Fuel blockchain data including transactions, receipts, and smart contract interactions on the Fuel network.Getting Started
Key Features
UTXO Model
Handle Fuel’s UTXO-based transaction model
Sway Contracts
Index Sway smart contract interactions
Receipts
Process transaction receipts and logs
Predicates
Monitor predicate executions and validations
Basic Processor Setup
Receipt Types
Fuel uses receipts to represent various operations:Transfer Receipts
Log Data Receipts
Call Receipts
Data Structures
Receipt Structure
Transaction Structure
Common Use Cases
Asset Transfers
Contract Interactions
Token Operations
Performance Optimization
Receipt Filtering
Filter by specific receipt types and contracts
Asset Targeting
Focus on specific assets or contracts
Batch Processing
Process receipts in optimized batches
Efficient Storage
Optimize data models for Fuel’s UTXO structure
Network Information
Mainnet
- Gateway:
https://v2.archive.subsquid.io/network/fuel-mainnet - RPC:
https://mainnet.fuel.network/v1/graphql - Block Time: ~1 second
- Finality: Near-instant
Testnet
- Gateway:
https://v2.archive.subsquid.io/network/fuel-testnet - RPC:
https://testnet.fuel.network/v1/graphql
Fuel-Specific Considerations
UTXO Model
- Transactions consume inputs and produce outputs
- No account-based state like Ethereum
- Each transaction is atomic
Asset Management
- Native multi-asset support
- Each asset has a unique asset ID
- ETH is represented as asset ID
0x00...00
Gas Model
- Gas is paid in the base asset (ETH)
- Predictable gas costs
- No gas price auctions
Examples
Best Practices
- Understand Fuel’s UTXO model for proper data modeling
- Use receipt filtering to reduce data processing overhead
- Handle different receipt types appropriately
- Monitor gas usage patterns for optimization
- Implement proper error handling for failed transactions
Next Steps
- Explore Fuel Network API
- Learn about Sway programming language
- Check Fuel examples

