mirror of https://github.com/bitcoin/bitcoin
Merge #16902: O(1) OP_IF/NOTIF/ELSE/ENDIF script implementation
pull/18279/heade6e622e5a0
Implement O(1) OP_IF/NOTIF/ELSE/ENDIF logic (Pieter Wuille)d0e8f4d5d8
[refactor] interpreter: define interface for vfExec (Anthony Towns)89fb241c54
Benchmark script verification with 100 nested IFs (Pieter Wuille) Pull request description: While investigating what mechanisms are possible to maximize the per-opcode verification cost of scripts, I noticed that the logic for determining whether a particular opcode is to be executed is O(n) in the nesting depth. This issue was also pointed out by Sergio Demian Lerner in https://bitslog.wordpress.com/2017/04/17/new-quadratic-delays-in-bitcoin-scripts/, and this PR implements a variant of the O(1) algorithm suggested there. This is not a problem currently, because even with a nesting depth of 100 (the maximum possible right now due to the 201 ops limit), the slowdown caused by this on my machine is around 70 ns per opcode (or 0.25 s per block) at worst, far lower than what is possible with other opcodes. This PR mostly serves as a proof of concept that it's possible to avoid it, which may be relevant in discussions around increasing the opcode limits in future script versions. Without it, the execution time of scripts can grow quadratically with the nesting depth, which very quickly becomes unreasonable. This improves upon #14245 by completely removing the `vfExec` vector. ACKs for top commit: jnewbery: Code review ACKe6e622e5a0
MarcoFalke: ACKe6e622e5a0
🐴 fjahr: ACKe6e622e5a0
ajtowns: ACKe6e622e5a0
laanwj: concept and code review ACKe6e622e5a0
jonatack: ACKe6e622e5a0
code review, build, benches, fuzzing Tree-SHA512: 1dcfac3411ff04773de461959298a177f951cb5f706caa2734073bcec62224d7cd103767cfeef85cd129813e70c14c74fa8f1e38e4da70ec38a0f615aab1f7f7
commit
67dfd18f44
Loading…
Reference in new issue