Admin: Created page with "This page describes the algorithm used for encrypting the '''wallet.dat''' file used in the original Bitcoin client. Wallet encryption uses [https..."

2019-03-27T06:33:44Z

Created page with "This page describes the algorithm used for encrypting the '''wallet.dat''' file used in the original Bitcoin client. Wallet encryption uses [https..."

New page

This page describes the algorithm used for encrypting the '''[[Wallet#Bitcoin_Core|wallet.dat]]''' file used in the original [[Bitcoin client]].

Wallet encryption uses [https://en.wikipedia.org/wiki/AES-256 <span title="Advanced Encryption Standard with 256 bit key and Cipher Block Chaining">AES-256-CBC</span>] to encrypt only the private keys that are held in a wallet. The keys are encrypted with a master key
which is entirely random. This master key is then encrypted with
AES-256-CBC with a key derived from the passphrase using [https://en.wikipedia.org/wiki/SHA-512 SHA-512] and
OpenSSL's <code>EVP_BytesToKey</code> and a dynamic number of rounds determined by
the speed of the machine which does the initial encryption (and is
updated based on the speed of a computer which does a subsequent
passphrase change). Although the underlying code supports multiple
encrypted copies of the same master key (and thus multiple passphrases)
the client does not yet have a method to add additional passphrases.

At runtime, the client loads the wallet as it normally would, however
the keystore stores the keys in encrypted form. When the passphrase
is required (to top up keypool or send coins) it will either be queried
by a GUI prompt, or must first be entered with the <code>walletpassphrase</code>
[[Original_Bitcoin_client/API_calls_list#Full_list|RPC command]]. This will change the wallet to "unlocked" state where the
unencrypted master key is stored in memory (in the case of GUI, only for
long enough to complete the requested operation, in RPC, for as long as
is specified by the second parameter to <code>walletpassphrase</code>). The wallet is
then locked (or can be manually locked using the <code>walletlock</code> RPC command)
and the unencrypted master key is removed from memory.

== Implementation details of wallet encryption ==

When the wallet is locked, calls to <code>sendtoaddress</code>, <code>sendfrom</code>, <code>sendmany</code>, and <code>keypoolrefill</code> will return ''Error -13: "Error: Please enter the wallet passphrase with walletpassphrase first."''

When the wallet is unlocked, calls to <code>walletpassphrase</code> will fail.

When a wallet is encrypted, the passphrase is required to top up the
keypool, thus, if the passphrase is rarely entered, it is possible that
keypool might run out. In this case, the default key will be used as the
target for payouts for mining, and calls to <code>getnewaddress</code> and <code>getaccount</code>
address will return an error. In order to prevent such cases, the keypool
is automatically refilled when <code>walletpassphrase</code> is called with a correct
passphrase and when <code>topupkeypool</code> is called (while the wallet is unlocked).
Note that the keypool continues to be topped up on various occasions when
a new key from pool is used and the wallet is unlocked (or unencrypted).

When wallet passphrase enrcyption becomes enabled, any unused keys from the keypool are flushed (marked as used) and new keys protected with encyption are added. <span style="color:red">For this reason, make a new backup of your wallet so that you will be able to recover the keys from the new key pool should access to your backups be necessary.</span>

==Source==

[http://bitcoin.it/ http://bitcoin.it/]

[[Category:EWallets]]
[[Category:Wallets]]
[[Category:Anonymity and security]]
[[Category:Bitcoin]]
==See Also on BitcoinWiki==
* [[Best Bitcoin Dice]]
* [[Gourl]]
* [[Bitcoin Jobs Report]]
* [[Test Cases]]
* [[Lets Talk Bitcoin]]

Wallet encryption - Revision history

Admin: Created page with "This page describes the algorithm used for encrypting the '''wallet.dat''' file used in the original Bitcoin client. Wallet encryption uses [https..."