Closed mfornet closed 3 years ago
This problem is due to the async nature of submitting transactions, since some of them might not be processed in order which is required.
The fix was implemented in #463. Transactions are sent in batches which are guaranteed to be processed in order, and batches are being sent synchronously (one batch is sent after the previous one is applied).
This is a log I see frequently while running the eth2near-relay.
The ethereum client on near is still making progress.