nostr:nprofile1qqsfuv8fgq3cek0ta0rr9qtkm4x3pxqjz22y9u4xcwrj0lrxlfl2jzsppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj7qg3waehxw309ahx7um5wgh8w6twv5hs25c7t0 I am currently testing nostr:nprofile1qqsf80gvdu7vhtj88z9srtrvuzevqyc3fh9yczxkufcj6nlhzsz68scpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqg0waehxw309aek7mr0vdhjumnvmxmjyh under Whonix VM enviroment and I had to disable the Wasabi TOR module to make it work (backend, sync, etc.). The reason I guess is because Whonix is by default connected via TOR.

My question is how the TOR identities are handle with this setup? Is #Wasabi wallet able to change TOR identities as same as it would so it under its own integrated TOR module?