To backup your wallet you will need to make a copy of the key file(s) located in your ethereum directory.
The file should look something like this:
I've suggested just saving the keystore ...
How to Access the Files to Back Up
Using Mist - Backup Accounts
Go to the top bar and select ACCOUNTS -> BACKUP -> ACCOUNTS.
This will open a folder. Inside this folder there are keystrore files that have long names starting with UTC--2016-04-14....... Each of these files represent an account. Back up these up.
Using Mist - Backup Wallet Contracts
Go to ...
In Parity 1.6 : Have a look at
OSX : ~/Library/Application\ Support/io.parity.ethereum/keys/
Linux : ~/.local/share/io.parity.ethereum/keys/
In Parity 1.5 : Have a look at ~/.parity/keys. You'll find what you're looking for.
PLEASE MAKE SURE TO ALSO BACKUP YOUR PASSWORDS
Each key file (as described in @Ethan's answer) is encrypted and only usable with the correct password.
Another safety tip: Before deleting any key files, after you have done the backup, please try the import/restore process on another system to make sure you can send a small amount of Ether. (To import, copy ...
When you run parity -h you can see the default keystore. It is listed as the default where the -d --base-path option is explained, under Operating Options.
On Linux: ~/.local/share/io.parity.ethereum/keys/
On Mac OS: ~/Library/Application\ Support/io.parity.ethereum/keys/
If you use the latest version of the Mist wallet 0.3.9, then you can
backup your wallet with saving the AppData. You can do that by clicking
on Backup in the Menu bar and click "Backup App Data" which points you
to the installation directory where your wallet is saved. In my case it is
located here "C:\Users\Andreas\AppData\Roaming" on Windows 10 - 64 Bit....
To backup your accounts from Ethereum Wallet, see How to backup mist wallets?.
The files that you need to backup will have names like the following:
In general, if you carefully generate your keys offline and on an untampered live system, with a strong passphrase, you are good to go.
In opposition to any other anwsers recommending cold/offline storage, I suggest strongly not to use offline storage. There are so many popular examples out there where huge amounts of value disappeared from cold storages ...
The passphrase mechanism is accurately described in BIP 39
How Ethereum keys are derived is described here
These mechanisms are common for Ethereum and other cryptocurrency wallets.
The short answer to your question is yes you can test your keys/wallets on different OS's.
KEEP MULTIPLE BACKUPS OF YOUR KEYS IN SECURE/SEPARATE PLACES
If you are intending to only use geth across your various OS's there shouldn't be an issue exporting and importing the keys as you have described. I made the first ...
They would have to crack your password to be able to steal your ETH, so it would be as secure as your password is strong. But if a keylogger virus was on the computer logging all your keystrokes, then they could see what your password is.
I recommend putting any large amounts of ETH in accounts into cold storage: save the account file inside an encrypted / ...
Yes, you can simply generate pairs of unencrypted or encrypted private and public keys. For example, use this bulk key generator:
When I switched from geth to parity, I noticed that parity imported my accounts from the .ethereum/keystore/* directory into parity somehow.
0 ✓ user@host ~ $ ll ~/.ethereum/keystore/
4.0K drwxr-xr-x 2 user users 4.0K May 13 10:36 .
4.0K drwx------ 9 user users 4.0K Jun 17 10:17 ..
4.0K -rw-r--r-- 1 user users 58 May 13 10:36 contract-...
According to the documentation for Parity's ethstore key management API:
secret store directory: It may be either parity, parity-test, geth,
geth-test or a path. default: parity
(Also of note is the ethkey key generator API and associated commands.)
Bitcoin operates under a UTXO (unspent transaction output) system, which necessitates new addresses for each transaction. Ethereum, in contrast, operates on an account based system. While it would be possible to deterministically generate a tree of accounts from a single seed in Ethereum, there's really no need to, because a single account can handle all of ...
I only know the mobile Jaxx app wallet for now that can handle Ethereum HD accounts all linked under a mnemonic. It can also handle bitcoin. It's my favorite wallet app for the moment if you only want to receive and send ether and not interact with contracts.
Note that Jaxx is still in beta, so use it with small amounts.
BIP32 and BIP39 are describing ways to generate hierarchical deterministic keypairs. In general you generate a deterministic private key first and generate a public key derived from that private key.
Yes, the keystore file is json and contains the encrypted private key.
The private key will never change and does not depend on the number of transactions it is involved in. Saving each keystore file and each password is what you need to do for backup. It is also recommended that you test your backup.
The name of the file doesn't lead to the private key: ...
You are correct.
rsync -avzh $HOME/.local/share/io.parity.ethereum/ /path/to/my/backup/parity
If you want to export the keys only, they are located in:
And if you want the blockchain or state only, you can directly export it via:
parity export blocks /path/to/chain
parity export state /path/to/state
Hope that ...
Yes, as long as everything in the ~/.ethereum folder is transferred, your node should work just fine.
You actually don't even need to migrate anything, you can mine from any computer with a synced node just by setting the coinbase to your address. You'd need to resync the node if it's a new computer, though.
In Quorum, all the nodes are synced up same way as regular Ethereum would, except the blocks may come in from a leader rather than another node. So, a new node joining the blockchain would sync up as usual by receiving blocks from the current leader + participants. Once it catches up, it will be receiving blocks from the leader.
Geth / Quorum allow for a ...
If you used the Ethereum geth client, then the key information required to access the accounts was in the folder "keystore". If you have lost this data, then it is impossible to restore access to the accounts.
There's no easy way to fix this, and it may be impossible.
Ideally you should stop using that machine immediately. At the very least, try not to write anything to the hard drive. The contents of the file you need might still be present on the hard drive in unallocated space. Each new file you or Windows creates might overwrite the data you want.
Check out ...
What exactly do you mean by "I've earned some ETH after that backup"? That you have received some ether in your account since the last time you backed it up?
If so then yes, you will have that ether. The UTC--year-month-day file is called a keystore and contains the private key of your ethereum account, which you could think of kind of like the password to ...
Looking at this question from a different perspective...
is it less secure to have the key store outside of the
Especially if you're using a shared machine used by other people.
Your $username$ directory is private to you. Yes, the administrator has access to it, but by moving your keystore you're ...
is it less secure to have the key store outside of the C:\Users\$username$ folder?
No, it isn't less secure. However If you are keeping your key store on your machine once compromised any location on that machine is no more or less secure. It may be slightly more secure depending on the nature of the attack vector. Though this would only be security through ...
Once a file is on your computer, its location doesn't matter, it is nowhere safe. The only security you can have on a wallet that you keep on your computer is to have a strong password. Make it very strong.
Anyway I recommend you not to use a critical wallet (one with a lot of ether in it) on a computer that you use to connect to the internet.
Have an ...
This depends upon the no. of accounts you create/use. Each account will have a unique private key stored in the keystore folder. So, if you are operating with a single account, you need to backup the corresponding private key only once. This key won't change over time.
But, if you keep on creating new accounts, new keys will be generated(one for each ...