|
Title: question about optional "-maxorphantx" Post by: lovecodelc on September 30, 2016, 11:00:17 AM Hi,all.
i have a question about optional "maxorphantx", when a transaction arrives, full node will verify it and put it into mempool if valid, if count of transactions in mempool is up to maxorphantx value ,the code will "sweep out expired orphan pool entries" or "evict a random orphan". Is there any possibility that "such transaction" will be obsoleted when all full node' mempool's maxorphantx values arrives max? if it happens, the block cannot record "such transaction" because it not in all full node' mempool. Thank you. Title: Re: question about optional "-maxorphantx" Post by: DannyHamilton on September 30, 2016, 12:53:42 PM if it happens, the block cannot record "such transaction" because it not in all full node' mempool. Solo miners and mining pools run nodes. If ALL nodes (including the sender, the receiver, and ALL miners) have dropped the transaction from their mempool, then the transaction will never confirm (unless someone rebroadcasts the transaction). If a solo miner or mining pool keeps the transaction in their mempool, that miner (or pool) can confirm the transaction into a block. The rest of the nodes will receive the transaction when they receive the block. |