[PROPOSAL] Auto-churn option in CLI wallet #146

Idea from https://github.com/monero-project/monero/issues/4305

Have an option in the CLI wallet where a user is able to type churn in wallet and runs a churning process automatically N times. Purportedly, churning helps increase the number of possible outputs for ring signatures.

Help wanted... If you are game for coding this, hop on to freenode IRC #wownero

You're on your own for the coding, but a churning feature should have the following options:

Number of churns. How many times should the configuration set in #2 occur?
Type of churn. Should the tool churn the entire wallet balance (e), each subaddress balance (s), only coinbase outputs (c), or each output independently (o)? Default each subaddress.
Spend distribution. Should default to a sensible distribution, but should allow users to manually specify the desired spend periods.
Proper warnings when using churning for "dumb" behavior. Example includes attempting to churn while connected to a remote node (though can bypass for their own-controlled remote node).

Example syntax:

churn sends one transaction for all funds in a subaddress to the same subaddress. Transaction takes multiple inputs in the first transaction for all inputs sent to the subaddress. Defaults to a normal spend distribution (approx. 2 days/tx).

churn 5 o sends 5 transactions for all outputs independently to the same subaddresses they were received at. Defaults to a normal spend distribution (approx. 2 days/tx).

churn 3 e 0.5 sends 3 transactions, beginning with the first transaction sending the entire balance of the account with multiple inputs, to the main address (4...). Sends these three transactions within 0.5 days, with each transaction approximately evenly spaced out over this time period with some variance.

Feel free to choose a better syntax, but this is my initial thought process given my recommended requirements.

Is there a desire to have the tool automatically churn a single ouptut? I feel users generally would manually send transactions with a specific output in that case.

This is ready to close?

@jwinterm yes, I think so.