New answers tagged


"tx_bad_seq" occurs when the transactions sequence number isn't exactly tx source accounts current sequence number + 1. When a transaction gets submitted successfully the sequence number is consumed and you'll need to calculate (or fetch) the next one. The SDKs normally do that for you with server.loadAccount(). So why does it fail in your case ...

Top 50 recent answers are included