What problem does your feature solve?
It is not easy to see the simulated cost of some of the transactions that the CLI generates and submits.
For example, when uploading a contract, there's no easy way to identify what the cost is going to be:
$ stellar contract upload --wasm contract.wasm --build-only \
| stellar tx simulate \
| stellar tx decode \
| jq '.tx.tx.fee'
1379621
What would you like to see?
An easier way to see the fees related to a tx simulation so that cost can be viewed for any operation before submitting.
The stellar contract invoke command has a --cost flag that when included causes cost information to be output to stderr. The same option could be added to stellar tx simulate.
Related
Discussed at https://discord.com/channels/897514728459468821/1533388251350568990/1533388251350568990
What problem does your feature solve?
It is not easy to see the simulated cost of some of the transactions that the CLI generates and submits.
For example, when uploading a contract, there's no easy way to identify what the cost is going to be:
What would you like to see?
An easier way to see the fees related to a tx simulation so that cost can be viewed for any operation before submitting.
The
stellar contract invokecommand has a--costflag that when included causes cost information to be output to stderr. The same option could be added tostellar tx simulate.Related
Discussed at https://discord.com/channels/897514728459468821/1533388251350568990/1533388251350568990