@schinzelh , can you have a look at the Travis build?
The reason it failed has nothing to do with my PR, and you're the only one who can add packages to this whitelist anyway :-)

WTF - whitelisted packages... this is new...

I'll consider migrating from Docker based Travis to native one..

Btw: They broke Ethereum builds as well

travis-ci/travis-ci#6822 (comment)

From the description it sounds like mixing session is using 1 input from each participant and uses 1 address only which can mislead people thinking that "oh, well I have addresses for 1000 sessions, I shouldn't really care". In reality it can use up to 9 inputs per person in one mixing session iirc + it uses addresses for collaterals + sometimes mixing fails at later stage if smth goes wrong with creation of final tx (someone might be misbehaving or disconnected for some reason e.g. closed his wallet) i.e. user would see no "Denominate" tx but some of his addresses were already consumed. I think it worth fixing it at least by changing "one of your addresses" to "few of your addresses" and mentioning that such keypool size should be enough for ~100 mixing events.

"Up to 9 inputs", together with "about 100 mixing events" sounds good to me.

I'll change it later today.

New help text: