What version of bitcoin core are you using?
According to this issue, there was a bug in the version 0.20.1 causing the "create new receiving address" button to be disabled in the newly created wallets.
If that's the case, the button should be enabled simply with closing and opening the wallet.

The problem isn't from Exodus wallet. The problem is with the smart contracts that allow sending 0 tokens without owning the private key.
Visit the following topics. The same thing has been already reported on TRON blockchain and Binance smart chain.

Watch out for this NEW TransferFrom Zero Transfer Scam!
I got scammed out of 100000 dollars by fake 0 dollars withdrawal on BSC

It may be better to generate a seed phrase and have a HD wallet instead of dealing with a single private key and a single address. In this way, you can have numerous addresses all generated from a seed phrase. Using a same address for all your transactions may not be good for your privacy.

Take note that your master public key is derived from your seed phrase and that's why in a single signature wallet, having the seed phrase is enough.
In a 2 of 3 multi-signature wallet, if you have two seed phrases, two of master public keys are derived from those seed phrases and you must have the third master public key.
If you use a 3 of 3 multi-signature wallet in which you have control over all three seed phrases, you won't need the master public keys, because they are derived from your seed phrases.

What matters is how you generated your wallet and how you use it.
If you generate your paper wallet and use it in the correct way, you can send fund from your wallet whenever you want without any problem.
In the case you generate your paper wallet in the incorrect way, your fund may be stolen even if you have never sent any fund from that.

Applying for avatar campaign:

Username: hosseinimr93
BTC SegWit Address: bc1qfwmmppsqlp3xuvghfsys32mtn86j6kfvu0e20z

Avatar:

Right. In December 2018, there were 68 non-coinbase transactions with zero fee.
Take note that it's almost impossible that you can make a transaction with zero fee. If you set the fee to zero, your transaction won't be broadcasted to the network at all. As mentioned by BlackBoss_ above, the minimum fee rate you can use is 1 sat/vbyte.
Those transactions that are made with zero fee are probably made by the miners/mining pools and they included their own transactions.

Take note that segwit transaction don't have smaller size.
With sending from segwit addresses, you decrease the transaction fee, because your transaction would include some witness data that are not counted counted as one quarter the size of regular data when calculating the transaction fee. With using segwit inputs, you actually decrease the virtual size of your transaction, not the size.

This post has been edited. Thanks o_e_l_e_o for the correction.

You can use blockchair explorer to get the data you are looking for.
Click here to see all the transactions that have been made with zero fee.

Note that most of transactions that are made with zero fee are coinbase transactions.
Click here to see the list of non-coinbase transactions that have been made with zero fee.

Right. According to the other thread created by OP, the problem is that they don't accept bech32 addresses.
OP's problem has been already solved with generating a legacy wallet on electrum.


Yes. Blockchain.com wallet generates both segwit and legacy addresses.

I don't really understand what they mean by "including the hash".
Your bitcoin address is the hash of your public key and there shouldn't be any problem.
The only thing that comes to my mind is that maybe they don't support bech32 addresses (addresses starting with bc1). Maybe, you need to provide a legacy address (an address starting with 1 or 3).

Can you tell us what casino you are trying to withdraw bitcoin from?

The string starting with bc1 is your bitcoin address.
Take note that a bitcoin address is public key hash, starts with either bc1, 1 or 3 and is all you need to receive bitcoin.

What's the problem now? Do you get any error when you enter your address and request a withdrawal?

As far as I can remember, it has been never like this.
For marking a thread as read, you can open any of its pages and it has been always worked in this way.

Some wallets like electrum allow you spend the unconfirmed outputs and you wouldn't have to wait for the receiving transaction to be confirmed.
It's just that as long as the parent transaction in unconfirmed, the child can't be confirmed.

Right. You did CPFP.
Your second transaction used the output of the first transaction and the miner had to include the first transaction as well.

When miners see a transactions spending an unconfirmed output, they usually calculate the effective fee rate and include the transactions (the child and the parent) in the same block if the fee rate is high enough.
For calculating the effective fee rate, they add the total fee of the transactions together and divide the result to the total size of transactions.

I don't think the problem is on your side.
I can't find Nigerian in the boards list either. I even did a hard refresh with CRTL+F5, but it wasn't helpful.

I don't know where the 16% in that article comes from, but that's not true.
The percentage of reduction in transaction fee with the help of using segwit addresses depends on number of inputs and outputs.
In a transaction with 1 input and 1 output, you can decrease the fee by around 42% using bech32 input.
In a transaction with 10 inputs and 1 output, you can decrease the fee by around 52% using bech32 inputs.
In a transaction with 1 input and 10 outputs, you can decrease the fee by around 20% using bech32 input.
(I used bitcoindata.science, the tool created by bitmover for the calculations.)

Using segwit outputs is also effective in reducing transaction fee, but as mentioned by nc50lc above, that's not significant.

Isn't paying to bech32 addresses slightly cheaper than paying to legacy addresses?
If I am not wrong, with replacing each of legacy outputs with a bech32 output, you reduce the virtual size of your transaction by 3 vbyte.

To add to Charles-Tim's reply:
Take note that bitcoin and BTC(Segwit) options that are shown on binance are not two different networks. They are just different address types and you can send bitcoin to any of them you want. We have only one bitcoin chain and there is no bitcoin on BEP20, BEP2, ERC20 networks. Binance always try to deceive users into using their fake bitcoins instead of the real bitcoin.

You are right. As we all know, each bitcoin is divided to 100 million units and there are 8 decimal places for bitcoin. You can send 0.001 BTC and your wallet or block explorers can show that as 0.001 BTC, 1 milliBTC or 1000 microBTC. But in the bitcoin protocol, there are no decimal places and we always deal with satoshis.