Managing nonces when sending high volume of concurrent transactions
This seems like a fairly major issue for developing server-side logic / an API that sends transactions that (I think) remains unresolved after nearly 3 years: https://github.com/ethereum/go-ethereum/issues/2880
Does anyone have a decent solution for sending many transactions from the same address, potentially near concurrently? The best solutions in the thread are just finding ways to try and manually track it, which ultimately desynchronizes when something fails and there is a nonce gap.
Submitted December 31, 2018 at 01:31PM }
via reddit http://bit.ly/2QhMbLH