~18 hours with recommended fee's, still no confirmation :(

alani123

legendary

Activity: 2422

Merit: 1451

Leading Crypto Sports Betting & Casino Platform

Quote from: shorena on March 01, 2016, 04:01:39 PM

Quote from: papa_face on March 01, 2016, 07:23:10 AM

Quote from: shorena on March 01, 2016, 04:24:46 AM

The double spend[1] is confirmed. You may want to use the fee estimate by core and make sure its ready to avoid these issues in the future. It shows a small text warning when its not ready, in this case wait a few more blocks.

[1] https://blockchain.info/tx/e2ffaf2034f8124904ef9441d32b8ded98dc7b56cff732208a1aa9e35d45a612

Thanks
Will the original two transactions be removed from the mempool and the double spend message be removed?

~~If they are not removed and showing as "conflicted" you need to remove them with -zapwallettxes. From what I read above you did this already though~~

Nevermind I just understood that you are talking about the message on e.g. blockchain.info. Yes, this message will only be shown for some time and be gone after that. I dont know the exact time, but not longer than a few days.

Already removed. Quote from the linked transactions in blockchain.info

Quote

Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: papa_face on March 01, 2016, 07:23:10 AM

Quote from: shorena on March 01, 2016, 04:24:46 AM

The double spend[1] is confirmed. You may want to use the fee estimate by core and make sure its ready to avoid these issues in the future. It shows a small text warning when its not ready, in this case wait a few more blocks.

[1] https://blockchain.info/tx/e2ffaf2034f8124904ef9441d32b8ded98dc7b56cff732208a1aa9e35d45a612

Thanks
Will the original two transactions be removed from the mempool and the double spend message be removed?

~~If they are not removed and showing as "conflicted" you need to remove them with -zapwallettxes. From what I read above you did this already though~~

Nevermind I just understood that you are talking about the message on e.g. blockchain.info. Yes, this message will only be shown for some time and be gone after that. I dont know the exact time, but not longer than a few days.

slcjohndoe

newbie

Activity: 3

Merit: 0

FYI- running "C:\Program Files\Bitcoin\bitcoin-qt.exe -zapwallettxes" (to clear the unconfirmed transactions) and them resubmitting them to the same wallet address with a higher transaction fee resolved this issue for me.

papa_face

member

Activity: 114

Merit: 10

Quote from: shorena on March 01, 2016, 04:24:46 AM

The double spend[1] is confirmed. You may want to use the fee estimate by core and make sure its ready to avoid these issues in the future. It shows a small text warning when its not ready, in this case wait a few more blocks.

[1] https://blockchain.info/tx/e2ffaf2034f8124904ef9441d32b8ded98dc7b56cff732208a1aa9e35d45a612

Thanks
Will the original two transactions be removed from the mempool and the double spend message be removed?

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

The double spend[1] is confirmed. You may want to use the fee estimate by core and make sure its ready to avoid these issues in the future. It shows a small text warning when its not ready, in this case wait a few more blocks.

[1] https://blockchain.info/tx/e2ffaf2034f8124904ef9441d32b8ded98dc7b56cff732208a1aa9e35d45a612

--Encrypted--

copper member

Activity: 924

Merit: 1007

hee-ho.

Quote from: papa_face on February 29, 2016, 02:53:49 PM

Thanks. I heard you can try to resend with a higher fee and it'll process the original and reject the 2nd attempt, is that correct or have I misunderstood?

well, it's called a race attack (a kind of double spend) so either one can be processed with right condition. you can successfully double spend if you have some help from a node and/or a miner.

Quote from: papa_face on February 29, 2016, 02:53:49 PM

Oh and how can I check if the network has dropped the transaction?

check blockchain.info and other block explorers for your tx. if they're not there then your tx is no longer in their mempool. then you can broadcast a new transaction to their node using the same inputs.

papa_face

member

Activity: 114

Merit: 10

Quote from: --Encrypted-- on February 29, 2016, 02:51:27 PM

Quote from: papa_face on February 29, 2016, 02:14:31 PM

Quote from: --Encrypted-- on February 29, 2016, 01:58:20 PM

Quote from: papa_face on February 29, 2016, 01:53:18 PM

It's weird, the 2nd transaction is high priority but I haven't changed anything....

that's because the priority is calculated from the amount of bitcoin sent and input age and transaction size. so an unconfirmed tx gets more priority as the input gets more confirmation (more old).

Thanks.c
Ok my wallet has reloaded and the two transactions have disappeared and my available balance has gone back up, what happens now lol.
Should I re-send or...

not now. it won't work because it'll be rejected as double spend. wait for the mempool to drop your tx completely before resending bitcoins using the same inputs as those transactions. this may take up to 3 days.

Thanks. I heard you can try to resend with a higher fee and it'll process the original and reject the 2nd attempt, is that correct or have I misunderstood?
Oh and how can I check if the network has dropped the transaction?

--Encrypted--

copper member

Activity: 924

Merit: 1007

hee-ho.

Quote from: papa_face on February 29, 2016, 02:14:31 PM

Quote from: --Encrypted-- on February 29, 2016, 01:58:20 PM

Quote from: papa_face on February 29, 2016, 01:53:18 PM

It's weird, the 2nd transaction is high priority but I haven't changed anything....

that's because the priority is calculated from the amount of bitcoin sent and input age and transaction size. so an unconfirmed tx gets more priority as the input gets more confirmation (more old).

Thanks.c
Ok my wallet has reloaded and the two transactions have disappeared and my available balance has gone back up, what happens now lol.
Should I re-send or...

not now. it won't work because it'll be rejected as double spend. wait for the mempool to drop your tx completely before resending bitcoins using the same inputs as those transactions. this may take up to 3 days.

papa_face

member

Activity: 114

Merit: 10

Quote from: --Encrypted-- on February 29, 2016, 01:58:20 PM

Quote from: papa_face on February 29, 2016, 01:53:18 PM

It's weird, the 2nd transaction is high priority but I haven't changed anything....

that's because the priority is calculated from the amount of bitcoin sent and input age and transaction size. so an unconfirmed tx gets more priority as the input gets more confirmation (more old).

Thanks.c
Ok my wallet has reloaded and the two transactions have disappeared and my available balance has gone back up, what happens now lol.
Should I re-send or...

wantjokull

sr. member

Activity: 700

Merit: 275

Quote from: watashi-kokoto on February 29, 2016, 08:45:20 AM

Quote from: papa_face on February 29, 2016, 03:33:31 AM

They seem to be taking forever to get confirmed. I always send using the recommended fee in bitcoin core.

Your fees are too small. Best fee now is 15 satoshi per byte.

(Fee: 0.00002376 BTC - Size: 372 bytes)

You should use 15 x 372 bytes = 5580 satoshi fee = 0.00005580 Bitcoin fee

(Fee: 0.00001587 BTC - Size: 225 bytes)

225 bytes x 15 = 0.00003375 BTC FEE

For what I remember a tx fee should be at least 0.00010353 or something like that....
Just wait your tx wil be processed in a a day or less...

--Encrypted--

copper member

Activity: 924

Merit: 1007

hee-ho.

Quote from: papa_face on February 29, 2016, 01:53:18 PM

It's weird, the 2nd transaction is high priority but I haven't changed anything....

that's because the priority is calculated from the amount of bitcoin sent and input age and transaction size. so an unconfirmed tx gets more priority as the input gets more confirmation (more old).

papa_face

member

Activity: 114

Merit: 10

Quote from: --Encrypted-- on February 29, 2016, 01:37:52 PM

Quote from: papa_face on February 29, 2016, 12:56:36 PM

I've tried this but when bitcoin core starts the unconfirmed transactions are still in my transaction list?
I'm doing:
"C:\Program Files\Bitcoin\bitcoin-qt.exe" -zapwallettex

it's -zapwallettxes. not -zapwallettex.
if that still doesn't work run it from the win+r or task manager.

btw make sure that the path is correct.

Thanks, I'll give that a try now. It's rescanning now, which it wasn't doing before.

It's weird, the 2nd transaction is high priority but I haven't changed anything....

--Encrypted--

copper member

Activity: 924

Merit: 1007

hee-ho.

Quote from: papa_face on February 29, 2016, 12:56:36 PM

I've tried this but when bitcoin core starts the unconfirmed transactions are still in my transaction list?
I'm doing:
"C:\Program Files\Bitcoin\bitcoin-qt.exe" -zapwallettex

it's -zapwallettxes. not -zapwallettex.
if that still doesn't work run it from the win+r or task manager.

btw make sure that the path is correct.

papa_face

member

Activity: 114

Merit: 10

Quote from: --Encrypted-- on February 29, 2016, 08:05:14 AM

Quote from: papa_face on February 29, 2016, 07:11:55 AM

Hi guys

I've tried this method https://blog.blockchain.com/2014/07/08/tutorial-how-to-rebroadcast-a-bitcoin-transaction/

but it just says the transaction already exists.
I have access to the wallet I sent these from (Bitcoin Core)

What else can be done? I really need these confirmed today Sad

you can only wait. that method you posted only works if blockchain.info or whatever service node you're pushing the tx to have dropped your tx.

or you can make the mempool drop that tx by stopping your core from re-broadcasting it and hope that the rest of the network will do the same. bitcoin core automatically re-broadcast your unconfirmed transaction after a while so you'll need to enter -zapwallettxes command from the console (back up your wallet.dat first!). doing that will remove every unconfirmed transaction that you have.
be aware that the btc will return to the sender's wallet if the mempool dropped the tx.

I've tried this but when bitcoin core starts the unconfirmed transactions are still in my transaction list?
I'm doing:
"C:\Program Files\Bitcoin\bitcoin-qt.exe" -zapwallettex

Quote from: watashi-kokoto on February 29, 2016, 08:45:20 AM

Quote from: papa_face on February 29, 2016, 03:33:31 AM

They seem to be taking forever to get confirmed. I always send using the recommended fee in bitcoin core.

Your fees are too small. Best fee now is 15 satoshi per byte.

(Fee: 0.00002376 BTC - Size: 372 bytes)

You should use 15 x 372 bytes = 5580 satoshi fee = 0.00005580 Bitcoin fee

(Fee: 0.00001587 BTC - Size: 225 bytes)

225 bytes x 15 = 0.00003375 BTC FEE

yeah not sure why it's low as I just used the recommended option in bitcoin core Sad

watashi-kokoto

sr. member

Activity: 689

Merit: 269

Quote from: papa_face on February 29, 2016, 03:33:31 AM

They seem to be taking forever to get confirmed. I always send using the recommended fee in bitcoin core.

Your fees are too small. Best fee now is 15 satoshi per byte.

(Fee: 0.00002376 BTC - Size: 372 bytes)

You should use 15 x 372 bytes = 5580 satoshi fee = 0.00005580 Bitcoin fee

(Fee: 0.00001587 BTC - Size: 225 bytes)

225 bytes x 15 = 0.00003375 BTC FEE

--Encrypted--

copper member

Activity: 924

Merit: 1007

hee-ho.

Quote from: papa_face on February 29, 2016, 07:11:55 AM

Hi guys

I've tried this method https://blog.blockchain.com/2014/07/08/tutorial-how-to-rebroadcast-a-bitcoin-transaction/

but it just says the transaction already exists.
I have access to the wallet I sent these from (Bitcoin Core)

What else can be done? I really need these confirmed today Sad

you can only wait. that method you posted only works if blockchain.info or whatever service node you're pushing the tx to have dropped your tx.

or you can make the mempool drop that tx by stopping your core from re-broadcasting it and hope that the rest of the network will do the same. bitcoin core automatically re-broadcast your unconfirmed transaction after a while so you'll need to enter -zapwallettxes command from the console (back up your wallet.dat first!). doing that will remove every unconfirmed transaction that you have.
be aware that the btc will return to the sender's wallet if the mempool dropped the tx.

papa_face

member

Activity: 114

Merit: 10

Hi guys

I've tried this method https://blog.blockchain.com/2014/07/08/tutorial-how-to-rebroadcast-a-bitcoin-transaction/

but it just says the transaction already exists.
I have access to the wallet I sent these from (Bitcoin Core)

What else can be done? I really need these confirmed today Sad

vlamer

member

Activity: 101

Merit: 11

N.E.E.T

I fix this problem with send again some coin including six confirmation request,

Code:

./bitcoin-cli sendtoaddress "bitcoinaddress" amount true #set paytxfee=0.0001 before
./bitcoin-cli sendfrom "account" "bitcoinaddress" amount 6

if not in the core Wallet, it may be already standard 6 confirmation.

alani123

legendary

Activity: 2422

Merit: 1451

Leading Crypto Sports Betting & Casino Platform

Are you in possesion of the private keys of the addresses that sent the unconfirmed transactions? What was the wallet used? It's probably the fee being too low for the current sat/Kb rate, you could do a rbf if it's urgent.

Swordsoffreedom

legendary

Activity: 2884

Merit: 1115

Leading Crypto Sports Betting & Casino Platform

Quote from: papa_face on February 29, 2016, 03:33:31 AM

Hey

Can anyone tell me if there's something wrong with these transactions please?
You can see both of them here:
https://blockchain.info/address/1Bc7uv7A1QjN4dNp6kAmc3xtBYJDuTjyT7

They seem to be taking forever to get confirmed. I always send using the recommended fee in bitcoin core.

thanks!

It looks fine to me but the fee might have ended up being a little to low, but perhaps its in need of a rebroadcasting since it is slow...
https://blockchain.info/pushtx
https://blockchain.info/decode-tx

Topic: ~18 hours with recommended fee's, still no confirmation :( (Read 1210 times)