You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Fuel Wallet, the user is allowed to pass a custom gas limit at tx approval. Using this new gas limit, it will then calculate the fee. Should this fee be greater than that set initially against the transaction request, it estimates and funds the entire transaction (via getTransactionCost). Source.
Within this flow, the SDK is fetching the gas price twice:
Once for fee calculation
And again to estimate and fund the transaction
If we allow passing of gasPrice at getTransactionCost we can reduce the redundant gas price call. This is already being done in estimateTxGasAndFee for the same reason.
In the Fuel Wallet, the user is allowed to pass a custom gas limit at tx approval. Using this new gas limit, it will then calculate the fee. Should this fee be greater than that set initially against the transaction request, it estimates and funds the entire transaction (via
getTransactionCost
). Source.Within this flow, the SDK is fetching the gas price twice:
If we allow passing of
gasPrice
atgetTransactionCost
we can reduce the redundant gas price call. This is already being done inestimateTxGasAndFee
for the same reason.The text was updated successfully, but these errors were encountered: