From: Olaoluwa Osuntokun <laolu32@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Elliptic Curve Operations for Bitcoin Script
Date: Sun, 24 Aug 2025 20:50:39 -0400 [thread overview]
Message-ID: <CAO3Pvs-Cwj=5vJgBfDqZGtvmoYPMrpKYFAYHRb_EqJ5i0PG0cA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
Hi y'all,
I've just published a draft of a BIP to add Elliptic Curve operation op
codes
as a soft fork utilizing the existing Taproot infrastructure and current tap
leaf version.
My primary motivation is enabling the commutation of the top level Taproot
output public key within Bitcoin Script. Alongside introspection enabling op
codes, this enables the creation of a new flavor of on-chain state machine
within Bitcoin Script. The set of op codes is also generic enough to enable
several other use cases related to (optimized DLCs, partial musig2 signature
verification, EC based sigma protocols, etc).
A total of 4 op codes are proposed (each allocated from the existing
OP_SUCCESS) range:
* `OP_EC_POINT_ADD`
* `OP_EC_POINT_MUL`
* `OP_EC_POINT_NEGATE`
* `OP_EC_POINT_X_COORD`
The full BIP text can be found here:
* https://github.com/bitcoin/bips/pull/1945
A reference implementation in `btcd` can be found here:
* https://github.com/btcsuite/btcd/pull/2413
--Laolu
--
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/CAO3Pvs-Cwj%3D5vJgBfDqZGtvmoYPMrpKYFAYHRb_EqJ5i0PG0cA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 1887 bytes --]
next reply other threads:[~2025-08-25 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 0:50 Olaoluwa Osuntokun [this message]
2025-08-25 16:45 ` [bitcoindev] " 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='CAO3Pvs-Cwj=5vJgBfDqZGtvmoYPMrpKYFAYHRb_EqJ5i0PG0cA@mail.gmail.com' \
--to=laolu32@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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