Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for providing a private key instead of mnemonic to run an element node #374

Closed
gjgd opened this issue Feb 19, 2022 · 1 comment · Fixed by #375
Closed

Add support for providing a private key instead of mnemonic to run an element node #374

gjgd opened this issue Feb 19, 2022 · 1 comment · Fixed by #375

Comments

@gjgd
Copy link
Contributor

gjgd commented Feb 19, 2022

I'm following instructions here and at some point the docs ask to provide a mnemonic. It's a bit inconvenient because:

  • Don't want to provide my metamask mnemonic which has mainnet ETH on another address
  • It's inconvenient to create a separate mnemonic because metamask only supports having one mnemonic, so would have to manage it some other way.

Instead, would it be possible to use Element using an exported private key? Would be easier because then people could create a separate address on metamask for Element, and export the key for running the node, while still maintaining separation with other addresses.

@gjgd gjgd changed the title Add support for for providing a private key instead of mnemonic to run an element node Add support for providing a private key instead of mnemonic to run an element node Feb 19, 2022
@gjgd
Copy link
Contributor Author

gjgd commented Feb 19, 2022

Will send a PR sometime this week

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant