From: waxwing/ AdamISZ <ekaggata@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: secp256k1lab: a Python library for prototyping
Date: Tue, 1 Apr 2025 06:01:43 -0700 (PDT) [thread overview]
Message-ID: <c9e7b769-b35f-4e3e-93b3-afdcd9470cd4n@googlegroups.com> (raw)
In-Reply-To: <d0044f9c-d974-43ca-9891-64bb60a90f1f@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2679 bytes --]
Thanks for this.
Seems like a great initiative for, as you say, prototyping and education.
(though iiuc your primary motive was standardising proposal "reference"
code).
I'm guessing that things like MuSig2 and/or adaptors would be out of scope
of this project? (i.e. you are only supplying the foundational ECC
operations here.. except you are providing Schnorr signatures). Those are
things that ate up time for me when I was prototyping stuff (like
"pathcoin" for example), hence the Q.
Regards,
AdamISZ/waxwing
On Tuesday, April 1, 2025 at 5:51:37 AM UTC-3 Jonas Nick wrote:
> Hello list,
>
> We're pleased to announce the initial release of secp256k1lab, an INSECURE
> implementation of the secp256k1 elliptic curve and related cryptographic
> schemes
> written in Python, intended for prototyping, experimentation and education.
>
> https://github.com/secp256k1lab/secp256k1lab
>
> Features:
>
> - Low-level secp256k1 field and group arithmetic.
> - Schnorr signing/verification and key generation according to BIP-340.
> - ECDH key exchange.
>
> We developed secp256k1lab as part of our work on the ChillDKG
> work-in-progress
> BIP [0]. It is based on the secp256k1 implementation in the Bitcoin Core
> test
> framework.
>
> Our goal was to avoid including yet another custom Python implementation
> of the
> secp256k1 curve in the ChillDKG reference code. Several existing BIPs
> (340, 324,
> 327, and 352) already contain custom and sometimes subtly diverging
> implementations of secp256k1. This library aims to provide a single,
> consistent
> interface for secp256k1-related cryptographic specifications.
>
> At the moment, secp256k1lab is included in the ChillDKG repository as a
> subtree.
> It remains an open question what would be the best approach for including
> ChillDKG
> (with the secp256k1lab dependency) into the bips repository [1].
>
> We welcome your feedback and contributions to this project.
>
> Best regards,
> The current secp256k1lab maintainers: Sebastian Falbesoner, Jonas Nick, Tim
> Ruffing
>
> [0] https://github.com/BlockstreamResearch/bip-frost-dkg
> [1] https://groups.google.com/g/bitcoindev/c/HE3HSnGTpoQ/m/Y2VhaMCrCAAJ
> (We renamed secp256k1proto to secp256k1lab)
>
--
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/c9e7b769-b35f-4e3e-93b3-afdcd9470cd4n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4177 bytes --]
prev parent reply other threads:[~2025-04-01 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 8:41 [bitcoindev] " Jonas Nick
2025-04-01 13:01 ` waxwing/ AdamISZ [this message]
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=c9e7b769-b35f-4e3e-93b3-afdcd9470cd4n@googlegroups.com \
--to=ekaggata@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