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 users have to manually run account.estimateFee before doing account.invoke and explicitly set maxFee as an option of the invoke. Ideally this would be done implicitly, by internally calling fee estimation, and multiplying it with a factor (see which factor others use).
This would be a breaking change since currently the maxFee is implicitly 0 by default.
The text was updated successfully, but these errors were encountered:
Currently users have to manually run
account.estimateFee
before doingaccount.invoke
and explicitly set maxFee as an option of the invoke. Ideally this would be done implicitly, by internally calling fee estimation, and multiplying it with a factor (see which factor others use).This would be a breaking change since currently the maxFee is implicitly 0 by default.
The text was updated successfully, but these errors were encountered: