Wo befinden sich meine Schlüssel und Kettendaten, wenn ich Parity verwende?

In Parität 1.6 : Schau mal

• OS X:~/Library/Application\ Support/io.parity.ethereum/keys/
• Linux:~/.local/share/io.parity.ethereum/keys/
• Fenster:%APPDATA%\Parity\Ethereum\keys

In Parity 1.5: Schau mal bei ~/.parity/keys. Sie werden finden, wonach Sie suchen.

Beim Ausführen parity -hkönnen Sie den Standardschlüsselspeicher sehen. Sie wird dort als Standard aufgeführt, wo die -d --base-pathOption erklärt wird, unter Betriebsoptionen.

Unter Linux:~/.local/share/io.parity.ethereum/keys/

Unter Mac OS:~/Library/Application\ Support/io.parity.ethereum/keys/

Parity speichert Schlüssel ~/.local/share/io.parity.ethereum/für Linux. Während sie für Windows unter C:\Users\{CurrentUser}\.parity\keys. `

Laut der Dokumentation für die ethstoreSchlüsselverwaltungs-API von Parity:

geheimes Speicherverzeichnis: Es kann entweder parity, parity-test, geth, geth-test oder ein Pfad sein. Standard: Parität

(Bemerkenswert sind auch die ethkeySchlüsselgenerator-API und die zugehörigen Befehle.)

Als ich von Geth zu Parity wechselte, bemerkte ich, dass Parity meine Konten .ethereum/keystore/*irgendwie aus dem Verzeichnis in Parity importierte.

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}}

Sie befinden sich jetzt auch 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
}

(Ich füge nur Bob Gills Antwort hinzu; habe nicht den Ruf, einen Kommentar abzugeben).

Unter Windows befinden sich die privaten Schlüssel in:

%appdata%\Parity\Ethereum

und Blockchain-Daten sind in:

%appdata%\..\Local\Parity\Ethereum\chains\ethereum\db\<nodeid>\overlayrecent\db

Sie müssen das " " nicht wirklich kennen <nodeid>; Es ist der einzige Ordner dort, es sei denn, Sie haben mehrere Knoten.

(%appdata% zeigt auf ...\AppData\Roaming)

Unter Windows...

• Private Schlüssel werden gespeichert in

     %AppData%\Roaming\Parity\Ethereum\keys\ethereum
  

• Blockchain-Daten werden gespeichert in

     %localappdata%\Parity\Ethereum\chains\ethereum\db\<nodeid>\overlayrecent\db
  

Unter Windows 7 und 10 musste ich hierher gehen:

C:\Users\{your_user_name}\AppData\Roaming\Parity\Ethereum\keys\ethereum

Die Dateien, die mit beginnen, UTC-sind die Schlüssel.