Then you can't use RBF (replace-by-fee). The only thing you can do is spending those unconfirmed coins again (if possible; you can even send them to yourself again) with a higher fee than the original transaction - it is called CPFP (Child Pays For Parent). If you don't need those coins to confirm urgently then you should wait. The mempool is clearing up.

20-50 sat/byte is way too much. 12-14 sat/byte should be enough for now to get any transaction confirmed in the next few blocks. The mempool cleared itself significantly in the last 24 hours. His first transaction (~10 sat/byte fee) should get confirmed soon.

No, what you are talking about is pay to many. Coin control allows you to select specific coins which you received so that you don't use two different addresses in a single transaction, for example.


Yes, they are UTXOs which later can be used as 2 separate inputs in a transaction. You don't have to spend all of the inputs at once if one of them is sufficient to cover the outputs' value.


Actually, you don't expose your private keys. Ledger needs to know your public key to generate addresses on its own.

@Down You're right. I have misread that part and wrote Ledger instead of Electrum.

He is worried that his device could be replaced with a fake one which could steal his coins. Extremely unlikely to happen and really difficult to pull off. Sorting centres are full cameras and delivery couriers are so busy that I don't think that they have time to look through every package. Nevertheless, as I wrote above, Ledger Live will verify the authenticity of the device so OP will know that it is is a genuine one before even sending coins to it.

You are too paranoid. You should take into account that deliveries are very likely to be delayed because of coronavirus. Lots of people order goods online now. As I wrote earlier, Ledger Live will verify the authenticity of your device so you have nothing to worry about.

He won't be able to spend all of these coins. Electrum will be missing information about UTXOs which are needed to sign a transaction.

@OP It seems to be a problem on your side. I have tried to create a watch-only wallet in Electrum with your address and I can see all transactions. Try using a VPN. Also, you should be careful when moving your private key around. Do not import it to any random wallet.

Not really, RBF has been already available before Bitcoin Core 0.16 but it wasn't turned on for every transaction by default. If you increase your transaction fee using RBF, you decrease one of your output's value; you don't add new ones or remove them completely. Such transaction replaces the old one without any problems. However, just as I described above, if you create another transaction spending the same inputs but with completely different outputs then most nodes by default will reject such transaction.

Edit: If the initial transaction is marked as replaceable, its inputs can be spent once again to different outputs if the transaction is forgot by your Bitcoin Core wallet (it can be done manually). The built-in "Bump fee" functionality forces users to decrease the change output's value and does not allow to modify other outputs. If the initial transaction is not marked as replaceable then most nodes will reject another transaction as a double-spend attempt.

Yes, while creating a wallet in Electrum, you will be asked to specify the type of address you used (in this case native SegWit - p2wpkh) and you will be able to modify the derivation path optionally. It should look like this:

m/84'/0'/0' - the last number is the number of your account. The first one is 0, the second one is 1 and so on.

If you want to restore your current native SegWit account then you should leave it at default.

I have no idea why both Ledger Live and Electrum don't show the first transaction. It could be some kind of connectivity issue. Try relaunching Electrum a few times or manually changing the server (click on the green dot in the bottom-right corner, go to 'Server' tab, untick "Select server automatically", right-click on any server on the list and select "Use as server"). Can you see the second transaction on Ledger Live?

Is this transaction the one you are talking about? It is fairly small, but it was sent to exactly the same address as the 0.39 BTC transaction so if it was sent by you, there is no reason why the first transaction shouldn't appear in the wallet.

Can you see if Ledger generates exactly the same receiving address as the one you sent the coins to? When I opened Ledger Live, some of my transactions were listed as unconfirmed even though they were confirmed a long time ago. In Ledger Live, open settings, go to 'Help' tab and try to clear cache. It forces your client to resynchronize with the network. It worked for me and now I can see my transactions as confirmed.

You can follow this guide to manually remove a transaction from your wallet and double-spend it. Keep in mind that most nodes by default will reject a transaction spending the same inputs even if it pays a higher fee. You are more likely to succeed after a few days when most nodes drop the first transaction from their mempools.

Their findings are related to a specific Secure Element; not necessarily the one Ledger uses in one of their devices. They would disclose the vulnerabilities but they can't because they have signed a non-disclosure agreement (NDA) to get the full documentation of the chip. Trezor claims that the vendor is not going to share those flaws with their clients as well.

That is why you need to change the derivation path while creating a wallet in Electrum with your hardware wallet. After choosing your device, you will be asked to select the type of address you used and you might need to modify the derivation path.

legacy (p2pkh) (1...) - m/44'/0'/0'
p2sh-segwit (p2wpkh-p2sh) (3...) - m/49'/0'/0'
native segwit (p2wpkh) (bc1...) - m/84'/0'/0'

The last number is the number of your account. The first one is 0, the second one is 1 and so on.


Yes, it does. However, you can't see a full list of your addresses and you can't generate a new address unless you use the previous one. In Electrum, you can generate as many addresses as you want at once.

Trezor announced the foundation of Tropic Square - a company whose aim will be to develop a chip which will be open and fully audible. The rest of the article reveals that Trezor attempted to create a new device with Secure Element and they managed to find some flaws in the chip which they are unable to disclose due to NDA. You should read the rest of the text on your own, especially if you are disappointed with the recently found vulnerabilities in Trezor.

Still, why would you waste bandwidth which is not unmetered for everyone and allow inflating the transaction fees? It would be also bad if the nodes could potentially crash.

The mempool would quickly fill with 1 sat/byte transaction and other people would end up filling the mempool with transactions with much higher fees so the spam transactions would be dropped eventually. Apparently, it also used to crash nodes.


Bitcoin Core developers set a default value. Every node operator is free to change the DUST_RELAY_TX_FEE parameter. The default value might be lowered in the future once the default minRelayTxFee value gets lowered.

This method does not work with the latest version of Tor browser which you obviously should keep up-to-date if you are concerned about your privacy and safety. Electrum + Tor or a local instance of Trezor Wallet are the easiest and the safest ways of overcoming that limitation for now.

You needn't have sent your BTC. Sweeping means that your wallet will automatically create a transaction sending the funds to your new wallet. Most wallets won't allow you to import a private key because the recovery phrase would not recover coins from imported addresses.

Exactly the same question was answered today in this topic. TL;DR one of your outputs is equal to or lower than 546 satoshis (0.00546 mBTC) or 296 satoshis (0.00296 mBTC) if you are using a SegWit address. You can find a more detailed explanation in that topic.