Broadcast transactions only to a single healthy RPC instead of all #14635
+35
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hedera doesn't have a mempool and has instant finality. Sending the transaction to the first node gets the transaction included so broadcasting to other nodes after leads to nonce too low errors. This normally wouldn't be a problem since these types of errors are usually surfaced upfront by the RPC, but in the case of Hedera, they make it on-chain and the error is only available through receipts which means NOPs have to pay for these transactions.
To avoid this we should only broadcast transactions to a single active RPC.