Fuels-ts uses 4 queries to fulfill one `get` request

[diyahir]

What this fails to answer is why there needs to be a back and forth between the client and the server, this is just wasted time and bandwidth

I’m assuming the client will not change those values so instead of doing 4 rounds of communication, the server should just perform all of this logic internally and return either an error or the queried value, or add a flag to accept let the server handle everything other than these rounds of validation that the client is potentially doing?

For get fn calls specifically.

`.get()` method calls `dryRun` and `estimateGasPrice`

Is it expected that the .get() requests execute estimateGasPrice and dryRun ? Yes, this is expected. The .get() method internally performs a dryRun, which allows us to retrieve the contract call response without executing a real transaction and incurring costs. The estimateGasPrice step is necessary because, even during a dryRun, the gas and fees must be accurately estimated to ensure proper validation of the call. You can use the multiCall feature to execute multiple contract .get() calls w…