Quote from: -ck on January 06, 2018, 03:31:21 AM

Quote from: LoneRangir on January 06, 2018, 03:29:29 AM

Quote from: -ck on January 06, 2018, 03:22:26 AM

Quote from: LoneRangir on January 06, 2018, 03:19:04 AM

Quote from: -ck on January 03, 2018, 09:10:08 PM

please be aware that bech32 addresses (starting with bc) which have started appearing in some wallets are not currently supported by this pool

Why is this? Just not popular enough to add support? The 'standard' has been around for a while now. I've found a few places reject this format, even though electrum has offered the format for some time now.

No code in the pool to support it? I'm also not sure on whether you can generate directly to a bech32 address since it's meant to be segwit to segwit only.

So we've not successfully mined a block to a native SewWit address? I'm a bit fascinated by the (lack of) SegWit adoption.

Segwit address yes we have, plenty. Bech32 is a unique segwit to segwit only address format. Virtually all segwit in use today is using the 3x address format though.

So you cannot spend a bech32 to a 'standard' address? If so, I was not aware. Maybe that's not what you said....

I get that '3' addresses are segwit-compatible-multi-sig addresses.

Anyways.. would you not be spending to a bech32 adddress upon a block found/payout? Is the finding address not a '1' or a '3' address?

Honestly... I'm not trying to be a troll. I just would like to know the reason for the slow rollout of such 'upgrades'. Is it technical? Political? Trying to understand the landscape...