DO NOT FORGET YOUR PASSWORD and BACKUP YOUR KEYSTORE Everything geth persists gets written inside its data directory (except for the PoW Ethash DAG, see note below).The default data directory locations are platform specific: Accounts are stored in the keystore subdirectory.The contents of this directories should be transportable between nodes, platforms, implementations (C++, Go, Python).To configure the location of the data directory, the --datadir parameter can be specified.See CLI Options for more details.Note: The Ethash DAG is stored at ~/.ethash (Mac/Linux) or %APPDATA%\Ethash (Windows) so that it can be reused by all clients.You can store this in a different location by using a symbolic link.Sometimes the internal database formats need updating (for example, when upgrade from before 0.9.20).This can be run with the following command (geth should not be otherwise running): Geth's blockchain and state databases can be removed with: This is useful for deleting an old chain and sync'ing to a new one.

It only affects data directories that can be re-created on synchronisation and does not touch the keystore.Export the blockchain in binary format with: Or if you want to back up portions of the chain over time, a first and last block can be specified.For example, to back up the first epoch: Note that when backing up a partial chain, the file will be appended rather than truncated.Import binary-format blockchain exports with: /ethereum/wiki/wiki/Blockchain-import-export for more info And finally: DO NOT FORGET YOUR PASSWORD and BACKUP YOUR KEYSTOREIt looks like you're new here.If you want to get involved, click one of these buttons!Sign In Register Categories Recent Discussions Activity Unanswered Best Of... Categories All Categories Mining Pool Discussion General Project Discussion (non-technical) Education Protocol and Client discussion web3-js Whisper Swarm 2 RLP IoT & Hardware Smart Contracts and Dapps Serpent Solidity Projects Reference clients code and builds Eth & AlethZero- Cpp Implementation Geth - Go Implementation Mist Node.js Implementation Python Implementation Mix Other Implementations Meetups Other Events Jobs & Skills Press and Articles Audio/Video Ether Sale Other Languages Chinese German Italian French 2 Hebrew 6 Japanese Portugese Romanian Russian Spanish Turkish Watercooler Change path for Ethereum Wallet folder "chaindata" Janus 4 May 2016 in Protocol and Client discussion 0 Answers Janus 4 May 2016 /questions/3622/my-c-drive-in-my-windows-pc-is-almost-full-how-can-i-change-both-geth-and-mist 0 StarryNight 1 September 2016 0 o0ragman0o 1,236 September 2016 @StarryNight You can pass command line parameters to the geth node by prefixing the parameter with --node- So ethereum-wallet --node-datadir='d:/chaindata' --node-keystore='c:/some_secure_directory' will start the wallet with the chain data on some spacious drive while you can secure your key store in perhaps an encrypted directory closer to your account.

1 chrizzo 100 October 2016 1 RiskyFire 15 May 17 Today a run into the same problem of my SSD being full of blockchain data, after doing a little research I found a simple way to do it.bitcoin what is mh/sI made a video showing the whole process here 1 Sign In or Register to comment.ethereum usd valueEthereum Sign up or log in to customize your list.bitcoin network ddos_ Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top up vote down vote favorite 3 Switched from geth to Parity and wondering where my information now is.bitcoin skimmer

parity keystore backup up vote down vote 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.bitcoin target audienceYou'll find what you're looking for.bitcoin price sgdup vote 8 down vote When you run parity -h you can see the default keystore.bitcoin kaufen ohne anmeldungIt is listed as the default where the -d --base-path option is explained, under Operating Options.bitcoin sheepOn Linux: ~/.local/share/io.parity.ethereum/keys/ On Mac OS: ~/Library/Application\ Support/io.parity.ethereum/keys/ up vote 6 down vote Parity stores keys in $HOME/.parity/keys In Windows, the $HOME parameter is equivalent to C:\Users\{CurrentUser}.feather bitcoin

Parity's local files live in $HOME/.parity making it C:\Users\{CurrentUser}\.parity.up vote 4 down vote 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.)up vote 4 down vote 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/ total 48K 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-0x1482xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.txt 4.0K -rw-r--r-- 1 user users 43 Oct 16 2015 contract-0x534cxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.txt 4.0K -rw-r--r-- 1 user users 43 Oct 16 2015 contract-0xe358xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.txt 4.0K -rw------- 1 user users 491 Oct 16 2015 UTC--2015-10-15T18-13-54.479132678Z--fcaexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 4.0K -rw------- 1 user users 491 Oct 16 2015 UTC--2015-10-15T20-25-00.928153131Z--a1c2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 4.0K -rw------- 1 user users 491 Jan 15 13:37 UTC--2016-01-15T12-37-23.415253096Z--1337xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 4.0K -rw------- 1 user users 491 Feb 2 01:18 UTC--2016-02-02T00-18-36.894929209Z--a989xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 4.0K -rw------- 1 user users 491 Feb 2 01:36 UTC--2016-02-02T00-36-01.611176405Z--0000xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 4.0K -rw------- 1 user users 491 Feb 4 14:51 UTC--2016-02-04T13-51-18.257136025Z--b195xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 4.0K -rw------- 1 user users 491 Feb 8 12:22 UTC--2016-02-08T11-22-19.471238279Z--006exxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0 ✓ user@host ~ $ cat .ethereum/keystore/UTC--2016-02-08T11-22-19.471238279Z--006exxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx {"address":"006exxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","crypto":{"cipher":"aes-xxx-xxx","ciphertext":"874axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","cipherparams":{"iv":"fb05xxxxxxxxxxxxxxxxxxxxxxxxxxxx"},"kdf":"scrypt","kdfparams":{"dklen":xx,"n":xxxxxx,"p":x,"r":x,"salt":"6c6bxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"},"mac":"a128xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"},"id":"f433aa7d-xxxx-xxxx-xxxx-xxxxxxxxxxxx","version":3}} They are now also located in .parity/keys/*: 0 ✓ user@host ~ $ ll ~/.parity/keys/ total 36K 4.0K drwxr-xr-x 2 user users 4.0K Apr 20 19:31 .

4.0K drwxr-xr-x 5 user users 4.0K Apr 26 09:58 .. 4.0K -rw-r--r-- 1 user users 605 Jun 24 10:52 1843f804-xxxx-xxxx-xxxx-xxxxxxxxxxxx 4.0K -rw-r--r-- 1 user users 605 Jun 24 10:52 37dce086-xxxx-xxxx-xxxx-xxxxxxxxxxxx 4.0K -rw-r--r-- 1 user users 605 Jun 24 10:52 52a91bfd-xxxx-xxxx-xxxx-xxxxxxxxxxxx 4.0K -rw-r--r-- 1 user users 605 Jun 24 10:52 8240bdb9-xxxx-xxxx-xxxx-xxxxxxxxxxxx 4.0K -rw-r--r-- 1 user users 605 Jun 24 10:52 af3e6350-xxxx-xxxx-xxxx-xxxxxxxxxxxx 4.0K -rw-r--r-- 1 user users 605 Jun 24 10:52 f433aa7d-xxxx-xxxx-xxxx-xxxxxxxxxxxx 4.0K -rw-r--r-- 1 user users 605 Jun 24 10:52 f4bf9894-xxxx-xxxx-xxxx-xxxxxxxxxxxx 0 ✓ user@host ~ $ cat parity/keys/f433aa7d-xxxx-xxxx-xxxx-xxxxxxxxxxxx { "address": "006exxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "crypto": { "cipher": "aes-xxx-xxx", "cipherparams": { "iv": "fb05xxxxxxxxxxxxxxxxxxxxxxxxxxxx" }, "ciphertext": "874axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "kdf": "scrypt", "kdfparams": { "dklen": xx, "n": xxxxxx, "p": x, "r": x, "salt": "6c6bxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }, "mac": "a128xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }, "id": "f433aa7d-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "version": 3 } up vote 0 down vote On Windows 7 and 10, I had to go here: C:\Users\{your_user_name}\AppData\Roaming\Parity\Ethereum\keys\ethereum The files that start with UTC- are the keys.