Quote from: ranochigo on Today at 02:33:29 AM

My question seems pretty trivial but why doesn't ChipMixer adopt Segwit yet? It was activated such a long time ago and even if they had planned to use Legacy from a long time ago, it seems like it would be better to have some mix of bc1 and p2pwsh addresses in the chips?

The last thing I read about it:

Quote from: ChipMixer on December 19, 2018, 01:20:17 PM

last few days some of low size chips were preloaded with Segwit (segwit over p2sh) instead of non-segwit (p2pkh). Out of all withdrawn Segwit chips - none were sweeped by our users. If you were affected - please contact our support - we will help you get your coins.

ChipMixer Segwit rollout will be delayed.

I haven't imported SegWit private keys in a long time, but last time I did it was a bit more complicated than native addresses:

Quote from: Xynerise on April 24, 2018, 08:00:01 AM

For P2SH-P2WPKH addresses (Addresses starting with "3")
Just add p2wpkh-p2sh: directly in front of your private key.
For example

Code:

p2wpkh-p2sh:5BitcoinPrivateKey

This should generate the corresponding p2wpkh-p2sh bitcoin address.

For P2WPKH addresses (Bech32, starting with 'bc1')
This time we'll add p2wpkh: in front of the private key.
For example

Code:

p2wpkh:5PrivateKey

This should generate the corresponding Bech32 address