Great Script Restoration (BIPs 440–441)
Rusty Russell and Julian Moik's 2026 drafts to restore the opcodes disabled in 2010 inside a new tapleaf version, kept safe by a “varops” runtime budget.
The wiki's angle: script restoration is the maximal answer to the covenant debate. Instead of adding one opcode, it gives back what was switched off in 2010 and puts a meter on it.[2][4]
Varops budget
BIP-440 defines a “varops budget” that extends the sigops budget of BIP-342 to non-signature operations, as a framework other BIPs can use[1].
Restoring disabled opcodes
BIP-441 introduces tapleaf version 0xc2, which restores Bitcoin script to its pre-0.3.1 capability and relies on BIP-440's budget to prevent the excessive computation behind CVE-2010-5137[2]. It re-enables disabled opcodes, raises the maximum stack object size from 520 bytes to 4,000,000 bytes and adds a total stack limit of 8,000,000 bytes[2]. Both BIPs are Drafts[3]. Optech's coverage of the LNHANCE debate in December 2025 noted calls for varops benchmarking[4].
References
- primaryBIP 440, “Varops Budget For Script Runtime Constraint”, bitcoin/bips
- primaryBIP 441, “Restoration of disabled script (Tapleaf 0xC2)”, bitcoin/bips
- primarybitcoin/bips repository [archived]
- secondaryBitcoin Optech Newsletter, 5 Dec 2025 — “LNHANCE soft fork”

