We are going through this verification pipeline. It's all those checks plus the fact that even if you were to try to amount to a successful attack in this way, you are only attacking your Parete. And by that time, you're not attacking the first set anymore. So it would be annoying for those that you're sending shit to, but you wouldn't take down the network because you would have to move on and take down the next set. Yeah. That's actually one of the first checks that we are doing.
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.