Topic: Send Bitcoins with Bitcoin-QT: What could I have done wrong? (Read 1823 times)
I realize it could be read either way, I was simply clarifying to prevent confusion. Guess I should have clarified my intent as well.
Actually, since you were using Bitcoin-Qt, the change went to a brand new address never seen in the wallet before.
This isn't quite true, while the address has never been used by the wallet before it is in the wallet along with another 99 addresses in the keypool. (99 assumes you haven't manually changed the size of the keypool)
I suppose it depends on your definition of "brand new" and "never seen".
While the address will have been pre-created for you before you used it, it wasn't shown to you anywhere in the user interface and wasn't visible anywhere in the blockchain. I'd say that fits the definition of "never seen" pretty well.
In addition, when the address was added to the key pool, it was not acquired from some other source nor was the user prompted to enter it into the wallet. I'm ok with calling that "brand new". When you buy something from the store it may have been sitting on the shelf for weeks, but most still consider it "brand new".
Actually, since you were using Bitcoin-Qt, the change went to a brand new address never seen in the wallet before.
This isn't quite true, while the address has never been used by the wallet before it is in the wallet along with another 99 addresses in the keypool. (99 assumes you haven't manually changed the size of the keypool)
Are you mining on your cell phone??
The tittle is because that wallet address was generated in that cell phone's Bitcoin Wallet.
But yes, I do use it also to mine, when in the cradle... giving me an astonish 2.2 MHash/s from it's 4 cores.
please provide screenshots.
Too late, as I already transferred the 0.09908462 BTC to my primary address (not Bitcoin-QT primary address, as this address is from my Android Bitcoin wallet) using blockchain.info site... Bitcoin-QT now displays that last transaction as a self transfer.
Code:
Status: 50 confirmations
Date: 21/06/2013 22:18
Debit: -0.09908462 BTC
Credit: 0.09908462 BTC
Net amount: 0.00 BTC
Transaction ID: 84b72902f79c14c9cf412ed3f0f69f040c9d77164de1f9b4c8dc22c2dbf617f7
https://blockchain.info/tx/84b72902f79c14c9cf412ed3f0f69f040c9d77164de1f9b4c8dc22c2dbf617f7Date: 21/06/2013 22:18
Debit: -0.09908462 BTC
Credit: 0.09908462 BTC
Net amount: 0.00 BTC
Transaction ID: 84b72902f79c14c9cf412ed3f0f69f040c9d77164de1f9b4c8dc22c2dbf617f7
- snip -
I always imagined that the change would come back to the same address.
- snip -
I always imagined that the change would come back to the same address.
- snip -
Unfortunately, you imagined incorrectly in the case of the Bitcoin-Qt wallet. There may be other wallets that work this way. Each wallet is allowed to handle change however the creator of the wallet program chooses.
In this case, the change went to the (probably) primary address of the Bitcoin-QT that started the transaction, regardless of the money being sent from an imported address and not from the primary one, generated upon installation of the Bitcoin-QT program.
Actually, since you were using Bitcoin-Qt, the change went to a brand new address never seen in the wallet before. This is how Bitcoin-Qt is designed to work. If there is any change in the transaction, Bitcoin-Qt gets a brand new address and sends the change there. It does not re-use this change address to receive any other bitcoins in the future.
Thanks for your help and support, DannyHamilton.
- snip -
I always imagined that the change would come back to the same address.
- snip -
I always imagined that the change would come back to the same address.
- snip -
Unfortunately, you imagined incorrectly in the case of the Bitcoin-Qt wallet. There may be other wallets that work this way. Each wallet is allowed to handle change however the creator of the wallet program chooses.
In this case, the change went to the (probably) primary address of the Bitcoin-QT that started the transaction, regardless of the money being sent from an imported address and not from the primary one, generated upon installation of the Bitcoin-QT program.
Actually, since you were using Bitcoin-Qt, the change went to a brand new address never seen in the wallet before. This is how Bitcoin-Qt is designed to work. If there is any change in the transaction, Bitcoin-Qt gets a brand new address and sends the change there. It does not re-use this change address to receive any other bitcoins in the future.
Many thanks for the explanation, deepceleron.
I now understand the logic of a digital currency transaction, but I always imagined that the change would come back to the same address. In this case, the change went to the (probably) primary address of the Bitcoin-QT that started the transaction, regardless of the money being sent from an imported address and not from the primary one, generated upon installation of the Bitcoin-QT program.
Next time, I'll send the money from the wallet that generated the address I use as primary one (the Android Bitcoin Wallet in my cellphone).
Quote
㋔ Geek Facts
Transactions are comprised of a list of inputs, individual payments that were previously received by a wallet, and outputs, a list of amounts and addresses to which the bitcoins will be transferred.
Only the full amount of an input can be spent. If the exact amount of the transaction can’t be constructed from available inputs, an additional output, called change, is added, which sends the remainder back to a new address in the user’s wallet. Change addresses are not shown to the user.
Transactions are comprised of a list of inputs, individual payments that were previously received by a wallet, and outputs, a list of amounts and addresses to which the bitcoins will be transferred.
Only the full amount of an input can be spent. If the exact amount of the transaction can’t be constructed from available inputs, an additional output, called change, is added, which sends the remainder back to a new address in the user’s wallet. Change addresses are not shown to the user.
please provide screenshots.
Too late, as I already transferred the 0.09908462 BTC to my primary address (not Bitcoin-QT primary address, as this address is from my Android Bitcoin wallet) using blockchain.info site... Bitcoin-QT now displays that last transaction as a self transfer.
Code:
Status: 50 confirmations
Date: 21/06/2013 22:18
Debit: -0.09908462 BTC
Credit: 0.09908462 BTC
Net amount: 0.00 BTC
Transaction ID: 84b72902f79c14c9cf412ed3f0f69f040c9d77164de1f9b4c8dc22c2dbf617f7
https://blockchain.info/tx/84b72902f79c14c9cf412ed3f0f69f040c9d77164de1f9b4c8dc22c2dbf617f7Date: 21/06/2013 22:18
Debit: -0.09908462 BTC
Credit: 0.09908462 BTC
Net amount: 0.00 BTC
Transaction ID: 84b72902f79c14c9cf412ed3f0f69f040c9d77164de1f9b4c8dc22c2dbf617f7
please provide screenshots.
New update: After all that address is mine. 
Now, what I can't understand it's why my bitcoin-QT insists in telling me that the address has 0 BTC and the address from whom I sent the 0.025 still has this 0.09908462 BTC, even after a bitcoin-QT start with "-rescan".
- I tried to list the addresses with the command listaccounts and I couldn't see the BTC "lost" or that address.
- But trying with the command "getbalance 1DrjveHXqQzT6CqS34whJScEtDoXRyB9JL" i got the answer "0.00000000".
- Next, I tried the command "dumpprivkey 1DrjveHXqQzT6CqS34whJScEtDoXRyB9JL" and I got a private key.
- With that private key, I imported it to blockchain.info without errors.
- In the option "Receive" I could now see "1DrjveHXqQzT6CqS34whJScEtDoXRyB9JL 0.09908462 BTC"... my "lost" BTC.
Now, what I can't understand it's why my bitcoin-QT insists in telling me that the address has 0 BTC and the address from whom I sent the 0.025 still has this 0.09908462 BTC, even after a bitcoin-QT start with "-rescan".
I sent today .025 BTC to the address BitcoinStarter gave me when I signed in, using Bitcoin-QT 0.8.2 for Windows. I forgot to previously select a transaction fee, that stayed at 0.00000 BTC
The status of the transaction:
But when seeing the transaction @ Blockchain (https://blockchain.info/tx/6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3), I see that the total of 0.12408462 BTC was sent by the program:
I don't know who is the owner of the 1DrjveHXqQzT6CqS34whJScEtDoXRyB9JL address, the Bitcoin-QT still gives me a balance of the value I had minus the 0.025BTC, but using the Bitcoin-Wallet for Android or the Blockchain site (I also have my private key on those 2 locations), the balance is the old value minus 0.12408462.
Log of the transaction (debug window):
What could I have done wrong?
UPDATE: After forcing a "bitcoin-qt -rescan", the balance stays the same, as if only 0.025 BTC went out...
The status of the transaction:
Code:
Status: 88 confirmations
Date: 21/06/2013 07:27
To: BitcoinStarter 1Ns4sPesjfpcCXX8SnwKsWpoABANmAq7ZM
Debit: -0.025 BTC
Net amount: -0.025 BTC
Transaction ID: 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3
Date: 21/06/2013 07:27
To: BitcoinStarter 1Ns4sPesjfpcCXX8SnwKsWpoABANmAq7ZM
Debit: -0.025 BTC
Net amount: -0.025 BTC
Transaction ID: 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3
But when seeing the transaction @ Blockchain (https://blockchain.info/tx/6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3), I see that the total of 0.12408462 BTC was sent by the program:
Code:
1LHcdewdDzSW5hNaLqfiEoe7R7SDwWz255 (0.12408462 BTC - Output)
[b]1DrjveHXqQzT6CqS34whJScEtDoXRyB9JL - (Unspent) 0.09908462 BTC[/b]
1Ns4sPesjfpcCXX8SnwKsWpoABANmAq7ZM - (Unspent) 0.025 BTC
Inputs and Outputs
Total Input 0.12408462 BTC
Total Output 0.12408462 BTC
Fees 0 BTC
Estimated BTC Transacted 0.025 BTC
[b]1DrjveHXqQzT6CqS34whJScEtDoXRyB9JL - (Unspent) 0.09908462 BTC[/b]
1Ns4sPesjfpcCXX8SnwKsWpoABANmAq7ZM - (Unspent) 0.025 BTC
Inputs and Outputs
Total Input 0.12408462 BTC
Total Output 0.12408462 BTC
Fees 0 BTC
Estimated BTC Transacted 0.025 BTC
I don't know who is the owner of the 1DrjveHXqQzT6CqS34whJScEtDoXRyB9JL address, the Bitcoin-QT still gives me a balance of the value I had minus the 0.025BTC, but using the Bitcoin-Wallet for Android or the Blockchain site (I also have my private key on those 2 locations), the balance is the old value minus 0.12408462.
Log of the transaction (debug window):
Code:
keypool reserve 2
CommitTransaction:
CTransaction(hash=6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2, 21), scriptSig=30440220181e8196310b6385)
CTxOut(nValue=0.09908462, scriptPubKey=OP_DUP OP_HASH160 8d09b931c2e1)
CTxOut(nValue=0.02500000, scriptPubKey=OP_DUP OP_HASH160 efd2ab47b3a3)
keypool keep 2
AddToWallet 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 new
WalletUpdateSpent found spent coin 0.12408462bc b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2
NotifyTransactionChanged b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2 status=1
NotifyTransactionChanged 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 status=0
NotifyTransactionChanged b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2 status=1
AddToWallet 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3
NotifyTransactionChanged 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 status=1
CTxMemPool::accept() : accepted 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 (poolsz 2065)
Relaying wtx 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3
NotifyAddressBookChanged 1Ns4sPesjfpcCXX8SnwKsWpoABANmAq7ZM BitcoinStarter isMine=0 status=0
updateWallet b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2 1
inWallet=1 inModel=1 Index=21-22 showTransaction=1 derivedStatus=1
updateWallet 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 0
inWallet=1 inModel=0 Index=15-15 showTransaction=1 derivedStatus=0
Flushed 14528 addresses to peers.dat 67ms
updateWallet b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2 1
inWallet=1 inModel=1 Index=22-23 showTransaction=1 derivedStatus=1
updateWallet 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 1
inWallet=1 inModel=1 Index=15-16 showTransaction=1 derivedStatus=1
CommitTransaction:
CTransaction(hash=6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2, 21), scriptSig=30440220181e8196310b6385)
CTxOut(nValue=0.09908462, scriptPubKey=OP_DUP OP_HASH160 8d09b931c2e1)
CTxOut(nValue=0.02500000, scriptPubKey=OP_DUP OP_HASH160 efd2ab47b3a3)
keypool keep 2
AddToWallet 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 new
WalletUpdateSpent found spent coin 0.12408462bc b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2
NotifyTransactionChanged b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2 status=1
NotifyTransactionChanged 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 status=0
NotifyTransactionChanged b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2 status=1
AddToWallet 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3
NotifyTransactionChanged 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 status=1
CTxMemPool::accept() : accepted 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 (poolsz 2065)
Relaying wtx 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3
NotifyAddressBookChanged 1Ns4sPesjfpcCXX8SnwKsWpoABANmAq7ZM BitcoinStarter isMine=0 status=0
updateWallet b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2 1
inWallet=1 inModel=1 Index=21-22 showTransaction=1 derivedStatus=1
updateWallet 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 0
inWallet=1 inModel=0 Index=15-15 showTransaction=1 derivedStatus=0
Flushed 14528 addresses to peers.dat 67ms
updateWallet b97e9c1293ad322ca4da0400add035dcbab2308cefbb00d7b6cc7e056e36bed2 1
inWallet=1 inModel=1 Index=22-23 showTransaction=1 derivedStatus=1
updateWallet 6e7b0460cf23fa456a1a6d1dbbdea56ef6c286ea230638cd30ee829ac8e551d3 1
inWallet=1 inModel=1 Index=15-16 showTransaction=1 derivedStatus=1
What could I have done wrong?
UPDATE: After forcing a "bitcoin-qt -rescan", the balance stays the same, as if only 0.025 BTC went out...
Jump to: