Mmgen-wallet

**New features:**

- Altcoin framework + full Litecoin support [(commit)](https://github.com/mmgen/mmgen/commit/35d10911596c76227b8cd6318681c6ac9dc02a42)

- Offline transaction autosigning [(commit)](https://github.com/mmgen/mmgen/commit/8fb3efd99cc2f62e7f12f0e1f9893dd287064035) [(manual)](https://github.com/mmgen/mmgen/wiki/man-autosign) [(VIDEO)](https://github.com/mmgen/mmgen/releases/tag/autosign)

**New features:**

- Bob and Alice regtest mode for testing MMGen in a mock two-user environment.
[Documented](https://github.com/mmgen/mmgen/wiki/MMGen-Quick-Start-with-Regtest-Mode) in the wiki, tests added to test suite

- Compressed P2PKH address support (address type 'C')

- BCH (Bitcoin Cash) support

- Segwit (address type 'S') support deployed after Segwit activation on mainnet

- and, of course, numerous bugfixes and small improvements

**Support for Segwit (P2SH-P2WPKH) addresses:**

- Generate Segwit addresses by invoking 'mmgen-addrgen' with the
'--type segwit' option
- Import Segwit addresses into the tracking wallet as usual
- Segwit and legacy MMGen addresses are distinguished by 'S' and 'L'
identifiers in the tracking wallet and command line

Transaction example:

mmgen-txcreate F00BAA12:L:21,1.23 F00BAA12:S:1

(spend 1.23 BTC to legacy address 21 of your default wallet (with Seed ID
F00BAA12) and send the change to Segwit address 1)

Segwit and legacy addresses for a given seed are generated from different
sub-seeds so are cryptographically unrelated to each other.

BIP 125 replace-by-fee (RBF) support:
- Create replaceable transactions using the `--rbf` switch to `mmgen-txcreate` and `mmgen-txdo`
- Create, and optionally sign and send, replacement transactions with the new `mmgen-txbump` command

Satoshis-per-byte format:
- Tx fees, both on the command line and at the interactive prompt, may be specified either as absolute BTC amounts or in satoshis-per-byte format (an integer followed by the letter 's')

Improved fee handling:
- Completely reworked fee-handling code with better fee checking
- default tx fee eliminated, max_tx_fee configurable in mmgen.cfg

Command scriptability:
- New `--yes` switch makes `mmgen-txbump` and `mmgen-txsign` fully non-interactive and `mmgen-txcreate` and `mmgen-txsend` mostly non-interactive

Bugfixes and usability improvements:
- 'mmgen-tool listaddresses' now list addresses from multiple seeds correctly
- Improved user interaction with all 'mmgen-tx*' commands

The RBF and new fee functionality are documented in the [Getting Started][01] guide.

The guide has also been updated with a new [Preliminaries][03] section and a new [Hot wallets and key-address files][02] section.

[01]: https://github.com/mmgen/mmgen/wiki/Getting-Started-with-MMGen#a_fee
[02]: https://github.com/mmgen/mmgen/wiki/Getting-Started-with-MMGen#a_hw
[03]: https://github.com/mmgen/mmgen/wiki/Getting-Started-with-MMGen#a_i

New features:
- New `mmgen-txdo` command creates, signs and sends transactions in one operation
- Export seed to hexadecimal (mmhex) format
- Support for 8-color terminals, better default colors on 256-color terminals
- `--force-256-color` option overrides terminfo entry and $TERM environment variable
- Selected commands of `mmgen-tool` now accept stdin input
- Transaction file format change: TXID appended to file after tx is broadcast

A new tutorial, [Recovering Keys Without MMGen](https://github.com/mmgen/mmgen/wiki/Recovering-Keys-Without-MMGen), has been added to the wiki

This release brings full functionality and wider testing to the MS Windows port. MMGen now works with both WinXP/MinGW32 and Win7+/MinGW64, and separate, updated installation instructions for both platforms have been added to the wiki. A working MinGW environment is now required to run MMGen.

**New Windows features:**
- Full non-interactive test suite support with pexpect (PopenSpawn)
- secp256k1 address generation support
- Secure wallet deletion with sdelete

**Windows bugfixes:**
- A critical bug in writing the encrypted keyaddrfile has been fixed. This bug
would have affected only online wallet use and would not have led to the loss
of coins
- Cookie filename fixed; RPC cookie authentication now functional

**General features:**
- `--bitcoin-data-dir`, `--rpc-port`, `--rpc-user`, and `--rpc-password` options