Author

Topic: BTC: different address-types, Not all were found in the blockchain explorer (Read 238 times)

hero member
Activity: 910
Merit: 5935
not your keys, not your coins!
Even though the issue is resolved, I'd like to add that bc1 > 1 transfers (native segwit to legacy) had issues (at least in the past). As far as I know, purely implementation bugs, though.
More about this here: https://bitcoin.stackexchange.com/a/93020/119879
It's the first time I hear this. I hadn't ever heard of any bug causing problem when making transaction from a native segwit address to a legacy address.
I read the thread you shared, but could't find any information about the issue you are talking about.
Am I missing something in that thread?
Oh, 'more about this' was meant more as 'more about address interoperability'.

The answer did shortly touch on implementation bugs: 'If you run into an issue where one address type will not send to another, this is not a limitation of the bitcoin code, rather the client.'
I remember experiencing the bug quite a while ago, but I'm the type of person who experiments with wallets and bc1q was still brand new. I'm just not sure / can't guarantee that every wallet has this ironed out. Wink
legendary
Activity: 2380
Merit: 5213
Even though the issue is resolved, I'd like to add that bc1 > 1 transfers (native segwit to legacy) had issues (at least in the past). As far as I know, purely implementation bugs, though.
More about this here: https://bitcoin.stackexchange.com/a/93020/119879
It's the first time I hear this. I hadn't ever heard of any bug causing problem when making transaction from a native segwit address to a legacy address.
I read the thread you shared, but could't find any information about the issue you are talking about.
Am I missing something in that thread?
hero member
Activity: 910
Merit: 5935
not your keys, not your coins!
Can I send BTC from an address like 372YbM...De5 to an address that looks like bc1qjn...4pt ? Or would this lead into problems?
Yes, you can send from any bitcoin address type to another any bitcoin address type, be it legacy address (1 prefix addresses), nested segwit (3 prefix addresses) or native segwit (bc1 prefix addresses). It is all valid.
Even though the issue is resolved, I'd like to add that bc1 > 1 transfers (native segwit to legacy) had issues (at least in the past). As far as I know, purely implementation bugs, though.
More about this here: https://bitcoin.stackexchange.com/a/93020/119879
full member
Activity: 212
Merit: 108
Oh, gut to know. Thank you.
legendary
Activity: 2380
Merit: 5213
I have mistaken 8l with 81.
So, you were entering the address manually.
If you are going to do the same thing instead of copy-pasting the address in the future for any reason, take note that to avoid confusion, some characters are always excluded.

Addresses that start with 1 or 3 can't contain 0 (zero), capital letter O, capital letter I and lowercase letter l.
Addresses that start with bc1 can't contain 1, B, I, O in their next characters.

Take note that native segwit addresses (those that that start with bc1) aren't case sensitive. So, both b and B, both i and I and both o and O are excluded in them.
full member
Activity: 212
Merit: 108
OK I have found the error.

I have mistaken 8l with 81.

Thank you all.
legendary
Activity: 2380
Merit: 5213
Thank you. I have checked the count. You are right: there are 42 characters.
But Explorer (https://www.blockchain.com/) nevertheless can't find the address.
There shouldn't be any problem from blockchain.com's side. If the address is valid, it should be found. You are probably making a mistake when copy-pasting the address.
Did you try searching for that address on other block explorers? You can use blockchair.com or blockstream.info.
legendary
Activity: 3346
Merit: 3130
Some weeks ago i made a post in the spanish section explaining the address to the users, i know there is a lot of information in english and that's why i post it there, but with a translation you will undestand the difference between address:

https://bitcointalksearch.org/topic/--5411330

There you will see an example of the most popular kind of address:

Code:
Base58 (P2PKH) 1AddyRpJ5SjfCH8N1WSkTX4FUPb4H2YfFx
Base58 (P2SH) 3Cad7LvtLjxWrQzdbLdnoQ9yP8Xr7rU1vH
BECH32 (P2WPKH) bc1qfkx8yykk6299gyx4d7adz4sgv5uzjjctzjz5n2
BECH32 (P2WSH) bc1qrp33g0q5c5txsp9arysrx4k6zdkfs4nce4xj0gdcccefvpysxf3qccfmv3

And with the same private key you can generate any kind of address.

You can send bitcoin from one kind to another because they are all for the same blockchain  Wink
full member
Activity: 212
Merit: 108
Thank you all.

Which wallet is that? It means the address is not valid if it can not be seen on blockchain explorer.
https://play.google.com/store/apps/details?id=de.schildbach.wallet&hl=de&gl=US

It seems that you are missing one character. An address starting with bc1q and containing 41 characters is surely invalid.
A native segwit address (an address starting with bc1) should contain either 42 characters or 62 characters.

Thank you. I have checked the count. You are right: there are 42 characters.
But Explorer (https://www.blockchain.com/) nevertheless can't find the address.
legendary
Activity: 2380
Merit: 5213
bc1qjn...4pt (total 41 characters)
It seems that you are missing one character. An address starting with bc1q and containing 41 characters is surely invalid.
A native segwit address (an address starting with bc1) should contain either 42 characters or 62 characters.
legendary
Activity: 1512
Merit: 4795
Leading Crypto Sports Betting & Casino Platform
The blockchain explorer just hasn't updated their system to include bech32 (native segwit) addresses.
It is just an explorer, all addresses transaction history can be seen on blockchain explorer. Only Blockchain.com wallet was late to support native segwit, but now also supporting it. That does not mean I can use the wallet, because it is a web wallet. Or am I getting something wrong?
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
The blockchain explorer just hasn't updated their system to include bech32 (native segwit) addresses.

General advice would be if you find something that doesn't accept native segwit, it's probably got a lot of problems with it so it's safer to stay away from those services. It's not a new update anymore, it's about 5 years old.

Addresses are compatible, 1 type, 3 type and bc1 type addresses can all send and receive funds from each other.

3 prefixed addresses are nested segwit as they're designed to look like legacy multisig addresses so they'll validate in any checker that a multisig address would (likely programmed into the block explorer).
legendary
Activity: 1512
Merit: 4795
Leading Crypto Sports Betting & Casino Platform
When I type this address into a blockchain manager it does not find this address. Why? What kind of address is this?
Which wallet is that? It means the address is not valid if it can not be seen on blockchain explorer.

Can I send BTC from an address like 372YbM...De5 to an address that looks like bc1qjn...4pt ? Or would this lead into problems?
Yes, you can send from any bitcoin address type to another any bitcoin address type, be it legacy address (1 prefix addresses), nested segwit (3 prefix addresses) or native segwit (bc1 prefix addresses). It is all valid.
full member
Activity: 212
Merit: 108
Hello,


1. Question:
I have installed a simple bitcoin Wallet on my Android phone.
It generates a bitcoin address for me that looks like this:
bc1qjn...4pt (total 41 characters)

When I type this address into a blockchain manager it does not find this address. Why? What kind of address is this?

But when I type into the same blockchain explorer one of my old address that looks like this:
372YbM...De5 (total 34 characters)
it finds the address.


2. Question:
Can I send BTC from an address like 372YbM...De5 to an address that looks like bc1qjn...4pt ? Or would this lead into problems?

Would appreciate some answers. Thank you.

Jump to: