The way Ledger Live works today is that the wallet is getting its balances from a central server run by a third party. This is convenient because it means the user doesn't have to run their own full node for each coin they have in their wallet. But this convenience comes at the cost of some security and privacy guarantees that full nodes provide.
I would like to be able to connect my Ledger Live app to my own full nodes, either nodes running locally on my computer or on a remote server. These full nodes might only be running traffic through Tor, so the wallet application should also support connecting to these nodes through Tor.
Settings
Agreed! This would be a very useful feature!
We need this, my node my rules, not my node not my rules!
This is a must.
Electrum is lightning years ahead of ledger live.
There should be an option to force the use of TOR + option to pin it to your NODE
Why would Ledger HQ keep logs of your IP address and what UTXOs are you checking!? Come on
Please allow this, even without TOR, it would be fine!
Any news on this?
Isn't this already by possible by just using your Ledger with Wasabi or Electrum, for example, which can be connected to your own node??
Many users have indeed switched to Electrum or Wasabi to connect their own node to the hardware-wallet, including me.
This feature request has been open for years now with no movement on the issue. What is the problem? Is Ledger making money from this data? I would rather not leave Ledger products/services, however since we are being ignored I may have no choice.
Following up on this
I've had no success using Ledger Live Desktop on my Ubuntu 20.04.1 laptop. I've been using Ledger Live on my Android phone in the meanwhile.
Sent with ProtonMail Secure Email.
โโโโโโโ Original Message โโโโโโโ
On Tuesday, September 1, 2020 5:23 PM, Jacksper13 notifications@github.com wrote:
Following up on this
โ
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Most helpful comment
3291 adds support for satstack. I think this addition will allow this issue to be closed.