In such a case, Electrum should decrease the value of your transaction's output just as if you cancelled the transaction by double-spending it. If you had some coins your wallet, Electrum would add a new input to your transaction.

Your transaction will be double-spent to you with a higher fee than your original transaction automatically. Unless you have to pay a specific amount of BTC to someone, it might be a better idea to select "Increase fee" and set it to 20 sat/byte which should be enough to get your transaction confirmed in the block.

Apart from inputs and outputs, each transaction contains some other data which also increase the weight. That's why it will be cheaper to send a transaction with 3 inputs rather than 3 smaller transactions.


The person with the 50 inputs will pay way more than the other person.


Yes, you can enter whatever transaction fee you want in sat/byte.

The Lightning Network is not designed to be used for single payments. You wouldn't be even able to open a channel bigger than about 0.16 BTC with most nodes. Also, the LN uses payment invoices instead of addresses. Consider reading "Basics of The Lightning Network" and "The Lightning Network FAQ" before you start playing around with the LN. There are plenty of things that you need to understand even if you are going to use a newbie friendly wallet, like BlueWallet.

That depends on the transaction. If you were the only recipient then 7 dollars was an overkill. ~25 cents should be enough for a small (1 input; 1 output) to be confirmed in the next block.


I use PLN instead of USD but it should not matter; the exchange rate changes every few minutes and the fiat value updates everywhere.


Yes, that's how you perform CPFP by the way. Both Electrum and Ledger Live can do that. Some other wallets might not allow you do it, though.

Legacy - 1..., (nested) SegWit - 3..., native SegWit - bc1... "SegWit address" can technically refer to both nested SegWit and native SegWit address. Adding "nested" helps to be more precise.


If you receive 3x 0.01 BTC and 1x 1 BTC then you will have 4 inputs when you try to spend 1.03 BTC. Such a transaction will be slightly more expensive if you send it from a nested SegWit address.


You're close. I meant spending 0.03 BTC after receiving 0.01 BTC 3 times.

When I and other people talk about a legacy address, we mean an address starting with 1. In terms of the fees, native SegWit > (nested) SegWit > legacy address.


That's correct.


It's no big deal if you just hold. It makes a huge difference if you receive many small frequent payments which you later spend in a single transaction.

Those sites might not be able to send coins to your address, but you will be always able to spend your coins.


That depends on what services you use. See this list. Pay attention to "Send to" or "Withdrawal address". You will be fine with the vast majority of exchanges and all payment processors. Other Bitcoin users usually keep their wallets up-to-date, so receiving coins from them shouldn't be a problem either.

My reply is correct. (nested) SegWit (3...) ensures full compatibility while sending to native SegWit (bc1...) addresses will be a problem for outdated software. However, I don't think that's a real problem since most services and exchanges updated their software.


I don't remember when it was added to Ledger Live, but I recall that it started to be enforced as a default about half a year ago.


You're right. There are no fees for receiving Bitcoin. I gave you an example showing that you are going to pay more for a transaction when you combine 3 small UTXOs (inputs) into 1 Bitcoin rather than when you use 1 UTXO worth 1 BTC.


I wrote that having your coins on a SegWit address is better than having them on a legacy address, but you could save more money in the future by moving to native SegWit.

Yes, I would recommend you doing that. Some old software won't be able to send coins to your native SegWit address, but if you use major exchanges, it shouldn't be a problem. Check out this compatibility list.


Ah, I see. You won't be able to spend from those two accounts in a single transaction. You will see their combined balance in Ledger Live, though.


I have just double-checked the fees and it looks like I was wrong. Despite the growing price, they are quite low. You should get your transaction confirmed in the next block if you pay 6 sat/byte. You would now pay 6 sat/byte no matter what type of address you used. The difference is in the size of the transaction made from each type of address. See the answer below.


There is no straight answer to this question. The final fee heavily depends on the transaction size. The size increases as you add more inputs and outputs. You will pay more for a 1 BTC transaction if you received, for example, 0.2 BTC, 0.5 BTC and 0.3 BTC and not 1 BTC in a single transaction. Also, inputs and outputs for each type of address have a different weight. Native SegWit inputs/outputs weight the least, thus transactions made from such an address are the cheapest.

A legacy input weights 149 vbytes; SegWit 93 vbytes and native SegWit 68 vbytes. As you can see, you can pay over 50% less for a single input if you move from a legacy address to a native SegWit one. The savings on outputs are negligible. See this post for more detailed information.

You can play with this website to see it for yourself. Keep in mind that this website does not have a slider for native SegWit.


It is better than keeping your coins on a legacy address. You get slightly lower fees, but why not use native SegWit and save even more money?

Ledger Live should automatically detect if you have any coins on a legacy account, and should suggest adding it. Otherwise, you won't be able to add it manually.


It has been defaulting to native SegWit for quite some time now. It was probably legacy in your case since Electrum generates only native SegWit addresses (bc1...) when you choose SegWit.


That's correct.


Yes, it is true. I have been using a native SegWit address as my main one for over 2 years now. You can keep your coins on a SegWit account for now and move them once the fees go down (or keep them where they are), but you can start receiving your future payments to your native SegWit account.

That's correct. You still need to be careful when you send it to someone else. Some malware could replace your address once you copy it to your clipboard.


No. Your Ledger will generate a new address once you use the one you are talking about.


Yes, it is your receiving address. What do you mean by "use" here? Even though your native SegWit account is empty, you can use it alongside your SegWit account for future payments. Most wallets and exchanges already support sending to native SegWit addresses.

Korzystam z https://haveibeenpwned.com/ od lat i nic takiego nigdy nie miało miejsca. Ta sama strona oferuje także opcję sprawdzenia czy i ewentualnie ile razy nasze hasło znalazło się w jakimś wycieku. Oczywiście, jest możliwość pobrania tej listy na swój komputer. Paczka waży około 10 GB. A tak przy okazji, czy ktoś z Was ucierpiał przez wyciek bazy danych Ledgera?

Edit: Właśnie przeczytałem pierwszy post drugi raz. Cygan już wspomniał o tej możliwości

Both are SegWit addresses. A legacy address starts with 1.


This function does not work. A standard of signing messages is currently being worked on. Only Electrum is able to verify its messages signed using SegWit addresses. Either import your private key for that address into Electrum and inform the other party that they will be able to verify your message only using Electrum or use a legacy address instead.

The fee of your replacement transaction is too low. You cannot replace the previously broadcast transaction without increasing the transaction fee.

Yes, your wallet will remain untouched. You should also verify the installer before doing every update. Since you need to cancel your transaction urgently, you can skip this step exceptionally.

If you are running Electrum 4.0.4 or newer and if the transaction is marked as replaceable then you should see "Cancel tx" under the context menu once you right-click on that transaction. Do you recognise the address to which the coins were sent? From where did you download your version of Electrum? The address should not have changed on its own.

There are hardly any Bitcoin forks that are worth anything. If you bought Bitcoin before 1st August then you should have some Bitcoin Cash and Bitcoin SV (a fork of BCH). Before accessing and moving any of the forked coins, you should send all of your BTC to a new wallet. As far as I remember, Bitcoin Cash has implemented replay protection, but that's not necessarily the case for all of the other forks. You can use this guide to claim Bitcoin Cash and this one for Bitcoin SV. In my opinion, the other forks are not worth the hassle due to their low price.

Note: You should be able to use your Electrum seed in Electron Cash, so there is no need to export and import private keys for individual addresses.

Download Electrum from the official website and verify the installer before doing the update.


It is a completely separate issue. You will still be able to claim the forked coins after upgrading Electrum. In which forks are you interested in particular?

You're right! Sorry about that; I have never had to use such a feature. The mobile version is inferior to the desktop one; it is missing some features like testnet, coin control and message signing and it looks like it is also the case for contacts. As I wrote above, you can request that feature on their Github. I highly doubt that it will be added any time soon since there are other important features missing.