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
Currently, when you run cargo stylus deploy --estimate-gas --private-key $PVT_KEY, the last log shows deploy gas estimate: 30989288 gas. While this is useful, the user would have to take additional steps and time to know if they have sufficient funds for deployment / get the actual cost of deployment.
Proposed Solution
It would be very convenient to have this displayed alongside an estimated_gas_fee (similar to how Metamask shows you the fee costs directly when estimating gas). If there was some additional log output that could fetch the current gas price and display an estimated amount in ETH, it makes it easy for the user to determine if they would like to deploy under current network conditions.
Benefits
Saves the user some steps/time, gives them confidence in the costs, and prevents users from having a poor experience if there is a spike in gas prices prior to deployment which may result in failed deployments, lost fees, etc.
The text was updated successfully, but these errors were encountered:
Problem
Currently, when you run
cargo stylus deploy --estimate-gas --private-key $PVT_KEY
, the last log showsdeploy gas estimate: 30989288 gas
. While this is useful, the user would have to take additional steps and time to know if they have sufficient funds for deployment / get the actual cost of deployment.Proposed Solution
It would be very convenient to have this displayed alongside an
estimated_gas_fee
(similar to how Metamask shows you the fee costs directly when estimating gas). If there was some additional log output that could fetch the current gas price and display an estimated amount in ETH, it makes it easy for the user to determine if they would like to deploy under current network conditions.Benefits
Saves the user some steps/time, gives them confidence in the costs, and prevents users from having a poor experience if there is a spike in gas prices prior to deployment which may result in failed deployments, lost fees, etc.
The text was updated successfully, but these errors were encountered: