Your bitcoin isn't stored on your computer.  Your bitcoin is on the blockchain and the keys you need to access your bitcoin are on your computer.


Electrum is an open-source wallet and there isn't anything hidden from the users. If it's used in the correct way, it's completely secure.


Yes. That's possible. Your safety depends on how you use electrum. There's always the possibility that your computer gets comprised.


If you want to be 100% secure, you should use electrum on an air-gapped device.

If you pick 24 words randomly, the probability of having a seed phrase which passes the checksum would be 1 in 256. For the last word, 8 out of the 2048 words would produce a valid seed phrase.

The checksum isn't the last word. In a 24 word BIP39 seed phrase, the last 8 bits are the checksum. The first 3 bits of the last word are chosen randomly.

The common derivation path which is usually used is m/x'/0'/0' not m/x'/0'/0'/0/0.
For example, m/44'/0'/0' is derivation path used for deriving legacy addresses and refers to the whole wallet while m/44'/0'/0'/0/0 refers to the first legacy receiving address and m/44'/0'/0'/1/0 refers to the first legacy change address.

The winners are determined through a provably fair lottery.
Every week, they publish a list containing user IDs of participants and their ticket numbers. Winning ticket numbers are determined through some mathematical calculations.
The provably fair lottery guarantees that the tickets numbers are picked randomly and there is no way for them to cheat the users.
For details on how the provably fair lottery works, go to "Lottery" tab and click on "the lottery is provably fair.".

A bitcoin private key should work for all bitcoin forks as well.
The most popular forked coin is bitcoin cash (BCH). The bitcoin cash fork happened on August, 1, 2017. Any bitcoin transaction made before that date exists in the bitcoin cash blockchain as well.
So, if a bitcoin address has received fund before that date, it has received bitcoin cash as well.

Take note that Bitcoin Gold and Bitcon SV are forks of bitcoin. So, if you find a private key of a bitcoin address funded before those hard forks time, you should be able to move the forked coins as well.
A bitcoin private key isn't a valid ethereum private key or a valid Dash private key and you can't use that private key to move fund in those blockchains.

The seed phrase you are talking about is called BIP39, not BIP32.

A 12 word BIP39 seed phrase provides 128 bits of entropy and is secure enough. Do not worry about the safety of your seed phrase.
Even if electrum doesn't support BIP39 seed phrases in the future updates, there won't be anything to worry about. There are many other tools that can be used to derive the private keys from a BIP39 seed phrase.

If you want to pay lower transaction fee, consider consolidating your UTXOs when transactions can be made with the fee rate of only 1 sat/vbyte.
If you haven't consolidate your UTXOs before and now you want to make a transaction, select your UTXOs so that the number of inputs is as small as possible. The more inputs you add to your transaction, the more fee you have to pay.
It doesn't really matter which UTXO has been received earlier and which one has been received later.

Note that in the case you care about your privacy, it may be bad if you use multiple UTXOs in a single transaction.

With that update, electrum should regenerate an address that has been generated before in another request, if the previous request has been expired and the address has never received any fund.
Since OP has set the expiry time to never, electrum shouldn't generate the same address again. I don't think what's happening in OP's wallet is the correct behavior.

16,480 EUR
hosseinimr93

Click on "sign" button and then broadcast the transaction.
After that, the original transaction will be replaced by a new one paying higher fee.

Edit:
As I see in the mempool, you increased the fee rate to 2.7 sat/byte successfully.

As the original transaction is still valid, you haven't increased the fee at all. If you had increased the fee, the original transaction should have been replaced by a new transaction.
What happens when you click on "OK" button? After that, a new window in which you broadcast the replacing transaction should popup.

The only thing that comes to mind is that you restored your wallet using your seed phrase and electrum generated your unused addresses again.
When you restore your wallet using your seed phrase, you create a new wallet file and electrum doesn't know which addresses have been generated before, unless they have received fund.

It has been more than 5 years since segwit soft fork has been introduced. So, almost any wallet should allow you to send bitcoin from legacy address to bech32 address and vice-versa.
If there's a wallet or an exchange that doesn't allow you to do so, you should avoid it. Because it would mean that they haven't updated their system even after 5 years.

Bitcoin protocol allows sending bitcoin from any address type to any address type.

Note that transaction fee doesn't depend on the amount you send. So, it doesn't matter whether you are sending 1000 BTC or 1000 satoshi.
When you make a transaction, you should set the fee rate according to network state and how fast you want your transaction to be confirmed. The total fee depends on number of inputs and outputs and address(es) type as well. You can use bitcoindata.science (a tool created by the forum user, bitmover) to calculate the total fee based on number of inputs and outputs, your address type and the fee rate.

Trust wallet isn't open-source and there is no way to know how the keys are generated and whether they have access to users keys or not. 
In their website, they claim that trustwallet is open-source, but they are lying. It used to be open-source and their source code has been last updated around 4 years ago.

Maybe, there's a problem with your internet connection. It's possible that your internet service provider is preventing the captcha from being loaded or the captcha service provider has blocked your ISP.
Have you tried loading the webpage with a VPN?

With using a multi-signature wallet, you may increase your security, but I recommend you use it if it's really required.
Multi-signature addresses are usually used when a transaction should be signed by multiple parties.
If you generate a single-signature wallet on an air-gapped device and keep your keys safe, it's secure enough.


Whether you use a single-signature address or a multi-signature address, that's impossible.


It depends.
If the address is a 3 of 3 multi-signature address, all the three private keys would be required.
If the address is a 1 of 3 multi-signature address, a single private key would be enough.


Yes. Each of private keys used for generating the multi-signature address can be used for generating a single-signature address individually.

That address is a multi-signature address and for generating that, you need all the three public keys.

In a m of n multi-signature address, there are n private keys and n public keys and you need m of the private keys to spend fund from that.
The address in question is 2 of 3 multi-signature. So, there are 3 public keys and 3 private keys and for spending fund from it, 2 of private keys are required.

No. It's not really hard.
As mentioned by jackg, you should use the redeem script to get the public keys.

I didn't know how it can be done. I just made a search and found out it's really easy.
Click here to see one of the transactions made from the address you referred to in the OP.
See the input with the index number 135. The sigscript includes 3 hex data. The last one is the redeem script.

Redeem script:

For getting the public keys, all you need to do is to decode the redeem script using coinb.in tool.
The three public keys used for generating the address in question are as follows.