It currently only supports ip:port but we are adding support for .onion and dns as well, will release soon
How to connect to a full node in nostr:nprofile1qqsf80gvdu7vhtj88z9srtrvuzevqyc3fh9yczxkufcj6nlhzsz68scpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqg0waehxw309aek7mr0vdhjumnvmxmjyh OVER TOR? #asknostr
(Settings => Connect to Bitcoin Node RPC)
The nostr:nprofile1qqsf80gvdu7vhtj88z9srtrvuzevqyc3fh9yczxkufcj6nlhzsz68scpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqg0waehxw309aek7mr0vdhjumnvmxmjyh docs are not explicit about tor connections: https://docs.wasabiwallet.io/using-wasabi/BitcoinFullNode.html
Discussion
Beautiful to hear. Your software made it to my testing ground. With the intention to recommend it to people with tradeoffs focusing on ease of use and uncluttered user interface. You might get a place right besides Sparrow Wallet for my onboarding process.
I need to learn more about the tradeoffs when using your default RPC settings. You write about tor request isolation, this might work good enough concerning privacy for my use cases, if tor request isolation can be implemented in a robust and safe way if at all.
h/t nostr:nprofile1qqstu7jjjx6n969erredexq539y2x0f7pks80zxhg9hh8dx8298s3espzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcqdv0pv