In bluewallet, you can generate a seed phrase with entering your own entropy manually.
The entropy source can be a coin flip, a 6 sided dice roll or a 20 sided dice roll.

For more information on how to create a wallet with providing manual entropy on bluewallet, click here.

No.
Since different websites may different methods for estimating halving date, they may give different dates.
For example, the website you mentioned predicts the halving to be 500 days later while buybitcoinworldwide and coinmarketcap predicts it be 480 days and 522 days later, respectively.

The official bitcoin twitter page?
Take note that there is no official account for bitcoin on twitter, just like there is no official bitcoin website.
Since bitcoin is a decentralized system, it's impossible to have an official website or an official account on social media platforms.

That's the official account of forum on twitter and is controlled by theymos.
Read the old post made by him.

If you have lost S1 and P2, you still have S2 and P1. If you have lost S2 and P1, you still have S1 and P2.
Since S1=S2 and P1=P2, you actually have the seed phrase and passphrase of your  single-sig wallet and you can easily recover it.

16,616 EUR
hosseinimr93

The problem is that there is no way to calculate how much you should pay as transaction fee, so your transaction is confirmed in a certain time. When you broadcast your transaction, you don't know what will happen to the mempool in the next minutes or hours and that's why you can only estimate the required fee rate.
Since different tools may use different methods for estimation of required fee rate, it's completely normal that they give you different estimations.

There is no way to know the total fee without knowing the transaction size and you can't say 2 sat/vbyte is equivalent to $0.05.
For example, if you have 100 legacy inputs and 2 outputs and set the fee rate to 2 sat/vbyte, you have to pay around 30,000 satoshi as transaction fee. That would be around 5 dollars.

Freebitco is using parimutuel betting system and the house has no role in determining the odds. The odds are determined by the users and it's not that the house increase/decrease the odds.  
The odds depend on the total money that has been bet on each of outcomes and the time weight multiplier. Note that there is no way to calculate the odds before betting is closed and that's why the odds shown in the website are just estimations.

To be more accurate, the final odds will depend on the total money that has been bet on each of outcomes, not the number of bets. Assuming 100 people each have bet 0.01 BTC on team A and 1 person has bet 1 BTC on team B, the odds would be the same for teams A and B.
The odds depend on when you made your bet as well.

If you have a seed phrase, it's not bitcoin core. Bitcoin core doesn't support seed phrase at all.
Most wallets use the BIP39 standard for generating seed phrase. We have also electrum which uses its own algorithm for generating seed phrase and supports importing BIP39 seed phrase as well.

Download electrum from its official website, verify your download, create a new wallet and select "Standard wallet" and then "I already have a seed".
Enter your seed phrase and see if it allows you to click on "Next" button. If the next button is grayed out, click on "Options" and select "BIP39". If you see a message saying '"BIP39 (checksum: ok)", click on Next".

But we can still have a block including a transaction with the same ID as an existing transaction, if the existing transaction has been fully spent. Right?
I know the chance of that happening is almost zero.

I think OP is talking about two coinbase transactions with the same ID in two different blocks, not in the single block.

In theory, it's possible that a block includes a transaction with the same ID as an existing transaction if the existing transaction has been fully spent. Whether it's a coinbase transaction or a normal transfer, there's nothing prevent network from accepeting such a transaction.
Before implementation of BIP30, a block could include a transaction with the same ID as an existing transaction, even if the existing transaction had been unspent.

With BIP34, it's very very unlikely that two coinbase transactions have the same ID, but in theory it's still possible that two transactions have the same transaction ID.
If a transaction has the same ID as an existing transaction, the second one would replace the first one and there wouldn't be any way to spend the fund received in the first one.
See blocks number 91,722 and 91,880. The coinbase transactions in these two blocks have the same ID. The person who received the block reward on block number 91,722 can't spend it.
The solution to this problem was BIP30. According to BIP30, a block can't include a transaction with the same ID as a not-fully-spent transaction.

To be more accurate, the transaction hash is calculated by hashing the transaction data through SHA256 function twice.


According to BIP34, the coinbase transaction must contain the block height.
Before implementation of BIP34, it was possible to duplicate a coinbase transaction.

Binance acquired trustwallet around four years ago and note that they get nothing from transaction fees. All the fee you pay for making transaction on trustwallet goes to miners.

Instead of just importing the wallet into electrum, it would be better to create a new wallet on electrum and send all the fund to that.
Also note that trustwallet allow you to adjust the fee rate manually too.

Since there is no way to know whether a close source wallet has been coded properly or not, I would always consider the worst case scenario and avoid any close source wallet. Everything is possible.
A good example is coinomi. Coinomi has been always a popular wallet and considered safe by many people, but it had a vulnerability sending users seed phrase to google servers.

When you use multiple inputs in a single transaction, there are all combined together.
It doesn't make sense to say which of the inputs has paid the transaction fee and which of them has been sent to the recipient(s).

May I ask what you are trying to achieve?

I am not familiar with Mac. I just guess that your library folder may be hidden.


You have a generated a private key as well.
The address you got and sent bitcoin to has been generated from a private key. That private key can be easily exported if you can open your wallet.

As you have created a wallet, you should have a wallet.dat. Click here to know the default location of bitcoin core data directory.
If you neither have the wallet.dat nor the private key, there won't be any way to recover the fund.