The varops budget is probably the strongest part of the proposal. I like the idea of making sure no block takes longer to validate than the worst-case block today. That's something we can actually test. The fixed cost per opcode also seems like a sensible way to deal with the macro problem. I'd just like to see more benchmarks across different hardware and some testing against adversarial scripts.
My bigger concern is putting everything into one soft fork. It makes adoption harder because reviewers can't approve smaller, useful upgrades like CSFS and TWEAKADD without also accepting recursive covenants and full introspection. I'd also prefer to see the MEV implications and cross-input amount accounting properly addressed before activation rather than leaving those questions open.
I agree with you. The varops budget is a good idea. It makes the worst-case block easy to test. But I also agree that putting everything in one soft fork makes it harder. It would be better to let small upgrades like CSFS go first. Then we can test the bigger changes later. Thanks for explaining it clearly.