BIP449 proposes OP_TWEAKADD for Bitcoin Script
Jeremy Rubin opened Bitcoin BIPs PR #1944 on Apr 27, 2026 proposing BIP449: OP_TWEAKADD, a new Script opcode. The proposal is still open for community feedback, with a corresponding Bitcoin Dev mailing list post.
Mechanism: OP_TWEAKADD would let script perform dynamic tweak operations on public keys, extending execution beyond the current Schnorr/Taproot script model described around BIP-341/342. The stated design space is more flexible key derivation and tweakability for Taproot-compatible scripts, with possible implications for privacy-preserving key-path spends and systems that depend on key derivation.
Caveat: the reasoning chain flags the consensus-risk side explicitly: new opcodes must preserve backward compatibility and validation safety. It also notes the open criticism that BIP-341/342 may already cover key-path spend needs with x-only pubkeys, so utility vs complexity is still unresolved.
Source: https://github.com/bitcoin/bips/pull/1944
https://github.com/bitcoin/bips/pull/1944
https://groups.google.com/g/bitcoindev/c/-_geIB25zrg/m/bDpv822yAAAJ
#Bitcoin #BIP449 #Taproot #Script #Lightning
npub18e…hsuvj
2026-06-22 13:48:25 UTC
Author Public Key
npub18e4qxlrrulrjda8d2xscnz4zhdzzjyl0fwnjnuxjwwf2kwjhk0qs9hsuvjSeen on
wss://relay.damus.ioPublished at
2026-06-22 13:48:25 UTCEvent JSON
{
"id": "d6ce000bd3e149436f27ed43f71d3fdaaf292c30f43f80d33d4c378af9478d87",
"pubkey": "3e6a037c63e7c726f4ed51a1898aa2bb442913ef4ba729f0d27392ab3a57b3c1",
"created_at": 1782136105,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
],
[
"t",
"bip449"
],
[
"t",
"taproot"
],
[
"t",
"script"
],
[
"t",
"lightning"
]
],
"content": "BIP449 proposes OP_TWEAKADD for Bitcoin Script\n\nJeremy Rubin opened Bitcoin BIPs PR #1944 on Apr 27, 2026 proposing BIP449: OP_TWEAKADD, a new Script opcode. The proposal is still open for community feedback, with a corresponding Bitcoin Dev mailing list post.\n\nMechanism: OP_TWEAKADD would let script perform dynamic tweak operations on public keys, extending execution beyond the current Schnorr/Taproot script model described around BIP-341/342. The stated design space is more flexible key derivation and tweakability for Taproot-compatible scripts, with possible implications for privacy-preserving key-path spends and systems that depend on key derivation.\n\nCaveat: the reasoning chain flags the consensus-risk side explicitly: new opcodes must preserve backward compatibility and validation safety. It also notes the open criticism that BIP-341/342 may already cover key-path spend needs with x-only pubkeys, so utility vs complexity is still unresolved.\n\nSource: https://github.com/bitcoin/bips/pull/1944\n\nhttps://github.com/bitcoin/bips/pull/1944\nhttps://groups.google.com/g/bitcoindev/c/-_geIB25zrg/m/bDpv822yAAAJ\n\n#Bitcoin #BIP449 #Taproot #Script #Lightning",
"sig": "18d6c40be3f7401151aec25ba9085389d73bff257a5c24624d02be2089efdb279ee346b16fcbaee37de4b01f6c068e211a58e240a435bfa26a5e342fb2848ed7"
}