Kano, any issues with setting our payout address to a SegWit address?
If you mean the buggy P2SH addresses that start with '3'?They've been around for a long time and I paid one from the very first pool block
They do that regularly with the getblocktemplate code, but no one (including core) really gives a crap about that anyway (yeah it keeps getting slower ...)
Original Bitcoin had another reasonably simple malleability 'issue' that's really a non-event, and was removed with a commit hiding in segwit.
P2SH and segwit, on the other hand, well that's a different story.
What's segwit? Segregated witness, or in simple terms, moving a bit of data, that's part of the transaction hash, to not being part of the transaction hash.
Why? Coz P2SH didn't get it right. The malleability in P2SH leads to clear 'issues' with some of the P2SH transaction types they designed ... badly.
The standard, non-segwit, transaction change for malleability, is really just a minor thing ... sorta like a side note, or an addendum, tacked on.
I can't even find it searching the recent docs of the releases - yeah it's in there somewhere in the tl;dr; sections
So core decided to pretend that segwit can only be done how they are doing it and with all the 'other' changes in there ... and the 4x cost for non 'P2SH segwit' transactions ... and throw in a magical 'soft' to the fork definition (that they came up with) even though anyone who doesn't upgrade is royally screwed, and wow lets screw things up even more.
There's been a lot of patches and changes to fix up all the problems that keep being found in P2SH, segwit being yet another of those, so thus my opinion of P2SH.