this is probably a dumb question. You can keep using the same btc address in your wallet. The reason I ask is I had 2 payouts rejected. One went through using the same address and the other 2 got rejected. I think it has to do with blockchain which is why I opened a new wallet instead of blockchain
-
-
Yes, same address should always work. Some wallets will generate a different address every time you select Receive but an old address should still be good.
If it's Bitcoin, there's the Legacy, Segwit, Native Segwit to sort through so make sure the wallet is compatible:
Use native segwit , so you have lower fees. Using a legacy address is pointless as it simply means slower confirmations and higher fees. Under the gear icon on top right > click experimental features > Native segwit to allow bech32 addresses as well which are even better , but you may want to also use a regular p2sh segwit account because some businesses have not upgraded to accept the newest address types.
Bech32 native segwit (P2WPKH and P2WSH ) (Addresses that start with BC1)
Pros -
native SegWit-Bech32 address to save ~39-58% in fees for same priority vs sending from non segwit address
Better checksum and better error correction and detection - https://github.com/bitcoin/bips/blob...0173.mediawiki
less blockweight used thus more tx per block
All lowercase so easier to read off without making mistakes
Cons-
Not all businesses and wallets support it right now https://en.bitcoin.it/wiki/Bech32_adoption
SegWit-P2SH (some addresses that start with 3)
Pros -
SegWit-P2SH address starting with 3 to save ~26-44% in fees for same priority vs sending from non segwit address
Backwards compatible with all wallets
Cons -
Higher fees than native segwit for same priority
larger txs than native segwit so more block congestion
Less ideal address format compared to advantageous of bech32
Legacy P2SH Addresses (some addresses that start with 3, common with multisig addresses)
Pros -
Like P2SH-segwit addresses compatible with all addresses and most wallets
Cons -
26 -58% higher fees than using a segwit transaction for the same priority
larger txs than segwit so more block congestion
Less ideal address format compared to advantageous of bech32
Legacy P2PKH Addresses (some addresses that start with 1)
Pros - Like P2SH-segwit addresses compatible with all addresses and most wallets
Cons -
26 -58% higher fees than using a segwit transaction for the same priority
larger txs than segwit so more block congestion
Less ideal address format compared to advantageous of bech32Comment
