this post highlights something that I don’t think bitcoiners are accustomed to contemplating when proposing new opcodes: how to charge for the computation time required. We really only consider “how many bytes are in your tx” not “how much cpu does this spend script take to verify”

Simplicity is pretty cool in that it was designed with “how to charge for computational complexity of arbitrary scripts”. How it does this is pretty cool. It still uses tx weight as the cost metric, but it provides a way to calculate the runtime cost of any script without running it. Once you know the runtime cost, you’d look at your tx weight. If it’s too low, youd use the taproot annex m as space to add more bytes such that you can meet the weight required by your tapscript’s complexity.

We don’t have simplicity yet though, so instead we need to do the work Rusty is here where he does rough calculations of complexity and assigns value based on that.