Your example would require someone to use the same inputs in both of these transactions. Transactions are conflicted if they attempt to spend the same inputs.


Most nodes should reject the second transaction if they have the first one in their mempool even if it offers a lower fee. That is why using RBF is recommended in case the fee is set too low. Still, this does not make 0-conf transactions completely safe because of the race attack.

Trezor claims not to log any user data in their Trezor Wallet. If you use the beta version, it sends some usage data and error logs due to experimental features. If you are really concerned about your privacy then you can use Trezor Wallet once - to initialize your device. For receiving and sending transactions you can pair your wallet with Electrum. It even supports more features (coin control and generating native SegWit addresses).


Trezor Bridge is required to use Electrum and Trezor Wallet if your browser doesn't support WebUSB.


Here is a tutorial for Electrum. You can skip the first part with the commands; follow the pictures step by step. Don't forget to download the latest Trezor Bridge.

It depends on the anti-virus software you use. I use Malwarebytes Premium and it doesn't block the website.

Great! One more thing before you update. Make sure to uninstall all the apps before updating to the latest version. It is a one time thing and you won't have to do it for the future updates.

Try connecting it to a different USB port. You can also try other steps from Ledger support website.


There is a gear icon in the top-right corner which will show you the settings when you click on it. The software itself should be fine.


As far as I know, Ledger Live does not support firmware versions under 1.3.

There could be several things causing such a behaviour. Try using a different USB cable or a different PC if it still doesn't work. Also, what version of Ledger Live do you have? You can check it the Settings -> About.

There is no need for you to buy a new device. What kind of error do you get when you try to connect your device? Does anything happen at all?

This might actually help. Instead of recovering you wallet, you can copy the wallet file. Press WIN + R and enter %appdata% . You should see 'Electrum' folder inside which there should be 'wallets' folder. Copy it to your desktop, uninstall Electrum and make sure that 'Electrum' folder in %appdata% is gone. If not, delete it as long as you have copied your wallet. Don't forget to put 'wallets' folder back there once you reinstall Electrum.

Try disabling your firewall and any anti-virus software you have. You can also try connecting to some server manually (although Electrum should change servers on each startup). Click on the red dot in the bottom-right corner, select 'Server' tab, untick 'Select server automatically', right-click on any server on the list and select 'Use as server'.

HD wallet does not protect from mixing coins from other addresses in the same wallet. Most wallets don't support coin control which helps not to use coins from specific addresses as inputs in a new transaction.


Yes, you can run a node in pruned mode. It will take significantly less space. Note that you will still have to download and verify all the blocks.

Bot Piggy'ego przestał działać kilka miesięcy temu. Pojawiły się dwie alternatywy. Bot od LoyceV, który aktualizuje powiadomienia dwa razy w ciągu godziny i przedstawia je w formie prostej strony (przykład) oraz bot od giammangiato, który przesyła powiadomienia o zdobytych meritach i zacytowanych postach poprzez Telegram.

So, you don't mind paying more for a ~90 sat/byte transaction with multiple inputs when the fees spike instead of consolidating them at 1 sat/byte and making a small ~90/byte transaction? Here is an example. Let's say you have 20 inputs and need to send all of your coins to a single address (assume all addresses are legacy).

Without consolidation (90 sat/byte): 0.0027036 BTC
With consolidation: 0.00003004‬ BTC (at 1 sat/byte) + 0.0001728‬ BTC (at 90 sat/byte) = 0.00020284 BTC

The savings are quite clear to me.


Apparently, OP sent a large transaction with 11 inputs and 142 outputs. One of those outputs, was his address from Electrum.

Not really but you are close. The number of inputs is related to the amount of coins you want to spend; not to the number of recipients. If you had two UTXOs - 0.1 BTC each and wanted to sent 0.15 BTC, you would use up 2 inputs and have 2 outputs. However, If you sent 0.05 BTC, you would use up 1 input and still have 2 outputs because of 0.05 BTC (minus the transaction fee) change .

It looks like you are a bit confused. There is nothing to consolidate here. Your address was one of the 142 outputs in that transaction. The number of its inputs is irrelevant. Since that output has been included in a transaction, it is now an Unspent Transaction Output (UTXO).


That UTXO can now be used as an input in a new transaction. Since you received only one transaction to your address, you will only have one input. If there is any change left from an input then another output is created. That output points to one of the addresses from the same wallet (either a change address or the address from which the coins were sent). If you received 10 transactions and wanted to spend all of your coins then you would have 10 inputs.


The more inputs and outputs you have in a transaction, the more fees you have to pay. Note that if you had to send the same amount of coins in separate transactions, you would pay more. As for the optimal values, let me quote LoyceV.

No, you can join a mining pool and try mining a block with other miners instead of solo mining. Every mining pool distributes rewards for contribution in a different way. Here you can find a detailed explanation of each type of reward.

You don't have to expose your private keys in order to be able to use coin control in Electrum. Open Electrum, create a new standard wallet and select 'Use a hardware device'. Once your device is detected, you will be prompted to select the type of address you used - legacy (1...), nested SegWit (3...) or native SegWit (bc1...). You might need to modify the derivation path during this step. Which type of address did you use? Are you trying to access the address from the first account or some other one? Your derivation path should look like this:

Legacy: m/44'/0'/account'
Nested SegWit: m/49'/0'/account'
Native SegWit: m/84'/0'/account'

'account' is the number of the account you are trying to access. The first account is 0, the second is 1 and so on.

You can check it using Electrum or you can copy the transaction ID you posted before and paste it into any block explorer (e.g. blockstream). I guess you should also get an e-mail from Coinbase since you paid for something.

No, of course not. You can log in to your coinbase account on a different device and see that your transaction listed as unconfirmed somewhere.

You will be able to spend those coins again once your transaction is dropped from other node's mempools. You can't reverse that transaction. You have to either wait for it to be dropped or use RBF to bump the fee.

Your transaction would take even longer time to confirm. You wouldn't lose your money. If a transaction is stuck in the mempool for 2 weeks (default value), the transaction is dropped and you can broadcast another one from your wallet. You could try removing your transaction manually from your wallet, but I am quite sure that most nodes would reject your new transaction.