There are a number of reasons why this kind of blacklisting is problematic in practice, but take it with a grain of salt, because I'm the creator of Wasabi, so I am biased.
This Elliptic report identifies 0.65% of all Bitcoin transactions are mixing transactions. This means, if that kind of blacklisting would happen, they would have to blacklist most ...
There was a bug in the full node software we were using to broadcast transactions: Bitcoin Knots 0.19. Adam Ficsor (nopara73) upgraded the backend yesterday with Bitcoin Knots 0.20, which has already fixed the bug. However things will take a few days to fully resolve (probably 99% of issues have already resolved though) as the backend's mempool have to get ...
Is this even possible?
You can move wallet contents from almost any Bitcoin wallet software to any other Bitcoin wallet software that supports the same standards. For example, if the first wallet supports Bech32, you will need the second wallet to also support Bech32.
There are only a couple of small pieces of data that need to be copied ...
Wasabi Wallet is usable right now.
"When will it be ready for mainstream use" is a question of opinion / service availability, and those are off-topic here. See the help centre for more info.
And who is validating the transactions in the wasabi wallet ? Is it a SPV concept or full node, or centralized, owned by wasabi company servers?
The Wasabi server ...
Maybe a hacky way, but you can export the xpub/zpub to electrum and do it there with a bit of Python.
Another option would be to use the same public key with this website that seems to be able to generates a CSV of addresses: https://iancoleman.io/bip39/
A single mnemonic seed phrase can be used to derive many different addresses, either via different derivation paths, different address types, etc.
It may often be possible to create multiple instances of the same wallet using different software, but the two wallet applications you've mentioned have nuanced operation and likely use different derivation ...
I think this doc will be helpful. https://docs.wasabiwallet.io/FAQ/FAQ-UseWasabi.html#what-derivation-paths-does-wasabi-use
Wasabi follows BIP 84: Derivation scheme for P2WPKH Based Accounts, so
the main path is m/84'/0'/0'. On TestNet and RegTest Wasabi uses
m/84'/0'/0', and not the standard m/84'/1'/0'. Due to the CoinJoin
implementation, the key ...
AFAIK Coinbase looks for a five hops before / after incoming / outgoing TX. So adding extra hops will be enough for now. It can be automated with Samourai Wallet's Ricochet or my scripts for bitcoin-qt.