Fuel
Fuel API is available on Web3 API platform.
Fuel is an operating system specifically designed for Ethereum Rollups, providing the necessary tools and infrastructure to maximize the efficiency of rollups while solving key challenges around scalability and performance. Fuel’s goal is to enhance the Ethereum ecosystem by optimizing for parallelization, state-minimized execution, and interoperability (PSI), without compromising on any of these aspects.
- FuelVM: Optimized execution engine enabling parallel transaction execution and state minimization using a UTXO model, improving scalability and throughput.
- Sway Language: A Rust + Solidity inspired language for smart contracts, offering safety, performance, and static auditing.
- Developer Experience: Streamlined, boilerplate-free development for efficient contract creation and interaction with the FuelVM.
- Unmatched Throughput: Leverages parallel processing for significantly higher transaction throughput compared to single-threaded blockchains.
In order for your Web3 application to interact with Fuel — either by reading blockchain data or sending transactions to the network — it must connect to a Fuel node. Developers interact with the blockchain using the methods provided by the API.
Responses come in JSON format.
Queries/Mutations supported
- getAddressAssetBalance — retrieves the balance of a specific asset of a given address.
- getAddressAssetBalances — retrieves balances of all assets of a given address.
- getTransactionsByOwner — retrieves all transactions of a given address.
- getLatestTransactions — retrieves the most recent transactions on the network.
- getContractAssetBalance — retrieves the balances of a specific asset of a given contract.
- getContractAssetBalances — retrieves all asset balances of a given contract.
- getLatestBlocks — retrieves several most recent blocks on the network.
- getLatestBlock — retrieves the most recent block on the network.
- getBlockByHeight — retrieves info on a block specified by height.
- getBlockById — retrieves info on a block specified by ID.
- getMessagesByAddress — retrieves all messages of a given address.
- dryRunTransaction — simulates a transaction without broadcasting it.
- submitTransaction — submits a transaction to the network.