Bitcoin isn't stored as just a "sum" number like cash in your bank account... it's stored in "chunks" called UTXO's (Unspent Transaction Outputs). So, every time you receive some Bitcoin, you get another chunk added to your collection. When you want to send someone some Bitcoin, unless you have a chunk that is exactly the right size to cover the amount you're sending + fee, then there will be leftovers... this is called "change" and is simply put back in your wallet as a new (smaller) chunk.

Let's say you have chunks worth 0.1, 0.2 and 0.3 BTC... you decide you need to send 0.15 to someone. You don't have a chunk that is exactly 0.15... so your wallet will use either the 0.2 or 0.3 chunk (depending on what sort of UTXO selection algorithm your wallet uses).

Let's assume your wallet uses the 0.2 chunk. Your wallet will create the transaction and says please send 0.15 to AddressA... and put the remaining 0.5 back in my ChangeAddressY (we'll ignore fees for now).

More reading here: https://en.bitcoin.it/wiki/Change
and here: https://en.bitcoin.it/wiki/Coin_analogy

Basically, unless you spend the exact amount of some combination of chunks, you're most likely going to have 1 extra output on any given transaction.

Note: The number of Outputs has a very minimal effect on the data size of a transaction compared with the number of Inputs which will have a much greater impact on the data size of transaction (and hence will affect the total fee more).

The reason for this is that an Input typically has 2-3 times the data size of an output. For instance, with transactions using older bitcoin addresses (P2PKH) an input would be around 148 bytes... and an output would be about 34 bytes. Newer addresses are slightly less.

Unless you're sending to multiple people in 1 transaction (like an exchange doing a batched send), chances are that the data size of your inputs is going to be far greater than the data size of your outputs.

This is why receiving a lot of small BTC amounts ends up costing a lot in fees to move... if you have 10x chunks of 0.01... and you want to send 0.1 BTC, you suddenly have 10 inputs and your transaction data size is going to be quite large and require a very large fee.


Correct, send the maximum amount in 1 transaction. If you use the max button in Electrum (or set the amount value to ! ) it will automatically calculate that "max" value for you based on the total amount in your wallet - minus the transaction fee.

I know I'm a little late to the party here, but that's not strictly true.

I have the Ledger Live app installed on my Android device (Samsung Galaxy S20 FE), and can connect my Ledger Nano S to it using a "USB C to USB A adapter" like this:


and then using a standard USB-A to Micro USB cable to connect the Nano S. (I don't have a USB-C to Micro USB cable to try)


It's fully functional, if somewhat of a janky solution


NOTE: There is a Ledger Live app on the Apple store as well, but I don't have a suitable iOS device (nor the appropriate adapters) to try and test connecting the Nano S to iOS devices.

This address does not appear in either of those transactions, so you have NOT sent any funds to it.


"Unpaid" tells me that what you've done is setup a transaction but then clicked "Save" instead of "Pay...".

Effectively, you entered an Address, the amount and then didn't actually sign or broadcast the transaction.

If you right click that "Invoice" item and then select "Details" it will probably show something like this:


except with your 3BVy8iSzyFGYSzqngk1tdhYiLCMuucRFZB address showing.


I have no explanation for where these other addresses/transactions came from... there is certainly something weird happening. Either your seed/wallet has been compromised and a 3rd party has restored your wallet and moved the funds, or the copy of Electrum you are using is "bad"™.

Given you stated you checked digital signatures etc, then it would appear your seed/wallet has been compromised in some other way. 

So, both of these transactions are showing in your Electrum client?

If so, can you please confirm which Coinbase address you were trying to send the funds to?

Also, did you attempt to "cancel" a transaction or do a "bump fee" on your transaction?

38 - HCP

Happy Holidays to all!

82 - HCP

Thank you kind sir...

82 - HCP

Amazing to see these raffles are still running... plus such cool prizes!

Firstly, amazing script... fantastic work. Made the image transfer and post modifications a mostly painless process. 

Although, I did have a couple of issues with the script... it was "hard crashing" on one post that had some "interesting" text in it. It didn't like all the URL text at all


So, I simply made a backup of the original post text, then removed all the url text, restarted the script and, once it finished, edited back in the original text.


Additionally, there were 2 or 3 other posts that ended up returning a "(403) Forbidden" when the script attempted the POST to edit the image URLs:


The posts in question definitely weren't in locked threads etc, as I was able to manually upload the images to TalkImg and then manually edit the image URLs into the posts, so I'm not sure what happened with those.

Thankfully it was only 2 or 3 posts out of my 10000+ posts over 514 pages that the script had to check and only about 3 or 4 pics in total, so it wasn't really a big deal.


Again, great work on the script... and a huge shout out to joker_josue for setting up TalkImg.

Working on it... was waiting for joker_josue to setup my TalkImg account.

Script is currently running... might take a while:


 

Last edit on the OP (according to BCT) appears to have been in September 2014:


Seems to check out, with that wayback machine URL showing the post in April 2014 not having the weird characters.

Thanks guys,

Yeah... I missed the whole Imgur debacle earlier this year. I was reading all the threads yesterday and I saw all the scripts and info regarding how to fix all my img links.

Now just waiting to hear back from @joker_josue about having an account setup on TalkImg.

I'll have to see if I can get these images working again... they still exist!

Links:
https://i.imgur.com/h9a6EXG.png
https://i.imgur.com/E5y91Wo.png
https://i.imgur.com/bWHV686.png

Interestingly... I have Armory and Bitcoin Core v0.25.1 working ok, but the Testnet version of Armory is exhibiting a similar behaviour to what the OP has. Armory Testnet is getting stuck at "Scanning Transaction History".

It is always at 88% (tried it 3 times now)... very strange. I can't find any obvious errors anywhere that are causing this issue. :-/

100% concur on this... DO NOT use the IOS mycelium wallet. It's pretty much "broken" at this point.

Indeed... malware devs aren't likely to waste time trying to implement malware for a closed ecosystem like iOS when it is likely much easier to find and exploit issues in an open source ecosystem like Android.

Especially given the market share disparity between the two globally... Android a little over 70%, iOS under 30%, refer: https://www.bankmycell.com/blog/android-vs-apple-market-share

Although it is interesting to note that in the US, iOS has ~57% market share.


In other case, using a wallet on your phone for anything other than casual day to day spending etc is likely a "bad idea"™... certainly not a place to be storing your main stash!

Then, unless you have an interest in learning repair, I'd recommend getting a replacement device. Definitely contact Ledger support and see if they'll offer repair or replacement first though. Costs nothing to ask.

Once you've sourced a replacement device (be it Ledger or something else), simply load it with the seed and away you go.

Once you have your new device setup and working, then if you decide you might want an "emergency backup" device, you can always try sourcing a replacement screen and giving it a go. If it doesn't work, you'll be out like $10 (for screen+shipping). If it does work, you will have a cheap backup device.

For now, I'd definitely stop using the current device to prevent any further damage unless you have a super urgent need to move coins (and even then, I'd recommend other solutions)

The short version is: your screen is buggered, you need a new device or screen.

Given you dislike of uncertainty and "new things", your options are:

1. Contact Ledger support and see if they'll replace the unit
2. If they won't replace it, see if you can get a discount on a new device from them
3. If they won't do a discount on a new device, then buy a new one full price
4. Buy a BIP39 compatible device from a different manufacturer

I do not recommend that you fiddle about with replacement screen options unless you have prior experience with electronics repair. It isn't exactly a super complicated process (as seen on this video: https://www.youtube.com/watch?v=hnJKEoBHZdY) and doesn't require soldering anything, but it isn't "changing a light bulb" easy.

Having said that, if the device is basically non functional, and Ledger won't replace (or provide a substantial discount) then spending a few dollars on a replacement screen from aliexpress might be worth a try as you're really got nothing left to lose at that point. You just need to ensure you buy the 12pin version of the screen (there are 8pin, 12pin and 14pin variants)

Hardware wallets have never really been very good at dealing with large numbers of UTXOs as they pretty much all run using relatively low-end hardware with the associated memory/CPU limitations.

What might be "fine" for you average PC/desktop, can really cause issues with hardware wallets as they struggle to process/verify all the data from 10s/100s of transactions etc.

They want you to deposit more money to withdraw funds you already have there? Honestly, this seems like a scam.

Have you ever used this "broker" before? Where/what service was this "withdrawal" from? Something definitely smells fishy here!

Yeah... I don't get that "toast" message (the in-app popup)... it just drops straight back to the wallet overview screen and there is no org.electrum.electrum folder created anywhere.

I'm running on a Samsung Galaxy S20FE on Android 13, so I assume it's related to the issue that Edwardard referenced regarding storage issues and the way that Electrum is attempting to access the file system. I'd take a dig around the source code, but I haven't done any Android dev work in a looooooooooong time... not even sure I have the ADB installed these days