I have seen discussion of CT being used on the a side chain. What are the chances it will be applied to Bitcoin Core itself?
Pretty good actually as it has become a lot easier after SegWit allowed for new script opcodes through soft forks. It might still be a few years out, as there are other priorities, but Gregory Maxwell is pretty active on CT.
This is not a question anyone can answer. If you'd asked me 2 years ago what the chances of raising the block size in the future were, I'd probably have said that they were pretty good.
I think we can all definitely agree that CT is unlikely to be merged into Bitcoin Core itself any time soon, if at all, as it would require major wallet changes across the board, and would be a massive hard fork...with all the push-back that goes along with that.
2SegWit allows CT to be done through soft fork. Wallet support would be opt in, I think. Also block size increase is going to happen within weeks now, so you were right 2 years ago. May 24, 2016 at 0:15
If it's not enforced on a protocol level it's not even worth discussing. Then it's about as useless as centralised mixers, marred by exceedingly low entropy and full of central failure points. As to the block size, where do you get that there's going to be a hard-fork increase within weeks? Segwit doesn't count. May 24, 2016 at 6:05
Saying it's useless doesn't make any sense. First of all it would be immensely easier and faster than centralised mixers and trustless. 2nd even if a small but steadily growing number of people start using CT then that's an improvement for the people involved and even others. That's the only way to transition to a mostly CT situation in a backwards compatible manner anyway. Next: i never mentioned hard fork in 2 weeks, i meant segwit which perfectly counts as it literally increases the block size. But this is not a discussion site, so don't bother please. May 25, 2016 at 10:45
Don't bother with the blocksize debate, is what i meant there. Valid points on the topic of this question+answer are welcome of course. May 25, 2016 at 10:53