Btc transaction with camoufled outputs

[FleurTunisienne]

Today i found a strange output format in a bitcoin transaction. Here it is: https://www.blockchain.com/btc/tx/dbe4d5ba8daeeba102b619a4229d3355dae344484d72569a3687c26a9958506f?fbclid=IwAR2UeAc4_AwgCHcpMnCfkgYz8lG7s5PJDYTXENuuG2widmTgaJ8N7eMBIQU

This is a screenshot:


I didn't see this kind of data before, so my first thought is it's a kinda of camouflage or a feature that is already implemented but not in frequent use. Am asking here about it's kind and how/when to use it.
I will lock this thread after getting the right answer to my questions.
Thanks in advance

[FleurTunisienne]

Note: A friend told me that this may be related to lightening network but didn't convaince me so. If my question reveals my ignorance, then maybe this is not the appropriate board to ask such a noob question. Perhaps i will move the topic to off topics board or begginners board. [need a MOD reply]

[Rath_]

The input is a nested SegWit address. All four outputs are native SegWit addresses. While creating a new wallet in Electrum, you can select whether you want to use standard addresses or SegWit ones (bc1). Using SegWit addresses allows you to save a lot of money on transaction fees (more detailed explanation here). You can learn more about Segregated Witness (SegWit) here. Native SegWit addresses are also used by every Lightning Network software. Channel funds are locked up in such addresses.

[ABCbits]

FYI, some people refer native SegWit address (starting with bc1) as Bech32 address and refer nested SegWit address as P2SH SegWit address. Just in case so you won't be confused with the terminology.

While SegWit have many advantage which mentioned by BitCryptex, not all Bitcoin wallet support sending Bitcoin to Bech32 address (but all of them support send to nested SegWit address).

[bob123]

As others already have mentioned, this is the 'new' segwit format (bech32). This is the 'true' segwit format.
Nested segwit (P2PKH nested into P2SH; address starting with 3..) is 'kind of segwit'. To be more precise, it is legacy data fetched into segwit format.


I guess you might be irritated and refering to it as camouflaged because you can't click on the address ?
If so, this has nothing to do with the address format itself, but with blockchain.com. They simply haven't updated their explorer since months.

Therefore you can't click on the addresses, they simply didn't invest a few hours to index them yet.
If you want to view the transaction of such an address, use another explorer. Most of them already support searching/viewing bech32 addresses.

[NeuroticFish]

People have already told you that it's a (bech32) "pure" SegWit address, but I'll also provide you some links where you could maybe read more:
https://en.bitcoin.it/wiki/Address
https://en.bitcoin.it/wiki/List_of_address_prefixes

[mocacinno]

As others already have mentioned, this is the 'new' segwit format (bech32). This is the 'true' segwit format.
Nested segwit (P2PKH nested into P2SH; address starting with 3..) is 'kind of segwit'. To be more precise, it is legacy data fetched into segwit format.


I guess you might be irritated and refering to it as camouflaged because you can't click on the address ?
If so, this has nothing to do with the address format itself, but with blockchain.com. They simply haven't updated their explorer since months.

Therefore you can't click on the addresses, they simply didn't invest a few hours to index them yet.
If you want to view the transaction of such an address, use another explorer. Most of them already support searching/viewing bech32 addresses.

^^ agreed
I just wanted to link to one of those explorers that supports bech32: https://bitupper.com/en/explorer/bitcoin/

It's not mine, but i like the way this guy is starting his explorer so i wanted to give him some support.

BTW, in this case it probably has nothing to do with opening or closing lightning channels, the values are to large, at this moment most segwit implementations only allow channels funded with up to 0.16 BTC (IIRC)