Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Import geth keys should be a one-off thing #1918

Closed
gavofyork opened this issue Aug 11, 2016 · 0 comments
Closed

Import geth keys should be a one-off thing #1918

gavofyork opened this issue Aug 11, 2016 · 0 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P7-nicetohave 🐕 Issue is worth doing eventually. Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow.

Comments

@gavofyork
Copy link
Contributor

Currently parity --import-geth-keys imports the Geth keys and continues.

It should really be parity import-geth-keys and be a one-time import and quit.
@gavofyork gavofyork added P7-nicetohave 🐕 Issue is worth doing eventually. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow. labels Aug 11, 2016
@gavofyork gavofyork mentioned this issue Aug 11, 2016
Merged
@gavofyork gavofyork added the M4-core ⛓ Core client code / Rust. label Sep 20, 2016
@svyatonik svyatonik mentioned this issue Oct 4, 2016
Merged
@snyk-bot snyk-bot mentioned this issue Sep 24, 2020
Open
@snyk-bot snyk-bot mentioned this issue Jan 18, 2022
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P7-nicetohave 🐕 Issue is worth doing eventually. Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gavofyork