Quote from: lostinthewild on Today at 02:01:13 PM

I give you a private key with about .01 BCH and all other forks, and you give me private keys containing dust for already split BCH/BSV/BCH-A/BTG/BCD so that I can avoid replay?

It's much easier if I can just dust your old Bitcoin addresses for you. Of course, this (slightly) compromises your privacy, but if you use any dust I send you, chain evidence will lead to the same addresses anyway.
If you're okay with this, just email or PM me the addresses, and I'll dust them all at once (unless you have many, then even Forkdust becomes expensive nowadays).
There's no replay risk for BTG/BCD, so those don't need dusting.

Quote

I had looked at Coinomi. My one question is that Coinomi creates hierarchical deterministic wallets. It doesn't import private keys, it sweeps them. My fear was that sweep would cause issues with the splitting of the unswept keys. I'm assuming that it doesn't, since I have the private key it's been swept to.

Even if you mess up the replay protection and end up moving coins on other chains too, you're basically back to square one: you'll have to get the private keys from Coinomi, and try again. Just don't make the mistake of sending replayed coins to an exchange.

Quote

For the coins that it can't deal with, I'd use that initial swept private key to sweep into the other wallets?

Correct.

Quote

In other words, start with the BCH, sweep the keys into Coinomi, send the swept keys to a new address using the dust from an already split BCH.

That's the wrong order: first add BCH dust to your old BTC address, then sweep the full BCH balance from that address into your Coinomi BCH-wallet.

Quote

After that, use that private key from the initial sweep in Coinomi to sweep into other wallets for the other coins. Is that basically correct?

Correct. I've used Electrum-clones for BCH-A and BCD. I just don't trust them enough to do it outside a VM.

Quote

So, how do we exchange the private keys?

This is the safest:

Quote from: LoyceV on March 05, 2021, 09:50:14 AM

Don't send private keys from a standard email that doesn't encrypt messages.
The easiest way to send private keys (or seed words, depending on your wallet) is if you create a Protonmail account. My email:

Code:

LoyceVswitzerland@protonmail.com

This way, the email has end-to-end encryption and should be secure. There's of course always the risk of your (or my) computer being compromised.
Alternatively, you can send half of each private key to my Protonmail email, and the other half by Bitcointalk PM. This way the parts don't end up on the same email account.

But considering it's only a small amount, a PM on Bitcointalk works too.