Skip to main content
replaced http://ethereum.stackexchange.com/ with https://ethereum.stackexchange.com/
Source Link

The best practice is to comply with the Web3 Secret Storage Definition. This will allow your private key to be easily imported into clients such as Geth and cpp-ethereum (eth). The definition encodes to a JSON fileJSON file (unlike a Base58Check-encoded printable string as in BIP38) and includes test vectors.

The best practice is to comply with the Web3 Secret Storage Definition. This will allow your private key to be easily imported into clients such as Geth and cpp-ethereum (eth). The definition encodes to a JSON file (unlike a Base58Check-encoded printable string as in BIP38) and includes test vectors.

The best practice is to comply with the Web3 Secret Storage Definition. This will allow your private key to be easily imported into clients such as Geth and cpp-ethereum (eth). The definition encodes to a JSON file (unlike a Base58Check-encoded printable string as in BIP38) and includes test vectors.

link to related question
Source Link
eth
  • 86.5k
  • 53
  • 287
  • 411

The best practice is to comply with the Web3 Secret Storage Definition. This will allow your private key to be easily imported into clients such as Geth and cpp-ethereum (eth). The definition encodes to a JSON fileJSON file (unlike a Base58Check-encoded printable string as in BIP38) and includes test vectors.

The best practice is to comply with the Web3 Secret Storage Definition. This will allow your private key to be easily imported into clients such as Geth and cpp-ethereum (eth). The definition encodes to a JSON file (unlike a Base58Check-encoded printable string as in BIP38) and includes test vectors.

The best practice is to comply with the Web3 Secret Storage Definition. This will allow your private key to be easily imported into clients such as Geth and cpp-ethereum (eth). The definition encodes to a JSON file (unlike a Base58Check-encoded printable string as in BIP38) and includes test vectors.

Source Link
eth
  • 86.5k
  • 53
  • 287
  • 411

The best practice is to comply with the Web3 Secret Storage Definition. This will allow your private key to be easily imported into clients such as Geth and cpp-ethereum (eth). The definition encodes to a JSON file (unlike a Base58Check-encoded printable string as in BIP38) and includes test vectors.