Every node in network has its own mem pool and it's like this subjective view of all the transactions that they have seen. So we try to never send that transaction twice if we know that that peer already received that transaction from us. We don't really like propagate it back because it doesn't make any questions. Although randomly we also choose peers that we kind of forget that we propagated the transactions to them to just keep the transactions flowing.
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.