README
¶
Operation backup
Shows a secret key, encoded as mnemonic string. The shown string can be written or copied as a (paper) backup of the secret key.
Command algo-key
Usage:
algo-key [FLAGS...] OPERATION [OPFLAGS...]
Operation generate
The generate operation creates a new keypair. The public address and
private mnemonic are saved to the a file. The file saved is named after
the public address: "ADDRESS.algo-key".
Operation genmulti
Creates multisign addresses for Algorand.
A multisign address is produced by combining several Algorand addresses.
This operation expects a list of addresses on stdin. If you have multiple
address in .cfg files, as produced by algo-key backup, you can generate a
multisign address with:
grep "address" *.cfg | algo-key genmulti -m 2 -n 3
(algo-key will use a regexp to parse addresses from the results of grep.)
Operation sign
Signs Algorand transaction(s).
Optional arguments are files, containing JSON-encoded transactions to sign.
If no arguments, JSON-encoded transactions are expected on stdin.
Use the "-as ADDRESS" flag to algo-key to specific a signing key. This is
required when producing multi-signatures. For single signatures, algo-key
attempt to learn the signing key from the transaction.
algo-key expects to find private keys in a files named "ADDRESS.algo-key",
in the format produced by algo-key generate.
Documentation
¶
Overview ¶
Operation backup
Shows a secret key, encoded as mnemonic string. The shown string can be written or copied as a (paper) backup of the secret key.
Command algo-key ¶
Usage:
algo-key [FLAGS...] OPERATION [OPFLAGS...]
Operation generate ¶
The `generate` operation creates a new keypair. The public address and *private* mnemonic are saved to the a file. The file saved is named after the public address: "ADDRESS.algo-key".
Operation genmulti ¶
Creates multisign addresses for Algorand.
A multisign address is produced by combining several Algorand addresses. This operation expects a list of addresses on stdin. If you have multiple address in .cfg files, as produced by `algo-key backup`, you can generate a multisign address with:
grep "address" *.cfg | algo-key genmulti -m 2 -n 3
(algo-key will use a regexp to parse addresses from the results of `grep`.)
Operation sign ¶
Signs Algorand transaction(s).
Optional arguments are files, containing JSON-encoded transactions to sign.
If no arguments, JSON-encoded transactions are expected on stdin.
Use the "-as ADDRESS" flag to `algo-key` to specific a signing key. This is required when producing multi-signatures. For single signatures, `algo-key` attempt to learn the signing key from the transaction.
`algo-key` expects to find private keys in a files named "ADDRESS.algo-key", in the format produced by `algo-key generate`.
Source Files