Can I get a transaction out of limbo with a high fee transaction from change?

iram66680

hero member

Activity: 630

Merit: 502

Quote from: ron7684 on October 14, 2015, 10:22:15 PM

So I made a 0.0006 transfer (225 bytes) with a fee of 225 satoshi using Bitcoin Core. The transaction has already been discarded from the blockchain.info mempool and I'd prefer to cancel the transaction anyway.

Will placing a new transaction from the change address with fees high enough to cover both transactions cause miners to pick up both?

Other simple suggestions for deleting the transactions would be appreciated as well. I've tried pywallet but it is appears to be no longer maintained.

What you could have done is to spend the output and thus those miners with CPFP patch would be happy to include the transaction. Even though blockchain.info has pruned your transaction, the majority of the network might have not since it is widely known that blockchain.info can have different rules compared to other clients.

ron7684

member

Activity: 90

Merit: 10

Quote from: achow101 on October 15, 2015, 09:02:03 PM

Quote from: ron7684 on October 15, 2015, 08:56:58 PM

AWESOME DUDE! I have my bitcoins back!

Good for you! Now send your transaction again with a high enough fee so this doesn't happen.

Or not at all, it was going to Hashnet but that shit closed down

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: ron7684 on October 15, 2015, 08:56:58 PM

AWESOME DUDE! I have my bitcoins back!

Good for you! Now send your transaction again with a high enough fee so this doesn't happen.

ron7684

member

Activity: 90

Merit: 10

Quote from: shorena on October 15, 2015, 02:04:25 AM

Quote from: ron7684 on October 14, 2015, 10:22:15 PM

So I made a 0.0006 transfer (225 bytes) with a fee of 225 satoshi using Bitcoin Core. The transaction has already been discarded from the blockchain.info mempool and I'd prefer to cancel the transaction anyway.

Will placing a new transaction from the change address with fees high enough to cover both transactions cause miners to pick up both?

Other simple suggestions for deleting the transactions would be appreciated as well. I've tried pywallet but it is appears to be no longer maintained.

Adding another TX that spends the change from the first will do nothing if the 1st TX is not widely known in the network.

To remove the old unconfirmed TX, launch core with -zapwallettxes

AWESOME DUDE! I have my bitcoins back!

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: ron7684 on October 15, 2015, 05:26:35 PM

Quote from: achow101 on October 15, 2015, 03:45:29 PM

Quote from: ron7684 on October 14, 2015, 10:22:15 PM

So I made a 0.0006 transfer (225 bytes) with a fee of 225 satoshi using Bitcoin Core. The transaction has already been discarded from the blockchain.info mempool and I'd prefer to cancel the transaction anyway.

Will placing a new transaction from the change address with fees high enough to cover both transactions cause miners to pick up both?

Yes, but only with some miners, like eligius. This is called Child Pays For Parent. You must have fees to cover both transactions and it should be sent directly through eligius's pool using their pushtx page. Also, don't send the transaction for something important like a payment but send it to yourself since it may not get confirmed.

This is what I had in mind when I asked. Cool to see that someone is taking care of it.

Are you going to be attempting a CPFP transaction or are you just waiting for it to be dropped? If you are waiting for it to be dropped, you need to close Bitcoin Core and remove the transaction so it doesn't keep broadcasting it.

ron7684

member

Activity: 90

Merit: 10

Quote from: shorena on October 15, 2015, 02:04:25 AM

Quote from: ron7684 on October 14, 2015, 10:22:15 PM

So I made a 0.0006 transfer (225 bytes) with a fee of 225 satoshi using Bitcoin Core. The transaction has already been discarded from the blockchain.info mempool and I'd prefer to cancel the transaction anyway.

Will placing a new transaction from the change address with fees high enough to cover both transactions cause miners to pick up both?

Other simple suggestions for deleting the transactions would be appreciated as well. I've tried pywallet but it is appears to be no longer maintained.

Adding another TX that spends the change from the first will do nothing if the 1st TX is not widely known in the network.

To remove the old unconfirmed TX, launch core with -zapwallettxes

I will try this as soon as my current TXs confirm

ron7684

member

Activity: 90

Merit: 10

Quote from: achow101 on October 15, 2015, 03:45:29 PM

Quote from: ron7684 on October 14, 2015, 10:22:15 PM

So I made a 0.0006 transfer (225 bytes) with a fee of 225 satoshi using Bitcoin Core. The transaction has already been discarded from the blockchain.info mempool and I'd prefer to cancel the transaction anyway.

Will placing a new transaction from the change address with fees high enough to cover both transactions cause miners to pick up both?

Yes, but only with some miners, like eligius. This is called Child Pays For Parent. You must have fees to cover both transactions and it should be sent directly through eligius's pool using their pushtx page. Also, don't send the transaction for something important like a payment but send it to yourself since it may not get confirmed.

This is what I had in mind when I asked. Cool to see that someone is taking care of it.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: ron7684 on October 14, 2015, 10:22:15 PM

So I made a 0.0006 transfer (225 bytes) with a fee of 225 satoshi using Bitcoin Core. The transaction has already been discarded from the blockchain.info mempool and I'd prefer to cancel the transaction anyway.

Will placing a new transaction from the change address with fees high enough to cover both transactions cause miners to pick up both?

Yes, but only with some miners, like eligius. This is called Child Pays For Parent. You must have fees to cover both transactions and it should be sent directly through eligius's pool using their pushtx page. Also, don't send the transaction for something important like a payment but send it to yourself since it may not get confirmed.

unholycactus

legendary

Activity: 1078

Merit: 1024

If I understand correctly how it works, the first transaction needs to be confirmed for the second to be as well.
It doesn't matter if you send another transaction using the change address, even with a high fee.
It should confirm the second one, but the first one will still be pending. All funds will be unconfirmed.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: ron7684 on October 14, 2015, 10:22:15 PM

So I made a 0.0006 transfer (225 bytes) with a fee of 225 satoshi using Bitcoin Core. The transaction has already been discarded from the blockchain.info mempool and I'd prefer to cancel the transaction anyway.

Will placing a new transaction from the change address with fees high enough to cover both transactions cause miners to pick up both?

Other simple suggestions for deleting the transactions would be appreciated as well. I've tried pywallet but it is appears to be no longer maintained.

Adding another TX that spends the change from the first will do nothing if the 1st TX is not widely known in the network.

To remove the old unconfirmed TX, launch core with -zapwallettxes

ron7684

member

Activity: 90

Merit: 10

So I made a 0.0006 transfer (225 bytes) with a fee of 225 satoshi using Bitcoin Core. The transaction has already been discarded from the blockchain.info mempool and I'd prefer to cancel the transaction anyway.

Will placing a new transaction from the change address with fees high enough to cover both transactions cause miners to pick up both?

Other simple suggestions for deleting the transactions would be appreciated as well. I've tried pywallet but it is appears to be no longer maintained.

Topic: Can I get a transaction out of limbo with a high fee transaction from change? (Read 1167 times)