https://tests.bitcoin.it/w/api.php?action=feedcontributions&user=MagicFab&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-28T09:20:42ZUser contributionsMediaWiki 1.30.0https://tests.bitcoin.it/w/index.php?title=How_to_import_private_keys&diff=44388How to import private keys2014-02-10T12:22:41Z<p>MagicFab: /* Using BIPS */</p>
<hr />
<div>'''WARNING'''<br />
<br />
Before reading this page, users should note that messing with ECDSA private keys is very dangerous and can result in losing bitcoins, even long after the import.<br />
It is recommended that outside of self-generated vanity addresses, users should ''never'' import (or export) private keys.<br />
<br />
= Using Blockchain.info =<br />
As of August 2012, possibly the easiest way to import a private key is using [[Blockchain.info]]'s My Wallet service. When successully imported through the "Import/Export" screen, the bitcoins assigned to a private key can be immediately sent to any Bitcoin address.<br />
<br />
= Using BIPS =<br />
As of August 2013, [[File:BIPS.gif|20px|link=https://bips.me]] [[BIPS]] allows for easy import of private key using Paper Wallet - Import. User can choose to type in the private key manually or scan a QR code containing the private key using the camera. The user must wait 6 confirmations for access to the funds, and system is based on batch importation.<br />
<br />
= Using Mt. Gox =<br />
The [[MtGox]] Bitcoin exchange will allow individual private keys to be redeemed but since they must sweep the address, the user must wait 6 confirmations for access to the funds. There is an API method to import an entire wallet.dat as well.<br />
<br />
= Using Mycelium =<br />
Steps described are with the following settings:<br />
* Export mode enabled<br />
* Aggregated view disabled<br />
<br />
== Partial spend from cold storage ==<br />
Use this function if you would like to keep some funds on the paper wallet.<br />
# Download [https://play.google.com/store/apps/details?id=com.mycelium.wallet&hl=en Mycelium] from the Android Play Store<br />
# Press the menu button and select "Cold Storage"<br />
# Scan in private key<br />
# Select your destination address<br />
# Select the amount <br />
## Press the blue currency tag at the top to toggle currency.<br />
# Send!<br />
<br />
After spending, the private key in memory is destroyed so the paper private key remains somewhat secure.<br />
<br />
== Import key from a paper wallet ==<br />
Use this function if you would like to import a private key so all funds are immediately available for spending.<br />
# Download [https://play.google.com/store/apps/details?id=com.mycelium.wallet&hl=en Mycelium] from the Android Play Store<br />
# Key Management<br />
# Press the blue '+' symbol<br />
# Scan in private key<br />
<br />
After importing this paper private key, you might consider destroying the original so it cannot be found and your funds stolen. Alternatively, you can keep it safe to be used as an offline backup.<br />
<br />
= Using bitcoind =<br />
'''If you have Version 7 or later it is now trival.''' See: [[How to import private keys v7+]]<br />
<br />
If you are using [[Cold storage]], a [[Paper wallet]] or generating [https://bitcointalk.org/index.php?topic=25804.0 vanity addresses] you may have a need to import a [[Private key]]. Since Bitcoin-QT/bitcoind v0.6.0, you can import private keys using built-in RPC command [[importprivkey]]. Before v0.6.0, you needed to rely on third-party [[wallet.dat]] manipulation tool such as [[Pywallet]]. <br />
<br />
<br />
<br />
<br />
This article describes how to import a private key through the RPC API of bitcoind, which is a topic for advanced users.<br />
<br />
'''Note that importing a key to bitcoind and/or Bitcoin-Qt may be dangerous and is not recommended unless you understand the full details of how it works'''<br />
<br />
== Start Bitcoin client ==<br />
Unlike third-party wallet.dat manipulation tools such as [[Pywallet]], you do not have to close the Bitcoin client before proceeding. Instead, you need to start the bitcoind server.<br />
* Close bitcoin-qt and start ''bitcoind -damon'' in Terminal Emulator. The version of bitcoind MUST be the same as bitcoin-qt!<br />
<br />
Bitcoin-QT does not enable its RPC interface by default. To enable it:<br />
* Close Bitcoin-QT and restart it with ''bitcoin-qt -server''.<br />
<br />
== Unlock your wallet ==<br />
If you have an encrypted wallet (recommended), you need to unlock it temporarily before importing private keys. The RPC command for unlocking an encrypted wallet is ''walletpassphrase <passphrase> <timeout>''. Typing this directly in a bash terminal will leave your wallet passphrase directly in the bash history but there are a couple of techniques you can use to avoid this. Simply add a space before the command:<br />
<br />
(space)bitcoind walletpassphrase yourpassphrase 120<br />
<br />
Another alternative is to use a bash variable:<br />
<br />
read x<br />
(input your passphrase)<br />
bitcoind walletpassphrase "$x" 120 # Do not set the timeout too long or too short.<br />
<br />
== Import Private key(s) ==<br />
The last command unlocked your wallet temporarily for 120 seconds, during which time you must import your private keys. Since private keys can be as important as your passphrase, you may want to use the same techniques as above to prevent their being recorded in bash history (bash variable or space before the command):<br />
<br />
(space)bitcoind importprivkey "5yourveryveryveryverylongprivatekeystring" "my-new-key" # "my-new-key" is a label for the key/address pair and is optional<br />
<br />
The importing process is now started. Bitcoind will rescan the entire block data to ensure this key has not been used before. This process will take from one to two minutes, depending on your CPU performance. DO NOT abort it before finishing!<br />
<br />
If no errors occurs, the import is a success and Bitcoin-QT users will be able to see the new address in the GUI immediately. If you need to import more keys, just repeat the instructions above. There is currently no command to import a batch of private keys so you will need to wait a minute or two for each key to be imported.<br />
<br />
== Cleaning up ==<br />
<br />
bitcoind walletlock<br />
<br />
This will lock your wallet again (so you don't have to wait for timeout)<br />
<br />
unset x<br />
unset y<br />
<br />
These commands will clear the passphrase and private key from memory if you used the ''read'' technique. If you started bitcoind, you will need to stop it before Bitcoin-QT will start again:<br />
<br />
bitcoind stop<br />
<br />
===Deleting Keys===<br />
At some point, you may wish to delete private keys from a wallet.dat file but as of version v0.6.0 of Bitcoin-QT/bitcoind, there is no RPC method available for this purpose.<br />
<br />
[[Category:Instructional]]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=How_to_import_private_keys&diff=44387How to import private keys2014-02-10T12:22:02Z<p>MagicFab: /* Using Blockchain.info */ removed Mt. Gox mention</p>
<hr />
<div>'''WARNING'''<br />
<br />
Before reading this page, users should note that messing with ECDSA private keys is very dangerous and can result in losing bitcoins, even long after the import.<br />
It is recommended that outside of self-generated vanity addresses, users should ''never'' import (or export) private keys.<br />
<br />
= Using Blockchain.info =<br />
As of August 2012, possibly the easiest way to import a private key is using [[Blockchain.info]]'s My Wallet service. When successully imported through the "Import/Export" screen, the bitcoins assigned to a private key can be immediately sent to any Bitcoin address.<br />
<br />
= Using BIPS =<br />
As of August 2013, [[File:BIPS.gif|20px|link=https://bips.me]] [[BIPS]] allows for easy import of private key using Paper Wallet - Import. User can choose to type in the private key manually or scan a QR code containing the private key using the camera. The user must wait 6 confirmations for access to the funds, and system is based on batch importation.<br />
<br />
= Using Mycelium =<br />
Steps described are with the following settings:<br />
* Export mode enabled<br />
* Aggregated view disabled<br />
<br />
== Partial spend from cold storage ==<br />
Use this function if you would like to keep some funds on the paper wallet.<br />
# Download [https://play.google.com/store/apps/details?id=com.mycelium.wallet&hl=en Mycelium] from the Android Play Store<br />
# Press the menu button and select "Cold Storage"<br />
# Scan in private key<br />
# Select your destination address<br />
# Select the amount <br />
## Press the blue currency tag at the top to toggle currency.<br />
# Send!<br />
<br />
After spending, the private key in memory is destroyed so the paper private key remains somewhat secure.<br />
<br />
== Import key from a paper wallet ==<br />
Use this function if you would like to import a private key so all funds are immediately available for spending.<br />
# Download [https://play.google.com/store/apps/details?id=com.mycelium.wallet&hl=en Mycelium] from the Android Play Store<br />
# Key Management<br />
# Press the blue '+' symbol<br />
# Scan in private key<br />
<br />
After importing this paper private key, you might consider destroying the original so it cannot be found and your funds stolen. Alternatively, you can keep it safe to be used as an offline backup.<br />
<br />
= Using bitcoind =<br />
'''If you have Version 7 or later it is now trival.''' See: [[How to import private keys v7+]]<br />
<br />
If you are using [[Cold storage]], a [[Paper wallet]] or generating [https://bitcointalk.org/index.php?topic=25804.0 vanity addresses] you may have a need to import a [[Private key]]. Since Bitcoin-QT/bitcoind v0.6.0, you can import private keys using built-in RPC command [[importprivkey]]. Before v0.6.0, you needed to rely on third-party [[wallet.dat]] manipulation tool such as [[Pywallet]]. <br />
<br />
<br />
<br />
<br />
This article describes how to import a private key through the RPC API of bitcoind, which is a topic for advanced users.<br />
<br />
'''Note that importing a key to bitcoind and/or Bitcoin-Qt may be dangerous and is not recommended unless you understand the full details of how it works'''<br />
<br />
== Start Bitcoin client ==<br />
Unlike third-party wallet.dat manipulation tools such as [[Pywallet]], you do not have to close the Bitcoin client before proceeding. Instead, you need to start the bitcoind server.<br />
* Close bitcoin-qt and start ''bitcoind -damon'' in Terminal Emulator. The version of bitcoind MUST be the same as bitcoin-qt!<br />
<br />
Bitcoin-QT does not enable its RPC interface by default. To enable it:<br />
* Close Bitcoin-QT and restart it with ''bitcoin-qt -server''.<br />
<br />
== Unlock your wallet ==<br />
If you have an encrypted wallet (recommended), you need to unlock it temporarily before importing private keys. The RPC command for unlocking an encrypted wallet is ''walletpassphrase <passphrase> <timeout>''. Typing this directly in a bash terminal will leave your wallet passphrase directly in the bash history but there are a couple of techniques you can use to avoid this. Simply add a space before the command:<br />
<br />
(space)bitcoind walletpassphrase yourpassphrase 120<br />
<br />
Another alternative is to use a bash variable:<br />
<br />
read x<br />
(input your passphrase)<br />
bitcoind walletpassphrase "$x" 120 # Do not set the timeout too long or too short.<br />
<br />
== Import Private key(s) ==<br />
The last command unlocked your wallet temporarily for 120 seconds, during which time you must import your private keys. Since private keys can be as important as your passphrase, you may want to use the same techniques as above to prevent their being recorded in bash history (bash variable or space before the command):<br />
<br />
(space)bitcoind importprivkey "5yourveryveryveryverylongprivatekeystring" "my-new-key" # "my-new-key" is a label for the key/address pair and is optional<br />
<br />
The importing process is now started. Bitcoind will rescan the entire block data to ensure this key has not been used before. This process will take from one to two minutes, depending on your CPU performance. DO NOT abort it before finishing!<br />
<br />
If no errors occurs, the import is a success and Bitcoin-QT users will be able to see the new address in the GUI immediately. If you need to import more keys, just repeat the instructions above. There is currently no command to import a batch of private keys so you will need to wait a minute or two for each key to be imported.<br />
<br />
== Cleaning up ==<br />
<br />
bitcoind walletlock<br />
<br />
This will lock your wallet again (so you don't have to wait for timeout)<br />
<br />
unset x<br />
unset y<br />
<br />
These commands will clear the passphrase and private key from memory if you used the ''read'' technique. If you started bitcoind, you will need to stop it before Bitcoin-QT will start again:<br />
<br />
bitcoind stop<br />
<br />
===Deleting Keys===<br />
At some point, you may wish to delete private keys from a wallet.dat file but as of version v0.6.0 of Bitcoin-QT/bitcoind, there is no RPC method available for this purpose.<br />
<br />
[[Category:Instructional]]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Securing_your_wallet&diff=42820Securing your wallet2013-12-02T19:47:29Z<p>MagicFab: /* Introduction */</p>
<hr />
<div>==Introduction==<br />
<br />
Wallet security can be broken down into two independent goals:<br />
# Protecting your wallet against loss.<br />
# Protecting your wallet against theft.<br />
<br />
In the case that your current wallet hasn't been protected adequately (e.g. put online with a weaker password):<br />
# Making a new secure wallet, using appropriate long-term protection.<br />
<br />
''For a brief overview see also: [[Wallet Security Dos and Don'ts|Wallet Security Dos and Don'ts]]''<br />
<br />
==Paper Wallets==<br />
[[Paper wallet]]s are a fairly simple way to store your bitcoins independent of a computer. When generated securely and stored on paper, or other offline storage media, a paper wallet decreases the chances of your bitcoins being stolen by hackers, or computer viruses.<br />
<br />
With each entry on a paper wallet, you are securing a sequence of secret numbers that is used to prove your right to spend the bitcoins assigned to one of your addresses. This secret number, called a [[private key]], is most commonly written as a sequence of fifty-one alphanumeric characters, beginning with a '5'.<br />
<br />
One way you can create a paper wallet is by visiting the [[BitAddress|BitAddress.org]] or [[BitcoinPaperWallet|BitcoinPaperWallet.com]] websites. These websites feature a free client-side paper wallet generator written in JavaScript. The HTML for either of these generators can be downloaded from GitHub and used on an offline computer. Using either of these generators online by directly connecting to their websites is relatively safe for storing smaller amounts of bitcoin, but extra precautions should be taken to ensure that keys are not compromised by spyware that may be monitoring browser activity. Blockchain.info offers a [https://blockchain.info/wallet/paper-tutorial tutorial on how to generate a paper wallet] with an online component so you can check your balance easily.<br />
<br />
To generate a safer paper wallet, first save the paper wallet generating code to a newly-formatted USB stick. Then "clean-boot" your computer with a bootable CD (such as a Linux Live CD) ''while disconnected from the Internet''. Disconnecting from the Internet guarantees that that the paper wallet generator is truly self-contained and isn't communicating with an online service. Then insert the USB stick and open the wallet generator's HTML file from the web browser. Print your paper wallets or store them on external media (do not save them on the computer), and then shut down the computer. You may need to load an appropriate printer driver in order to print while booted from the live CD.<br />
<br />
A paper wallet includes at least one public bitcoin address and its corresponding private key. You can send bitcoins to the public address and they will be inaccessible until the private key is imported into a wallet. As of version 0.6.0, the bitcoin QT software has a command line feature called "importprivkey" that can load private keys. Online exchanges and wallets such as [[MtGox]], CoinBase and Blockchain.info have features for importing (or "sweeping") private keys as well.<br />
<br />
Remember, spyware and viruses often attempt to monitor your computer activities so that their authors can steal from you. They are interested in passwords to online accounts, and anything of value. Bitcoin wallets and private keys are something of value that have already been targeted by malware. Paper wallets isolate you from much of this risk.<br />
<br />
If your computer is infected with spyware or viruses - even if there are no symptoms, or your antivirus isn't reporting anything - then anything you type, view, or save on your computer, could potentially be stolen by someone remotely controlling your computer. Your private key can then be intercepted while you enter it, so only enter a Bitcoin private key into your computer when your intent is to redeem its value ''immediately''.<br />
<br />
== Hardware wallets ==<br />
They are not operational yet, but [[Hardware wallet]]s are a major effort to provide a good combination of enhanced security and usability.<br />
<br />
==Importance of security updates==<br />
<br />
No software is perfect, and from time to time there may be security vulnerabilities found in your Bitcoin client as well.<br />
Be sure you keep your client updated with the latest bug fixes, especially when a new vulnerability is discovered.<br />
We maintain a [[CVEs|list a known vulnerabilities]] on this wiki - you can watch that page to get updates.<br />
Note that you ''don't'' need to be running the latest major client version: some clients, including the popular Bitcoin-Qt, have older versions available with bugfix-only updates.<br />
<br />
==Securing the Bitcoin-QT or bitcoind wallet==<br />
<br />
Bitcoin transactions send Bitcoins to a specific public key. A Bitcoin address is an encoded hash of a public key. In order to use received Bitcoins, you need to have the private key matching the public key you received with. This is sort of like a super long password associated with an account (the account is the public key). Your Bitcoin wallet contains all of the private keys necessary for spending your received transactions. If you delete your wallet without a backup, then you no longer have the authorization information necessary to claim your coins, and the coins associated with those keys are lost forever.<br />
<br />
The wallet contains a pool of queued keys. By default there are 100 keys in the [[key pool]]. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.<br />
<br />
Creating a new address generates a new pair of public and private keys, which are added to your wallet. Each keypair is mostly random numbers, so they cannot be known prior to generation. If you backup your wallet and then create more than 100 new addresses, the keypair associated with the newest addresses will not be in the old wallet because the new keypairs are only known after creating them. Any coins received at these addresses will be lost if you restore from the backup.<br />
<br />
The situation is made somewhat more confusing because the receiving addresses shown in the UI are not the only keys in your wallet. Each Bitcoin generation is given a new public key, and, more importantly, each sent transaction also sends some number of Bitcoins back to yourself at a new key. When sending Bitcoins to anyone, you generate a new keypair for yourself and simultaneously send Bitcoins to your new public key and the actual recipient's public key. This is an anonymity feature – it makes tracking Bitcoin transactions much more difficult.<br />
<br />
So if you create a backup, do more than 100 things that cause a new key to be used, and then restore from the backup, some Bitcoins will be lost. Bitcoin has not deleted any keys (keys are never deleted) – it has created a new key that is not in your old backup and then sent Bitcoins to it.<br />
<br />
== Making a new wallet ==<br />
<br />
If a wallet or an encrypted wallet's password has been compromised, it is wise to create a new wallet and transfer the full balance of bitcoins to addresses contained only in the newly created wallet. Examples of ways a wallet may be compromised are through password re-use, minimal strength passwords, computer hack or virus attack.<br />
<br />
There are a number of ways to create a new wallet with Bitcoin-QT or bitcoind but this is a process that has been tested with bitcoind 0.6.3. We use the copy command to minimize the chance of any data loss but you are warned to make backups of any wallet.dat that holds a balance for you.<br />
<br />
:1. Shut down the Bitcoin program.<br />
:2. Find and make a backup of the "compromised" wallet.dat file and rename it, perhaps adding a short description:<br />
:::wallet.dat -> wallet-compromised.dat<br />
:Depending on your OS, the wallet file will be located at:<br />
:::Windows: %APPDATA%\Bitcoin\<br />
:::Linux: ~/.bitcoin/<br />
:::Mac: ~/Library/Application Support/Bitcoin/<br />
:3. Start the Bitcoin program and it will create a new wallet.dat. You may then encrypt the wallet as desired and make a new backup.<br />
:4. Once you've made a new wallet, you can obtain one or more addresses and copy them into a text editor. After obtaining the new address(es), shut down the Bitcoin program, make a backup of the new wallet.dat file and copy it to a new file named wallet-new.dat.<br />
:5. Copy the wallet-compromised.dat file back to wallet.dat, start the Bitcoin program and transfer your balance to the new address(es) you put in your text editor. Once the balance is back to 0 for your compromised wallet, you may want to wait a couple minutes or for a confirmation or check block explorer to be sure the transactions have been broadcasted. Then you may shut down the Bitcoin program.<br />
:6. Rename wallet.dat to wallet-compromised.dat. <br />
:7. Rename wallet-new.dat to wallet.dat.<br />
<br />
You should now have a new wallet with all the bitcoins from the old wallet.<br />
<br />
==Making a secure workspace==<br />
<br />
If you are using your computer to handle bitcoins, a wallet, Bitcoin-related passwords, or Bitcoin private keys, you must take care that the system is free of malware, viruses, keyloggers, remote access tools, and other tools that may be used to make remote copies of any of the above. In the case that your computer is compromised, the precautions taken below may provide additional protection.<br />
<br />
===Debian-based Linux===<br />
<br />
The first step is to make a [http://www.howtogeek.com/howto/ubuntu/add-a-user-on-ubuntu-server/ new user]. In order for that new user to have an encrypted home directory, you'll first need the encryption utility. Run:<br />
<br />
<code>sudo apt-get install ecryptfs-utils</code><br />
<br />
Now you're ready to create a new user<br />
<br />
<code>sudo adduser --encrypt-home new_user_name</code><br />
<br />
You'll need to come up with a [[#Choosing_A_Strong_Password|secure]] new password for that user.<br />
<br />
When you get to the prompt 'Enter the new value, or press ENTER for the default', just keep hitting ENTER.<br />
<br />
Then switch user to the new user. To get to the new user you can use the switch user icon for your system, which on Ubuntu is in the 'System/Quit' screen, or if there is no switch icon on your system you can log out and log back in as the new user.<br />
<br />
Since the home folder of this user is encrypted, if you're not logged in as that user, data that is saved there can't be browsed, even by a root user. If something goes wrong with your system, and you need to decrypt the new user's files, you'll need its decryption key.<br />
<br />
<code>ecryptfs-unwrap-passphrase</code><br />
<br />
It will ask you for your user's password and give you the decryption key. '''WRITE DOWN OR SAVE THE CODE IT RETURNS''' because you will need it if you ever have to pull your data off while the OS is not working. (You can run it again later if you need to, but run it now so that you can get your data if your Linux install gets botched.)<br />
<br />
The encrypted folder data is not encrypted while it's in memory, and so if it's ever sent to the swap partition it can be stolen from there unless that too is encrypted - be aware that this will mean you cannot use Hibernate anymore, as the bootloader won't be able to restore the hibernation data.<br />
<br />
<code>ecryptfs-setup-swap</code><br />
<br />
Then click on a folder in the new user to display the file browser, then keep going up folders until you see the new user home directory, then right click to bring up the Properties dialog, then click on the Permissions tab, then in the Others section, set the folder access to None.<br />
<br />
For secure browsing, open Firefox, and then go into the Edit menu and click Preferences. Starting from the left, click on the General tab, and in the 'Startup/When Firefox starts' pop up menu, choose 'Show a Blank Page'. Then click on the Content tab, and deselect 'Load images automatically' and deselect 'Enable JavaScript'. Then click on the Privacy tab, and in the 'History/Firefox will' pop up menu, choose 'Never remember history'. Then click on the Security tab, and in the Passwords section, deselect 'Remember passwords for sites' and deselect 'Use a master password'. Then click on the Advanced tab, then click on the Update tab, and then in the 'Automatically check for updates to' section, deselect 'Add-ons' and 'Search Engines'.<br />
<br />
When JavaScript is disabled, the [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.23/bitcoin-0.3.23-linux.tar.gz/download Linux download page] will not download automatically, so you'll have to click on the 'direct link' part of the "Problems with the download? Please use this 'direct link' or try another mirror." line.<br />
<br />
===Mac===<br />
This solution '''does not scale'''; the amount of needed space can grow beyond the image size.<br />
<br />
===Windows===<br />
<br />
Due to the frequency with which Windows computers are compromised, it is advised to encrypt your wallet or to keep your wallet on an encrypted disk image created by third-party software, such as [http://www.truecrypt.org/ TrueCrypt] (open source) or [http://www.jetico.com/encryption-bestcrypt/ Jetico BestCrypt] (commercial). This also applies to the storage of passwords, private keys and other data that can be used to access any of your Bitcoin balances.<br />
<br />
Assuming that you have installed the Windows Bitcoin client and run it at least once, the process is described below.<br />
<br />
<p><b>To mount the Bitcoin data directory on an encrypted drive</b></p><br />
<ol start=1 type=1><br />
<li>Use the third-party disk image encryption program of your choice to create and mount an encrypted disk image of at least 5GB in size. This procedure stores the entire block chain database with the wallet.dat file so the required size of the encrypted disk image required may grow in the future.</li><br />
<li>Locate the Bitcoin data directory, and copy the directory with all contents to the encrypted drive.<br />
<p>For help finding this directory, see <b>[[Securing_your_wallet#Locating_Bitcoin_s_data_directory|Locating Bitcoin's Data Directory]]</b>.</p></li><br />
<li>Create a Windows shortcut that starts Bitcoin with the <code>-datadir</code> parameter and specifies the encrypted drive and directory.<br />
<p>For example, if you installed Bitcoin in the default directory, mounted your Bitcoin encrypted drive as <code>E:\</code>, and stored your Bitcoin data directory on it as <code>Bitcoin</code>, you would type the following command as the shortcut Target:</p><br />
<blockquote><code>C:\Program Files\Bitcoin\bitcoin.exe -datadir=E:\Bitcoin</code></blockquote></li><br />
<li>Open Bitcoin's settings and configure it <b>NOT</b> to start automatically when you start Windows.<br />
<p>This is to allow you to mount the Bitcoin encrypted disk image before starting Bitcoin.</p></li><br />
<li>Shut down Bitcoin, and then restart it from the new shortcut.</li><br />
</ol><br />
<br />
After doing this, any time you want to use Bitcoin, you must first mount the Bitcoin encrypted disk image using the same drive designation, and then run Bitcoin from the shortcut that you created, so that it can find its data and your wallet.<br />
<br />
<br />
=== General Solutions ===<br />
<br />
Your wallet.dat file is not encrypted by the Bitcoin program by default but the most current release of the Bitcoin client provides a method to encrypt with a passphrase the private keys stored in the wallet. Anyone who can access an unencrypted wallet can easily steal all of your coins. Use one of these encryption programs if there is any chance someone might gain access to your wallet.<br />
* [http://www.7-zip.org/ 7-zip] - Supports strongly-encrypted archives.<br />
* [http://www.axantum.com/axcrypt/ AxCrypt by Axantum]<br />
* [http://lrzip.kolivas.org lrzip] - Compression software for Linux and OSX that supports very high grade password protected encryption<br />
* [http://www.truecrypt.org/ TrueCrypt] - Volume-based on-the-fly encryption (for advanced users)<br />
<br />
There is also a list of [[OpenSourceEncryptionSoftware|open source encryption software.]]<br />
<br />
Decrypting and encrypting the wallet.dat every time you start or quit the Bitcoin client can be ''tedious'' (and outright error-prone). If you want to keep your wallet encrypted (except while you're actually running the Bitcoin client), it's better to relegate the automation to a [http://lorelei.kaverit.org/bitcoin.sh small shell script] that handles the en/decryption and starting up Bitcoin client for you (Linux and OSX). <br />
<br />
There is also a method to print out and encrypt your wallet.dat as a special, scannable code. See details here: [[WalletPaperbackup]]<br />
<br />
==== Password Strength ====<br />
Brute-force password cracking has come a long way. A password including capitals, numbers, and special characters with a length of 8 characters can be trivially solved now (using appropriate hardware). The recommended length is '''at least''' 12 characters long. You can also use a multi-word password and there are techniques to increase the strength of your passwords without sacrificing usability. [http://www.baekdal.com/tips/password-security-usability The Usability of Passwords] <br />
<br />
However, simply using dictionary words is also insecure as it opens you up to a dictionary attack. If you use dictionary words, be sure to include random symbols and numbers in the mix as well.<br />
<br />
If you use keyfiles in addition to a password, it is unlikely that your encrypted file can ever be cracked using brute-force methods, even when even a 12 character password might be too short.<br />
<br />
Assume that any encrypted files you store online (eg. Gmail, Dropbox) will be stored somewhere forever and can never be erased.<br />
<br />
===== Choosing A Strong Password =====<br />
Make sure you pick at least one character in each group:<br /><br />
<br />
Lowercase: abcdefghijklmnopqrstuvwxyz<br />
Uppercase: ABCDEFGHIJKLMNOPQRSTUVWXYZ<br />
Number: 1234567890<br />
Symbol: `~!@#$%^&*()-_=+\|[{]};:'",<.>/? (space)<br />
<br />
<9 char = unsuitable for use<br />
09 char = insecure<br />
10 char = low security<br />
11 char = medium security<br />
12 char = good security (good enough for your wallet)<br />
13 char = very good, enough for anything.<br />
<br />
You might want to read [http://security.stackexchange.com/questions/662/what-is-your-way-to-create-good-passwords-that-can-actually-be-remembered What is your way to create good passwords that can actually be remembered?] and [http://security.stackexchange.com/questions/6095/xkcd-936-short-complex-password-or-long-dictionary-passphrase XKCD #936: Short complex password, or long dictionary passphrase?]<br />
<br />
== Backing up your wallet ==<br />
See [[Backingup_your_wallet|Backing up your wallet]].<br />
<br />
==Erasing Plain-text Wallets==<br />
<br />
In most operating systems, including Windows, Linux, and Mac OS X, simply deleting a wallet.dat file will ''not'' generally destroy it. It is likely that advanced tools can still be used to recover the wallet.dat file, even after it has been deleted.<br />
<br />
The Linux '''shred''' command can be used to overwrite the wallet file with random data prior to deleting; this particular copy of the file will then be practically impossible to recover. Using shred (and similar tools on Windows) however does not guarantee that still other copies don't exist somewhere hidden on your HD. That will depend on your system configuration and what packages you have installed. Some system restore and backup tools, for instance, create periodic snapshots of your filesystem, duplicating your wallet.dat.<br />
<br />
In Mac OS, the equivalent of '''shred''' is '''srm''' (introduced in Leopard). Using the Finder to remove files, clicking "Secure Empty Trash" in the Finder menu will shred the contents of the trash can. As with any OS this doesn't guarantee that there are not other copies elsewhere on your system.<br />
<br />
For Windows, the built-in command ''cipher /W'' will shred all previously-deleted files. [http://www.cylog.org/utilities/cybershredder.jsp CyberShredder] can securely deleted individual files.<br />
<br />
==Online and Mobile Wallets==<br />
<br />
Thus far, this article has been discussing the security of a wallet file for Bitcoin-QT or bitcoind that is under your sole control. Additional wallets applications and services have become available that offer other features and more convenience but not without introducing additional risk. When storing bitcoins with an [[eWallet]] such as Instawallet or Easywallet, you are essentially storing your private keys or wallet with that provider. <br />
<br />
Online wallets have a number of pros and cons to consider. For example, you can access your wallet on any computer in the world, but depending on the service, your bitcoins may be lost if the service is compromised. <br />
<br />
Mobile wallet applications are available for Android devices that allow you to send bitcoins by QR code or NFC, but this opens up the possibility of loss if mobile device is compromised. It may be possible to encrypt and backup the wallet or private keys on a mobile device but it is not advisable to store a large amount of bitcoins there without doing your own research and testing.<br />
<br />
==See Also==<br />
<br />
* [[Data directory]]<br />
* [[How to import private keys]]<br />
* [http://startbitcoin.com/how-to-create-a-secure-bitcoin-wallet/ Secure Bitcoin Wallet Tutorial]<br />
* [[How to set up a secure offline savings wallet]]<br />
* [http://arimaa.com/bitcoin/ Bitcoin Gateway - A Peer-to-peer Bitcoin Vault and Payment Network]<br />
* [http://blog.cyplo.net/2012/04/01/bitcoin-wallet-recovery-photorec/ Find lost wallet eg. after disk format, using Photorec]<br />
<br />
[[Category:Security]]<br />
<br />
[[de:Sichere deine Geldbörse]]<br />
[[ru:Bitcoin и безопасность]]<br />
[[es:Cómo asegurar su monedero]]<br />
[[zh-cn:保护你的钱包]]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Wallet_Security_Dos_and_Don%27ts_(general)&diff=42818Wallet Security Dos and Don'ts (general)2013-12-02T19:19:29Z<p>MagicFab: refactored from Windows Do's & don't s</p>
<hr />
<div>*'''Don't''' keep all your bitcoins in one wallet.<br />
<br />
*'''Don't''' develop a carefree attitude towards wallet security. Handle bitcoins with the same amount of diligence as you handle physical cash. <br />
<br />
*'''Don't''' use a password for wallet encryption that you use elsewhere on the web.<br />
<br />
*'''Don't''' use weak passwords. If a password is easy to remember without rehearsal, it is probably weak.<br />
<br />
*'''Don't''' forget your passwords. If you write them down on a piece of paper, keep that piece of paper in safe storage (safety box, etc.).<br />
<br />
*'''Don't''' run bitcoin wallet software on an untrusted or badly maintained machine. <br />
<br />
*'''Don't''' run software that has been copied illegally (eg, "warez")<br />
<br />
*'''Don't''' send bitcoins to a wallet that hasn't been backed up ''beforehand''.<br />
<br />
*'''Don't''' send [[Securing_your_wallet#General_Solutions|unencrypted]] copies of your wallets over the Internet.<br />
<br />
*'''Don't''' store unencrypted copies of your wallets on online backup/storage services.<br />
<br />
*'''Don't''' run or install programs from questionable sources on the system where you are running bitcoin wallet software.<br />
<br />
*'''Don't''' insert any devices of doubtful origin.<br />
<br />
*'''Don't''' store unencrypted copies of your wallets on a device that you insert into machines of friends, at work, or while traveling.<br />
<br />
<br />
*'''Do''' wipe your HD and perform a clean OS install if you believe your computer has been compromised.<br />
<br />
*'''Do''' keep at least one [[How to set up a secure offline savings wallet|offline savings wallet]].<br />
<br />
*'''Do''' backup your spending wallet regularly.<br />
<br />
*'''Do''' keep dated versions of each backed up wallet.<br />
<br />
*'''Do''' [[Securing_your_wallet#General_Solutions|encrypt]] all wallets as soon as they leave your system.<br />
<br />
*'''Do''' keep encrypted backups of all your wallets in at least 3 physically separate locations.<br />
<br />
*'''Do''' use strong, unique passwords to encrypt your wallets.<br />
<br />
*'''Do''' update your operating system with the latest security patches.<br />
<br />
*'''Do''' invest time and money in order to secure any large number of bitcoins you may have, just like you would with other valuables. If you lack the technical expertise, ask or pay somebody else to do it for you.</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Wallet_Security_Dos_and_Don%27ts_(Windows)&diff=42817Wallet Security Dos and Don'ts (Windows)2013-12-02T19:18:53Z<p>MagicFab: Refactored in transcluded files</p>
<hr />
<div>{{:Wallet Security Dos and Don'ts (intro)}}<br />
<br />
== In general ==<br />
{{:Wallet Security Dos and Don'ts (general)}}<br />
<br />
== When using Windows specifically ==<br />
<br />
*'''Do''' use [http://www.truecrypt.org/docs/?s=keyfiles keyfiles] to encrypt your wallets<br />
<br />
*'''Do''' use a good antivirus and firewall, and keep them up to date (but understand their limitations). <br />
<br />
*'''Do''' keep your installed programs updated to the latest version.<br />
<br />
*'''Do''' uninstall all programs that you don't use regularly.<br />
<br />
*'''Do''' run programs from questionable sources inside a virtual machine, such as [http://www.virtualbox.org/ VirtualBox].<br />
<br />
*'''Do''' browse questionable websites from inside a virtual machine.<br />
<br />
*'''Do''' connect the bitcoin client and IRC via [[Tor]]. <br />
<br />
<br />
[[Category:Instructional]]<br />
[[Category:Security]]<br />
<br />
[[es:Qué se debe y qué no se debe hacer respecto a la seguridad del monedero (Windows)]]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Wallet_Security_Dos_and_Don%27ts_(intro)&diff=42816Wallet Security Dos and Don'ts (intro)2013-12-02T19:18:17Z<p>MagicFab: Created page with "[Note - There are varying levels of security appropriate for the level of risk. The following might be general recommendations for consumer-level risks. Service providers an..."</p>
<hr />
<div>[Note - There are varying levels of security appropriate for the level of risk. The following might be general recommendations for consumer-level risks. Service providers and large investors requiring enterprise level security might have a very specific list of Dos and Dont's that varies from this list.]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Wallet_Security_Dos_and_Don%27ts_(general)&diff=42814Wallet Security Dos and Don'ts (general)2013-12-02T18:53:58Z<p>MagicFab: Testing transclusion of templates</p>
<hr />
<div>*If you own a large number of bitcoins, '''do''' invest time and money in order to secure them, just like you would with other valuables. If you lack the technical expertise, ask or pay somebody else to do it for you.<br />
<br />
*If you believe your computer has been compromised, '''do''' wipe your HD and perform a clean OS install.</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Securing_your_wallet&diff=42804Securing your wallet2013-12-02T16:38:29Z<p>MagicFab: Separated backup + restore in its own page</p>
<hr />
<div>==Introduction==<br />
<br />
Wallet security can be broken down into two independent goals:<br />
# Protecting your wallet against loss.<br />
# Protecting your wallet against theft.<br />
<br />
In the case that your current wallet hasn't been protected adequately (e.g. put online with a weaker password):<br />
# Making a new secure wallet, using appropriate long-term protection.<br />
<br />
''For a brief overview see also: [[Wallet Security Dos and Don'ts (Windows)|Wallet Security Dos and Don'ts]]''<br />
<br />
==Paper Wallets==<br />
[[Paper wallet]]s are a fairly simple way to store your bitcoins independent of a computer. When generated securely and stored on paper, or other offline storage media, a paper wallet decreases the chances of your bitcoins being stolen by hackers, or computer viruses.<br />
<br />
With each entry on a paper wallet, you are securing a sequence of secret numbers that is used to prove your right to spend the bitcoins assigned to one of your addresses. This secret number, called a [[private key]], is most commonly written as a sequence of fifty-one alphanumeric characters, beginning with a '5'.<br />
<br />
One way you can create a paper wallet is by visiting the [[BitAddress|BitAddress.org]] or [[BitcoinPaperWallet|BitcoinPaperWallet.com]] websites. These websites feature a free client-side paper wallet generator written in JavaScript. The HTML for either of these generators can be downloaded from GitHub and used on an offline computer. Using either of these generators online by directly connecting to their websites is relatively safe for storing smaller amounts of bitcoin, but extra precautions should be taken to ensure that keys are not compromised by spyware that may be monitoring browser activity. Blockchain.info offers a [https://blockchain.info/wallet/paper-tutorial tutorial on how to generate a paper wallet] with an online component so you can check your balance easily.<br />
<br />
To generate a safer paper wallet, first save the paper wallet generating code to a newly-formatted USB stick. Then "clean-boot" your computer with a bootable CD (such as a Linux Live CD) ''while disconnected from the Internet''. Disconnecting from the Internet guarantees that that the paper wallet generator is truly self-contained and isn't communicating with an online service. Then insert the USB stick and open the wallet generator's HTML file from the web browser. Print your paper wallets or store them on external media (do not save them on the computer), and then shut down the computer. You may need to load an appropriate printer driver in order to print while booted from the live CD.<br />
<br />
A paper wallet includes at least one public bitcoin address and its corresponding private key. You can send bitcoins to the public address and they will be inaccessible until the private key is imported into a wallet. As of version 0.6.0, the bitcoin QT software has a command line feature called "importprivkey" that can load private keys. Online exchanges and wallets such as [[MtGox]], CoinBase and Blockchain.info have features for importing (or "sweeping") private keys as well.<br />
<br />
Remember, spyware and viruses often attempt to monitor your computer activities so that their authors can steal from you. They are interested in passwords to online accounts, and anything of value. Bitcoin wallets and private keys are something of value that have already been targeted by malware. Paper wallets isolate you from much of this risk.<br />
<br />
If your computer is infected with spyware or viruses - even if there are no symptoms, or your antivirus isn't reporting anything - then anything you type, view, or save on your computer, could potentially be stolen by someone remotely controlling your computer. Your private key can then be intercepted while you enter it, so only enter a Bitcoin private key into your computer when your intent is to redeem its value ''immediately''.<br />
<br />
== Hardware wallets ==<br />
They are not operational yet, but [[Hardware wallet]]s are a major effort to provide a good combination of enhanced security and usability.<br />
<br />
==Importance of security updates==<br />
<br />
No software is perfect, and from time to time there may be security vulnerabilities found in your Bitcoin client as well.<br />
Be sure you keep your client updated with the latest bug fixes, especially when a new vulnerability is discovered.<br />
We maintain a [[CVEs|list a known vulnerabilities]] on this wiki - you can watch that page to get updates.<br />
Note that you ''don't'' need to be running the latest major client version: some clients, including the popular Bitcoin-Qt, have older versions available with bugfix-only updates.<br />
<br />
==Securing the Bitcoin-QT or bitcoind wallet==<br />
<br />
Bitcoin transactions send Bitcoins to a specific public key. A Bitcoin address is an encoded hash of a public key. In order to use received Bitcoins, you need to have the private key matching the public key you received with. This is sort of like a super long password associated with an account (the account is the public key). Your Bitcoin wallet contains all of the private keys necessary for spending your received transactions. If you delete your wallet without a backup, then you no longer have the authorization information necessary to claim your coins, and the coins associated with those keys are lost forever.<br />
<br />
The wallet contains a pool of queued keys. By default there are 100 keys in the [[key pool]]. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.<br />
<br />
Creating a new address generates a new pair of public and private keys, which are added to your wallet. Each keypair is mostly random numbers, so they cannot be known prior to generation. If you backup your wallet and then create more than 100 new addresses, the keypair associated with the newest addresses will not be in the old wallet because the new keypairs are only known after creating them. Any coins received at these addresses will be lost if you restore from the backup.<br />
<br />
The situation is made somewhat more confusing because the receiving addresses shown in the UI are not the only keys in your wallet. Each Bitcoin generation is given a new public key, and, more importantly, each sent transaction also sends some number of Bitcoins back to yourself at a new key. When sending Bitcoins to anyone, you generate a new keypair for yourself and simultaneously send Bitcoins to your new public key and the actual recipient's public key. This is an anonymity feature – it makes tracking Bitcoin transactions much more difficult.<br />
<br />
So if you create a backup, do more than 100 things that cause a new key to be used, and then restore from the backup, some Bitcoins will be lost. Bitcoin has not deleted any keys (keys are never deleted) – it has created a new key that is not in your old backup and then sent Bitcoins to it.<br />
<br />
== Making a new wallet ==<br />
<br />
If a wallet or an encrypted wallet's password has been compromised, it is wise to create a new wallet and transfer the full balance of bitcoins to addresses contained only in the newly created wallet. Examples of ways a wallet may be compromised are through password re-use, minimal strength passwords, computer hack or virus attack.<br />
<br />
There are a number of ways to create a new wallet with Bitcoin-QT or bitcoind but this is a process that has been tested with bitcoind 0.6.3. We use the copy command to minimize the chance of any data loss but you are warned to make backups of any wallet.dat that holds a balance for you.<br />
<br />
:1. Shut down the Bitcoin program.<br />
:2. Find and make a backup of the "compromised" wallet.dat file and rename it, perhaps adding a short description:<br />
:::wallet.dat -> wallet-compromised.dat<br />
:Depending on your OS, the wallet file will be located at:<br />
:::Windows: %APPDATA%\Bitcoin\<br />
:::Linux: ~/.bitcoin/<br />
:::Mac: ~/Library/Application Support/Bitcoin/<br />
:3. Start the Bitcoin program and it will create a new wallet.dat. You may then encrypt the wallet as desired and make a new backup.<br />
:4. Once you've made a new wallet, you can obtain one or more addresses and copy them into a text editor. After obtaining the new address(es), shut down the Bitcoin program, make a backup of the new wallet.dat file and copy it to a new file named wallet-new.dat.<br />
:5. Copy the wallet-compromised.dat file back to wallet.dat, start the Bitcoin program and transfer your balance to the new address(es) you put in your text editor. Once the balance is back to 0 for your compromised wallet, you may want to wait a couple minutes or for a confirmation or check block explorer to be sure the transactions have been broadcasted. Then you may shut down the Bitcoin program.<br />
:6. Rename wallet.dat to wallet-compromised.dat. <br />
:7. Rename wallet-new.dat to wallet.dat.<br />
<br />
You should now have a new wallet with all the bitcoins from the old wallet.<br />
<br />
==Making a secure workspace==<br />
<br />
If you are using your computer to handle bitcoins, a wallet, Bitcoin-related passwords, or Bitcoin private keys, you must take care that the system is free of malware, viruses, keyloggers, remote access tools, and other tools that may be used to make remote copies of any of the above. In the case that your computer is compromised, the precautions taken below may provide additional protection.<br />
<br />
===Debian-based Linux===<br />
<br />
The first step is to make a [http://www.howtogeek.com/howto/ubuntu/add-a-user-on-ubuntu-server/ new user]. In order for that new user to have an encrypted home directory, you'll first need the encryption utility. Run:<br />
<br />
<code>sudo apt-get install ecryptfs-utils</code><br />
<br />
Now you're ready to create a new user<br />
<br />
<code>sudo adduser --encrypt-home new_user_name</code><br />
<br />
You'll need to come up with a [[#Choosing_A_Strong_Password|secure]] new password for that user.<br />
<br />
When you get to the prompt 'Enter the new value, or press ENTER for the default', just keep hitting ENTER.<br />
<br />
Then switch user to the new user. To get to the new user you can use the switch user icon for your system, which on Ubuntu is in the 'System/Quit' screen, or if there is no switch icon on your system you can log out and log back in as the new user.<br />
<br />
Since the home folder of this user is encrypted, if you're not logged in as that user, data that is saved there can't be browsed, even by a root user. If something goes wrong with your system, and you need to decrypt the new user's files, you'll need its decryption key.<br />
<br />
<code>ecryptfs-unwrap-passphrase</code><br />
<br />
It will ask you for your user's password and give you the decryption key. '''WRITE DOWN OR SAVE THE CODE IT RETURNS''' because you will need it if you ever have to pull your data off while the OS is not working. (You can run it again later if you need to, but run it now so that you can get your data if your Linux install gets botched.)<br />
<br />
The encrypted folder data is not encrypted while it's in memory, and so if it's ever sent to the swap partition it can be stolen from there unless that too is encrypted - be aware that this will mean you cannot use Hibernate anymore, as the bootloader won't be able to restore the hibernation data.<br />
<br />
<code>ecryptfs-setup-swap</code><br />
<br />
Then click on a folder in the new user to display the file browser, then keep going up folders until you see the new user home directory, then right click to bring up the Properties dialog, then click on the Permissions tab, then in the Others section, set the folder access to None.<br />
<br />
For secure browsing, open Firefox, and then go into the Edit menu and click Preferences. Starting from the left, click on the General tab, and in the 'Startup/When Firefox starts' pop up menu, choose 'Show a Blank Page'. Then click on the Content tab, and deselect 'Load images automatically' and deselect 'Enable JavaScript'. Then click on the Privacy tab, and in the 'History/Firefox will' pop up menu, choose 'Never remember history'. Then click on the Security tab, and in the Passwords section, deselect 'Remember passwords for sites' and deselect 'Use a master password'. Then click on the Advanced tab, then click on the Update tab, and then in the 'Automatically check for updates to' section, deselect 'Add-ons' and 'Search Engines'.<br />
<br />
When JavaScript is disabled, the [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.23/bitcoin-0.3.23-linux.tar.gz/download Linux download page] will not download automatically, so you'll have to click on the 'direct link' part of the "Problems with the download? Please use this 'direct link' or try another mirror." line.<br />
<br />
===Mac===<br />
This solution '''does not scale'''; the amount of needed space can grow beyond the image size.<br />
<br />
===Windows===<br />
<br />
Due to the frequency with which Windows computers are compromised, it is advised to encrypt your wallet or to keep your wallet on an encrypted disk image created by third-party software, such as [http://www.truecrypt.org/ TrueCrypt] (open source) or [http://www.jetico.com/encryption-bestcrypt/ Jetico BestCrypt] (commercial). This also applies to the storage of passwords, private keys and other data that can be used to access any of your Bitcoin balances.<br />
<br />
Assuming that you have installed the Windows Bitcoin client and run it at least once, the process is described below.<br />
<br />
<p><b>To mount the Bitcoin data directory on an encrypted drive</b></p><br />
<ol start=1 type=1><br />
<li>Use the third-party disk image encryption program of your choice to create and mount an encrypted disk image of at least 5GB in size. This procedure stores the entire block chain database with the wallet.dat file so the required size of the encrypted disk image required may grow in the future.</li><br />
<li>Locate the Bitcoin data directory, and copy the directory with all contents to the encrypted drive.<br />
<p>For help finding this directory, see <b>[[Securing_your_wallet#Locating_Bitcoin_s_data_directory|Locating Bitcoin's Data Directory]]</b>.</p></li><br />
<li>Create a Windows shortcut that starts Bitcoin with the <code>-datadir</code> parameter and specifies the encrypted drive and directory.<br />
<p>For example, if you installed Bitcoin in the default directory, mounted your Bitcoin encrypted drive as <code>E:\</code>, and stored your Bitcoin data directory on it as <code>Bitcoin</code>, you would type the following command as the shortcut Target:</p><br />
<blockquote><code>C:\Program Files\Bitcoin\bitcoin.exe -datadir=E:\Bitcoin</code></blockquote></li><br />
<li>Open Bitcoin's settings and configure it <b>NOT</b> to start automatically when you start Windows.<br />
<p>This is to allow you to mount the Bitcoin encrypted disk image before starting Bitcoin.</p></li><br />
<li>Shut down Bitcoin, and then restart it from the new shortcut.</li><br />
</ol><br />
<br />
After doing this, any time you want to use Bitcoin, you must first mount the Bitcoin encrypted disk image using the same drive designation, and then run Bitcoin from the shortcut that you created, so that it can find its data and your wallet.<br />
<br />
<br />
=== General Solutions ===<br />
<br />
Your wallet.dat file is not encrypted by the Bitcoin program by default but the most current release of the Bitcoin client provides a method to encrypt with a passphrase the private keys stored in the wallet. Anyone who can access an unencrypted wallet can easily steal all of your coins. Use one of these encryption programs if there is any chance someone might gain access to your wallet.<br />
* [http://www.7-zip.org/ 7-zip] - Supports strongly-encrypted archives.<br />
* [http://www.axantum.com/axcrypt/ AxCrypt by Axantum]<br />
* [http://lrzip.kolivas.org lrzip] - Compression software for Linux and OSX that supports very high grade password protected encryption<br />
* [http://www.truecrypt.org/ TrueCrypt] - Volume-based on-the-fly encryption (for advanced users)<br />
<br />
There is also a list of [[OpenSourceEncryptionSoftware|open source encryption software.]]<br />
<br />
Decrypting and encrypting the wallet.dat every time you start or quit the Bitcoin client can be ''tedious'' (and outright error-prone). If you want to keep your wallet encrypted (except while you're actually running the Bitcoin client), it's better to relegate the automation to a [http://lorelei.kaverit.org/bitcoin.sh small shell script] that handles the en/decryption and starting up Bitcoin client for you (Linux and OSX). <br />
<br />
There is also a method to print out and encrypt your wallet.dat as a special, scannable code. See details here: [[WalletPaperbackup]]<br />
<br />
==== Password Strength ====<br />
Brute-force password cracking has come a long way. A password including capitals, numbers, and special characters with a length of 8 characters can be trivially solved now (using appropriate hardware). The recommended length is '''at least''' 12 characters long. You can also use a multi-word password and there are techniques to increase the strength of your passwords without sacrificing usability. [http://www.baekdal.com/tips/password-security-usability The Usability of Passwords] <br />
<br />
However, simply using dictionary words is also insecure as it opens you up to a dictionary attack. If you use dictionary words, be sure to include random symbols and numbers in the mix as well.<br />
<br />
If you use keyfiles in addition to a password, it is unlikely that your encrypted file can ever be cracked using brute-force methods, even when even a 12 character password might be too short.<br />
<br />
Assume that any encrypted files you store online (eg. Gmail, Dropbox) will be stored somewhere forever and can never be erased.<br />
<br />
===== Choosing A Strong Password =====<br />
Make sure you pick at least one character in each group:<br /><br />
<br />
Lowercase: abcdefghijklmnopqrstuvwxyz<br />
Uppercase: ABCDEFGHIJKLMNOPQRSTUVWXYZ<br />
Number: 1234567890<br />
Symbol: `~!@#$%^&*()-_=+\|[{]};:'",<.>/? (space)<br />
<br />
<9 char = unsuitable for use<br />
09 char = insecure<br />
10 char = low security<br />
11 char = medium security<br />
12 char = good security (good enough for your wallet)<br />
13 char = very good, enough for anything.<br />
<br />
You might want to read [http://security.stackexchange.com/questions/662/what-is-your-way-to-create-good-passwords-that-can-actually-be-remembered What is your way to create good passwords that can actually be remembered?] and [http://security.stackexchange.com/questions/6095/xkcd-936-short-complex-password-or-long-dictionary-passphrase XKCD #936: Short complex password, or long dictionary passphrase?]<br />
<br />
== Backing up your wallet ==<br />
See [[Backingup_your_wallet|Backing up your wallet]].<br />
<br />
==Erasing Plain-text Wallets==<br />
<br />
In most operating systems, including Windows, Linux, and Mac OS X, simply deleting a wallet.dat file will ''not'' generally destroy it. It is likely that advanced tools can still be used to recover the wallet.dat file, even after it has been deleted.<br />
<br />
The Linux '''shred''' command can be used to overwrite the wallet file with random data prior to deleting; this particular copy of the file will then be practically impossible to recover. Using shred (and similar tools on Windows) however does not guarantee that still other copies don't exist somewhere hidden on your HD. That will depend on your system configuration and what packages you have installed. Some system restore and backup tools, for instance, create periodic snapshots of your filesystem, duplicating your wallet.dat.<br />
<br />
In Mac OS, the equivalent of '''shred''' is '''srm''' (introduced in Leopard). Using the Finder to remove files, clicking "Secure Empty Trash" in the Finder menu will shred the contents of the trash can. As with any OS this doesn't guarantee that there are not other copies elsewhere on your system.<br />
<br />
For Windows, the built-in command ''cipher /W'' will shred all previously-deleted files. [http://www.cylog.org/utilities/cybershredder.jsp CyberShredder] can securely deleted individual files.<br />
<br />
==Online and Mobile Wallets==<br />
<br />
Thus far, this article has been discussing the security of a wallet file for Bitcoin-QT or bitcoind that is under your sole control. Additional wallets applications and services have become available that offer other features and more convenience but not without introducing additional risk. When storing bitcoins with an [[eWallet]] such as Instawallet or Easywallet, you are essentially storing your private keys or wallet with that provider. <br />
<br />
Online wallets have a number of pros and cons to consider. For example, you can access your wallet on any computer in the world, but depending on the service, your bitcoins may be lost if the service is compromised. <br />
<br />
Mobile wallet applications are available for Android devices that allow you to send bitcoins by QR code or NFC, but this opens up the possibility of loss if mobile device is compromised. It may be possible to encrypt and backup the wallet or private keys on a mobile device but it is not advisable to store a large amount of bitcoins there without doing your own research and testing.<br />
<br />
==See Also==<br />
<br />
* [[Data directory]]<br />
* [[How to import private keys]]<br />
* [http://startbitcoin.com/how-to-create-a-secure-bitcoin-wallet/ Secure Bitcoin Wallet Tutorial]<br />
* [[How to set up a secure offline savings wallet]]<br />
* [http://arimaa.com/bitcoin/ Bitcoin Gateway - A Peer-to-peer Bitcoin Vault and Payment Network]<br />
* [http://blog.cyplo.net/2012/04/01/bitcoin-wallet-recovery-photorec/ Find lost wallet eg. after disk format, using Photorec]<br />
<br />
[[Category:Security]]<br />
<br />
[[de:Sichere deine Geldbörse]]<br />
[[ru:Bitcoin и безопасность]]<br />
[[es:Cómo asegurar su monedero]]<br />
[[zh-cn:保护你的钱包]]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Backing_up_your_wallet&diff=42803Backing up your wallet2013-12-02T16:29:16Z<p>MagicFab: Added Email archival, offline storage, automated backup in Gnu/Linux, from Securing your wallet</p>
<hr />
<div>== Locating Bitcoin's data directory ==<br />
The [[data directory]] is the location where Bitcoin's data files are stored, including the wallet data file.<br />
<br />
=== Gnu/Linux ===<br />
<br />
By default Bitcoin will put its data here:<br />
<br />
~/.bitcoin/<br />
<br />
You need to do a "ls -a" to see directories that start with a dot.<br />
<br />
If that's not it, you can do a search like this:<br />
<br />
find / -name wallet.dat -print 2>/dev/null<br />
<br />
To change the directory Bitcoin stores its data in:<br />
Run in terminal or script: ./bitcoin-qt -datadir=./[Directory_Name]<br />
<br />
=== Mac OSX ===<br />
<br />
By default Bitcoin will put its data here:<br />
<br />
~/Library/Application Support/Bitcoin/<br />
<br />
=== Windows ===<br />
Go to Start -> Run (or press WinKey+R) and run this:<br />
<br />
explorer %APPDATA%\Bitcoin<br />
<br />
Bitcoin's data folder will open. For most users, this is one of the following locations:<br />
<br />
C:\Documents and Settings\YourUserName\Application data\Bitcoin (Windows XP)<br />
<br />
C:\Users\YourUserName\Appdata\Roaming\Bitcoin (Windows Vista and 7)<br />
<br />
If you have trouble browsing to these folders, note that "AppData" and "Application data" are hidden by default.<br />
<br />
==Backing up your wallet files==<br />
<br />
'''Note''': Using Dropbox to back up your Bitcoin data is not recommended as doing so introduces the following [https://en.wikipedia.org/wiki/Dropbox_(service)#Reception security concerns]:<br />
<br />
# Dropbox stores your encryption key (meaning that a disgruntled Dropbox employee or an attacker who gained access to the system could decrypt your Dropbox data and steal your bitcoins)<br />
# the Dropbox client only needs a password for the first login. After it authenticates once, the server assigns it a token which it uses to show that, at one time, its user knew the password rather than sending the actual password (meaning that if you ever use the Dropbox client on another PC, that PC's users can access your Dropbox - even if you change your password - and can steal your bitcoins or get a virus that will steal your bitcoins).<br />
<br />
For these reasons, an alternative that always uses password authentication such as [http://www.wuala.com/en/bitcoin Wuala] should be used. Wuala's servers do not store your encryption key and the program authenticates with the password each time it is started.<br />
<br />
Whether you use Dropbox as your backup or not, it is advised to use what Steve Gibson calls "pre-Internet encryption" which means to use some form of encryption on your files before you back them up, in case an attacker gains access to that backup. Make sure to pick a password that is memorable but secure.<br />
<br />
The only file you need to back up is "wallet.dat" which can be done one of two ways. To make a copy of the wallet.dat file, ensure that Bitcoin is closed and copy this file somewhere else. The other way is to use the [[api|backupwallet]] JSON-RPC command to back up without shutting down Bitcoin. <br />
<br />
Once a copy has been made, encrypt it, and put it in two or more safe locations. Consider the risk due to theft, fire, or natural disaster in proportion to the value of bitcoins stored in the wallet.<br />
<br />
===Backup wallet and blochain data===<br />
Follow these instructions to backup all the bitcoin data (wallet and block chains) to an encrypted disk image.<br />
# Open Disk Utility<br />
# Click New Image and choose a big enough size, 128-bit or 256-bit (faster or more secure) encryption and single partition.<br />
# Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)<br />
# Choose a safe and strong password<br />
# Move everything from ~/Library/Application Support/Bitcoin/ to the image<br />
# Symlink it back so the app would be able to use it<br />
:::ln -s /Volumes/Bitcoin ~/Library/Application Support/Bitcoin<br />
<br />
Don't forget to mount your image before using Bitcoin and unmount it after quitting.<br />
<br />
===Backing up just your wallet file===<br />
Follow these instructions to backup just the wallet.dat file. This results in a smaller disk image, but it's more complicated to do.<br />
# Open Disk Utility<br />
# Click New Image and choose a big enough size, 128-bit or 256-bit (faster or more secure) encryption and single partition.<br />
# Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)<br />
# Choose a safe and strong password<br />
# Move your wallet.dat file to the image<br />
# Symlink it back so the app would be able to use it<br />
:::ln -s /Volumes/Bitcoin/wallet.dat ~/Library/Application Support/Bitcoin/wallet.dat<br />
<br />
[[File:MountWalletAndLauchnBitcoin_OSX_Automator.png|thumbnail|150px|Mount Wallet and launch Bitcoin]]<br />
Don't forget to mount your image before using Bitcoin and unmount after quitting it.<br />
<br />
'''Note''': If you start the Bitcoin application without having the image mounted, the application will overwrite your symlink with a new wallet. If that happens, don't panic. Just delete the new wallet.dat, mount the image, and recreate the symlink like above.<br />
<br />
'''Automation''': You can create a small application using [http://en.wikipedia.org/wiki/Automator_%28software%29 Automator] (included in OS X) to automatically mount the wallet and then launch Bitcoin App. See the Screenshot on how to do this.<br />
<br />
If one ''doesn't'' want to use encrypted Disk images, then a '''small shell script''' can be used instead that takes care of decrypting the wallet, launching bitcoin client, and encrypting it after the client exits. This script works on both OSX and Gnu/Linux: [http://lorelei.kaverit.org/bitcoin.sh bitcoin-launch-script]<br />
<br />
=== Email-based Archival and Remote Backup ===<br />
One of the simplest methods for storing an appropriately '''encrypted''' archive of your wallet.dat file is to send the archive as an email attachment to your own e-mail address. Services like Gmail use very comprehensive distributed networks that make the loss of data very unlikely. One can even obfuscate the name of the files within the archive, and name the archive something less inviting, such as: 'personal notes' or 'car insurance'.<br />
<br />
Another solution is to use a file storage service like [http://www.wuala.com/bitcoin Wuala] ( encrypted, [http://www.bitcoin.org/smf/index.php?topic=5817.0 instructions]), [http://www.dropbox.com Dropbox] (after encrypting the wallet first) and [http://en.wikipedia.org/wiki/Comparison_of_online_backup_services others], including the more secure [http://www.spideroak.com SpiderOak].<br />
<br />
=== Automated backups using Cron, Bash and GNU/Linux ===<br />
<br />
Linux users can setup backups using cron by telling it to run a backup script at set intervals of time. Run 'crontab -e' and add this line near the bottom:<br />
<br />
01 * * * * /usr/local/bin/backupwallet.sh<br />
<br />
This cron line will run the /usr/local/bin/backupwallet.sh script at the 01 minute of every hour. Remember to add a newline after the last line of the crontab file, or else the last line won't run. You may also wish to ignore the script's output by appending " > /dev/null 2>&1" to the line (this will also prevent emails from being sent).<br />
<br />
Create /usr/local/bin/backupwallet.sh:<br />
<br />
#!/bin/bash<br />
# /usr/local/bin/backupwallet.sh<br />
#<br />
# Performs backup of bitcoin wallet.<br />
#<br />
# Written by: https://en.bitcoin.it/wiki/Securing_your_wallet<br />
<br />
#<br />
# Standard Options<br />
#<br />
TS=$(date "+%Y%m%d-%H%M")<br />
WALLET=/tmp/wallet-${TS}<br />
WALLET_E=/tmp/wallet-${TS}.crypt<br />
BITCOIN=bitcoind # /path/to/bitcoind<br />
GPG=gpg # /path/to/gpg<br />
GPG_USER=username # Username of gpg recipient. User should have gpg setup.<br />
RM=rm<br />
RM_OPTS='--force'<br />
USE_SHRED=0 # Flip to 1 to use `shred` instead of `rm`.<br />
SHRED=shred<br />
SHRED_OPTS='--force --iterations=9 --zero --remove'<br />
<br />
#<br />
# Storage Options<br />
# Only 1 set of options should be un-commented (the last one will be used).<br />
# Update CP_DEST paths as neccessary.<br />
#<br />
# CP - Storage on a local machine. Could be Dropbox/Wuala folder.<br />
#CP=cp<br />
#CP_DEST='/var/data/backups/' # '~/Dropbox/', etc.<br />
#<br />
# SSH - Storage on a remote machine.<br />
CP=scp<br />
CP_DEST='remoteuser@example.com:~/wallets/'<br />
#<br />
# S3 - Storage on Amazon's S3. Be sure s3cmd is installed and properly setup.<br />
# You may need "s3cmd put --force" if you use a sub-directory in CP_DEST.<br />
#CP=s3cmd put<br />
#CP_DEST='s3://bucket'<br />
<br />
do_clean() {<br />
# Remove temporary wallets.<br />
if [ 1 -eq $USE_SHRED ]; then<br />
$SHRED $SHRED_OPTS $WALLET $WALLET_E<br />
else<br />
$RM $RM_OPTS $WALLET $WALLET_E<br />
fi<br />
}<br />
<br />
do_fail() {<br />
do_clean<br />
echo failed!<br />
exit 1<br />
}<br />
<br />
# Perform the backup.<br />
echo -n Making backup...<br />
$BITCOIN backupwallet $WALLET<br />
[ ! -s "$WALLET" ] && do_fail # If the backup does not exist or is empty, fail.<br />
echo done.<br />
echo -n Encrypting backup...<br />
$GPG -r $GPG_USER --output $WALLET_E --encrypt $WALLET<br />
[ 0 -ne $? ] && do_fail # If gpg returns a non-zero result, fail.<br />
echo done.<br />
echo -n Copying to backup location...<br />
$CP $WALLET_E "$CP_DEST"<br />
[ 0 -ne $? ] && do_fail # If the $CP command returns a non-zero result, fail.<br />
echo done.<br />
do_clean<br />
<br />
exit 0<br />
<br />
The shell script:<br />
<br />
* Calls bitcoind backupwallet to create a time/date-stamped wallet.<br />
* GPG encrypts the wallet with your public key.<br />
* Copies the result using one of several storage options (cp, scp, and s3cmd).<br />
* Uses the rm or shred command to remove the temporary wallet files.<br />
<br />
Be sure to modify the script options to fit your setup. After you save, make sure the file can be executed properly by the cron user. Common permissions for files in /usr/local/bin/ can be applied using (verify with your distribution!):<br />
<br />
cd /usr/local/bin/ && chown root:root backupwallet.sh && chmod 755 backupwallet.sh<br />
<br />
==Restoring your wallet file==<br />
<br />
Assuming your backup is recent enough that you haven't used up all of your key pool... restoring a wallet to a new (or old) location and rescanning the block chain should leave you with all your coins. Just follow these steps:<br />
* Shut down the Bitcoin program.<br />
* Copy your backed-up wallet.dat into your bitcoin data directory.<br />
* If you are copying in a backed-up wallet.dat that was last used on a Bitcoin version prior to 0.3.21 into an existing profile, delete files ''blk*.dat'' to make the client re-download the block chain. You may also need to do this if your transactions don't all show up after you restart Bitcoin.</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Backing_up_your_wallet&diff=42802Backing up your wallet2013-12-02T16:22:14Z<p>MagicFab: Added restore section</p>
<hr />
<div>== Locating Bitcoin's data directory ==<br />
The [[data directory]] is the location where Bitcoin's data files are stored, including the wallet data file.<br />
<br />
=== Gnu/Linux ===<br />
<br />
By default Bitcoin will put its data here:<br />
<br />
~/.bitcoin/<br />
<br />
You need to do a "ls -a" to see directories that start with a dot.<br />
<br />
If that's not it, you can do a search like this:<br />
<br />
find / -name wallet.dat -print 2>/dev/null<br />
<br />
To change the directory Bitcoin stores its data in:<br />
Run in terminal or script: ./bitcoin-qt -datadir=./[Directory_Name]<br />
<br />
=== Mac OSX ===<br />
<br />
By default Bitcoin will put its data here:<br />
<br />
~/Library/Application Support/Bitcoin/<br />
<br />
=== Windows ===<br />
Go to Start -> Run (or press WinKey+R) and run this:<br />
<br />
explorer %APPDATA%\Bitcoin<br />
<br />
Bitcoin's data folder will open. For most users, this is one of the following locations:<br />
<br />
C:\Documents and Settings\YourUserName\Application data\Bitcoin (Windows XP)<br />
<br />
C:\Users\YourUserName\Appdata\Roaming\Bitcoin (Windows Vista and 7)<br />
<br />
If you have trouble browsing to these folders, note that "AppData" and "Application data" are hidden by default.<br />
<br />
==Backing up your wallet files==<br />
<br />
'''Note''': Using Dropbox to back up your Bitcoin data is not recommended as doing so introduces the following [https://en.wikipedia.org/wiki/Dropbox_(service)#Reception security concerns]:<br />
<br />
# Dropbox stores your encryption key (meaning that a disgruntled Dropbox employee or an attacker who gained access to the system could decrypt your Dropbox data and steal your bitcoins)<br />
# the Dropbox client only needs a password for the first login. After it authenticates once, the server assigns it a token which it uses to show that, at one time, its user knew the password rather than sending the actual password (meaning that if you ever use the Dropbox client on another PC, that PC's users can access your Dropbox - even if you change your password - and can steal your bitcoins or get a virus that will steal your bitcoins).<br />
<br />
For these reasons, an alternative that always uses password authentication such as [http://www.wuala.com/en/bitcoin Wuala] should be used. Wuala's servers do not store your encryption key and the program authenticates with the password each time it is started.<br />
<br />
Whether you use Dropbox as your backup or not, it is advised to use what Steve Gibson calls "pre-Internet encryption" which means to use some form of encryption on your files before you back them up, in case an attacker gains access to that backup. Make sure to pick a password that is memorable but secure.<br />
<br />
The only file you need to back up is "wallet.dat" which can be done one of two ways. To make a copy of the wallet.dat file, ensure that Bitcoin is closed and copy this file somewhere else. The other way is to use the [[api|backupwallet]] JSON-RPC command to back up without shutting down Bitcoin. <br />
<br />
Once a copy has been made, encrypt it, and put it in two or more safe locations. Consider the risk due to theft, fire, or natural disaster in proportion to the value of bitcoins stored in the wallet.<br />
<br />
===Backup wallet and blochain data===<br />
Follow these instructions to backup all the bitcoin data (wallet and block chains) to an encrypted disk image.<br />
# Open Disk Utility<br />
# Click New Image and choose a big enough size, 128-bit or 256-bit (faster or more secure) encryption and single partition.<br />
# Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)<br />
# Choose a safe and strong password<br />
# Move everything from ~/Library/Application Support/Bitcoin/ to the image<br />
# Symlink it back so the app would be able to use it<br />
:::ln -s /Volumes/Bitcoin ~/Library/Application Support/Bitcoin<br />
<br />
Don't forget to mount your image before using Bitcoin and unmount it after quitting.<br />
<br />
===Backing up just your wallet file===<br />
Follow these instructions to backup just the wallet.dat file. This results in a smaller disk image, but it's more complicated to do.<br />
# Open Disk Utility<br />
# Click New Image and choose a big enough size, 128-bit or 256-bit (faster or more secure) encryption and single partition.<br />
# Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)<br />
# Choose a safe and strong password<br />
# Move your wallet.dat file to the image<br />
# Symlink it back so the app would be able to use it<br />
:::ln -s /Volumes/Bitcoin/wallet.dat ~/Library/Application Support/Bitcoin/wallet.dat<br />
<br />
[[File:MountWalletAndLauchnBitcoin_OSX_Automator.png|thumbnail|150px|Mount Wallet and launch Bitcoin]]<br />
Don't forget to mount your image before using Bitcoin and unmount after quitting it.<br />
<br />
'''Note''': If you start the Bitcoin application without having the image mounted, the application will overwrite your symlink with a new wallet. If that happens, don't panic. Just delete the new wallet.dat, mount the image, and recreate the symlink like above.<br />
<br />
'''Automation''': You can create a small application using [http://en.wikipedia.org/wiki/Automator_%28software%29 Automator] (included in OS X) to automatically mount the wallet and then launch Bitcoin App. See the Screenshot on how to do this.<br />
<br />
If one ''doesn't'' want to use encrypted Disk images, then a '''small shell script''' can be used instead that takes care of decrypting the wallet, launching bitcoin client, and encrypting it after the client exits. This script works on both OSX and Gnu/Linux: [http://lorelei.kaverit.org/bitcoin.sh bitcoin-launch-script]<br />
<br />
==Restoring your wallet file==<br />
<br />
Assuming your backup is recent enough that you haven't used up all of your key pool... restoring a wallet to a new (or old) location and rescanning the block chain should leave you with all your coins. Just follow these steps:<br />
* Shut down the Bitcoin program.<br />
* Copy your backed-up wallet.dat into your bitcoin data directory.<br />
* If you are copying in a backed-up wallet.dat that was last used on a Bitcoin version prior to 0.3.21 into an existing profile, delete files ''blk*.dat'' to make the client re-download the block chain. You may also need to do this if your transactions don't all show up after you restart Bitcoin.</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Backing_up_your_wallet&diff=42801Backing up your wallet2013-12-02T16:19:33Z<p>MagicFab: New page to simplify "Securing your wallet"</p>
<hr />
<div>== Locating Bitcoin's data directory ==<br />
The [[data directory]] is the location where Bitcoin's data files are stored, including the wallet data file.<br />
<br />
=== Gnu/Linux ===<br />
<br />
By default Bitcoin will put its data here:<br />
<br />
~/.bitcoin/<br />
<br />
You need to do a "ls -a" to see directories that start with a dot.<br />
<br />
If that's not it, you can do a search like this:<br />
<br />
find / -name wallet.dat -print 2>/dev/null<br />
<br />
To change the directory Bitcoin stores its data in:<br />
Run in terminal or script: ./bitcoin-qt -datadir=./[Directory_Name]<br />
<br />
=== Mac OSX ===<br />
<br />
By default Bitcoin will put its data here:<br />
<br />
~/Library/Application Support/Bitcoin/<br />
<br />
=== Windows ===<br />
Go to Start -> Run (or press WinKey+R) and run this:<br />
<br />
explorer %APPDATA%\Bitcoin<br />
<br />
Bitcoin's data folder will open. For most users, this is one of the following locations:<br />
<br />
C:\Documents and Settings\YourUserName\Application data\Bitcoin (Windows XP)<br />
<br />
C:\Users\YourUserName\Appdata\Roaming\Bitcoin (Windows Vista and 7)<br />
<br />
If you have trouble browsing to these folders, note that "AppData" and "Application data" are hidden by default.<br />
<br />
==Backing up your wallet files==<br />
<br />
'''Note''': Using Dropbox to back up your Bitcoin data is not recommended as doing so introduces the following [https://en.wikipedia.org/wiki/Dropbox_(service)#Reception security concerns]:<br />
<br />
# Dropbox stores your encryption key (meaning that a disgruntled Dropbox employee or an attacker who gained access to the system could decrypt your Dropbox data and steal your bitcoins)<br />
# the Dropbox client only needs a password for the first login. After it authenticates once, the server assigns it a token which it uses to show that, at one time, its user knew the password rather than sending the actual password (meaning that if you ever use the Dropbox client on another PC, that PC's users can access your Dropbox - even if you change your password - and can steal your bitcoins or get a virus that will steal your bitcoins).<br />
<br />
For these reasons, an alternative that always uses password authentication such as [http://www.wuala.com/en/bitcoin Wuala] should be used. Wuala's servers do not store your encryption key and the program authenticates with the password each time it is started.<br />
<br />
Whether you use Dropbox as your backup or not, it is advised to use what Steve Gibson calls "pre-Internet encryption" which means to use some form of encryption on your files before you back them up, in case an attacker gains access to that backup. Make sure to pick a password that is memorable but secure.<br />
<br />
The only file you need to back up is "wallet.dat" which can be done one of two ways. To make a copy of the wallet.dat file, ensure that Bitcoin is closed and copy this file somewhere else. The other way is to use the [[api|backupwallet]] JSON-RPC command to back up without shutting down Bitcoin. <br />
<br />
Once a copy has been made, encrypt it, and put it in two or more safe locations. Consider the risk due to theft, fire, or natural disaster in proportion to the value of bitcoins stored in the wallet.<br />
<br />
===Backup wallet and blochain data===<br />
Follow these instructions to backup all the bitcoin data (wallet and block chains) to an encrypted disk image.<br />
# Open Disk Utility<br />
# Click New Image and choose a big enough size, 128-bit or 256-bit (faster or more secure) encryption and single partition.<br />
# Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)<br />
# Choose a safe and strong password<br />
# Move everything from ~/Library/Application Support/Bitcoin/ to the image<br />
# Symlink it back so the app would be able to use it<br />
:::ln -s /Volumes/Bitcoin ~/Library/Application Support/Bitcoin<br />
<br />
Don't forget to mount your image before using Bitcoin and unmount it after quitting.<br />
<br />
===Backing up just your wallet file===<br />
Follow these instructions to backup just the wallet.dat file. This results in a smaller disk image, but it's more complicated to do.<br />
# Open Disk Utility<br />
# Click New Image and choose a big enough size, 128-bit or 256-bit (faster or more secure) encryption and single partition.<br />
# Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)<br />
# Choose a safe and strong password<br />
# Move your wallet.dat file to the image<br />
# Symlink it back so the app would be able to use it<br />
:::ln -s /Volumes/Bitcoin/wallet.dat ~/Library/Application Support/Bitcoin/wallet.dat<br />
<br />
[[File:MountWalletAndLauchnBitcoin_OSX_Automator.png|thumbnail|150px|Mount Wallet and launch Bitcoin]]<br />
Don't forget to mount your image before using Bitcoin and unmount after quitting it.<br />
<br />
'''Note''': If you start the Bitcoin application without having the image mounted, the application will overwrite your symlink with a new wallet. If that happens, don't panic. Just delete the new wallet.dat, mount the image, and recreate the symlink like above.<br />
<br />
'''Automation''': You can create a small application using [http://en.wikipedia.org/wiki/Automator_%28software%29 Automator] (included in OS X) to automatically mount the wallet and then launch Bitcoin App. See the Screenshot on how to do this.<br />
<br />
If one ''doesn't'' want to use encrypted Disk images, then a '''small shell script''' can be used instead that takes care of decrypting the wallet, launching bitcoin client, and encrypting it after the client exits. This script works on both OSX and Gnu/Linux: [http://lorelei.kaverit.org/bitcoin.sh bitcoin-launch-script]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Paper_wallet&diff=42800Paper wallet2013-12-02T15:16:12Z<p>MagicFab: /* Producing safe paper wallets */ Added information about Blockchain tutorial, offline precautions when using generators</p>
<hr />
<div>A '''paper wallet''' is a mechanism for storing bitcoins offline as a physical document that can be secured like cash or anything else of real-world value. Paper wallets are generally created by printing a brand new public address and private key onto paper, and then sending bitcoins from a "live" wallet to the printed wallet's public address for safekeeping. If good security practices are followed, paper wallets are one of the safest ways to to store a virtually unlimited number of Bitcoins. <br />
<br />
__TOC__<br />
<br />
==Producing safe paper wallets==<br />
<br />
[[File:BitcoinPaperWallet-sample.jpg|frame|right|400px|Wallet with private key secured beneath folds (BitcoinPaperWallet.com)]]<br />
A Bitcoin [[private key]] can be represented in several formats, but Wallet Import Format (WIF) is typically used for paper wallets since these keys are very short (51 characters) and thus easy to re-enter when importing or "sweeping" the wallet for withdrawal.<br />
<br />
Several tools exist for producing paper wallets, including [[BitAddress.org]], [[BitcoinPaperWallet|BitcoinPaperWallet.com]], [[vanitygen]], [https://safepaperwallet.com Safe Paper Wallet], and [[Bitcoin Address Utility]]. <br />
<br />
Care must be taken to securely generate paper wallets since an attacker can steal the present ''and future'' balance of a paper wallet if the private key is exposed, transmitted, or generated with insufficient entropy.<br />
<br />
[[BitAddress.org]] and [[BitcoinPaperWallet|BitcoinPaperWallet.com]] feature a free client-side paper wallet generator written in JavaScript. The HTML for either of these generators can be downloaded from GitHub and used on an offline computer. Using either of these generators offline (not directly running from their websites) is relatively safe, but extra precautions should be taken when used while being connected to ensure that keys are not compromised by spyware that may be monitoring browser activity. <br />
<br />
Blockchain.info offers a [https://blockchain.info/wallet/paper-tutorial tutorial on how to generate a paper wallet] with an online component so you can check your balance easily.<br />
<br />
'''Recommendations:'''<br />
* Paper wallets should be produced on a computer not connected to the Internet.<br />
* Be aware that malware often allows a remote third party to view your screen and see your keystrokes, and these can compromise the integrity of your paper wallet. Also consider that antivirus software cannot completely rule out the possibility of malware. However, using bootable CD's prevents the vast majority of malware from being able to run. If you can generate a paper wallet with a bootable CD such as an Ubuntu LiveCD, the likelihood of malware being able to compromise your keys is very low.<br />
* The private keys of paper wallets should never be saved to a computer hard drive. You should also never scan your paper wallet into your computer or type the private keys or save them in e-mail, except at the moment you are redeeming the balance.<br />
* If possible, the private key of a paper wallet should be kept hidden, for example by folding the paper to hide the private key so that a photograph or photocopy of the wallet will not reveal or replicate the private key.<br />
* A web-based paper wallet generator should be written so that all of the generation happens on your computer, not the web server. After you load the paper wallet generating website in your web browser, you should disconnect from the Internet, and observe that the paper wallet generator continues to function. Afterward, you should close your browser before reconnecting to the Internet.<br />
* A paper wallet generator should use an appropriate source of random numbers (entropy). This means that the generated addresses aren't predictable. If the addresses come from a predictable or partially-predictable pattern, someone else who can predict the pattern addresses can steal the balance. Generally, this rules out any "web-based" generator unless you can be sure that both your browser and the JavaScript code are taking advantage of the strongest cryptographic routines available.[http://www.w3.org/TR/WebCryptoAPI/]<br />
<br />
===Operating System Cache Security===<br />
<br />
The problem with printing out secure documents—even if your computer is 100% virus/trojan free—is that your printer driver and/or operating system may be keeping copies of the documents you print in a "spool" or print queue. If a hacker or virus gets into your computer and knows to look for these cache files, then they can get your private keys and sweep your paper wallets. Precautions to mitigate this type of attack include:<br />
<br />
* Enabling encryption of your entire filesystem so that cache files cannot be 'undeleted'.<br />
<br />
* Setting up a symbolic link from your OS spool directory (e.g. /private/var/spool/cups/cache/ on OS X) to a removable media volume (e.g. a SD card) and disconnecting it when not in use.<br />
<br />
* Using a live-boot CD instead of a regular hard drive OS install. This way when you reboot your computer, all cache files are deleted from memory and no jobs are ever written to disk.<ref>[https://bitcoinpaperwallet.com/#security BitcoinPaperWallet.com] ''Security Tips''</ref><br />
<br />
===Printer Security===<br />
<br />
Some advanced printers have internal storage (even hard drives) that preserve copies of printouts. This is a risk if someone gets access to your printer, or if you dispose of your printer. There is also the possibility that a smart enough printer can be hacked. (Consider [http://en.wikipedia.org/wiki/Stuxnet StuxNet] which was able to rewrite the firmware of non-computer devices indirectly connected to the Internet) If this concerns you, use a "dumb" printer, and never let your printer have access to the Internet or to an Internet-connected computer.<br />
<br />
==Redeeming Keys and Withdrawing Funds==<br />
<br />
Paper wallets are very different from "live" wallets such as the Bitcoin-QT client in that it is not possible to transfer (withdraw) a ''portion'' of a paper wallet's bitcoin balance. The only way to withdraw funds from a paper wallet is to import or "sweep" the ''entire'' balance of the paper wallet to a new address, typically a live wallet or online exchange. Once the transfer has been confirmed, ''the paper wallet should no longer be used''.<ref>[http://www.reddit.com/r/Bitcoin/comments/1c9xr7/psa_using_paper_wallets_understanding_change/ reddit.com] ''Using Paper Wallets and Understanding Change''</ref><br />
<br />
There are various methods for copying the private key data from a paper wallet to other wallets.<br />
bitcoind supports an "importprivkey" RPC method for this purpose.<br />
Bitcoin-Qt's debug console can also be used in a similar way (see also [[how to import private keys v7+]]).<br />
[[BlockChain.info]] and [[Armory]] can also import them directly into wallets.<br />
[[MtGox|Mt. Gox]] provides the ability to Add Funds using a private key:<br />
the exchange will then create a "sweep" transaction that spends any amount for that paper wallet address so that the amount is added to your account with them; it will also sweep to your account any bitcoins received to that address in the future as well.<br />
<br />
==References==<br />
<references /><br />
<br />
==See Also==<br />
<br />
* [[Private key]]<br />
<br />
* [[Securing_your_wallet#Paper_Wallets]]<br />
<br />
* [[How to import private keys]]<br />
<br />
* [http://localbitcoins.blogspot.fi/2012/11/start-your-own-money-press.html Guide to paper wallets]<br />
<br />
* [https://www.youtube.com/watch?v=a47rrYBWjWQ YouTube video demonstration of generating a paper wallet]<br />
<br />
[[Category:Security]]<br />
<br />
[[es:Monedero de papel]]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Meetups&diff=42024Meetups2013-10-28T14:19:36Z<p>MagicFab: Added Bitcoin Embassy meetups</p>
<hr />
<div>Don't add everyone who's going in the "Who?" column, just prominent Bitcoin members and organizers. Also see [http://bitcoin.meetup.com bitcoin.meetup.com]. Also see [[Conferences]].<br />
<br />
Keep an eye on the [http://bitcointalk.org/index.php?board=86.0 Meetups] forum board on BitcoinTalk for announcements.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group<br />
! When?<br />
! Where?<br />
! Who?<br />
! Other Notes<br />
|-<br />
| [http://bitcoinembassy.ca Bitcoin Embassy]<br />
| Monthly meetups, weekly workshops<br />
| Montreal, QC, Canada<br />
| Local and international participants - guest speakers welcome. Come and visit our hackerspace, startup incubator and soon, Bitcoin store.<br />
| Presentations and workshops, discussion & trade. [http://eepurl.com/GRzAf Register to our mailing list] to receive event invitations. We also post on [https://bitcointalk.org/index.php?board=86.0 BitcoinTalk Meetups], [http://bitcoinembassy.eventbrite.ca/ EventBrite], [https://www.facebook.com/bitcoinembassy Facebook Bitcoin Embassy page], [https://plus.google.com/u/0/100266464273886488866 Google +], etc.<br />
|-<br />
|-<br />
| [https://bitcash.cz/forum/ Bitcash.cz]<br />
| Ocasionally<br />
| Prague, Brno, Ostrava<br />
| Meetup for Czech and Slovak bitcoin pioneers. <br />
| Discuss and trade with Bitcoin. Events posted also on our [https://www.facebook.com/Bitcash.cz Facebook] profile.<br />
|-<br />
|-<br />
| [http://www.meetup.com/Sydney-Bitcoin-Users-Group/ BitcoinSYD]<br />
| Every Wednesday @ 1800<br />
| [http://www.gposydney.com/GPO-SYDNEY-BARS-AND-CLUB-6.html GPO Bar], Downstairs, George St end. Look for the guy in the Red Cap.<br />
| Local, National and International peeps looking to Talk and Trade Bitcoin<br />
| We also post our meetups on Reddit and [https://www.facebook.com/pages/Bitcoin-Sydney-Australia/457681220943285 Facebook]<br />
|-<br />
|-<br />
| [https://bitcointalk.org/index.php?topic=27191.0;all Bitcoin Stammtisch]<br />
| each first Thursday of the month<br />
| [http://www.room77.de/ Room 77], Gräfestr. 77, Berlin-Kreuzberg<br />
| Anyone interested in Bitcoin: technically, economically, socially or philosophically.<br />
| If questions contact andreas(at)schildbach.de (founder).<br />
|-<br />
|-<br />
| [http://www.meetup.com/bitcoins/ Bitcoin NYC]<br />
| monthly<br />
| [http://www.xcubicle.com/ xCubicle Hackerspace - New York, NY]<br />
| Any and all Bitcoin aficionados. <br />
|<br />
|-<br />
|-<br />
| [https://en.bitcoin.it/wiki/Bitcoin_Wednesday Bitcoin Wednesday Amsterdam]<br />
| First Wednesday of the Month<br />
| [http://lanyrd.com/2013/bitcoinamsterdam/ Sign Up - Amsterdam, The Netherlands]<br />
| Open to anyone interested in Bitcoin. <br />
| [https://www.PikaPay.com PikaPay.com @PikaPay or hello-AT-PikaPay.com]<br />
|-<br />
|-<br />
| [http://hitspace.org/ HIT Space - Hack it Together]<br />
| monthly<br />
| [http://hitspace.org/where-we-are/ HIT Space - Porto, Portugal]<br />
| Hackerspace members and anyone who want to join us<br />
| send us an email geral[at]hitspace.org<br />
|-<br />
|-<br />
| [http://bitcoin-austria.at Bitcoin Austria]<br />
| monthly - check the [http://bitcoin-austria.at wiki] or subscribe to the [http://lists.bitcoin-austria.at/listinfo/bitcoin mailinglist]<br />
| [https://metalab.at/wiki/Lage Metalab], Vienna hacker space, Rathausstraße 6, 1010 Wien<br />
| Everybody interested in Bitcoin <br />
| <br />
|-<br />
| [http://brmlab.cz brmlab, prague hackerspace]<br />
| 14th Nov 2011<br />
28th Nov 2011<br />
([http://brmlab.cz/event/bitcoin_seminar])<br />
| [http://brmlab.cz/place Brmlab, Bubenska 1]<br />
| brmlab crew, slush, genjix<br />
| <br />
|-<br />
| [http://www.facebook.com/groups/175596065827848/ Bitcoin Boston]<br />
| Every Friday at 4:30 and bi-weekly on Saturday or Sunday ([http://www.facebook.com/groups/175596065827848/ See Facebook page])<br />
| Starbucks in Kendall Square (Ames St & Broadway) and bi-weekly at Starbucks in Harvard Square<br />
| Anyone is welcome!<br />
| Our bi-weekly meetings have been somewhat sporadic but we aim to gain some regularity.<br />
|-<br />
| [http://www.meetup.com/Milwaukee-Area-Bitcoin-Meetup/ Milwaukee Area Bitcoin Meetup]<br />
| Every other Thursday at 6:00pm<br />
| 17025 West Rogers Drive, New Berlin WI<br />
| Open to anyone interested in Bitcoin<br />
| [https://www.facebook.com/groups/BTCMKE Milwaukee Area Bitcoin Meetup Facebook]<br />
|-<br />
| [http://www.meetup.com/bitcoin New York Bitcoin Users]<br />
| 6:00 PM, 3rd Sunday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])<br />
| OnlyOneTV Studios - 290 Fifth Ave New York, NY<br />
| Bruce Wagner (Organizer) and others<br />
| <br />
|-<br />
|-<br />
| [http://www.meetup.com/bitcoin New York Bitcoin Users]<br />
| 6:00 PM, every Wednesday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])<br />
| Just Sweet Dessert House - 83 Third Ave New York, NY<br />
| Yifu Guo (Organizer) and crew<br />
| hosted by Bitsyncom, the people behind [[Bitnavigator]], walk-ins welcome;<br />
|-<br />
|[http://www.meetup.com/MichiganBitcoinMeetup Michigan Bitcoin Meetup]<br />
|<br />
|<br />
|Kinnard Hockenhull (Organizer)<br />
|Sponsored by [[BitBox]]<br />
|-<br />
| [http://www.meetup.com/PhillyBitcoin Philadelphia Bitcoin User Group]<br />
| TBD<br />
| TBD<br />
| Brian Cohen (Organizer) and others<br />
|<br />
|-<br />
| [http://www.meetup.com/BitcoinDC Washington, DC Bitcoin Users]<br />
| 7:00 PM, 1st Monday of every month ([http://www.meetup.com/BitcoinDC/#past past meetings])<br />
| Northside Social, 3211 Wilson Blvd Arlington, VA<br />
| [[User:Dduane|Darrell Duane]] (Organizer) and others<br />
|<br />
|-<br />
| [http://www.meetup.com/Silicon-Valley-Bitcoin-Users Silicon Valley Bitcoin Users]<br />
| 7:00 PM, Tuesday, June 14, 2011 ([http://www.meetup.com/Silicon-Valley-Bitcoin-Users/events/past past meetings])<br />
| 140B S Whisman Road Mountain View, CA <br />
| Brian Mcqueen and others<br />
|<br />
|-<br />
| [http://www.meetup.com/BitcoinChicago Chicago]<br />
| No regular schedule yet ([http://www.meetup.com/BitcoinChicago/events/past past meetings])<br />
| Sunnyvale Art Gallery Cafe, 251 W El Camino Real Sunnyvale, CA<br />
| Igor<br />
|<br />
|-<br />
| [http://www.meetup.com/denver-bitcoin Denver]<br />
| First meeting June 4th, 2011 ([http://www.meetup.com/denver-bitcoin/events/past past meetings])<br />
| Gypsy House Cafe - 1279 Marion St Denver, CO<br />
| bearbones<br />
|<br />
|-<br />
| [http://www.meetup.com/bitcoinSF Bitcoin SF]<br />
| Saturday, June 4, 2011 ([http://www.meetup.com/bitcoinSF past meetings])<br />
| SFSU - 1600 Holloway Ave. San Francisco, CA<br />
| Brian Mcqueen and others<br />
|<br />
|-<br />
| [http://www.meetup.com/Los-Angeles-Digital-Currency-Innovators-Group Los Angeles Digital Currency Innovators]<br />
| Thursday July 7th, 2011, 7 PM<br />
| (mt)/Media Temple, Culver City, CA<br />
| [[User:sgornick|Stephen Gornick]] (Interim organizer) and others<br />
| Seeking meetup coordinator<br />
|-<br />
| [http://Hackerish.org Las Vegas Crypto Party]<br />
| 3rd Thursday 7pm. [http://BitcoinsInVegas.com Weekly Wednesday lunch mobs]<br />
| /Usr/Lib @ The Beat Coffee House, 520 Fremont, 2nd floor, Las Vegas, NV<br />
| Julian Tosh / Tuxavant<br />
|<br />
|-<br />
| [https://www.facebook.com/groups/195492163844669/ Free State Bitcoin Consortium]<br />
| Every Saturday, at 6:30 PM<br />
| Strange Brew Tavern, Manchester, NH<br />
| ben-abuya (organizer)<br />
| Weekly<br />
|-<br />
| [https://www.facebook.com/groups/195492163844669/ Twin Cities Users]<br />
| Friday, June 10, 2011, 6:30 PM<br />
| Joule - 1200 Washington Ave S Minneapolis, MN<br />
| Mac Manson<br />
|<br />
|-<br />
| [http://www.meetup.com/Portland-Bitcoin-Meetup-Users Portland Bitcoin Users Meetup Group]<br />
| forming<br />
| <br />
| Steven Wagner<br />
|<br />
|-<br />
| [http://www.meetup.com/Bitcoin-Orlando Bitcoin Orlando]<br />
| ([http://www.meetup.com/Bitcoin-Orlando#past past meetings])<br />
| Frank & Steins 150 S. Magnolia Ave, Orlando, FL<br />
| Antonio Gallippi<br />
|<br />
|-<br />
| [http://www.meetup.com/Bitcoin-Enthusiasts/ Bitcoin Tampa]<br />
| Monthly meetings<br />
| Matt Branton -- [https://www.coinlock.com/ Coinlock.com] founder<br />
|<br />
|-<br />
| [http://www.hive13.org/?p=310 Hive13 Hackerspace]<br />
| Bitcoin Exchange, Every Tuesday, 7:30 PM<br />
| Hive13 - 2929 Spring Grove Avenue, Cincinnati, OH<br />
| <br />
|<br />
|-<br />
| [https://www.facebook.com/bitcoinaus Bitcoin Australia]: Melbourne <br />
| [https://www.facebook.com/events/345430765511234/ Wednesday, 23 May 2012, 18:45]<br />
| Melbourne CBD(TBA)<br />
| Facebook, IRC, Bitcointalk Forum...<br />
|<br />
|-<br />
| [[Bitcoin:Tokyo meetup|Tokyo]]<br />
| Usually first monday of the month<br />
| Shibuya<br />
| Roger Ver (Organizer) and others<br />
|<br />
|-<br />
| [http://meetup.com/Bitcoin-Canada Vancouver Canada]<br />
| ([http://www.meetup.com/Bitcoin-Canada/#past past meetings])<br />
| The Brickhouse - 730 Main St.<br />
| humble (and others)<br />
|<br />
|-<br />
| [https://plus.google.com/u/0/communities/113055238568417913658 Zurich / Geneva Switzerland]<br />
| Twice a month<br />
| Kennedy's Irish Pub, Zurich; Lord Nelson Pub, Geneva<br />
| Stefan Thomas (WeUseCoins), Mike Hearn (BitcoinJ), bitdragon, Luzius (Wuala), more ... <br />
|<br />
|-<br />
| Seattle Bitcoin Meetup<br />
| [http://www.meetup.com/SeattleBitCoin/ Semi-regularly].<br />
| [http://maps.google.com/maps?q=cafe+solstice&daddr=4116+University+Way,+Seattle,+WA+98105-6214&hl=en&ll=47.657424,-122.31313&spn=0.007328,0.01929&gl=us&view=map&geocode=CRT9Bdg7zX3vFdcx1wIdWqa1-CFcJ9qrr9CcEQ&t=h&z=16 Solstice Cafe, 2pm]<br />
| [https://bitcointalk.org/index.php?action=profile;u=36217 indolering]<br />
|<br />
|-<br />
| [https://bitcointalk.org/index.php?topic=135723.0 Munich Germany]<br />
| First wednesday of the month, 6:00PM<br />
| [http://www.openstreetmap.org/?minlon=11.5800867080688&minlat=48.1336479187012&maxlon=11.5804319381714&maxlat=48.1338386535645 Nero Pizza], Rumfordstrasse 34, 80469 München<br />
| Bitcoin-users from Munich and around<br />
| [http://www.meetup.com/Bitcoin-Munchen/ @meetup.com]<br />
|-<br />
| [http://www.meetup.com/bitcoin-il/ Israel Bitcoin Meetup Group]<br />
| Occasional<br />
| TBD<br />
| Meni Rosenfeld<br />
|<br />
|-<br />
| [http://www.meetup.com/Dallas-Bitcoin-User-Meetup/ Dallas Bitcoin Meetup Group]<br />
| Biweekly on Saturdays, 6:00PM<br />
| [http://freemandallas.com/ The Free Man Cajun Cafe]<br />
| Justus Ranvier (organizer)<br />
|<br />
|-<br />
| [https://en.bitcoin.it/wiki/Cafe Café Bitcoin Sevilla]<br />
| <br />
| Seville, Spain<br />
| Randy Brito (rdymac / btcven), Eduardo (bitcoin.com.es), Jorge and Alfredo<br />
| http://cafebitcoin.com<br />
|-<br />
|}<br />
<br />
==See Also==<br />
<br />
* [http://hackerspaces.org/wiki/List_of_Hacker_Spaces List of Hacker Spaces]<br />
* [http://bitimap.net Bitimap.net - Find local meetups (up-to-date)]<br />
<br />
[[Category:Local]]<br />
[[Category:Meetups]]<br />
<br />
<br />
[[de:Treffen]]</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=User:MagicFab&diff=41914User:MagicFab2013-10-24T14:43:04Z<p>MagicFab: First version</p>
<hr />
<div>Chief Ambassador, [http://bitcoinembassy.ca Bitcoin Embassy]<br />
Montreal, Canada<br />
<br />
== Primary interests / contributions ==<br />
* Documentation<br />
* Translation<br />
* Bitcoin advocacy: end-users & businesses, focusing in Montreal / Canada<br />
<br />
==Contact Information==<br />
<br />
* http://www.bitcoinembassy.ca<br />
* http://www.magicfab.ca</div>MagicFabhttps://tests.bitcoin.it/w/index.php?title=Talk:Real_world_shops&diff=41913Talk:Real world shops2013-10-24T14:39:43Z<p>MagicFab: /* Please use CoinMap */</p>
<hr />
<div>note: the parser does not always include all markers.<br/><br />
use action=purge if necessary: https://en.bitcoin.it/wiki/Real_world_shops?action=purge<br />
<br />
== Cyberspace is not imaginary ==<br />
<br />
Maybe the term "real world" should be replaced by "physical world"? The fact that bitcoin is a virtual currency doesn't make it any less real....<br />
<br />
== https for the google map ==<br />
<br />
When I load the page in chrome it says that the map cannot be loaded, however it loads up just fine after allowing insecure content through (albeit causing the green https to go red and have a nasty red line through it)<br />
<br />
== Please use CoinMap ==<br />
<br />
Hi,<br />
please use [http://coinmap.org/#zoom=4&lat=42.39&lon=3.25&layer=OpenStreetMap CoinMap] instead of the current map.--[[User:Stemby|Stemby]] ([[User talk:Stemby|talk]]) 16:33, 1 July 2013 (GMT)<br />
:I added a note for every entry with geographical coordinates. Example: http://www.openstreetmap.org/?note=11792 --[[User:Stemby|Stemby]] ([[User talk:Stemby|talk]]) 11:06, 6 July 2013 (GMT)<br />
::I manually added also a note for every entry without geographical coordinates; example: http://www.openstreetmap.org/?note=12189<br />
::I think the current buggy map should be replaced by CoinMap right now. Thank you!--[[User:Stemby|Stemby]] ([[User talk:Stemby|talk]]) 12:13, 8 July 2013 (GMT)<br />
<br />
+1 for this [[User:MagicFab|MagicFab]] ([[User talk:MagicFab|talk]]) 14:39, 24 October 2013 (GMT)</div>MagicFab