Daniel's avatar
Daniel 6 months ago
Incorrect. Nodes broadcast the transactions to the mempool/ miners. That’s the whole point for a node network all running the software in consensus. Think of it this way, when Bitcoin is double spent, or the data of a transaction is too high, it won’t be picked up by then nodes, and broadcasted to the mempool. And it will not be included in the block once it’s mined. Same goes for spam filters. My private instance of the mempool could be vastly different from the public one at .space, because of the filters I’ve set. Some transactions simply don’t exist on my instance because of my parameters. If I was able to mine that block myself, those transactions that I have filtered out will not exist in that block.

Replies (1)

rieger_san's avatar
rieger_san 6 months ago
I can send a transaction directly to a miner or mine transactions myself. So your mempool policy is completely useless! The only thing you will get with such bullshit is that people are sending transactions directly to miners.