The network part and the net pool part is not really part of the consensus. So we don't really need to have a shirt and common view that we all agreed upon. It's just like subjective to every node. Given the design of this network, why can't I just send a billion transactions and take this whole thing down? You could send those transactions. But you probably couldn't take the whole thing down because first you are only connected to a limited number of peers. Then these peers, like the transaction is received by them and it goes to this verification pipeline. And we make sure that this verification pipeline first does all the checks that are really cheap to do. This is actually pretty
In this episode, we are joined by Tomasz Drwięga, a Core Developer at Parity Technologies, to discuss the lifecycle of a transaction on the Ethereum network and how the mempool works.
We will be covering the following topics:
- What a mempool/transaction queue/transaction pool is.
- How a transaction reaches a mempool and what the mempool does with it.
- Looking at what causes the CPU increase and delays in the network.
- What happens when a transaction gets stuck.
- Gossip.
- The security properties of the mempool.
- What a network attack could look like.
Here are some additional links and ressources if you want to dig deeper.