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
The user should be able to create a new Transaction object and estimate how much gas it will cost to execute the transaction.
Ideally, less information is required to retrieve this information. I'm ill-informed on the variables that go into gas cost. If it's possible, maybe the user only needs to provide the following to a function:
number of orders
whether it's an offer/cancel
pair
To receive an estimate of the gas cost.
The text was updated successfully, but these errors were encountered:
We pushed an update to the repo recently whereby if gas is not passed in the Transaction object then when placing the transaction the gas cost is automatically estimated.
This has the additional benefit of verifying that the transaction would occur successfully on chain.
As such if you are currently passing gas values to transactions you should be able to remove this.
I'm not sure but this may solve what you are talking about above.
However I can also look at exposing the estimate_gas call on a transaction. However, I would need to look into how to do this. Let me know if you want me to look into this
We pushed an update to the repo recently whereby if gas is not passed in the Transaction object then when placing the transaction the gas cost is automatically estimated.
This has the additional benefit of verifying that the transaction would occur successfully on chain.
As such if you are currently passing gas values to transactions you should be able to remove this.
I'm not sure but this may solve what you are talking about above.
However I can also look at exposing the estimate_gas call on a transaction. However, I would need to look into how to do this. Let me know if you want me to look into this
@adamamsmith from my understanding, the goal here would be to expose the estimated gas cost to the user before the transaction is actually executed. that way, they can build more responsive systems that are more gas conscious, correct me if i am wrong @perryascott. today, we ship the transaction before giving the user the chance to check the estimated gas cost.
The user should be able to create a new Transaction object and estimate how much gas it will cost to execute the transaction.
Ideally, less information is required to retrieve this information. I'm ill-informed on the variables that go into gas cost. If it's possible, maybe the user only needs to provide the following to a function:
To receive an estimate of the gas cost.
The text was updated successfully, but these errors were encountered: