Topic: Unconfirmed transaction (1BTC bounty paid for resolution!) - page 2. (Read 7454 times)

Ok, here's the what the wallet is attempting to spend.


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?

16:08:45

getrawtransaction f68e7fe0c28586ed965a5cce64ee473b4fa818eb6be0b96bb12d292c06d63868


16:08:45

01000000018d92b3efedf8a30052c6470f83811421cbf028bab01d424c0499081d7f49078b00000 0006a4730440220799fc6897c2bde35253fea64dd2eec331fedb2e317533a38525284e4393ca813 02205fc85c304b60a9651d7b2e7eb2097d1f68c085046e47df8e05a20f9e2efe68c501210233e67 b77903e32cd823204ea1484489488bae73863a590d75b34cd4b339f529cffffffff0200cb4c0001 0000001976a9142923a16ba5942c4b9963a332fa152cb3845cca5688ace8847405000000001976a 9143e32449feae9a9cb742d8a2ea56e98bd144ab6f288ac00000000

Send the 43 BTC to your MultiBit wallet.

When it shows unconfirmed, run getrawtransaction on the new transaction ID.

Post the rawtransaction here.

Which tx would you like me to post?

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.

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!

16:00:04

listunspent


16:00:04

[
]

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.

please run:


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.

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.

I'm beginning to wonder if the wallet is reporting the 43 BTC based on inputs that no longer exist.  Either spent from somewhere else that this wallet is unaware of, or lost in a blockchain reorganization where the inputs were spent and confirmed to some other address instead of yours.

Your wallet then wouldn't be able to broadcast the transaction, because all the peers would see it as invalid (trying to spend either non-existant, or already spent, outputs).

Then the re-scan would allow your wallet to discover that the inputs don't exist and would set your balance back to 0.

Analyzing the raw transaction would reveal if this is what is happening.

deepceleron, any thoughts on this possibility?

I deleted the tx from the wallet! I will restore backup wallet now. Is it worth trying to resend it again.

Also, it might be worth noting that I done listaddressgroupings, dumpprivkey on the address which held the 43BTC, import to blockchain.info wallet and it says 0BTC is held at that address....

And when searching for the address on the blockchain, nothing can be found.

If you have your original wallet.dat backup containing the keys to spend your bitcoins, and haven't forgotten the password, then your money is always recoverable and spendable. What we are doing is attempting to remove the "reservation" of coins your wallet thinks you spent, but have never been included in a block.

The -rescan command looks through all blocks you have downloaded one-by-one to update your balance, adding payments to you and deducting payments you have sent. What you should see after a rescan is that the transactions tab shows all transactions this wallet has ever made, but with the unconfirmed ones removed.

Bitcoin-Qt needs to have completed downloading all blocks before you will see an accurate balance though. You should have the "up-to-date" checkmark in the lower right of your client before wondering WTF.

If pywallet seemed to operate normally, there are a few things that may have gone wrong:

- the rescan option might not have been called correctly (it needs a single hyphen for -rescan when you type it), this must launch a new copy of Bitcoin (it wasn't already running), and you should see the rescan dialog take considerable time when Bitcoin starts.

- was Bitcoin running when you ran pywallet? Bitcoin must be completely closed before anything accesses wallet.dat or you attempt to make a backup. In options, be sure "Start Bitcoin on system login", "minimize on close", and "minimize to the tray" (or whatever equivalent OSX options there are) are unchecked, and restart your computer to be sure Bitcoin-Qt is absolutely not running,

- pywallet didn't do what it was supposed to. Perhaps berkeley database libs were the wrong version or not installed correctly, or other unanticipated problems,

- you are not starting Bitcoin under your user name from the command prompt, which would create a new wallet for whatever user that was (root, etc),

- you didn't run pywallet under your username. File permissions or ownership may be incorrect, or it didn't find your wallet or save changes correctly,

- OSX Bitcoin-qt client is known for having blockchain database problems more often than it should (some bug that hasn't been identified yet), this could have happened coincidentally, making your blockchain or it's index un-scannable.

If you are sure the rescan was performed, looks like we need to try again.

I would rename the non-working wallet.dat, and restore your wallet.dat backup (which, for that much in BTC, it should be backed up in multiple places) to the ~/.bitcoin data directory. Everything should be like it was before when you run Bitcoin, including your unconfirmed transactions, confirming that your coins are still there and your backup is good.

Then meticulously follow the remove-transaction steps again, with a restart first to be sure Bitcoin isn't locking the wallet file. The file names in the pywallet "delete" tab are filled in correctly on most operating systems, but be sure they reference the correct full home directory path with your user name.

If you really need wallet recovery, I could do this for you, but would have you phone call me personally to communicate a strong password to 7zip up your wallet backup when sending it, etc. It would take about 5 minutes since I already have pywallet working. I could send send back the balance-restored original wallet.dat, or transfer all bitcoins to a brand new wallet you create and we pre-verify with test transactions is working 100%.

Edit: see that you got money transferred out of wallet.

Great.  Then we can analyze the transaction to see if we can figure out what's wrong with it (if anything), and if the transaction looks good, we can manually push it onto the bitcoin network in case your wallet is just having a communication problem.

Clearly, so please stop.


OP isn't looking for opinions.  He's looking for assistance with a very specific problem.

My guess, from what i am readed, is that or his web is blocking btc OR his Multibit is just bugged.

i may not understand much but that are my opinions.

Hey Danny, the tx came out fine on getrawtransaction. I will post results when I have finished messing around.

Agreed, Tymer can you please stop posting.

Please don't give advice if you have no idea what you are talking about. You just clutter up the thread with useless noise and increase confusion.

The OP is having a problem broadcasting transactions from his Bitcoin-Qt wallet.  The transactions are never making it onto the bitcoin network.  This has nothing to do with his MultiBit wallet.

Yes like i said here:

Just delete everything from multibit & install again.

Are you at a university? I know my university has blocked bitcoin so using the client over their wifi is a no go.

Edit: Using any client except a web wallet is a no go at my university.