feat(tor): add initial tor support support#89
Conversation
83c4154 to
3edb701
Compare
95c249d to
4fa345f
Compare
4fa345f to
aad22e1
Compare
|
@benthecarman @futurepaul 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. |
aad22e1 to
fb4f747
Compare
0cc9847 to
9991554
Compare
|
seems that is needed for the tor stuff |
4b0d93b to
11b65ff
Compare
11b65ff to
95a38c0
Compare
IIRC I was trying to fix the Nix environment, and there was some error related to it and the rust version being used. |
It bumps the fedimint version to this commit https://github.com/fedimint/fedimint/tree/54acaa63a45e6bd14e872cdaaf020e8c100d6b33, as Tor MVP support has landed on master, but hasn't been released yet (planned for 0.5.x).
As Harbor mainly uses the
Client, we basically need to specifically use theConnector::Toras an option, through the.with_tor_connector()auxiliary method.