Ethereum update: 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](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.
Ethereum is a decentralized platform that runs smart contracts: applications that run exactly as programmed without any possibility of downtime, censorship, fraud or third-party interference.
Don’t forget to share the post if you love it !