Are there times where transactions are sent and they're just like actually lost before they hit anything? Like are there cases of that? Oh, yeah, sure. Because either you're propagating that to appear that just goes offline right after it receives that transaction or your transaction fee is too low to get that transaction propagated over the network. And would that just that would just knock it offline for like a little bit? Yeah, I mean, it would probably knock it offline until everyone can sort of take their nodes down and like re-key their identities and get it back up again.
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.