I think I was quite clear that I’m not against the concept - I just haven’t seen anything that requires it near term to justify pushing the change at this time or linking it with multiple OP_RETURN. If I missed such an argument (which contains practical examples) please point it out to me.
My role is to get a valuable change into BCH as quickly as possible so the BCH community will benefit from it. That necessarily requires anticipating objections and criticisms that are both rational and uninformed/irrational and being prepared to address/mitigate both as most appropriate. I am also a stakeholder in that my own app is blocked from deploying into production unless this change is made.
I have to protest “nonsense” with this assertion. The two are in no way linked any more than any other feature or capability of BCH which may be impacted by larger tx sizes. You’ve made no case for this whatsoever. Such a conclusion is unnatural.
there is nothing unique about OP_RETURN that is impacted by increasing legal tx sizes. Most aspects of BCH are equally impacted. What you’re asking for amounts to saying “we can have more of these if the tx size is increased” which is true of just about everything. The CHIP quite directly addresses the impact of tx sizes by being neutral about them and assuring the audience that it has zero impact on tx sizes - which is a policy decision made because a) it makes it easier to get adopted, and b) there’s no known justification at this time for multiple OP_RETURN to require or benefit from a change in the tx size.
I frankly don’t understand your hangup with this. You’ve implied that I’m not being intellectually honest here which is incorrect. Why don’t we separate the issues and let raising the tx size proposal stand on it’s own? (I’m ready and willing to support it most likely.) There is ZERO reason to delay multiple OP_RETURN to after May 2021 as it is defined. I’ve reached out and made considerable efforts to verify this. If you have a legitimate technical reason to do so please present it in the chat on that CHIP.
- I’ve been quite explicit about my concern and don’t think I can add anything to it except to refer you back to my prior explanation. It’s an opinion since it deals with things that are naturally political in nature, and you may have a different conclusion - but I don’t think it impacts the consensus for this proposal whatsoever so I don’t appreciate the desire to tie them together. Seems sloppy. Certainly if your proposal/CHIP has real-world use cases in which the size increase is demanded because of limits on OP_RETURN aggregate sizes then make that argument. Again, I’d support such a compelling argument. But let’s proceed in the proper order.