Binance bitcoin withdrawal fee isn't really dynamic.
Currently, at the time I am making this post, the mempool is almost empty and 1 satoshi/vbyte is enough for getting confirmation in the next block. Binance is still charging 0.0005 BTC as bitcoin withdrawal fee.

No.
Coinfloor is an exchange and you cannot import your private key(s) into an exchange. If you want your fund to appear in an exchange, you have to make a transaction to your deposit address.
Note that in exchanges, you have no control over the keys and therefore and there is no import/export private key(s) feature.

How did you find out the user's email address has been changed? Security log doesn't show email changes at all. It only reports password changes. Am I missing something here?
BPIP (which also uses seclog for exporting the data) doesn't show any email changes.

So, I misunderstood you. Sorry.
As you said that the second command doesn't generate a multi-signature wallet, I thought the first one may do it if we add an option to it.
So, none of the commands can create a multi-signature wallet and the only way to create a multi-signature is to use the GUI.

I used the GUI. I selected "Multi-signature wallet and then "I already have a seed". After that I entered the seed phrase generated by create() command and another seed as the second co-signer's seed.
I didn't know it's possible to create a multi-signature wallet using console. How did you do that? What's the command?

It's possible.
o_e_l_e_o made a post about this command some days ago. I didn't notice it's the same command. Click here to read the post made by o_e_l_e_o.

To specify the wallet name, you need to add wallet_path to the command.
The command should be as follows.

Change the path as needed.

As long as you use a SPV wallet like electrum and you don't run your own full node, using a new address for any transaction and coin control don't guarantee your privacy (or your anonymity).

Let's say I create an HD wallet in electrum. I always use new addresses and I never spend multiple UTXOs in a single transaction. This doesn't mean my privacy is protected.
The server I connect to knows that all addresses belongs to a same person. The server can also know my IP address and my region.

It's weird. Seems that something is wrong on my side. Below is the error I get.





What's the error you get?

I just created a 2of2 wallet using the seed phrase shown on your screenshot and another seed phrase.
It worked well.

Seed phrases I used:



The wallet I created using above seeds:

---

That's probably to encourage people to use segwit addresses.

I just tested this command and it didn't work.

---

To OP:
For creating a legacy multi-signature wallet in the case you want to be the owner of all the keys, generate legacy seed phrase as many as you need (for example 2 legacy seeds, if the wallet is supposed to be 1of2 or 2of2). After that, create a new wallet, select "Multi-signature wallet" and then "I already have a seed".

If the wallet is supposed to be owned by different people, you need to ask them their master public key (xpub).

By the way, why do you want to have a legacy wallet?
Using a segwit wallet, you can pay lower fees and it's not recommended to use a legacy wallet.
If a service doesn't support segwit addresses and that's why you want to use legacy addresses, my suggestion is to look for an alternative.

They are addresses that have been imported using private keys, not addresses generated by the wallet.
To see all addresses generated by the wallet, you should go to "Wallet & addresses" and then click on "Manage". Addresses will be displayed if you click on "Reveal addresses".

Old legacy wallets are not converted to HD wallets automatically. That's not possible at all.

The link you shared is used for recovering wallets created before their 2016 upgrade, not the wallets including 12-word seed phrase.
If the blockchain wallet seed phrase includes 12 words, that's definitely BIP39 and can be imported into any wallet supporting BIP39 seed phrases.

---

RapTarX, the best is to follow the suggestion given by JeromeTash.
In order to export the seed phrase, the guy should click on "Security" at top right corner of page and then select "View Secret Private Key Recovery Phrase".

Why should the total supply increase? Are you saying that we should increase the total supply, because the accessible coins are less than 21 million?

Increasing the 21 million limit is against the consensus rules and it will never happen in bitcoin.
For changing the 21 million limit, we need a hard fork.

I have also used Exodus for very small balances and till now, I haven't heard of any security issue with it.
Exodus gives you full control over you keys. Your seed phrase (or your private keys) can be used for recovering your fund in the case Exodus isn't accessible one day for any reason.

The problem is Exodus is close-source and there is no way to know whether your keys are stored on their server or or not.
Exodus may be a good option for keeping small funds and if can't use a hardware wallet for any reason. But I don't recommend it for huge balance.

The casino will lose money in the long term.
In any casino, some people win and some people lose. The casino get money from losers and give it to winners.
If a significant number of losers cheat the casino with double-spending, the money that casino must pay to winners will be bigger than the money they get from losers and the casino lose money.

Assuming all losers cheat the casino with invalidating their deposits, it would be like that all gamblers win money and there is no loser.

Assume that 10 people have deposited bitcoin into a casino. All deposits have been credited before confirmation.
All 10 people start to gamble after their deposit were credited. 5 of them lose and 5 of them win.
The losers double-spend the UTXOs deposited into the casino. The winners wait for their transaction to be confirmed and withdraw all their balance.
This is how the casino lose money.

Electrum is open-source and you can be sure that you are the only one who has control over the keys.

If you want your wallet to be 100% secure, you should generate the wallet on an air-gapped device. This means that you should use a device which has never connected to internet and will remain offline forever.
Note that your keys shouldn't touch the internet even when you want to make a transaction. You should create an unsigned transaction in a watch-only wallet, sign it on the air-gapped device and broadcast it using an online device. 

As Coinomi is close-source, there is no guarantee that your keys are stored only in your device. You can't be sure your keys are not stored on their server.


There is no way to know whether they store the IP addresses on their server or not. They may store IP addresses and link them with transactions.  
As long as a wallet is close-source, you cannot know whether they say the truth or not.

It's true that accepting an unconfirmed RBF transaction is much riskier than accepting an unconfirmed non-RBF transaction, but there is no guarantee that a non-RBF transaction will finally be confirmed.


Both CPFP and RBF can be used when you want to accelerate a transaction. But in my opinion, it's not true to call CPFP a kind of RBF.

In CPFP, you spend the outputs of the unconfirmed transaction with a high fee and encourage miners to include both transactions in a same block. In this method, you don't make any change in the original transaction. CPFP must be done by the receiver. (It can be done by the sender if there's a change in the transaction)
In RBF, you replace the original transaction with a new one and make it invalid. RBF can be done only by the sender.


RBF also allows you to change the inputs and outputs. A requirement is that the replacing transaction has to have at least 1 same input.

In Freebitco, odds are calculated in a different way.
Here, the odds depends on the money people have put on different outcomes. 5% of the total money goes to the house and the other 95% is shared among the winners.  
The odds also depend on the time weigh multiplier. The sooner you place your bet, the bigger prize you can win.
In other casinos, odds are fixed and are calculated by bookmakers.

Not exactly. That's an estimation.
The odds you see now are not final.

Short answer:
No, that's not possible.

Long answer:
Bitcoin transactions cannot be cancelled even if they are unconfirmed let alone they have received a confirmation.  
For making a transaction invalid, you need to double-spend its input(s), so the new transaction replaces the original one.  There is no way to cancel a transaction that has been broadcast.

If a transaction is unconfirmed and has been flagged as RBF, you can replace it with a new one spending same input(s).
If a transaction is unconfirmed and hasn't been flagged as RBF, it's possible to replace it with a new one, but that's very very unlikely.  
If a transaction is confirmed, for double-spending the input(s), you need to perform a 51% attack. It's almost impossible, because it needs a significant amount of total hashrate and is very very expensive.


What do you mean by pool? Do you mean mempool?
If so, take note that once a transaction is confirmed, that's no longer in the mempool at all. It has been included in a block and will receive next confirmations at the rate of 1 per 10 minutes on average.