mirror of
https://github.com/tendermint/tendermint.git
synced 2026-01-08 06:15:33 +00:00
lint: add markdown linter (#5254)
This commit is contained in:
@@ -12,31 +12,34 @@ arrived (via RPC or from other nodes).
|
||||
So the only way to specify the order is to send them to a single node.
|
||||
|
||||
valA:
|
||||
- tx1
|
||||
- tx2
|
||||
- tx3
|
||||
|
||||
- tx1
|
||||
- tx2
|
||||
- tx3
|
||||
|
||||
If the transactions are split up across different nodes, there's no way to
|
||||
ensure they are processed in the expected order.
|
||||
|
||||
valA:
|
||||
- tx1
|
||||
- tx2
|
||||
|
||||
- tx1
|
||||
- tx2
|
||||
|
||||
valB:
|
||||
- tx3
|
||||
|
||||
- tx3
|
||||
|
||||
If valB is the proposer, the order might be:
|
||||
|
||||
- tx3
|
||||
- tx1
|
||||
- tx2
|
||||
- tx3
|
||||
- tx1
|
||||
- tx2
|
||||
|
||||
If valA is the proposer, the order might be:
|
||||
|
||||
- tx1
|
||||
- tx2
|
||||
- tx3
|
||||
- tx1
|
||||
- tx2
|
||||
- tx3
|
||||
|
||||
That said, if the transactions contain some internal value, like an
|
||||
order/nonce/sequence number, the application can reject transactions that are
|
||||
|
||||
Reference in New Issue
Block a user