Skip to content

Fix a gas/storage limit check in the client

vbot requested to merge nomadic-labs/tezos:vbot@fix_client_limits into master

Context

When injecting an operation, the client modifies its gas and/or storage usage when the user specifies a gas (resp. storage) that corresponds to the hard_gas_limit_per_operation (resp. hard_storage_limit_per_operation) which would be considered valid by the protocol. This MR fixes this.

Manually testing the MR

  • Make a transfer using the client that declares a gas limit corresponding to the hard_gas_limit_per_operation (usually 1040000)
  • Notice that it is considered valid by the mempool and that the baker accepts it

Merge request reports