Brandon Kite

cc @vlopes11

Given change amounts are only set post-execution, I'm not sure if there's a real use case for `GTF_OUTPUT_CHANGE_AMOUNT`.

We should still support CLI args as well, since they are easier to templatize and configure in helm charts. Toml based config files would align with other parts of our...

reopening since we need to make a pr to fuel-core to automate this type of configuration

The most recent run seems to have taken 47mins compared to 20mins on master, so I think we need to do some more investigating before merging this in.

Looks like we still need to replace chrono in `fuel-client`: https://github.com/FuelLabs/fuel-core/blob/controlc/time/fuel-client/src/client/schema/primitives.rs#L12

Most of this PR is just additional logic for the block producer. I brought in the P&A concepts as I went along because I ran into blockers directly integrating with...

Just pushed a bunch of changes: - No longer using the mpsc channels, using a simpler async trait approach for the block producer instead. - Cleaned up the integ test...

blocked by: https://github.com/FuelLabs/fuel-tx/pull/189

> Look good!=) It is hard to read the integration test, but maybe in the future, we will find how to make it more readable=D I think once the followup...