The goal is to turn Bitcoin’s scripting language from a set of specific instructions back into a flexible toolkit. Bitcoin Optech’s Julian explains that BIP 440 establishes a ‘VarOps’ budget, a general computational limit that would let the network safely re-enable 15 opcodes Satoshi disabled over a decade ago. The old bans were a blunt fix for denial-of-service risks; the new system prices each operation, from signatures to hashing, shifting security from arbitrary restriction to measurable resource consumption.
“[BIP 440] establishes a computational budget, called VAR OPS, for Bitcoin script by generalizing the existing SIG OPS limit to also account for hashing and future operations.”
- Julian, Bitcoin Optech
The philosophical divide is over how much power to give builders. One camp advocates for narrow, purpose-built opcodes like CheckTemplateVerify (CTV). Julian and the Script Restoration team argue for general-purpose building blocks like OpCat, which could enable zero-knowledge verifiers and complex vaults in ways developers haven’t yet imagined. Julian’s bet is that the fee market will be the ultimate filter, allowing useful applications to outcompete junk for block space.
This technical renaissance arrives alongside a push for better privacy. On Citadel Dispatch, Sparrow Wallet creator Craig Raw detailed how Silent Payments solve Bitcoin’s chronic address reuse problem. By using a static payment code that generates a fresh address for every transaction, the tech aligns privacy with user convenience. But it introduces a heavy scanning burden, forcing wallets to check every on-chain output.
A recent BIP 352 update flags a dangerous edge case. If a sender pays the same recipient twice in one transaction - common in batch payments - and the first output is tiny ‘dust,’ a wallet set to ignore low-value outputs might stop scanning early and miss the second, larger payment. As Bitcoin Optech’s Merch notes, this makes the protocol significantly more expensive to support reliably than standard transactions.
Full hardware wallet support is the final hurdle for broad silent payment adoption. Raw is calling on Ledger, Trezor, and Coldcard to implement standards like BIP 376, which would let secure signing devices handle the new transaction types. Without this integration, the tech remains confined to hot wallets, leaving cold storage users in the old, less private paradigm.
“The primary technical challenge for silent payments is client-side scanning cost. Early implementations required hours of computation, making them impractical for average users.”
- Craig Raw, Citadel Dispatch
The underlying theme is Bitcoin’s gradual shift from a fixed protocol to a more programmable system. Proponents of script restoration see it as unlocking a wave of innovation; privacy advocates see tools like silent payments as essential for real-world use. Both efforts face the same challenge: moving from proposal to deployed, secure code that the entire ecosystem can trust.
