[Idea] createNonceManager with Redis

[Songkeys]

With today's implementation, the nonceManager won't work as expected when in multiple server instances that relies on redis or an external database to share the current value of nonce.

While currently developers can implement the createNonceManager themselves, I think we could expose the configuration of consume, increment, get and reset methods?

Also a built-in redis interface that only requires to pass in a redis instance would be great as well.

[jxom]

Check out the source parameter: https://viem.sh/docs/accounts/createNonceManager#source

[Songkeys]

I think the source only works on one server because the in-memeory map is not sharable across machines?

[jxom]

The purpose of that is to manage the delta while the retrieval of the nonce is in flight (which may happen when functions are executed in the same event loop). It also reset after the source retrieval is finalized.
This is really to manage the case when executing transactions across an event loop on the client.
You’d face issues regardless of the source you use if you executed transactions on the same event loop on a server, since it would take more time to replicate the source on the external database/store. So it is recommended to execute transactions sequentially (ie. don’t use Promise.all) on the server (while using some Redis source for the nonce manager).

[Songkeys]

Yes. I got you. I meant if we have multiple servers using redis to store the nonce, the current implementation won't work as expected.

For example:

• Current nonce is 1.
• 2 requests are coming at the same time. The load balancer distributes them to server A and server B at the same time.
• These two servers retrieve the current nonce from redis, found that it's 1.
• Both servers increments them locally using map to 2 and use this nonce value to call the action, which will cause transaction replacement.

I think in this case the increment method should call INCR in redis, rather than a local variable that is not able to share across machines.

[jxom]

Happy to expose increment on the API and see how it goes!

[DIYgod]

We are experiencing the same issue. Is there an estimated completion time or any progress for the increment API? @jxom