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 ...
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 ...