@NomadicLabs thank you for identifying this issue. I would love to hear your thoughts on how the community could bring the patch process on-chain, instead of relying on user activated protocol overrides in scenarios like this.
If you don’t think it’s worth it that’s fine too, I’d love to understand why.
I started a thread about this quite a while back,l: How can we incorporate the patching of issues found during protocol upgrade testing into the on-chain governance process?.
