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
During Tech strategy meeting, review nonce management strategy with @ClementWalter
after v0.7.5 fixes, we are still observing strong occurrences of "failed to relay transactions" errors in the RPC. This suggests nonces in the relayer fleet are still subject to falling out of sync a lot, cf:
Where we see in the "logs occurence" dozens of nonce errors.
The text was updated successfully, but these errors were encountered:
In order to reduce the nonce errors, the final decision is to call Starknet each time to get the relayer nonce before sending the transaction and to remove the local nonce handling.
Investigate as well a way to "lock" the relayer for as long as we don't receive Starknet's status of the transaction.
Duration: 3 hours
greged93
changed the title
[URGENT] gemba: review the nonce management strategy for the relayer fleet
[URGENT] gemba: review the nonce management strategy for the relayer fleet [3]
Oct 28, 2024
Describe the enhancement request
During Tech strategy meeting, review nonce management strategy with @ClementWalter
after v0.7.5 fixes, we are still observing strong occurrences of "failed to relay transactions" errors in the RPC. This suggests nonces in the relayer fleet are still subject to falling out of sync a lot, cf:
Where we see in the "logs occurence" dozens of nonce errors.
The text was updated successfully, but these errors were encountered: