Unconfirmed Transaction - DELAY - SOLVED - - page 2.

brianddk

jr. member

Activity: 47

Merit: 16

Quote from: BitNow on July 31, 2015, 01:40:26 PM

There is not a "delete transaction" command in the Bitcoin Core Wallet.

There is a "delete-all-TX" (-zapwallettxes) but that does not delete the TX from people who have already received it.

This is not a bug... it is designed into the protocol so that a sent transaction cannot be unsent (aka "no-chargeback").

You should read the thread: https://bitcointalksearch.org/topic/faq-all-about-unconfirmed-0-confirmation-transaction-fee-read-before-posting-232979 and listen the audio stream I linked at the end of it.

BitNow

legendary

Activity: 1260

Merit: 1003

Quote from: achow101 on July 31, 2015, 01:37:09 PM

You could also do the standard delete transaction from wallet and wait a few days but that will take a few days.

There is not a "delete transaction" command in the Bitcoin Core Wallet.

BitNow

legendary

Activity: 1260

Merit: 1003

Quote from: brianddk on July 31, 2015, 01:32:54 PM

If you want to redo the transaction with higher fees, you need to shutdown your wallet app, or all your wallet apps if you have imported your keys on multiple apps.

Once the effected wallets are off, you need to do a bit of wallet surgery to purge the TX from the TX database of your wallet.

Then wait 2-3 days checking all the block explorers for your transaction to get ejected from the pool.

Then boot up your wallet, craft your transaction and resend.

This (wait... wait... wait... resend) is what most people do.

Good information in the "READ THIS FIRST" thread: https://bitcointalksearch.org/topic/faq-all-about-unconfirmed-0-confirmation-transaction-fee-read-before-posting-232979

I saw this thread. Thank You.

The fact that the (allowhighfees) parameter, in the

Code:

sendrawtransaction "hexstring" (allowhighfees)

command is new in Bitcoin Core 0.11.0 make me thinking that now is possible to re-send transactions with higher fees without doing all the things you suggested to do.

Instead doing all the thing you suggested me to do I prefer to wait... wait... wait... until the transaction gets confirmed and ask the receiver to send the money back to me.

Normal people don't do all the stuffs that you asked me to do.

I'll try to stay normal for the time being.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: BitNow on July 31, 2015, 01:20:00 PM

Is it possible to re-send the transaction with higher fees?

If yes, how is it possible to re-send the transaction with higher fees?

yes, but it is going to take longer than either waiting for a confirmation or asking brianddk to help you with CPFP. You could try doing RBF which is Replace By Fee, but very few nodes and miners implement that. Much less than CPFP. With CPFP, you will need to wait for Eligius to mine a block with your transaction. I don't know of any miner that does RBF yet. You could also do the standard delete transaction from wallet and wait a few days but that will take a few days.

brianddk

jr. member

Activity: 47

Merit: 16

Quote from: BitNow on July 31, 2015, 01:20:00 PM

Is it possible to re-send the transaction with higher fees?

If you want to redo the transaction with higher fees, you need to shutdown your wallet app, or all your wallet apps if you have imported your keys on multiple apps.

Once the effected wallets are off, you need to do a bit of wallet surgery to purge the TX from the TX database of your wallet.

Then wait 2-3 days checking all the block explorers for your transaction to get ejected from the pool.

Then boot up your wallet, craft your transaction and resend.

This (wait... wait... wait... resend) is what most people do.

Good information in the "READ THIS FIRST" thread: https://bitcointalksearch.org/topic/faq-all-about-unconfirmed-0-confirmation-transaction-fee-read-before-posting-232979

BitNow

legendary

Activity: 1260

Merit: 1003

Quote from: shorena on July 31, 2015, 01:01:42 PM

Help -> Debug window -> console -> enter gettransaction TXID and confirm with enter -> copy the long hex code -> sendrawtransaction HEX_CODE and confirm w/ enter You might however be annoying to other nodes and end up on their blocklist is you do this too often.

This is the help of the ssendrawtransaction command:

Code:

sendrawtransaction "hexstring" (allowhighfees)

Is it possible to re-send the transaction with higher fees?

If yes, how is it possible to re-send the transaction with higher fees?

I don't want to rebroadcast without knowing if that can be done or now, I don't want to put useless noise on the network.

Quote from: brianddk on July 31, 2015, 01:11:53 PM

Sure... I can sweep the TX with a CPFP.... Which is the address you were sending to?

Give me a minute I will try to re-send the transaction with higher fees to see if that solve the problem.

I will give you the TX if that didn't work.

Thank you for the help by then.

brianddk

jr. member

Activity: 47

Merit: 16

Sure... I can sweep the TX with a CPFP.... Which is the address you were sending to?

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: BitNow on July 31, 2015, 11:19:59 AM

There is a way of forcing a transaction broadcast without having to wait the 30 minutes Bitcoin Core period?

I've posted the same question here:
https://bitcointalksearch.org/topic/howto-use-pybitcointools-to-make-cpfp-transaction-with-tip-to-bounty-1126665
and here:
https://bitcointalksearch.org/topic/bitcoin-rpc-based-cpfp-script-1122324

Help -> Debug window -> console -> enter gettransaction TXID and confirm with enter -> copy the long hex code -> sendrawtransaction HEX_CODE and confirm w/ enter You might however be annoying to other nodes and end up on their blocklist is you do this too often.

BitNow

legendary

Activity: 1260

Merit: 1003

There is a way of forcing a transaction broadcast without having to wait the 30 minutes Bitcoin Core period?

I've posted the same question here:
https://bitcointalksearch.org/topic/howto-use-pybitcointools-to-make-cpfp-transaction-with-tip-to-bounty-1126665
and here:
https://bitcointalksearch.org/topic/bitcoin-rpc-based-cpfp-script-1122324

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: BitNow on July 31, 2015, 11:11:29 AM

Quote from: achow101 on July 31, 2015, 10:59:18 AM

You need to wait for smart fee to initialize. It even told you so. Smart fee looks at fees from recent transactions and blocks so it needs to see those transactions and blocks before it can create a good estimate for a fee. Next time, you can either leave Bitcoin Core open or wait for smart fee to initialize before sending any Bitcoin.

I've used Bitcoin Core 0.11.0 since 07/26/1015 and it only initialize Smart Fee yesterday?

Seems strange that it took 4 days to initialize smart fee.

I have it open 4/6 hours a day in those 4 days.

It probably only started initializing when you selected the option to use smart fee. Otherwise it would just be a waste of resources.

BitNow

legendary

Activity: 1260

Merit: 1003

Quote from: achow101 on July 31, 2015, 10:59:18 AM

You need to wait for smart fee to initialize. It even told you so. Smart fee looks at fees from recent transactions and blocks so it needs to see those transactions and blocks before it can create a good estimate for a fee. Next time, you can either leave Bitcoin Core open or wait for smart fee to initialize before sending any Bitcoin.

I've used Bitcoin Core 0.11.0 since 07/26/1015 and it only initialized Smart Fee yesterday?

Seems strange that it took 4 days to initialize smart fee.

I have it open 4/6 hours a day in those 4 days.

Quote from: achow101 on July 31, 2015, 10:59:18 AM

To fix this, if you have change from that transaction, you can try a CPFP transaction. This is another transaction that spends the outputs of the first transaction but has a higher fee so that the fee covers both transaction's fees. You can ask this user https://bitcointalksearch.org/user/brianddk-538273, brianddk, for help doing this.

I'm looking into it.

Thanks.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

It needs a while to analyze the blocks. You can avoid this if you let it be for a while before you create a TX. When the "Smart fee not initialized yet" warning is gone the estimate should be accurate.

~~There is no reasonable way to speed this up.~~ You could try to create a double spend, but I doubt it would improve the situation. Keep the client open so your TX gets rebroadcasted and it will confirm eventually.

Edit: CPFP might actually improve the situation, Im not up to speed how common this is among miners.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

You need to wait for smart fee to initialize. It even told you so. Smart fee looks at fees from recent transactions and blocks so it needs to see those transactions and blocks before it can create a good estimate for a fee. Next time, you can either leave Bitcoin Core open or wait for smart fee to initialize before sending any Bitcoin.

To fix this, if you have change from that transaction, you can try a CPFP transaction. This is another transaction that spends the outputs of the first transaction but has a higher fee so that the fee covers both transaction's fees. You can ask this user https://bitcointalksearch.org/user/brianddk-538273, brianddk, for help doing this.

BitNow

legendary

Activity: 1260

Merit: 1003

Good afternoon,
yesterday I sent a transaction with this transaction fee configuration:

"(Smart fee not initialized yet. This usually takes a few blocks...)"

I thought it was the fastest way to send a transaction but the transaction after 24 hours hasn't confirmed yet.

This morning I've checked again my Bitcoin Wallet at it says:

"Estimated to begin confirmation within 1 block."

What has it changed?!?

I've downloaded Bitcoin Core 0.11.0 on Monday and since then I've sent with fixed transaction fee of BTC0.00050 but yesterday I send BTC0.20000 and decided to use the "Smart fee" feature of the Bitcoin Core Wallet.
Transaction: https://blockchain.info/tx/24e04b9b5913cd6aed0db212db18c35e2115e05e0124a2ba4d1e273f81719fcb
Transaction fee: BTC0.00000373
Estimated Confirmation Time: Within 6 Blocks (Medium Priority)

When I sent the transaction the low transaction fee I thought was a new feature of the Bitcoin Core 0.11.0 I was wrong, the transaction fee was not initialised.

Is there something I can do to resend the unconfirmed transaction or is there something I can do to not make this thing ever happens again?

Thank you for the reply you will or you will not gave me.

Thanks.

Topic: Unconfirmed Transaction - DELAY - SOLVED - - page 2. (Read 3204 times)