Can Reinforced Transactions Handle Concurrent Transactions?

Written by Killiane Menand

Published on October 9, 20241 min read

---

Reinforced Transactions provide enhanced reliability and speed for sending blockchain transactions, but you might wonder how they handle concurrent transactions - sending multiple transactions before earlier ones are confirmed.

Can I Send Concurrent Transactions Without Issues?

Yes, Reinforced Transactions can support concurrent transactions. However, it’s important to understand that we do not manage nonce assignment. When using Reinforced Transactions, you send fully signed and encoded transaction payloads, including the assigned nonce, via the same eth_sendRawTransaction method you would use in any regular transaction.

How Does It Work with Multiple Transactions?

You can send multiple concurrent transactions with sequential nonces. For example:

1. You send Transaction 1 with nonce X.

2. Before Transaction 1 is confirmed, you send Transaction 2 with nonce X+1.

This process will work as long as the transactions have sequential nonces and are correctly signed and encoded. Reinforced Transactions will ensure that these transactions are propagated and mined efficiently, but managing the nonce is the responsibility of the user.

Why Nonce Management Matters

Nonce management is crucial to ensure that your transactions are processed in the correct order. If you send two transactions with the same nonce (a nonce clash), only one will be accepted, and the other will be rejected. Reinforced Transactions do not manage this aspect; therefore, it’s essential to ensure that each transaction is correctly sequenced with the proper nonce.

Final Thoughts

Reinforced Transactions support concurrent transactions, but you must handle nonce management to avoid clashes. As long as you send sequential nonces, Alchemy will ensure these transactions are efficiently propagated and mined.