3 ms·
> the nodes will just reject your transaction if you don't follow the dumb protocol Calling things dumb doesn't help your argument at all. It should reject you
by latchkey 3y ago
> the nodes will just reject your transaction if you don't follow the dumb protocol
Calling things dumb doesn't help your argument at all. It should reject your transaction if you don't follow the rules.
> Except if there's congestion, and the base fee isn't enough so you get your transaction rejected
Subtle, but important point: The transaction isn't rejected. It is not picked up out of the mempool and sits there until the congestion goes down. Again, this is supply/demand pricing and that's ok in a system like this.
> Many things in Ethereum stops working well
This is handwaving without actual examples.
- littlestymaar 3y ago> Subtle, but important point: The transaction isn't rejected. It is not picked up out of the mempool and sits there until the congestion goes down. Not if you submit another transaction in the meantime, because then your initial transaction's nonce will have become invalid. Now you start to get why I called the nonce system “dumb”, because it has emergent implications with lots of things like this, for no good reason (the requirement should be nonce's uniqueness, that's enough for transaction deduplication, but they felt smart and added the “monotonically increasing” as well, and boom, concurrent transaction processing is a nightmare now, well done).