The introduction of descriptor wallets presents an opportunity to introduce a new database backend as descriptor wallets are backwards incompatible. The following is taken from Andrew Chow's blog post on what's coming to the Bitcoin Core wallet in 0.21. (There was also discussion on this GitHub Issue.)
Why move from Berkeley DB?
Not designed to be used as ...
Does it create a public key based of private?
Yes, a cryptographic routine exists that computes the public key from the private key.
maybe on the wallet.dat file?
All modern wallet software generates keys derministically from some sort of master key, or seed phrase. That master key is stored in the wallet, and all other private keys are derived from it, ...
Does wallet.dat contain every address that I created? Even if I didn't get any coins from it?
To be clear, suppose I run bitcoin-qt in Linux, and, in the GUI, I click on Receive then click on Create new receiving address:
At this point, no coins are received. Will this immediately generate a new public-private key pair?
Yes. Well, not quite, but in ...
With bitcoin-core version 0.21, A default wallet is no longer automatically created
Here is the command to create a new wallet.
$ bitcoin-wallet -wallet=wallet.dat create
Topping up keypool...
HD (hd seed available): yes
Keypool Size: 2000
Address Book: 0
I would approach this using JSON-RPC with the programming language of your choice and the walletpassphrase command.
walletpassphrase "12345" 60
The 60 at the end is number of seconds before the passphrase times out and needs to be entered again. Now all you need to do is create a loop that iterates through all number combinations.
If the guess is ...
As you are using the Bitcoin Core wallet you can look at the right bottom if your wallet is locked or unlocked in the padlock icon.
Go to Window > Console and type: walletpassphrase "your passphrase" 60
After you type this command and you get an Error "The wallet passphrase entered was incorrect" that means your passphrase is wrong so ...
This is called steganography. Invented in Greece two and a half thousand years ago.
Usually, to make the embedded data inconspicuous the embedded data is distributed throughout the whole image as small variations in hue or luminance etc.
People viewing an image would notice an ugly and obvious rectangular patch in a corner. Especially as wallet data might ...
An encrypted wallet may be cracked if its password is weak with enough budget and computing power, while a watch-only wallet doesn't give any information other than the address and what can be derived from the address.
If you are using Bitcoin Core:
1 - Go to window > console
2 - Type listunspent
3 - You will get a list of addresses with the spendable amount
4 - Copy one of those addresses
5 - Type dumpprivkey pasteYourAddressHere
Electrum doesnt use wallet.dat file, those are used by Bitcoin Core. Electrum creates wallet files in %UserProfile%\AppData\Roaming\Electrum\\wallets for Windows, /home/user/.electrum/wallets/ for Linux and /data/data/org.electrum.electrum/files/data/wallets for Android. If forgot seed words, move BTC to another wallet and keep backup info safe if you can.
I finally got this. Here is a brief summary for the future searcher:
use the old software to launch the node with the old wallet.db file
run the dump wallet command. This creates a file that is in a text format that is more portable than bdb.
run load wallet command on the new node.
rescan the new node (the default scan does not look very far back)
Sure, if you know the addresses of your wallet, you can look it up in a Bitcoin block explorer, and find the current balance of each address. There are also wallets, like Electrum, that will use third party nodes to track your balance, but cryptographically verify everything to ensure the third party node cannot lie to you.
A technique with which I've had success in the past:
db5.3_dump corrupted_wallet.dat | db5.3_load fresh_wallet.dat
(obviously replacing corrupted_wallet.dat with the actual filename, and making a backup first).
and then trying to load fresh_wallet.dat into a modern Bitcoin Core
These tools are in the Ubuntu package db5.3-util.
Note: you'll need a Bitcoin ...
how i go more deeper in this to get those private keys and addresses?
Well the basic process I would start with would be
Don't use the computer that contains the damaged file
Use a bootable USB to make a copy of the file onto external media
Lock the computer away until you have repaired the file or extracted keys on a new computer
make copies of the ...
Generally, the wallet shipped with Bitcoin Core only keeps copies of any transactions that directly involve the wallet. When you import a key, your node scans the entire blockchain to see if any transactions involved that key.
A pruned node has processed the whole blockchain, but only keeps the tail end of the data. This means that when you import a private ...
Close core, find your bitcoin.conf file, and change the datadir setting. e.g.
# Specify a non-default location to store blockchain and other data.
Then re-open core. It should pick up where your wallet last synced to on the external drive.
Start Bitcoin Core with the wallet.dat you want to export
Dump your private keys via Bitcoin Core's Console using dumpwallet
You'll get a list of private key to address pairs in the following format:
L4ysibEFMBQc3hfr7tvUyV4nBP1YQ3AgDewszoYq5czMtXotmmro 2020-08-21T14:36:58Z change=1 #addr=bc1qpw40dkvcj23zt3efvdwqr7ddfunwktx11f3tjf
Extract all private keys (...
Commands can be entered after opening Window -> Console
in Bitcoin Core
Create a new empty wallet with
createwallet 'wallet_name' true
importmulti command with "watchonly": true