donch wrote:Aren't random and deterministic terms with opposite meanings?
It's "random" only in the sense that it's not predictable by those submitting the transactions and should be thought of as effectively random from their point of view. As you know, once the servers decide on the unordered set of transactions that will be included in the next ledger they all deterministically order them the same (e.g. possibly by the hash of the transaction).
Note that if someone submits two transactions for different accounts (so sequence number of a single account isn't an issue) to the same server then, even if there is an deterministic ordering for the pair if they get into the same ledger
, I think it's possible (but rare) that one might be pushed back to the next ledger (say for some reason it doesn't get relayed to sufficient validators in time to be included or something) causing them to be processed in the "opposite order" in separate ledgers. In other words, I think it's a mistake for users to rely on any
ordering for multiple inflight transactions with the sole exception being those from the same account with sequential sequence numbers.