Sorry if this sounds like a dumb question but I don't understand the implications - what does " it will be enabled on mainnet with block 293000" really mean since bare multi-sig is still the default method used going forward at least in the near future. Is the protocol capable of automatically switching to pubkeyhash if it fails to create a bare multisig transaction and relay it successfully.
It means the protocol will parse this kind of encoded transactions from block 293000, but it does not mean the client will encode in this way.
Ah that makes sense
I don't see this as a threat as you state, even if the protocol is capable of parsing it, the client is not yet sending this transaction. This ensures continuity for XCP in the short term, its a business continuity plan in an adverse situation that has not been triggered. Hopefully saner heads will prevail. In the meantime, XCP has a way forward even if the situation deteriorates from where we stand currently.
PP has always been against creating transactions with unspendable outputs. It looks like the devs are looking after worse case scenarios, nothing more than that. If counterwallet were to start sending these messages, I would agree with everything you are saying. But we are not there yet and hopefully will not be.