Reticulum is protocol allowing to build own network, wallet can just use node connection
Confirmed, problem is in the arti lib. Version 0.38 connects at Windows, 0.44+ is not, exploring possible fixes, according to changelog https://gitlab.torproject.org/tpo/core/arti/-/blob/main/CHANGELOG.md they switched to windows-sys crate for Windows since June, what can be a reason.
Downgrading arti to 0.43 helped, related issue created week ago: https://gitlab.torproject.org/tpo/core/arti/-/work_items/2678
- Tor connection issue fixed in the last release Release v0.3.7-dev · GetGrin/grim · GitHub
- Also includes Fix PIBD resume stall with newer archive target by wiesche89 · Pull Request #3932 · mimblewimble/grin · GitHub
For a few minutes after opening, the 0.3.7 wallet remains connected, but then it regresses to connecting indefinitely. Resolved by closing Grim and reopening, but can only stay connected briefly, not long enough for pool payout which occurs once every 2h.
What webtunnel url do you use? can try different url if current is not stable for you
Using this string of 10 different Webtunnel bridges, unlikely that my ISP is blocking them all. Solution was to revert to Grim v0.3.5, after which wallet reconnects and stays connected.
now it uses single webtunnel endpoint per try and put successful on top, also fixed restart on connection tor: fix restart on config change · GetGrin/grim@6b16f89 · GitHub you can also use obfs4 or snowflake bridges if webtunnel is not working for you, but it will require manual installation

