Tor testing / validation

[futurepaul]

From @oleonardolima:

I think we could make use of shadow or chutney for testing, but I still need to grasp more about Harbor's project structure and testing.

I also wonder about validations that we could implement, and make use of compile_error! & co macros to make sure it's using the proper connector, and really annoy any user that changes that to clearnet for example, let me know what you think.

TIL what shadow / chutney are: https://research.torproject.org/tools/

For now we don't plan on having anything BUT tor, are there ways we should still be validating that comms are happening over tor? Would be sweet to be able to tell the user "yes tor is work" if that's possible.

[oleonardolima]

As the plan is to be Tor only I think that we need both:

(1) An integration testing suite, that uses either shadow or chutney, to simulate a Tor network, and use it for running tests for the main connection-related features/operations

(2) I guess I'd add further questions: (2.1) What other services/resources does Harbor rely on, besides the Federation ? Are those accessible/exposed via OnionV3 address ? (2.2) Do we want to allow it to connect to clearnet federations/resources over Tor ? I'm asking because I think those are the points that require more validation that everything is going over Tor.

PS.: Regarding (1), I tend more towards shadow as by previous research, I assume it's way easier to add it in Harbor, then in Fedimint because the CI is "fresh"/small.