Green Baneling

It is related to devops and CI more. The main idea is to automate benchmark result generation. Right now it is done manually.

Related https://github.com/FuelLabs/fuel-vm/issues/164

It was fixed during https://github.com/FuelLabs/fuel-core/pull/1434

Closing for now since we don't see the problem anymore in the testnet

During the work on https://github.com/FuelLabs/fuel-core/pull/1625 `Message`s became part of the on-chain database, and the block importer has exclusive write ownership in the `Messages` table. This means that messages became part...

- [x] https://github.com/FuelLabs/fuel-core/issues/1167 - [x] Currently, we request each header one by one. Instead, it will be faster and better(from a performance perspective) to send the range of headers. In...

During refactoring for `no_std` support in `fuel-vm` we replaced `std::io::Error` with anyhow or another errors.

Blocked by https://github.com/FuelLabs/fuel-core/issues/1189 and https://github.com/FuelLabs/fuel-core/issues/1229

@Voxelot Do we need this issue?

You should already be able to fetch blocks with all transactions and any additional data via GraphQL. On the rust side, you can reuse types from `fuel-core-client` and compose them...