Wallet: Difference between revisions
No edit summary |
→Armory: Specification |
||
| Line 23: | Line 23: | ||
=== [[Armory]] === | === [[Armory]] === | ||
The [[Armory]] client uses a custom [http://bitcoinarmory.com/developers/armory-wallet-files/ binary wallet format]. | The [[Armory]] client uses a custom [http://bitcoinarmory.com/developers/armory-wallet-files/ binary wallet format] and runs on top of Bitcoin-Core<ref>[https://www.bitcoinarmory.com Armory Bitcoin Wallet]</ref>. | ||
=== Blockchain.info === | === Blockchain.info === | ||
Revision as of 01:02, 28 May 2015
A Bitcoin wallet is a file that contains a collection of private keys.
Bitcoin Qt
The original Bitcoin client wallet file is named wallet.dat and contains[1]:
- keypairs for each of your addresses
- transactions done from/to your addresses
- user preferences
- default key
- reserve keys
- accounts
- a version number
- Key pool
- Since 0.3.21: information about the current best chain, to be able to rescan automatically when restoring from a backup.
The data file for the wallet is wallet.dat and is located in the Bitcoin data directory.
It is intended that a wallet be used on only one installation of Bitcoin at a time. Attempting to clone a wallet for use on multiple computers will result in "weird behavior"[2].
The format of this file is Berkeley DB. Tools that can manipulate wallet files include pywallet.
Armory
The Armory client uses a custom binary wallet format and runs on top of Bitcoin-Core[3].
Blockchain.info
Blockchain.info use a plain text JSON wallet format documented here. Private keys Keys are stored in base58.
Multibit
Multibit uses the bitcoinj protobuf wallet file.