Discussion
So they backtracked a little, but just enough to send a false and confusing message, and to not have any useful impact for node runners. I’m completely appalled by the level of political shenanigans happening in Core at the moment and in the last 2 years.
I’ve heard it both ways from various sources and I’m not sure if Leo’s statement about it being broken is correct.
It is indeed broken. Intentionally. Undeprecating the documentation is a smokescreen.
BITCOIN CORE v30 IS MALWARE
Sticking with 29 for the foreseeable future. Why is it broken though? I know that multiple OP_RETURN outputs are now going to be allowed adding up to the `datacarriersize` limit within a single tx, but it does not seem to be that relevant IMO
It is indeed broken. Intentionally. Undeprecating the documentation is a smokescreen.
BITCOIN CORE v30 IS MALWARE