Mårten Blankfors

> I think we can merge it without benchmarks=) Wonderful, let's get the multi-get merged first and follow up with this one afterwards https://github.com/FuelLabs/fuel-core/pull/2396

Retargeted this PR to `master` since the multi-get PR is on hold for now.

Still waiting

These errors seem related so I'm not opening separate issues for them right now: ``` SIGABRT [ 9.128s] fuel-core-tests::integration_tests recovery::gas_price_updater__if_no_metadata_history_start_from_current_block --- STDOUT: fuel-core-tests::integration_tests recovery::gas_price_updater__if_no_metadata_history_start_from_current_block --- running 1 test Stopping fuel...

I like the idea of the separate trait as a starting point because it would allow us to migrate implementations of this trait to any new solution one by one,...

> Initially, the idea was to remove all complex queries from fuel-core and make it part of the indexer's responsibility. But the SDK is deeply integrated with these basic queries,...

> Perhaps we should consider feature gating more complex queries so that node operators can choose to support them or not. This would allow node operators to opt for running...

Wonderful to see this! If there's any help, we created a localnet guide for the MPC contract at https://github.com/near/mpc/blob/main/docs/localnet/localnet.md - it's very MPC specific but does show how to deploy...

> Now everything is cached one by one but there is an issue that I'm having hard time to find a solution. When we successfully had the header but never...

Note that this is a pretty substantial refactor, but it makes a lot of sense to support constructing transactions without redundant node interactions.