Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can't send transaction with Ledger when "Use change addresses" is unchecked - Windows #1679

Closed
filchef opened this issue Feb 14, 2016 · 2 comments
Closed

Can't send transaction with Ledger when "Use change addresses" is unchecked - Windows #1679

filchef opened this issue Feb 14, 2016 · 2 comments
Labels
hw-ledger

Comments

@filchef
Copy link

filchef commented Feb 14, 2016

Can't send transaction with Ledger when "Use change addresses" in settings is unchecked.
I like to use the same address for change of transaction to consolidate bitcoins in one address but with Ledger this is impossible.Give me error "Multiple outputs with no change not supported"
Version of Electrum 2.5.4
@filchef filchef changed the title Can't send transaction with Ledger when "Use change addresses" is unchecked Can't send transaction with Ledger when "Use change addresses" is unchecked - Windows Feb 14, 2016
@kyuupichan
Copy link
Contributor

Sounds like a hardware limitation. I'm really not clear why they enforce all this daft rules; it's not just Ledger.

@ecdsa
Copy link
Member

ecdsa commented Oct 21, 2016

it works for me, with the ledger nano S. the only problem is that it displays the wrong address on the screen, but that's a separate issue.

@ecdsa ecdsa closed this as completed Oct 21, 2016
Toporin pushed a commit to Toporin/electrum-satochip that referenced this issue Dec 3, 2019
@cculianu
Improvements to Export History
54ba444 
This closes spesmilo#1679

Exporting history has been improved:

- It now returns a fee (if known) -- best efforts are made to examine
prevout_tx (and if the inputs are from wallet & known), it uses those
values to calculate fee.  This calculation is done in a thread with a
250ms timeout (because it does involve deserializing tx's, etc),
leveraging the pre-existing  fee calc code in transaction.py.  It
doesn't go out to the network to do this, though.

- Fees that are so-computed while exporting history are saved back to
the wallet in self.tx_fees

- The export history CLI has been updated as well as the Qt GUI to
always export fee (if known)

Also in this commit:

- Some small nits/fixups to Transaction class
Toporin pushed a commit to Toporin/electrum-satochip that referenced this issue Feb 16, 2021
@cculianu
Improvements to Export History
8a011d2 
This closes spesmilo#1679

Exporting history has been improved:

- It now returns a fee (if known) -- best efforts are made to examine
prevout_tx (and if the inputs are from wallet & known), it uses those
values to calculate fee.  This calculation is done in a thread with a
250ms timeout (because it does involve deserializing tx's, etc),
leveraging the pre-existing  fee calc code in transaction.py.  It
doesn't go out to the network to do this, though.

- Fees that are so-computed while exporting history are saved back to
the wallet in self.tx_fees

- The export history CLI has been updated as well as the Qt GUI to
always export fee (if known)

Also in this commit:

- Some small nits/fixups to Transaction class
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
hw-ledger
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ecdsa @kyuupichan @filchef