The precise formula is like X over square root of X if I remember correctly. A node transaction gets priority because, sorry, a local transaction gets priority in your own client. So that's the first thing that goes out. Then it goes to a random number of people, but arandom number of nodes. How many? If you have like 10,000 peers, it would be 1000 peers. It's just like politeness and preventing network contention.
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.