Topic: [Classic] Resetting Blockchain Doesn't Bring Back BTC from Rejected Transaction (Read 414 times)

Yes, checked most of explorers you mentioned and transaction had been dropped.
If you check my post, you'll realize that IT WAS DROPPED BY MULTIBIT ALSO when I reset the blockchain. The problem was: it was not showing me my BTC that were part of the pruned transaction. The transaction was gone from Multibit, but the BTC didn't return.

@ HI-TEC99: Thanks, I was aware of the method, I just wanted to check if there was a resolution in Multibit to avoid going to Electrum. However after seeing no resolution, I imported my private keys into Electrum. The balance shows up there and everything is OK.

Now I'm fully on Electrum.

Congratulations on waiting a whole 1hr and 14 minutes for a response... 

Which block explorers were you looking at to determine that the transaction had been dropped? Did you check blockchain.info, blockr.io, live.blockcypher.com, blocktrail.com, btc.com, blockexplorer.com etc etc?

Just because it has been dropped by one explorer (which effectively represents one node)... does not mean that it has been dropped by all nodes.

It might be that the nodes that MB Classic is scanning from still contain that transaction in their mempool or some other weirdness...

Did you get your Bitcoins back from your multibit wallet?

What version of multibit classic were you using? If you didn't get your coins back and you were using a version more recent than 0.4.0, then try these instructions to get your coins.

Start multibit, select the wallet containing your coins, then click "tools", then select "export private keys" as shown in the screenshot.



A new tab should open like the one below. Select "do not password protect export file" at the bottom of the window, then click the "export private keys button".



Click the windows start button, then copy and paste the line of text below into the search box that appears, then press the enter key to open the hidden folder containing your multibit wallet files.

%appdata%\Multibit

This is what your search box should look like after you have copied and pasted the line above into it.



Inside the folder that opens there should be a file with an extension ending in ".key". Open it in notepad and copy your wallet's private key. In the example file below the private key is the bit in red.



After you get your private key use these instructions to import it into electrum.

http://docs.electrum.org/en/latest/faq.html#can-i-import-private-keys-from-other-bitcoin-clients

Multibit classic's maximum allowable fees aren't high enough for dealing with today's massive backlog of unconfirmed transactions. It's best to import the private key into electrum, enable dynamic fees in it, and spend your coins from there. That way you will get fast confirmations.

18 views and 0 replies, that says a lot. Switched to Electrum. Move along, nothing to see here.

I made a transaction with Multibit Classic which had low fees (thanks to MB Classic's inability to recognize sufficient fees or allow user to easily control it).

Eventually I realized it was never going to confirm, so I just let it expire. As expected, the transaction was rejected eventually and pruned from blockchain.

I then went back to fire up Multibit and the transaction still sat there unconfirmed. Obviously I was pissed to see my BTC locked up in limbo, so I just went ahead and did the "Reset Blockchain & Transactions". It took a few minutes and the transaction was gone. But unlike I was expecting, it shows me ZERO balance, instead of showing the balance from rejected/pruned transaction.

To double-check, I put the address in blockchain.info and it shows me the balance. So my BTC have returned to the original address, but Multibit is refusing to show it to me.

Is this a known issue? Is there any resolution?

I am now seriously thinking of switching to Electrum.