I have read about CPFP very well, I now understand how it works. The output from the previous transaction which remain on the wallet balance can only be used to make a transaction that will help to make the low fee unconfirmed parent transactions to be confirmed along the child (new) transactions.
Topic: CPFP bitcoin transaction. (Read 221 times)
So that my first transaction will be confirmed at the same time with the second transaction.
-snip-
Yes, the parent and child must be included is the same block if the child has higher fee than the parent.-snip-
Since the child has a high fee but can't be mined without the parent, miners will take the parent in consideration when prioritizing the transaction(s).
Miners will compute the total fee-rate based from the total paid fee and size of the parent & children.
Worth reading: Wiki: Miner fees - CPFP
For CPFP to work... you need to spending one of the outputs of the previous unconfirmed transaction.
Ie.
UnconfirmedTransaction1:
So, you need to be spending the outputs that went to RecipientAddressA or ChangeAddressB in the CPFP transaction... ie the "children" of the transaction... which means you need to be the recipient of the original transaction, or the owner of any change address that was used.
So, with the above scenario, the receiver could setup a CPFP like this:
or the original sender could spend their unconfirmed change like this:
Basically, you can only do CPFP if you have received unconfirmed coins... you cannot use CPFP if you were just the sender and didn't get any change:
In this scenerio... only ReceiverB can do CPFP... as they're the only "child"
Ie.
UnconfirmedTransaction1:
Code:
InputA ---> RecipientAddressA
|-> ChangeAddressB
|-> ChangeAddressB
So, you need to be spending the outputs that went to RecipientAddressA or ChangeAddressB in the CPFP transaction... ie the "children" of the transaction... which means you need to be the recipient of the original transaction, or the owner of any change address that was used.
So, with the above scenario, the receiver could setup a CPFP like this:
Code:
RecipientAddressA ---> OutputX
or the original sender could spend their unconfirmed change like this:
Code:
ChangeAddressB ---> OutputY
Basically, you can only do CPFP if you have received unconfirmed coins... you cannot use CPFP if you were just the sender and didn't get any change:
Code:
SenderA ---> ReceiverB
In this scenerio... only ReceiverB can do CPFP... as they're the only "child"
I have been studying about bitcoin and wallet technically so far, I have already know how to use replace by fee (rbf), it was very simple for me. But I do not get how to use child pay for parent (cpfp). That is why I want to ask the question here, for you people help me out. Maybe I am just getting it wrong.
For instance, if I transfer bitcoin from bitcoin core wallet with a very low amount of fee but the transaction did not get a single confirmation, normally I can use rbf to pump the fee.
But if I want to make another payment to another bitcoin address, if I use higher fee that can make my transaction to be confirmed fast. Is that cpfp? So that my first transaction will be confirmed at the same time with the second transaction.
Or cpfp only work if I transfer bitcoin again to the previous address but with a higher fee that can make both to be confirmed on time?
For instance, if I transfer bitcoin from bitcoin core wallet with a very low amount of fee but the transaction did not get a single confirmation, normally I can use rbf to pump the fee.
But if I want to make another payment to another bitcoin address, if I use higher fee that can make my transaction to be confirmed fast. Is that cpfp? So that my first transaction will be confirmed at the same time with the second transaction.
Or cpfp only work if I transfer bitcoin again to the previous address but with a higher fee that can make both to be confirmed on time?
Jump to: