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
if a gap-nonce-tx with same from&auth arrived first time, checkDelegationLimit would return at line-618, because this tx has gaped nonce, it couldn't be executed.
And if I want to replace it, checkDelegationLimit would return ErrOutOfOrderTxFromDelegated because it has no pending
And if I want to fix the gap, because the from & the auth has the same address, checkDelegationLimit would return ErrInflightTxLimitReached?
The text was updated successfully, but these errors were encountered:
rekyyang
changed the title
Does deadlock exist if send a nonce gaped set-code-tx that has the same auth&from?
Does it stuck if send a nonce gaped set-code-tx that has the same auth&from?
Apr 22, 2025
sorry, I test this case and there are some questions I want to ask 🙏
My test case is (disable local tx):
prepare a account A without auth, nonce is 0
send a tx from A, and auth a contract to A, tx nonce is 3, auth nonce is 4 (this tx will be queued)
I can only send nonce 0 1 2 tx to fill the gap ONE BY ONE, but I cannot replace the first nonce 3 gapped auth tx directly
Is it expected? If I send a gaped auth tx with a large gap, I have to wait the tx expire or fill the gap one by one(by the way, I mean I cannot send a bunch of txs to fill the gap one time)
if a gap-nonce-tx with same from&auth arrived first time, checkDelegationLimit would return at line-618, because this tx has gaped nonce, it couldn't be executed.
And if I want to replace it, checkDelegationLimit would return ErrOutOfOrderTxFromDelegated because it has no pending
And if I want to fix the gap, because the from & the auth has the same address, checkDelegationLimit would return ErrInflightTxLimitReached?
The text was updated successfully, but these errors were encountered: