I believe exchanges too are going to allow us to withdraw to native segwit addresses in the future.
many already do, so I also believe the same thing
Topic: Compatibility of Legacy w Native Segwit w Nested Segwit (Read 582 times)
many already do, so I also believe the same thing
Blockchain.info, no Segwit, but started accepting Ethereum, Bitcoin Cash, Ripple, and Stellar. Really clear what side its people are.
Blockchain.info wallet supports bc1 address the last time I checked. You can try paste a bc1 address and pretend as if you want to send a transaction out. It's the only legacy wallet I know to have implemented that.
I believe exchanges too are going to allow us to withdraw to native segwit addresses in the future.
Quote
https://en.bitcoin.it/wiki/Bech32_adoption#Web_Wallets
Bitcoin wiki says they can send to bc1 addresses.
Bitcoin wiki says they can send to bc1 addresses.
But not receive? That is weird. I thought it would be the other way.
Sending to bc1 addresses is pretty simple to implement. Receiving at a BC1 address means you need to implement most of segwit.
If you were thinking 'receiving from' then of course they can, there is no "from address" in a bitcoin transaction. And if any service ever fails to accept a confirmed payment from you because of the form of scriptpubkey you got paid at... that is a serious red flag of epic technical incompetence on their part. As far as I now, bc.i has no such issue.
I believe that it might be another political issue. Blockchain.info might go full Segwit, but slowly, and "showing reluctance". Haha.
Quote
https://en.bitcoin.it/wiki/Bech32_adoption#Web_Wallets
Bitcoin wiki says they can send to bc1 addresses.
Bitcoin wiki says they can send to bc1 addresses.
But not receive? That is weird. I thought it would be the other way.
Sending to bc1 addresses is pretty simple to implement. Receiving at a BC1 address means you need to implement most of segwit.
If you were thinking 'receiving from' then of course they can, there is no "from address" in a bitcoin transaction. And if any service ever fails to accept a confirmed payment from you because of the form of scriptpubkey you got paid at... that is a serious red flag of epic technical incompetence on their part. As far as I now, bc.i has no such issue.
Blockchain.info, no Segwit, but started accepting Ethereum, Bitcoin Cash, Ripple, and Stellar. Really clear what side its people are.
https://en.bitcoin.it/wiki/Bech32_adoption#Web_WalletsBitcoin wiki says they can send to bc1 addresses.
But not receive? That is weird. I thought it would be the other way.
Not clear on Binance.
Binance still doesn't support native segwit withdrawals. Adding a Bech32 type of address as a withdrawal destination apparently results in an error message: 'Address verification failed' when you try to enter the 2FA code.https://bitcoinops.org/en/compatibility/binance/
They probably will be over-charging their users on withdrawal fees for profit anyway.
Blockchain.info, no Segwit, but started accepting Ethereum, Bitcoin Cash, Ripple, and Stellar. Really clear what side its people are.
https://en.bitcoin.it/wiki/Bech32_adoption#Web_WalletsBitcoin wiki says they can send to bc1 addresses.
Not clear on Binance.
Binance still doesn't support native segwit withdrawals. Adding a Bech32 type of address as a withdrawal destination apparently results in an error message: 'Address verification failed' when you try to enter the 2FA code.https://bitcoinops.org/en/compatibility/binance/
Are there any exchanges, that matter, left that doesn't support Segwit?
I think there are a few services that are quite popular, but they still not support SegWit. I read that Binance is one of them, but also very popular blockchain.com and BitPay. Maybe they do not care too much for their users, or they like to take more fees when they withdraw, but they can set fixed withdraw fees even with SegWit.
Bitpay already supports Segwit, although it promotes Bitcoin Cash as a zero-fee, faster alternative. Easy to trick the newbies with this.
Blockchain.info, no Segwit, but started accepting Ethereum, Bitcoin Cash, Ripple, and Stellar. Really clear what side its people are.
I believe both are anti-Bitcoin.
Not clear on Binance.
I usually use Bisq to buy and sell crypto, I would like it to make possible the use of segwit.
I think it's in development and soon we'll be able to make use of native segwit.
I think it's in development and soon we'll be able to make use of native segwit.
... but it won't create a Nested SegWit wallet without a workaround -
My workaround is to use something else to generate a ypub/ypriv extended private/public key. That should always work, and on Electrum should come up with the same set of nested segwit addresses. At least when I tried it recently, just this week, it worked on both Electrum for Windows and Electrum for Android.
I think that iancoleman39 site? It gives a different set of nested segwit addresses on the page itself (probably due to a different derivation path), but on both Electrum wallets it gives a different set, but identical on both wallets.
Furthermore, it is possible to have both Legacy, Nested and Native SegWit addresses in the same Electrum wallet if you import the private keys. When creating a new wallet, select "Import Bitcoin addresses or private keys". In the box that pops up, paste your private keys, and prefix them with "p2pkh:" for Legacy, "p2wpkh-p2sh:" for Nested SegWit, and "p2wpkh:" for Native Segwit.
I forgot about that. I should import a few of them together in the same wallet to consolidate some inputs and save on fees. 1 sat/byte possible if you wait a day.
it's unlikely that you'll find a wallet that stills uses Legacy and also supports sending to Native SegWit.
Mobile wallet Mycelium supports all formats:- Tap for P2PKH
- Tap for P2SH
- Tap for Bech32
Coinomi allows that as well. You can even choose to send with legacy or nested and receive the change in native segwit.
Many people bash coinomi here but I like it
You could create 3 different wallets, but have to use them separately.
Electrum will only create P2PKH/Legacy and Bech32/Native SegWit addresses. It will support P2SH/Nested SegWit addresses, but it won't create a Nested SegWit wallet without a workaround - either importing a mnemonic phrase you generated elsewhere, or "borrowing" a mnemonic phrase that Electrum itself generated for a different type of wallet.Furthermore, it is possible to have both Legacy, Nested and Native SegWit addresses in the same Electrum wallet if you import the private keys. When creating a new wallet, select "Import Bitcoin addresses or private keys". In the box that pops up, paste your private keys, and prefix them with "p2pkh:" for Legacy, "p2wpkh-p2sh:" for Nested SegWit, and "p2wpkh:" for Native Segwit.
Bitcoin Core wallet (as of version 0.18.1, even as early as 0.16.x) allows to use all types of addresses. You can send to and from a Legacy address, as well as send to either of the SegWit addresses. You can even have all 3 address types in the same wallet.
Electrum allows you to do something similar with a little bit of difficulty, since by default it uses deterministic wallets. You could create 3 different wallets, but have to use them separately.
Electrum allows you to do something similar with a little bit of difficulty, since by default it uses deterministic wallets. You could create 3 different wallets, but have to use them separately.
There is a nice list of exchanges and wallets that support Bech32 here: https://whensegwit.com/
I just don't know how up-to-date it is and many services are not on the list. For example they don't list Ledger devices but Trezor is there.
I just don't know how up-to-date it is and many services are not on the list. For example they don't list Ledger devices but Trezor is there.
it's unlikely that you'll find a wallet that stills uses Legacy and also supports sending to Native SegWit.
Mobile wallet Mycelium supports all formats:- Tap for P2PKH
- Tap for P2SH
- Tap for Bech32
Are there any exchanges, that matter, left that doesn't support Segwit?
I think there are a few services that are quite popular, but they still not support SegWit. I read that Binance is one of them, but also very popular blockchain.com and BitPay. Maybe they do not care too much for their users, or they like to take more fees when they withdraw, but they can set fixed withdraw fees even with SegWit.
If I remember correctly the Legacy wallet address is compatible with all types since it can send and receive to all types of bitcoin address. But Native Segwit and Nested Segwit have limited compatibility I guess they can only send and receive from legacy but not from each other.
You can send from any type of Bitcoin address to another address from your personal wallet, there is no problem with that. Problem is in fact that some services/exchanges still not supporting native SegWit (bc1), so if you use such address in your wallet and try to withdraw from exchange that not support it, only way around is to switch to nested SwgWit (address starting with 3) or to use Legacy type address.
If I remember correctly the Legacy wallet address is compatible with all types since it can send and receive to all types of bitcoin address. But Native Segwit and Nested Segwit have limited compatibility I guess they can only send and receive from legacy but not from each other. Though I am not that sure since this topic is already old but if you are doubtful then just use a legacy wallet address to avoid the issue on compatibility.
Can I safely assume that sending from one to other are safe, just that the fees are different?
the ONLY problem that you will ever face involving SegWit is when you are going to receive a payment from someone else (like withdrawing from an exchange) and that other person doesn't want to pay to a native SegWit address (address starting with bc1). otherwise there is no difference and there is no safety or lack of it when using any of the different formats.
and you won't even face the problem when you are the payer (eg. making a deposit to an exchange) you can use bc1 addresses in this case without a problem!
Are there any exchanges, that matter, left that doesn't support Segwit? Plus why would a person NOT start using nested-Segwit?
Although there some "persons" in the community who refuse to use it for "political" reasons.
Can I safely assume that sending from one to other are safe, just that the fees are different?
the ONLY problem that you will ever face involving SegWit is when you are going to receive a payment from someone else (like withdrawing from an exchange) and that other person doesn't want to pay to a native SegWit address (address starting with bc1). otherwise there is no difference and there is no safety or lack of it when using any of the different formats.
and you won't even face the problem when you are the payer (eg. making a deposit to an exchange) you can use bc1 addresses in this case without a problem!
It is safe and they're compatible, but it's unlikely that you'll find a wallet that stills uses Legacy and also supports sending to Native SegWit.
I asked a similar question a couple of years back, I would recommend checking it out: https://bitcointalksearch.org/topic/difference-between-segwit-addresses-2347427
I asked a similar question a couple of years back, I would recommend checking it out: https://bitcointalksearch.org/topic/difference-between-segwit-addresses-2347427
Jump to: