|
omgitsmehehe (OP)
|
 |
November 13, 2013, 03:57:16 PM |
|
Backup has been restored and 43.xxxBTC sitting in wallet. The address holding is: 16sfAJDmdEZahYva5YWa3RZ7FF6BMzU4Hj which says 0BTC is held at this address... :/ Just thought I would also add that 6.02 and 0.28 tx's are still showing as unconfirmed in the wallet too.  |
|
|
|
|
|
|
|
|
|
|
Unlike traditional banking where clients have only a few account numbers, with Bitcoin people can create an unlimited number of accounts (addresses). This can be used to easily track payments, and it improves anonymity.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
DannyHamilton
Legendary
 Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 03:58:59 PM |
|
Backup has been restored and 43.xxxBTC sitting in wallet.
The address holding is: 16sfAJDmdEZahYva5YWa3RZ7FF6BMzU4Hj which says 0BTC is held at this address... :/
please run: listunspent
Also note, you should be able to copy and paste from the console into bitcointalk. It shouldn't be necessary to create a screen capture to show what's in the console. |
|
|
|
|
deepceleron
Legendary
Offline
Activity: 1512
Merit: 1025
|
|
November 13, 2013, 04:00:15 PM |
|
Backup has been restored and 43.xxxBTC sitting in wallet.
The address holding is: 16sfAJDmdEZahYva5YWa3RZ7FF6BMzU4Hj which says 0BTC is held at this address... :/
Just thought I would also add that 6.02 and 0.28 tx's are still showing as unconfirmed in the wallet too.
A wallet has many addresses, most of which are not shown to you. Much of your balance will be in "change" addresses if you have used your wallet to send payments. |
|
|
|
|
|
omgitsmehehe (OP)
|
|
November 13, 2013, 04:00:27 PM |
|
Backup has been restored and 43.xxxBTC sitting in wallet.
The address holding is: 16sfAJDmdEZahYva5YWa3RZ7FF6BMzU4Hj which says 0BTC is held at this address... :/
please run: listunspent
16:00:04  listunspent 16:00:04  [ ] |
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 04:02:40 PM |
|
A wallet has many addresses, most of which are not shown to you. Much of your balance will be in "change" addresses if you you have used your wallet to send payments.
deepceleron, Yes but, look at his screen capture. listaddressgroupings appears to show the BTC in unspent outputs that were sent to that particular address... And yet listunspent indicates NO unspent outputs!  |
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 04:04:28 PM |
|
If you don't mind (and if deepceleron doesn't object), I'd really like to see the raw transaction.
I suspect it may tell us something about what bitcoins the wallet thinks it has, and why the transactions aren't broadcasting.
|
|
|
|
|
|
omgitsmehehe (OP)
|
|
November 13, 2013, 04:05:13 PM |
|
If you don't mind (and if deepceleron doesn't object), I'd really like to see the raw transaction.
I suspect it may tell us something about what bitcoins the wallet thinks it has, and why the transactions aren't broadcasting.
Which tx would you like me to post? |
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 04:06:47 PM |
|
If you don't mind (and if deepceleron doesn't object), I'd really like to see the raw transaction.
I suspect it may tell us something about what bitcoins the wallet thinks it has, and why the transactions aren't broadcasting.
Which tx would you like me to post? Send the 43 BTC to your MultiBit wallet. When it shows unconfirmed, run getrawtransaction on the new transaction ID. Post the rawtransaction here. |
|
|
|
|
|
omgitsmehehe (OP)
|
|
November 13, 2013, 04:08:59 PM |
|
If you don't mind (and if deepceleron doesn't object), I'd really like to see the raw transaction.
I suspect it may tell us something about what bitcoins the wallet thinks it has, and why the transactions aren't broadcasting.
Which tx would you like me to post? Send the 43 BTC to your MultiBit wallet. When it shows unconfirmed, run getrawtransaction on the new transaction ID. Post the rawtransaction here. 16:08:45  getrawtransaction f68e7fe0c28586ed965a5cce64ee473b4fa818eb6be0b96bb12d292c06d63868 16:08:45  01000000018d92b3efedf8a30052c6470f83811421cbf028bab01d424c0499081d7f49078b00000 0006a4730440220799fc6897c2bde35253fea64dd2eec331fedb2e317533a38525284e4393ca813 02205fc85c304b60a9651d7b2e7eb2097d1f68c085046e47df8e05a20f9e2efe68c501210233e67 b77903e32cd823204ea1484489488bae73863a590d75b34cd4b339f529cffffffff0200cb4c0001 0000001976a9142923a16ba5942c4b9963a332fa152cb3845cca5688ace8847405000000001976a 9143e32449feae9a9cb742d8a2ea56e98bd144ab6f288ac00000000 |
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 04:22:23 PM |
|
16:08:45
01000000018d92b3efedf8a30052c6470f83811421cbf028bab01d424c0499081d7f49078b00000 0006a4730440220799fc6897c2bde35253fea64dd2eec331fedb2e317533a38525284e4393ca813 02205fc85c304b60a9651d7b2e7eb2097d1f68c085046e47df8e05a20f9e2efe68c501210233e67 b77903e32cd823204ea1484489488bae73863a590d75b34cd4b339f529cffffffff0200cb4c0001 0000001976a9142923a16ba5942c4b9963a332fa152cb3845cca5688ace8847405000000001976a 9143e32449feae9a9cb742d8a2ea56e98bd144ab6f288ac00000000
Ok, here's the what the wallet is attempting to spend. "vin" : [
{
"txid" : "8b07497f1d0899044c421db0ba28f0cb211481830f47c65200a3f8edefb3928d",
"vout" : 0,
"scriptSig" : {
It seems to believe that you received 43.091522280 BTC in transactionID 8b07497f1d0899044c421db0ba28f0cb211481830f47c65200a3f8edefb3928d. However, that transaction does not exist in the blockchain. As I suspected, this is why your transaction isn't confirming, and why it isn't being relayed on the network. As far as the rest of the bitcoin network is concerned, those bitcoins have never existed. I'm not yet sure why your wallet thinks it received such a transaction. If you look in the "Transactions" section of your wallet, and search for address 16sfAJDmdEZahYva5YWa3RZ7FF6BMzU4Hj, can you find the date and time that the wallet received the transaction? If so, do you recall who you would have received the 43.091522280 BTC from on that day? |
|
|
|
|
deepceleron
Legendary
Offline
Activity: 1512
Merit: 1025
|
|
November 13, 2013, 04:27:02 PM |
|
Just deleted tx's through pywallet, done bitcoin -rescan and balance shows 0 confirmed and 0 unconfirmed.
Looks like this might be showing the correct balance, based on the input above! |
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 04:31:58 PM |
|
Just deleted tx's through pywallet, done bitcoin -rescan and balance shows 0 confirmed and 0 unconfirmed.
Looks like this might be showing the correct balance, based on the input above! Agreed. It looks like the OP is a victim of a double spend. Possibly intentional, possibly accidental. The transactions aren't confirming because peers refuse to relay the transaction with an invalid input, and the rescan shows the proper (0 BTC) balance because it discovers that the 43 BTC transaction never made it into the blockchain. |
|
|
|
|
|
Moebius327
|
|
November 13, 2013, 04:42:05 PM |
|
Type listreceivedbyaddress in console and paste all the addresses here.
Edit: If it's ok for you. Or send me a PM.
|
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 04:43:38 PM |
|
Type listreceivedbyaddress in console and paste all the addresses here.
We already know what address received the bad transaction. How is this going to help? |
|
|
|
|
|
Moebius327
|
|
November 13, 2013, 04:44:46 PM |
|
Type listreceivedbyaddress in console and paste all the addresses here.
We already know what address received the bad transaction. How is this going to help? Well as I see you run out of ideas. Why bother other people that want to help? |
|
|
|
|
Amitabh S
Legendary
Offline
Activity: 1001
Merit: 1003
|
|
November 13, 2013, 04:48:13 PM |
|
16:08:45
01000000018d92b3efedf8a30052c6470f83811421cbf028bab01d424c0499081d7f49078b00000 0006a4730440220799fc6897c2bde35253fea64dd2eec331fedb2e317533a38525284e4393ca813 02205fc85c304b60a9651d7b2e7eb2097d1f68c085046e47df8e05a20f9e2efe68c501210233e67 b77903e32cd823204ea1484489488bae73863a590d75b34cd4b339f529cffffffff0200cb4c0001 0000001976a9142923a16ba5942c4b9963a332fa152cb3845cca5688ace8847405000000001976a 9143e32449feae9a9cb742d8a2ea56e98bd144ab6f288ac00000000
It seems to believe that you received 43.091522280 BTC in transactionID 8b07497f1d0899044c421db0ba28f0cb211481830f47c65200a3f8edefb3928d. However, that transaction does not exist in the blockchain. As I suspected, this is why your transaction isn't confirming, and why it isn't being relayed on the network. As far as the rest of the bitcoin network is concerned, those bitcoins have never existed. I'm not yet sure why your wallet thinks it received such a transaction. This is what likely happened. A quick google search shows that your client indeed tried to broadcast but it was rejected. Here is a cached copy of blockchain's rejected transactions, which shows that the tx was indeed broadcasted. Looks like the coins were double spent soon afterwards. Do you remember when the tx was received and the sender's address? It is strange that QT attempted to send the tx without it confirming! very unusual! |
|
|
|
Tymer
Member
Offline
Activity: 98
Merit: 10
|
|
November 13, 2013, 04:49:53 PM |
|
16:08:45
01000000018d92b3efedf8a30052c6470f83811421cbf028bab01d424c0499081d7f49078b00000 0006a4730440220799fc6897c2bde35253fea64dd2eec331fedb2e317533a38525284e4393ca813 02205fc85c304b60a9651d7b2e7eb2097d1f68c085046e47df8e05a20f9e2efe68c501210233e67 b77903e32cd823204ea1484489488bae73863a590d75b34cd4b339f529cffffffff0200cb4c0001 0000001976a9142923a16ba5942c4b9963a332fa152cb3845cca5688ace8847405000000001976a 9143e32449feae9a9cb742d8a2ea56e98bd144ab6f288ac00000000
It seems to believe that you received 43.091522280 BTC in transactionID 8b07497f1d0899044c421db0ba28f0cb211481830f47c65200a3f8edefb3928d. However, that transaction does not exist in the blockchain. As I suspected, this is why your transaction isn't confirming, and why it isn't being relayed on the network. As far as the rest of the bitcoin network is concerned, those bitcoins have never existed. I'm not yet sure why your wallet thinks it received such a transaction. This is what likely happened. A quick google search shows that your client indeed tried to broadcast but it was rejected. Here is a cached copy of blockchain's rejected transactions, which shows that the tx was indeed broadcasted. Looks like the coins were double spent soon afterwards. Do you remember when the tx was received and the sender's address? It is strange that QT attempted to send the tx without it confirming! very unusual! Resuming: You Got Scammed. |
|
|
|
deepceleron
Legendary
Offline
Activity: 1512
Merit: 1025
|
|
November 13, 2013, 05:03:51 PM |
|
It is strange that QT attempted to send the tx without it confirming! very unusual! This ability is needed because of change, if you had to wait for your change to confirm before you could send another transaction from Bitcoin, you would be limited to one transaction per block. Bitcoin considers all money you've received as spendable, it is up to you to use the information about number of confirmations to see if you should be spending amounts that need the unconfirmed coins. ...
How is this going to help? I'm posting because I have assistance to offer, not for a bounty. Adding a bounty to a tech support thread attracts others that want a bounty but do not offer assistance. |
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 05:07:12 PM |
|
...
How is this going to help? I'm posting because I have assistance to offer, not for a bounty. Adding a bounty to a tech support thread attracts others that want a bounty but do not offer assistance. Agreed. A bounty in the Technical Support thread is usually a good way to fill a thread with useless chatter and random guesses. |
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
November 13, 2013, 05:10:26 PM |
|
Well as I see you run out of ideas.
I haven't run out of ideas. I've assisted in directing the user to discover exactly what is happening in their wallet. I've also asked that they find the date & time of the transaction that funded their wallet so they can attempt to figure out where & when the double-spend that messed up their wallet came from. Why bother other people that want to help?
Because your random guessing and instructions that add no value distract from the problem, waste time, and cause confusion. |
|
|
|
|
|
