Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[URGENT] gemba: review the nonce management strategy for the relayer fleet [3] #1502

Open
Eikix opened this issue Oct 27, 2024 · 1 comment
Labels
enhancement Enhancement of the code, not introducing new features.

Comments

@Eikix
Copy link
Member

Eikix commented Oct 27, 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:
image
Where we see in the "logs occurence" dozens of nonce errors.

@Eikix Eikix added the enhancement Enhancement of the code, not introducing new features. label Oct 27, 2024
@greged93
Copy link
Collaborator

greged93 commented Oct 28, 2024

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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement of the code, not introducing new features.
Projects
Status: 🔖 Current sprint
Development

No branches or pull requests

2 participants