public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: jeremy <jeremy.l.rubin@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] OP_TWEAKADD
Date: Sat, 23 Aug 2025 10:35:58 -0700 (PDT)	[thread overview]
Message-ID: <bc9ff794-b11e-47bc-8840-55b2bae22cf0n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1052 bytes --]

Hi all,

I've made a draft BIP writeup of an (often discussed) simple opcode, 
OP_TWEAKADD, deployable as an OP_SUCCESSx upgrade.

https://github.com/bitcoin/bips/pull/1944

This opcode is relatively simple. The main design choices are:

1) Verify v.s. Push semantics -- Push, for succinctness on-chain
2) Argument order -- Key on top, for tweak in witness
3) Plain tweak or something else -- Plain tweak, if hashing is desirable 
the user can do it. The most flexible is to do a plain tweak. Future work 
could add TapTree opcodes to construct taproot tweaks.

Feedback and discussion are welcome.

Best,

Jeremy

[^1] OP_SHA256 in these example prevents key-cancellation.

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/bc9ff794-b11e-47bc-8840-55b2bae22cf0n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1568 bytes --]

             reply	other threads:[~2025-08-23 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23 17:35 jeremy [this message]
2025-08-23 18:24 ` [bitcoindev] Re: [BIP Proposal] OP_TWEAKADD jeremy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bc9ff794-b11e-47bc-8840-55b2bae22cf0n@googlegroups.com \
    --to=jeremy.l.rubin@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox