Invalid Sequence Error about go-sdk HOT 4 CLOSED

Hi, send the transaction of the same address simultaneously will indeed cause Invalid sequence error.
To defend the replay attack, the sequence of an address should increase in order. But if send transaction too fast(use async/sync) or simultaneously, the previous transaction haven't included in block yet, go-sdk will fetch the current sequence and sign new transaction, cause sequence discontinuous.
Because there is no guarantee the previous transaction will be included in block, so we get account sequence each time before send the transaction instead of increase it automatically.

from go-sdk.

@guagualvcha Is it possible to allow users to assign sequence number for each transaction manually? For applications like market making bot it's fatal to send both bid & ask orders at the same time.

from go-sdk.

make sense. I will submit a PR soon.

from go-sdk.

@touhonoob hi, go-sdk have updated to support custom sequence.
example:

acc,err:=client.GetAccount(client.GetKeyManager().GetAddr().String())
_, err = client.CreateOrder(tradeSymbol, nativeSymbol, msg.OrderSide.BUY, 100000000, 100000000, true, transaction.WithAcNumAndSequence(acc.Number,acc.Sequence))
_, err = client.CreateOrder(tradeSymbol, nativeSymbol, msg.OrderSide.BUY, 100000000, 100000000, true, transaction.WithAcNumAndSequence(acc.Number,acc.Sequence+1))
_, err = client.CreateOrder(tradeSymbol, nativeSymbol, msg.OrderSide.BUY, 100000000, 100000000, true, transaction.WithAcNumAndSequence(acc.Number,acc.Sequence+2))

from go-sdk.