Green Baneling

It is bad that we did double work=( We could cooperate together to deliver but it is too late. We did the [same in the OpenBrush](https://github.com/Supercolony-net/openbrush-contracts/pull/104). But it is still...

Hmm, I think we already did it with new rustfmt rules https://github.com/FuelLabs/fuel-core/pull/575 and https://github.com/FuelLabs/fuel-core/pull/605

Do you ask about `coinsToSpend` method signature or changes also in the database? `coinsToSpend` is an inevitable change because we want to work with different objects(coins, messages). Because it breaks...

Before I will update the tests let's discuss the final query signature in the issue=)

The developer doesn't need to install/interact precisely with `fuel-core`. We can have a separate package that starts the indexer and `fuel-core` together. Indexer has a GraphQL port exposed to the...

> Ideally, we move all the core impl logic inside the graphql resolvers into a Rust API directly accessible on FuelService. Then, suppose we wanted to make a fuel-api-node that...

You can check what the code looks like and decide whether it is okay or not=) And maybe better to merge other PR first before this one.

We actually can remove it because it is very fas check(~10 seconds) =)

> I think its a good thing to have a fmt standard. But then if we are diverging from the default of rustfmt, we might want to enforce that to...

@Voxelot What do you think about renaming all `Database`'s methods by underscore? To highlight that they are internal methods, and you need to work with `StorageMutate` and `StorageInspect`. - `Database::insert`...