Bitcoin Forum
May 05, 2024, 08:58:55 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: UNCONFIRMED transaction for BTC moved between wallets for ZERO fee?  (Read 885 times)
drbrock (OP)
Member
**
Offline Offline

Activity: 63
Merit: 10

New to BTC not new to the Empire of Chaos


View Profile
January 15, 2015, 07:03:50 PM
 #1

I have a transaction not confirmed as I moved BTC between wallets and didn't include a fee. Then every tx after that (even when included a fee) is also not confirmed. This has been coming close to 48 hours now. Any ideas?

https://blockchain.info/address/17aHtbvRq7ixzcXiopDrqiszcYgjBzrFm8

████████████
A  S  K   C O I N        Plug&Play Exchange Integrated with Twitter !
BitcoinCleanup.com: Learn why Bitcoin isn't bad for the environment
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714942735
Hero Member
*
Offline Offline

Posts: 1714942735

View Profile Personal Message (Offline)

Ignore
1714942735
Reply with quote  #2

1714942735
Report to moderator
1714942735
Hero Member
*
Offline Offline

Posts: 1714942735

View Profile Personal Message (Offline)

Ignore
1714942735
Reply with quote  #2

1714942735
Report to moderator
1714942735
Hero Member
*
Offline Offline

Posts: 1714942735

View Profile Personal Message (Offline)

Ignore
1714942735
Reply with quote  #2

1714942735
Report to moderator
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1079


Gerald Davis


View Profile
January 15, 2015, 07:08:03 PM
 #2

Well every transaction afterwards can't be confirmed until the parent is confirmed.  In theory miners could use child pays parent and include both the child and parent txn in the same block but I don't know if any are searching for txns that way.   There is (currently) no mechanism to support txn replacement.    Most wallets do not allow spending unconfirmed outputs for this reason.   What wallet were you using? 
drbrock (OP)
Member
**
Offline Offline

Activity: 63
Merit: 10

New to BTC not new to the Empire of Chaos


View Profile
January 15, 2015, 07:11:39 PM
 #3

Well I have my blocchain wallet and the wallet I sent the unconfirmed tx to is a brainwallet. (basically I was messing around on luckybit and once I got to 0.5btc I would transfer the 0.5 to thew brain-wallet and carry on playing with the change in the blockchain wallet.

So is this a matter of waiting (which is fine by me) or am I going to lose some funds/have funds locked up?
Also if you notice I made a new purchase of BTC (the latest transaction) and this was confirmed no problem. So does this mean I am able to spend some of the coins but a certain amount is till locked?

Thanx for reply

████████████
A  S  K   C O I N        Plug&Play Exchange Integrated with Twitter !
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1079


Gerald Davis


View Profile
January 15, 2015, 07:18:15 PM
 #4

You can't lose funds.   They might remain stuck for a bit.  I would also stop making new txns it will just make the problem worse.

If I read this right the txn that had no fee and is unconfirmed (parent) was Blockchain.info -> brainwallet?

Ultimately either
a) a miner will include the no fee parent in a block and then all the paying child txns will be confirmed shortly
OR
b) blockchain.info will eventually delete the unconfirmed txn (the parent) and you can make a new one.   One bad thing is if this happens all the child txns will become invalid so if you used them to deposit funds at say a casino and won they likely will not give you credit.

Either way you just have to wait.

In the future don't create no fee txns unless you are willing to wait a long time (potentially days or weeks) for it to confirm and if you do then don't create any new txns from the change until it confirms.
drbrock (OP)
Member
**
Offline Offline

Activity: 63
Merit: 10

New to BTC not new to the Empire of Chaos


View Profile
January 15, 2015, 07:25:33 PM
 #5

You can't lose funds.   They might remain stuck for a bit.  I would also stop making new txns it will just make the problem worse.

If I read this right the txn that had no fee and is unconfirmed (parent) was Blockchain.info -> brainwallet?

Ultimately either
a) a miner will include the no fee parent in a block and then all the paying child txns will be confirmed shortly
OR
b) blockchain.info will eventually delete the unconfirmed txn (the parent) and you can make a new one.   One bad thing is if this happens all the child txns will become invalid so if you used them to deposit funds at say a casino and won they likely will not give you credit.

Either way you just have to wait.

In the future don't create no fee txns unless you are willing to wait a long time (potentially days or weeks) for it to confirm and if you do then don't create any new txns from the change until it confirms.


Yes thats right blockchain.info to Brainwallet

Ok so yeah the transactions after that were to a casino but any winnings were not much at all so no problem there.
Yeah I made one more transaction (the latest confirmed one) which I hope I will have access to. In fact like you said dont make anymore transactions, otherwise I would have logged into my blockchain account and tried to move the newly purchased 0.5 into my brainwallet.

Ok so hopefully its either a waiting game which is fine or I will lose some earnings made with the small unconfirmed btc after the parent transaction. JUST SO LONG AS the newly bought 0.5 (which is already confimed but is in the same blockchain wallet) is not affected.

And yeah from now on always TX fees. (Didn't think it would be a problem as it was between wallets - my bad)

Thanx yo

EDIT - would you recommend moving the confirmed amount of 0.5 out of this blockchain wallet? Or just leave it be?

████████████
A  S  K   C O I N        Plug&Play Exchange Integrated with Twitter !
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!