This repository has been archived by the owner on Apr 18, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
Allow to set private key instead of mnemonic words in .env #61
Labels
config
About config files(service.vvisp.json, state.vvisp.json, .env etc)
enhancement
New feature or request
utils
About vvisp-utils
Milestone
Comments
cloudinertia
added a commit
that referenced
this issue
Jan 22, 2019
cloudinertia
added a commit
that referenced
this issue
Jan 22, 2019
cloudinertia
pushed a commit
that referenced
this issue
Jan 22, 2019
cloudinertia
pushed a commit
that referenced
this issue
Jan 23, 2019
cloudinertia
pushed a commit
that referenced
this issue
Jan 23, 2019
cloudinertia
pushed a commit
that referenced
this issue
Jan 23, 2019
cloudinertia
added a commit
that referenced
this issue
Jan 23, 2019
cloudinertia
pushed a commit
that referenced
this issue
Jan 23, 2019
cloudinertia
pushed a commit
that referenced
this issue
Jan 23, 2019
cloudinertia
pushed a commit
that referenced
this issue
Jan 23, 2019
JhChoy
added a commit
that referenced
this issue
Jan 23, 2019
Closed with #70 |
cloudinertia
added a commit
that referenced
this issue
Jan 23, 2019
junbeomlee
pushed a commit
that referenced
this issue
Jan 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
config
About config files(service.vvisp.json, state.vvisp.json, .env etc)
enhancement
New feature or request
utils
About vvisp-utils
I'm submitting a...
Current behavior
Only mnemonic words and key index are allowed.
Expected behavior
At
.env
we can addMinimal reproduction of the problem with instructions
Considering conflicts of mnemonic and private key
What is the motivation / use case for changing the behavior?
Environment
The text was updated successfully, but these errors were encountered: