Hi Greg,
> Going to need a citation for this.
Sorry for the confusion, this was in reply to Joost's point on "Opt-in annex (every input must commit to an annex even if its is empty) -> make sure existing multi-party protocols remain unaffected"
What is unclear to me is if we're talking about opt-in of non-deployed-yet protocols like the pre-signed vaults or deployed protocols like coinjoin/lightning spending P2TR outputs, where a counterparty script spend path can inflate the witness, and we would like to commit *now* to avoid future interferences. E.g 0-conf dual-funding and we loosened the limit from 126 bytes to 256, the worst-case liquidity griefing is not the same anymore.
If the opt-in mechanism we're talking about is just adding an annex for non-deployed-yet protocols as a script spend path of a currently deployed protocol could always be opted-in to the new annex policy through script spend path in the context of collaborative added inputs, no ?
> People should really not be building protocols that are meant to go into production on top of undeveloped upgrade hooks,
and we should not be encumbered by these premature choices if so.
> People should really not be building protocols that are meant to go into production on top of undeveloped upgrade hooks,
> and we should not be encumbered by these premature choices if so. Maybe I'm misunderstanding, which is why a citation
> would be handy.
Yes ideally we should not be encumbered by these premature choices. Still if those use-cases catched up in terms of economic weight, the coordination cost of deploying a new policy might be prohibitive, or require very long periods, somehow like we're seeing with mempoolfullrbf. And I don't think we can say the use-cases would be illegitimate, or that base-layer policy should always have the last word. In the example of lightning, we're doing major re-work of the mempool, partially to improve lightning operations. Personally, I think we should care more about sound and "firewalled" signaling and upgrading mechanisms that let us deploy new policy rules for new use-cases more smoothly.
Best,
Antoine