
A rising wave of inquiries about configuring Tor IP addresses on Trezor Suite Desktop has sparked a heated dialogue among users. Many are struggling to set up their wallets with Tor, leading to calls for clearer instructions and better integration of privacy features.
New comments from multiple user boards highlight confusion over setting a custom IP for the Tor external connection at port 9050. One user pointed out that Trezor may not allow setting a custom IP directly since it usually expects Tor to run locally.
Another user questioned, "Is it possible to point your Trezor Suite to exclusively self-hosted services?" This indicates a desire for greater control over privacy-related settings.
Local Connection Expectations: Many believe Trezor assumes Tor will run locally, complicating configurations for those using remote Tor setups.
Desire for Customization: Users are voicing their eagerness for the ability to link Trezor Suite with self-hosted services, including for exchange rate data.
Call for Enhanced Documentation: The community is actively calling for better documentation and guidance on integrating Tor with Trezor Suite.
"The settings have to be more straightforward to avoid confusion," one frustrated user commented, echoing the sentiments of others.
While some users celebrated existing Tor integration, others expressed frustration when they couldn't easily locate the settings.
Interestingly, a comment revealed that earlier updates may have changed the appearance or function of these features, contributing to ongoing confusion.
β οΈ Users express uncertainty about the feasibility of custom IP configurations for Tor in Trezor Suite.
π Many are interested in self-hosted options for improved privacy and exchange data.
π‘ The community rallies for clearer guidance, reflecting the urgency of user needs.
Trezor's challenge remains clear: how to enhance security without sacrificing user experience. Will the upcoming updates address these concerns? Keep an eye on this developing story.