You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very similar to #6572, but would help with automation and docker use of seedwords import. Currently having an issue where the space separated word lists is been picked up as additional args on the command line.
If the word list would be encoded as Mbase58 or if the seedwords would be imported via a file, then container and similar used (kubernetes) setup would have less problems.
The text was updated successfully, but these errors were encountered:
SWvheerden
changed the title
[feat] Console wallet support base64 seedwords import via env or file
[feat] Console wallet support base58 seedwords import via env or file
Oct 18, 2024
SWvheerden
changed the title
[feat] Console wallet support base58 seedwords import via env or file
[feat] Console wallet support Mbase58 seedwords import via env or file
Oct 18, 2024
SWvheerden
changed the title
[feat] Console wallet support Mbase58 seedwords import via env or file
[feat] Console wallet support Mbase58 cipher seed or seedwords import via env or file
Oct 18, 2024
This should work very similarly to how the console wallet does paper wallet import.
You should be able to specify seed words or the cipherseed as base58.
These can be encrypted or not.
Very similar to #6572, but would help with automation and docker use of seedwords import. Currently having an issue where the space separated word lists is been picked up as additional args on the command line.
If the word list would be encoded as Mbase58 or if the seedwords would be imported via a file, then container and similar used (kubernetes) setup would have less problems.
The text was updated successfully, but these errors were encountered: