So the node itself, like it's sending local transactions. It's propagating other transactions that it's picking up. And I'm just wondering, is this like, is it pinging at a beat of like this? Is it like fat? That's sort of what I'm trying to get to. Yeah. So, so it's, it's like interval based. Every second we are doing quite a lot of work. We are taking the, the, like the best transactions that we have in a pool. The network is getting more congested and the blockchain is getting bigger. A common misconception of like the CPU increases actually, there's now so much transaction spam.
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.