Delivery-date: Tue, 01 Apr 2025 07:49:14 -0700
Sender: bitcoindev@googlegroups.com
Date: Tue, 1 Apr 2025 06:01:43 -0700 (PDT)
From: waxwing/ AdamISZ <ekaggata@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <c9e7b769-b35f-4e3e-93b3-afdcd9470cd4n@googlegroups.com>
In-Reply-To: <d0044f9c-d974-43ca-9891-64bb60a90f1f@gmail.com>
References: <d0044f9c-d974-43ca-9891-64bb60a90f1f@gmail.com>
Subject: [bitcoindev] Re: secp256k1lab: a Python library for prototyping
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_44020_1279097027.1743512503775"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_44020_1279097027.1743512503775
Content-Type: multipart/alternative; 
	boundary="----=_Part_44021_377990646.1743512503775"

------=_Part_44021_377990646.1743512503775
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks for this.

Seems like a great initiative for, as you say, prototyping and education.=
=20
(though iiuc your primary motive was standardising proposal "reference"=20
code).

I'm guessing that things like MuSig2 and/or adaptors would be out of scope=
=20
of this project? (i.e. you are only supplying the foundational ECC=20
operations here.. except you are providing Schnorr signatures). Those are=
=20
things that ate up time for me when I was prototyping stuff (like=20
"pathcoin" for example), hence the Q.

Regards,
AdamISZ/waxwing

On Tuesday, April 1, 2025 at 5:51:37=E2=80=AFAM UTC-3 Jonas Nick wrote:

> Hello list,
>
> We're pleased to announce the initial release of secp256k1lab, an INSECUR=
E
> implementation of the secp256k1 elliptic curve and related cryptographic=
=20
> schemes
> written in Python, intended for prototyping, experimentation and educatio=
n.
>
> 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=20
> work-in-progress
> BIP [0]. It is based on the secp256k1 implementation in the Bitcoin Core=
=20
> test
> framework.
>
> Our goal was to avoid including yet another custom Python implementation=
=20
> of the
> secp256k1 curve in the ChillDKG reference code. Several existing BIPs=20
> (340, 324,
> 327, and 352) already contain custom and sometimes subtly diverging
> implementations of secp256k1. This library aims to provide a single,=20
> consistent
> interface for secp256k1-related cryptographic specifications.
>
> At the moment, secp256k1lab is included in the ChillDKG repository as a=
=20
> subtree.
> It remains an open question what would be the best approach for including=
=20
> 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, T=
im
> 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)
>

--=20
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 e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
c9e7b769-b35f-4e3e-93b3-afdcd9470cd4n%40googlegroups.com.

------=_Part_44021_377990646.1743512503775
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div>Thanks for this.</div><div><br /></div><div>Seems like a great initiat=
ive for, as you say, prototyping and education. (though iiuc your primary m=
otive was standardising proposal "reference" code).</div><div><br /></div><=
div>I'm guessing that things like MuSig2 and/or adaptors would be out of sc=
ope of this project? (i.e. you are only supplying the foundational ECC oper=
ations here.. except you are providing Schnorr signatures). Those are thing=
s that ate up time for me when I was prototyping stuff (like "pathcoin" for=
 example), hence the Q.</div><div><br /></div><div>Regards,</div><div>AdamI=
SZ/waxwing</div><br /><div class=3D"gmail_quote"><div dir=3D"auto" class=3D=
"gmail_attr">On Tuesday, April 1, 2025 at 5:51:37=E2=80=AFAM UTC-3 Jonas Ni=
ck wrote:<br/></div><blockquote class=3D"gmail_quote" style=3D"margin: 0 0 =
0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hel=
lo list,
<br>
<br>We&#39;re pleased to announce the initial release of secp256k1lab, an I=
NSECURE
<br>implementation of the secp256k1 elliptic curve and related cryptographi=
c schemes
<br>written in Python, intended for prototyping, experimentation and educat=
ion.
<br>
<br><a href=3D"https://github.com/secp256k1lab/secp256k1lab" target=3D"_bla=
nk" rel=3D"nofollow" data-saferedirecturl=3D"https://www.google.com/url?hl=
=3Den&amp;q=3Dhttps://github.com/secp256k1lab/secp256k1lab&amp;source=3Dgma=
il&amp;ust=3D1743598589364000&amp;usg=3DAOvVaw30w9CzRVAFj3VnXkU79qQQ">https=
://github.com/secp256k1lab/secp256k1lab</a>
<br>
<br>Features:
<br>
<br>- Low-level secp256k1 field and group arithmetic.
<br>- Schnorr signing/verification and key generation according to BIP-340.
<br>- ECDH key exchange.
<br>
<br>We developed secp256k1lab as part of our work on the ChillDKG work-in-p=
rogress
<br>BIP [0]. It is based on the secp256k1 implementation in the Bitcoin Cor=
e test
<br>framework.
<br>
<br>Our goal was to avoid including yet another custom Python implementatio=
n of the
<br>secp256k1 curve in the ChillDKG reference code. Several existing BIPs (=
340, 324,
<br>327, and 352) already contain custom and sometimes subtly diverging
<br>implementations of secp256k1. This library aims to provide a single, co=
nsistent
<br>interface for secp256k1-related cryptographic specifications.
<br>
<br>At the moment, secp256k1lab is included in the ChillDKG repository as a=
 subtree.
<br>It remains an open question what would be the best approach for includi=
ng ChillDKG
<br>(with the secp256k1lab dependency) into the bips repository [1].
<br>
<br>We welcome your feedback and contributions to this project.
<br>
<br>Best regards,
<br>The current secp256k1lab maintainers: Sebastian Falbesoner, Jonas Nick,=
 Tim
<br>Ruffing
<br>
<br>[0] <a href=3D"https://github.com/BlockstreamResearch/bip-frost-dkg" ta=
rget=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https://www.google=
.com/url?hl=3Den&amp;q=3Dhttps://github.com/BlockstreamResearch/bip-frost-d=
kg&amp;source=3Dgmail&amp;ust=3D1743598589364000&amp;usg=3DAOvVaw3TQ72C3b2M=
a-Q-OsCt0r_E">https://github.com/BlockstreamResearch/bip-frost-dkg</a>
<br>[1] <a href=3D"https://groups.google.com/g/bitcoindev/c/HE3HSnGTpoQ/m/Y=
2VhaMCrCAAJ" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"htt=
ps://www.google.com/url?hl=3Den&amp;q=3Dhttps://groups.google.com/g/bitcoin=
dev/c/HE3HSnGTpoQ/m/Y2VhaMCrCAAJ&amp;source=3Dgmail&amp;ust=3D1743598589364=
000&amp;usg=3DAOvVaw2QHHtwASRIyVnSnWd4d9Y0">https://groups.google.com/g/bit=
coindev/c/HE3HSnGTpoQ/m/Y2VhaMCrCAAJ</a>
<br>     (We renamed secp256k1proto to secp256k1lab)
<br></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/c9e7b769-b35f-4e3e-93b3-afdcd9470cd4n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/c9e7b769-b35f-4e3e-93b3-afdcd9470cd4n%40googlegroups.com</a>.<br />

------=_Part_44021_377990646.1743512503775--

------=_Part_44020_1279097027.1743512503775--