There is an issue I have been encountering when two separate sessions are submitting the same transaction at the same time. What happens is that one transaction succeeds but the same hash is returned to both sessions. This is not what I thought would happen. What I think is going on is the same sequence number is being used in both transactions. I still don't understand why one doesn't fail though.
I resolved this issue by adding in a unique ID to the memo field of the transactions. So even if the sequence number is the same, the transactions are different, and one of the transactions will fail for being out of sequence.
I don't know if this is an issue or more of an FYI. I don't have more of a fix aside from using the memo field.
There is an issue I have been encountering when two separate sessions are submitting the same transaction at the same time. What happens is that one transaction succeeds but the same hash is returned to both sessions. This is not what I thought would happen. What I think is going on is the same sequence number is being used in both transactions. I still don't understand why one doesn't fail though.
I resolved this issue by adding in a unique ID to the memo field of the transactions. So even if the sequence number is the same, the transactions are different, and one of the transactions will fail for being out of sequence.
I don't know if this is an issue or more of an FYI. I don't have more of a fix aside from using the memo field.