Quote from: blacksmithtm on January 07, 2017, 06:47:18 PM

Quote from: clgrissom3 on January 07, 2017, 06:21:51 PM

Quote from: blacksmithtm on January 07, 2017, 06:05:22 PM

Hello, what is the status for SegWit? Brian Armstrong from Coinbase recently endorsed it https://twitter.com/brian_armstrong/status/817258015619321857

I don't think you will see it here anytime soon...

https://bitcointalk.org/index.php?topic=789369.msg16868494#msg16868494

Thank you. Do the pros outweigh the cons?

Quote

In ckpool/ckdb we have a structure called the workinfo, that's the break down of the common data required for all stratum work sent to miners.
One part of that is what we call coinbase2 - it's got a limit of 256 hex bytes.
Since 1-Mar this year, in all work, coinbase2 has been 196 hex bytes.
segwit has put coinbase2 over 256 hex bytes - more than 30% bigger ...

How big of an issue is that?

And i think the sidechain part is irrelevant. Who cares what people do with bitcoin? As long as they pay the fees to miners and dont ddos (In fact SegWit improves verification times afaik) etc. There are many benefits of SegWit and the cost and risks seem neglicible. Anyway im out. Peace.

Well, there's also the hidden and avoided question of "Why segwit?"

There is actually no problem with current standard transactions, and the malleability issue, though effectively no longer relevant, is fixed with a very minor change that's not part of segwit, but in the segwit change also, but I guess the devs don't want people to notice that.

Segwit is a fix for maleability in P2SH (3xxxx transactions)
When the bitcoin devs designed P2SH, they got it wrong, they added a faulty P2SH.
Segwit is a fix for some of their mistakes.
But it also forces everyone to use P2SH instead of standard transactions.
So basically forcing everyone into whatever other problems there are with P2SH, and out of using standard 1xxxx transactions.
All your 1xxxxx addresses will become a thing of the past if segwit activates (which it wont)