We had Segwit deposit addresses, Segwit hot wallet refill and segwit cold wallets on the day of activation on btcpop.co
Just to realize that the change goes straight to a p2pkh address when processing withdrawals.
Its easy to blame services but maybe blame Core for still not having a fully supporting wallet?
Good to see an early adopter for the technology we awaited so long. I concur that the lack of Segwit change address support is quite irritating. That
should have been done at least a few months ago. But I will not so badly blame Core, given the sorts of time sinks which have sucked away developer effort since long before Segwit activatedand reached a time-sucking nadir in the past few months. For but one of the more recent examples:
Reading in the recent release notes a list of
Network fork safety enhancements, I can well imagine the internal monologue which must have gone through some devs head. I need to finally finish this patch for Segwit change address support (plus tests, tests, tests).
No wait, first I need to find some ingenious hack to ban fork nodes who lie about their identities so that they can waste node resources and try to subvert the whole network. Network safety first. Sigh.
It requires prodigious engineering effort to produce mission-critical financial software which handles hundreds of billions of dollars worth of value, operates in a hostile network environment, and is never, ever allowed to make the sort of mistake which could drop huge amounts of money on the floor because somebody rushed the change address patch. Im so glad that Core gives this to you, me, and everybody else
for free so we can run our businesses, whether or not we pitch in what we can for what
is an
open-source project.
For sure i'm not going to invest money to create own work arounds or own patches to core code.