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, in order to choose a value for gas_limit a UI would first dry-run the extrinsic via state_call and use the resulting ContractResult::gas_required as a parameter to the actual extrinsic.
Now that weights are two dimensional and also include proof_size, we should add that to the ContractResult in order for UIs to correctly populate that value, without having to manually supply a value.
Currently, in order to choose a value for
gas_limita UI would first dry-run the extrinsic viastate_calland use the resultingContractResult::gas_requiredas a parameter to the actual extrinsic.Now that weights are two dimensional and also include
proof_size, we should add that to theContractResultin order for UIs to correctly populate that value, without having to manually supply a value.Rel paritytech/subxt#679