|
Title: Every Miner Should be Running Child Pays for Parent Post by: Razick on August 06, 2014, 12:28:25 AM Why isn't child-pays-for-parent the default behavior for miners and pools? Sending low fee transactions is an easy mistake to make, and can be a huge disaster. New users are especially vulnerable since many may have heard that transactions will confirm without fees.
I am currently trying to pay a seller for a purchase that he was nice enough to send before payment. Now though, he can't receive a confirmed payment because I forgot my rarely-used Blockchain.info wallet was set to "frugal" fee mode. This would be so easy to fix if miners would implement child-pays-for-parent, but as it is, it looks like the seller will have to wait 9.4 days (according to an estimate on another thread) to receive payment, which isn't fair to him. There really isn't any reason not to implement CPP. It not only benefits consumers, but also miners since they get fees for otherwise free transactions. Title: Re: Every Miner Should be Running Child Pays for Parent Post by: cloverme on August 08, 2014, 11:16:22 PM I don't understand what you're getting at here... are you talking about passing the fee somehow? Can you give a better example of how this would work in mining?
Title: Re: Every Miner Should be Running Child Pays for Parent Post by: eleuthria on August 08, 2014, 11:30:44 PM I don't understand what you're getting at here... are you talking about passing the fee somehow? Can you give a better example of how this would work in mining? I believe he's referring to a making a second transaction using the inputs of the inadequate fee one (no confirmations), and attaching a large(r) fee to this second transaction in order to get the first one confirmed faster. Which I could have sworn was part of bitcoind's default behavior... Title: Re: Every Miner Should be Running Child Pays for Parent Post by: cloverme on August 08, 2014, 11:45:16 PM I believe he's referring to a making a second transaction using the inputs of the inadequate fee one (no confirmations), and attaching a large(r) fee to this second transaction in order to get the first one confirmed faster. Which I could have sworn was part of bitcoind's default behavior... I think you're right, I thought there was some allowance for that in there as well, but it might not be supported by the particular wallet. I don't fuss with it, I pay the fee and hope that some of it comes back my way in the mining process later ;) Kick the leprechaun today and hope for gold tomorrow |