prysm-pulse/cmd/ethkey
Raul Jordan dafcfb2e18 Upstream Merge (#227)
sharding: merge upstream
Former-commit-id: 5129a4d5bc4395cd7c115b7f8db23541a512df3f [formerly e4f2b25a4277464c51b4c45384114a305464d3c4]
Former-commit-id: 2b4f0e356d3823889466d0f6ff22d5632f827f48
2018-07-02 14:25:06 -05:00
..
changepassphrase.go Upstream Merge (#227) 2018-07-02 14:25:06 -05:00
generate.go Upstream Merge (#227) 2018-07-02 14:25:06 -05:00
inspect.go Upstream Merge (#227) 2018-07-02 14:25:06 -05:00
main.go Upstream Merge (#227) 2018-07-02 14:25:06 -05:00
message_test.go accounts/abi: use unpackTuple to unpack event arguments 2018-02-16 11:46:25 +01:00
message.go Upstream Merge (#227) 2018-07-02 14:25:06 -05:00
README.md accounts/abi: use unpackTuple to unpack event arguments 2018-02-16 11:46:25 +01:00
run_test.go accounts/abi: use unpackTuple to unpack event arguments 2018-02-16 11:46:25 +01:00
utils.go Upstream Merge (#227) 2018-07-02 14:25:06 -05:00

ethkey

ethkey is a simple command-line tool for working with Ethereum keyfiles.

Usage

ethkey generate

Generate a new keyfile. If you want to use an existing private key to use in the keyfile, it can be specified by setting --privatekey with the location of the file containing the private key.

ethkey inspect <keyfile>

Print various information about the keyfile. Private key information can be printed by using the --private flag; make sure to use this feature with great caution!

ethkey sign <keyfile> <message/file>

Sign the message with a keyfile. It is possible to refer to a file containing the message.

ethkey verify <address> <signature> <message/file>

Verify the signature of the message. It is possible to refer to a file containing the message.

Passphrases

For every command that uses a keyfile, you will be prompted to provide the passphrase for decrypting the keyfile. To avoid this message, it is possible to pass the passphrase by using the --passphrase flag pointing to a file that contains the passphrase.