Wallet-key-tool is an incredibly useful application with a graphical interface for those who deal with bitcoin wallets. It allows you to conveniently and securely edit the contents of various wallet file extensions, such as .dat/.key/.aes.json/.txt/.wallet. With this app, users can easily modify the data in their wallets without any hassle or risk of damage. It also provides additional features such as password protection and encryption to ensure maximum security of users’ funds and information.
Possibilities of wallet-key-tool:
- Read one format and export to another
- moving keys between different wallets, etc.
- add or remove keys
How to use WalletKeyTool
- GitHub: https://github.com/prof7bit/wallet-key-tool/releases/
IMPORTANT – The Wallet Key Tool requires java (v7.0+).
Through the graphical interface (GUI)
- On Windows you probably just need to double-click the .exe\.jar file and it will run (if you have Java installed, the GUI will not work without it).
- To open a file with a Bitcoin wallet: select the item “load wallet” and select your wallet. then the program will ask for a password (if the wallet file / wallet is encrypted). After entering the password, the main menu of the program will display all public and private keys.
Through the command line (CLI)
On systems where there is a command line interface (it also works on Windows, it’s a bit harder to find there, they really hate their own users), you can also run it by running the following command
java -jar wallet-key-tool.jar
This will open a GUI window that you can interact with, information and error messages will be printed to stderr. If you want to increase the log level, run it like this:
java -Dorg.slf4j.simpleLogger.defaultLogLevel=TRACE -jar wallet-key-tool.jar
Note: the -D option must go before the -jar option, it is passed directly to java. Acceptable log levels are ERROR, WARN, INFO, DEBUG, TRACE, the default is INFO, if you want to see stack traces, use TRACE.
If you just want to dump the contents of the wallet to the console without interacting with the GUI, you can give it a filename, if you do that, it will not try to open the GUI, it will just dump the contents of the wallet. to the standard output and output. Note that the dump format can still be changed, keep that in mind when writing a parser for it.
java -jar wallet-key-tool.jar <filename>
The program will prompt for a password in case the file is encrypted. If you want to avoid the password prompt, you can specify the password with key -password = “my passphrase” (you need quotes if it contains spaces). Example of a session in the console (I did not enter the passphrase, I just pressed Enter, so no private keys were decrypted):
java -jar build/libs/wallet-key-tool.jar /home/bernd/Schotter/Schotter.wallet [main] INFO org.multibit.store.MultiBitWalletProtobufSerializer - Loading wallet extension org.multibit.walletProtect.2 Wallet is encrypted. Enter passphrase: no passphrase entered, will skip decryption 1QKm5sWXuFJ6Zrvqw7NR7gYXyipPSqfv4n KEY DECRYPTION SKIPPED 1DrL3o6ZMAGttc96SPxqTo2yooq52P62kf KEY DECRYPTION SKIPPED 1E79vvzr1KkHXVXNUBwqoW7XDsMYULVqrq KEY DECRYPTION SKIPPED [...]