-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fee informations #1721
Comments
I think the user should eventually define the gas and fees (amount + coin denomination) by herself and also provide the option in the settings to define a default gas and fee |
cc: @alessio what's the cmd/parameter to estimate the gas cost ? |
The flag If you use |
absolutely - we need to do a better job of communicating gas and fees! |
After the discussion in the sdk channel, I think gas is not relevant to our end users. Clients (voyager) could run a simulation previously and check the estimated gas used and set that value on the gas field. Regarding fees, imo we should eventually define an input field within the txs modals (Deposit, Vote, Delegate, etc) and have a custom value set as default on the preferences/settings page that's pre-filled on the modals |
Proposal: |
Scope:
|
|
I am not sure we can identify this. Transactions will go to the mempool ready to be claimed by a block proposer and will only after several blocks be dropped. I propose we do 4. in another iteration |
moved to #2238 |
UI Version: 0.X.X
Description:
For a user is a bit hard to understand that he's paying Gas for transactions and to retrive this information later. It would be nice to have in the Voting, Depsit and Transaction actions and show it in a confirmation box: The fee of this operation is X
The text was updated successfully, but these errors were encountered: