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
The idea is to refactor the bumping mechanism, when a user wants to bump the fee for a proof.
For this in the SDK there should be a function that takes either:
% to bump
amount to bump
new max fee (current implementation
bump to match a batch of size N
This functions should also be callable via the aligned CLI.
After this bump mechanism is working, the previous bumping mechanism should be deprecated, the mechanism of replacement messages; Replacing a same nonce with a highest fee brings all sorts of problems, from the WS connection, to the known limits to max_fee, and the need for the user to know the nonces he sent (which he never does).
The text was updated successfully, but these errors were encountered:
The idea is to refactor the bumping mechanism, when a user wants to bump the fee for a proof.
For this in the SDK there should be a function that takes either:
This functions should also be callable via the aligned CLI.
After this bump mechanism is working, the previous bumping mechanism should be deprecated, the mechanism of replacement messages; Replacing a same nonce with a highest fee brings all sorts of problems, from the WS connection, to the known limits to max_fee, and the need for the user to know the nonces he sent (which he never does).
The text was updated successfully, but these errors were encountered: