On edit: looks like the mystery miner supports p2sh.
coinbase: 040c350b1a028d06062f503253482f
decoded: 5�/P2SH/
Where can this information be found?
Your link doesn't support anything you just said.
You don't seem to pay much attention. Within approx 2 hours and merely 4 posts, I posted two links right here in this thread. You replied to each of them, so you had a chance to open them. Generally I don't like to repeat myself, but I hear you asking for me to elaborate and so I will explain again (this time; and more to the point hopefully).
The first link was:
https://bitcointalksearch.org/topic/m.775108It supports two of the claims, namely a) BIP16 renders old clients vulnerable to DoS attacks and b) not processing TXs "hot fixes" this threat until the client software can be updated. If you think the link isn't supportive enough for claim a) because
I said it, then please read the whole thread or at least the part which explains how exactly the exploit works:
https://bitcointalksearch.org/topic/m.772311The second link was:
https://bitcointalksearch.org/topic/m.711055It supports the other claim, namely that those who can't update their client are excluded from voting (for/against BIP16). If you are in a hurry, you may want to skip all but the last paragraph.
As a technical person, my summary is:
Question: Is updating necessary? Answer: no. Wait, maybe. Wait, YES! You may be DoS'ed by malicious TXs.
Question: Can I gain more time by voting against? Answer: No. You must update first, then you may vote.
This means: Solve your own problems yourself.
And that's all what happened, problems have been solved. There is no conspiracy behind it.
And a personal comment, if I may add:
I really mean just this, without personal attitude. The project is great and the board is great too. You may think I am opposing multisig or P2SH or whatever. The only thing I am opposing here is the update spiral / time pressure.
A more compatible transition may exist, and people could try to find it. I know I could find one if I tried. But the opposition between LukeJr and "the world" shows me that any such attempt is waste. The transition to multisig must happen in the way it is supposed to happen. A bit rougher maybe than desired (by all parties), but nonetheless. And to my delight, I also hear that a smoother compatibility path is prepared for future protocol changes (fingers crossed).