If you want to extract the keys from the recovered wallet file you can open it directly with Notepad or Notepad++ you should be able to see the private keys inside.

Or you can import the wallet.dat file directly to bitcoin core and use "dumpprivkey" to dump private keys.

Why would you give your personal documents to the Pi network? It's not a wise decision to share your documents with the Pi network. Their pi miner on mobile trying to solve anything but it doesn't actually solve anything and it is known as a scam project.

I was in the same situation before I got D3 units not directly from the manufacturer, but through someone who sells 2nd hand/used units. I never made a profit, so I made the choice to sell it to others at a low price with a negative return. The profitability of this unit before is very attractive forcing you to buy it.

I attempted to withdraw my 0.005BTC 4 hours ago with a 1-hour delay, but I haven't received the BTC yet. I already check the explorer but no incoming transaction. It seems that the transaction has been put on hold or stopped on their backend.

I withdrew my BTC there without issue last week, however, it didn't work this time, the same as other people reported a few days ago.

I'm curious if other Whirlwind campaign participants are having the same problem withdrawing BTC?

I don't understand what you are trying to say but you mean you modify the dbcache but it corrupts the Bitcoin core downloaded blockchain files?

And you want to recover your bitcoin from your wallet?

I believe you may resolve this issue by running Bitcoin Core with the "-reindex" option.

Most of these people (newbies who only care about profitability) are only interested in the daily profits that they see on calculators like in "asicminervalue.com," but they don't realize that once these units are released and start operating, the difficulty will skyrocket.

@OP if you are making a profit right now I suggest before the price of the coin drop exchange it to stable coin like USDT to secure your profit.

Have you read our previous posts for a corrupted wallet.dat file above?
Please test it first and report back here.

If it doesn't work, is it possible that the "wallet.dat" file you're attempting to recover is an altcoin backup wallet rather than a Bitcoin backup wallet?

How did you obtain this information? If you don't know what blockchain is, it is where all Bitcoin transactions are recorded. You might be just heard blockchain to any site and social media but Blockchain.com is only a blockchain explorer that offers a web wallet and their wallet is not as safe as Electrum. They have many issues with their wallet that have yet to be resolved. So you shouldn't use a blockchain wallet; instead, use Electrum, create an offline wallet, or purchase a hardware wallet. Then learn how to make raw or offline transactions, which are far safer than using an online device or a web wallet that stays connected to the internet.

Since you made a backup every year why not use those other wallet backups to retrieve your wallet if you make a backup every year?
Did you remove the old wallet.dat every time you made a backup?


Whether you install the old or updated version of the Bitcoin core wallet. That should work just fine because it is backward compatible.

The clearnet is currently under DDOS attack you can use the Tor version I just tried today and it works fine with me.

If you don't know how to access it download a Tor browser and paste the whirlwind Tor link there.

Are you using the same PC where this wallet.dat was created? You can maybe try to recover it through pywallet to recover the missing wallet or private keys.
Sample command you can use with Pywallet


Just replace the recovery size 500 with the current size of your hard drive sample if the current hard drive is 256 GB then replace it with 256.


I don't think Bitcoin Core supports seed mnemonic.

Based on this error like the above said the wallet.dat file might be corrupted you have a similar case here "Another recovery attempt".

What I think is to use -salvagewallet but it was moved to bitcoin-wallet.exe there is a guide here on how to perform salvage wallet using bitcoin-wallet tool.

But before you salvage this wallet make sure you make a backup copy of your wallet.dat file first.

If you have then you should be able to export or dump the keys on the Bitcoin-qt console or pywallet.

What issue or errors did you get when trying to dump the keys from Qt and Pywallet?

Here are the sample commands on the Bitcoin-qt


And then dump the private key

Btcrecover is supposed to be used for recovering missing characters or seed phrases or brute-forcing passphrases. Did you forget the password of your wallet.dat?

If not, then maybe you didn't include the command for the passphrase before you use dumpprivkey from the bitcoin-qt console or PyWallet.

If you forgot the password there is documentation for BTCrecoved from this link below that you can follow you can also check the sample commands under that link.

- https://btcrecover.readthedocs.io/en/latest/

Are you talking about the farm proxy of the BraiinsOS?
If I'm right according to them it is used to "Reduce data loads, configure parallel usage of multiple pools, set backup pools, and more".

About setting it up better read their documentation about this you can read the documentation below on how to set up this proxy.

- https://braiins.com/farm-proxy/documentation

He might be not satisfied or maybe he doesn't want to wait for 360 seconds wait-time. Since the OP is a newbie he can't able to respond right away.
Or maybe he just doesn't know how to go back or find his old thread.

For the main topic about CryptoPay, they are offering cards since 2016 based on their official thread that they created here on the forum I don't know what you mean by a new card program or you might be talking about their app?
Before there is a signup or join button on the site but right now they force you to open an account through the app I don't know what's the reason but it is way easier to use than before.

Why not check their social media accounts about their service from the official thread below?

- https://bitcointalk.org/index.php?topic=1384807.0

I never heard of this compassmining I tried to search and pointed me to compassmining.io is this the site you talking to?

If yes then I never heard of this website before some old posts mention this site but almost all posts are made by newbies. So I can't give any insight if they are legit or not.

And I checked their website and some guides but it looks like they are not offering a hosting service but selling mining units and hosting it to their hosting partners. We do not know if they have these units physically and it seems a cloud mining.

It's too risky to deal with them without the units physically and look at this below just copy and paste it to your browser I just want to link them here. According to the link, you can't send your own miner to their facility unless you buy from them which we don't know if they have these units on hand.

If you are looking for escrow service the forum has a list of trusted escrow you can check them below.

- https://bitcointalk.org/index.php?topic=276897.0

About Bitify I heard a few people complain about their issues using Bitify that until now haven't resolved but some people use it without any issues.

Check this similar topic Has anyone used http://bitify.com and what's the authencity ?

I agree with multiple outputs but I just want to add this based on the Bitcoin wiki the fee is not just calculated on the size of the output but also the inputs. Both of them shares the transaction size in total.

There are some calculators about this how to calculate the size of a transaction with a better explanation you can check the link below.

-  https://bitcoinops.org/en/tools/calc-size/

I never heard of the vkbit.com pool and according to Whois it was just created last year if I were you I suggest use a well-known pool like https://solo.ckpool.org/ or Viabtc pool.

You can try them and update here if still didn't work then post the logs of the unit here just don't forget to put the logs inside the insert code tag so that we can easily read them.