╰─$ docker run --rm -it -v ~/:/app/output/:rw ashelkov/owg:latest -m -p -o ~/.wallets/ solo
Custom mnemonic to use for generating wallets/addresses: [redacted]
Password for mnemonic used to generate wallet master key:
[Confirm mnemonic password:]
[com.ashelkov.owg.Application] [2024-03-13 05:57:29] [SEVERE] Can only specify option -o once.

edit:

Here's the updated command:

╰─$ docker run --rm -it -v ~/:/app/output/:rw owg:latest -m -p -K -o ~/.wallets/ solo AVAX

It would be useful to support multiple output formats like JSON, YAML, etc. so that this tool can be used in a multi-step pipeline, or it's output consumed by other applications.

E.g.,

bin/owg-local.sh -o ~/.wallets/test.json -p cold -c BTC --format json

test.json

{
  "createdAt": 1635296673,
  "currency": "BTC",
  "mnemonic": "test test test ... test",
  "xpub": "zpub123456.....lskdfjasdklfj",
  "accounts": [
    {
      "address": "0x12345...ABCD",
      "path": "m/44'/60'/0'/0/0"
    },
  ]
}

Steps

1. Run the following command, but with the flags in different orders:

WALLET_ID=$(date +%s) WALLET_CURRENCY=BTC bin/owg-local.sh -o ~/.wallets/cold/$WALLET_CURRENCY/$WALLET_ID -p cold -c $WALLET_CURRENCY

For example:

WALLET_ID=$(date +%s) WALLET_CURRENCY=BTC bin/owg-local.sh -o ~/.wallets/cold/$WALLET_CURRENCY/$WALLET_ID -c $WALLET_CURRENCY -p cold

Expected behavior

A user can call owg with the required flags (-o, -p, etc.) in different order permutations, and the wallet should be generated as expected.

Actual behavior

output varies, perhaps depends on the order of flags?

SEVERE: Expected a command, got -c

SEVERE: Was passed main parameter '-o' but no main parameter was defined in your arg class

A new command mode where one can generate multiple mnemonics for a single wallet, each representing a 1 of n multi-sig

https://ergoplatform.org/

I've been using Ian Coleman's website to double-check that the addresses and keys are correct. Currently, there is no support for Algorand. I have no pressing need for ALGO private/public keys right now, so if someone else would like to add them, that would be appreciated.

I've been using Ian Coleman's website to double-check that the addresses and keys are correct. Currently, there is no support for Avalanche. I have no pressing need for AVAX private/public keys right now, so if someone else would like to add them, that would be appreciated.