But you would be running makers AND takers?
I would probably write a Maker implementation, which ran interfaced directly between the rest of the AM Hot Wallet system and the Join Market Network, which essentially runs on auto-pilot
*I would also probably write a Taker implementation, which is kicked off on an Ad-Hoc Basis from existing GUI software I've written to manage everything, including performing Cold Signatures for Cold Trades. In this case I would be initiating a CoinJoin and Digitally Signing it off from a Hardware Wallet
* As I said earlier, I don't think that TX graph is a big JM issue to begin with... plausible deniability is good enough for me, especially by the time it gets to depth 4, let alone if it has been circling there for months. I'm just picking on your claim that the advantage of this service (over using JM directly) is that would break the TX graph, which it doesn't really do, or at least doesn't do it any better. And it could make input commingling a bigger problem. If I'm not mistaken the default maker tries to avoid co-spending my own inputs at all depths. If I send coins to your proposed service there's probably a higher a chance my coins could be spent together as early as the next CoinJoin after the initial one.
I have had a think about what you said some more, over a long walk. I still think there is merit to this and that I wouldn't be cutting into the branch I'm sitting on, the key point here is that UTXOs are not only circulated by continual CoinJoining but also through conventional mixing, which is what I am already doing. Essentially your deposits are switched out, later, after being CoinJoined, so this hypothetical branch we speak of 20 CoinJoins down the line - I don't think would actually be a likely scenario.
* Exact details of the implementation, precisely, exactly how this would work, including ensuring that I didn't co-spend (or even present to the network) more than one of your deposit inputs in a CoinJoin that you had deposited in a trade, is a detail and a problem that I would solve, which is part of actually doing it and takes time - the kind of detail that needs to be solved later - if I decided to actually go ahead and do that.
For the moment I am only trying to gauge people's feelings on this. You have a JoinMarket node running permanently, but others do not.
I am specifically trying to gauge how people feel about receiving a Coin that has been "CoinJoined" VS a Coin that may or may not have a directly "questionable" lineage.
Just to point out the absolutely obvious, in-case anyone was wondering. A Coin that is Deposited in a Trade would never be CoinJoined then sent back out to the user ---- that would be fantastically rubbish.
I am going to continue to think and sleep on it. Stuff appears to happen in sleep and sleep-like states, for me at least anyway.