Delivery-date: Tue, 22 Jul 2025 15:03:51 -0700
Sender: bitcoindev@googlegroups.com
Date: Tue, 22 Jul 2025 14:44:02 -0700 (PDT)
From: Josh Doman <joshsdoman@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <8fbe1fe3-425d-4056-8387-993f6ecc1been@googlegroups.com>
Subject: [bitcoindev] Revisiting secp256r1 signatures (i.e. P256, mobile HSM support)
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1096_1724980226.1753220642283"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_1096_1724980226.1753220642283
Content-Type: multipart/alternative; 
	boundary="----=_Part_1097_1344044231.1753220642283"

------=_Part_1097_1344044231.1753220642283
Content-Type: text/plain; charset="UTF-8"

A brief search on gnusha.org <https://gnusha.org/pi/bitcoindev/?q=secp256r1> 
suggests that it's been over 10 years since the Bitcoin community last 
discussed adding secp256r1 support (also known as P256). The most in-depth 
discussions I found were on BitcoinTalk in 2011 
<https://bitcointalk.org/?topic=2699.0> and 2013 
<https://bitcointalk.org/index.php?topic=151120.0>.

Since then, P256 has gained widespread adoption across the modern internet 
and on mobile. Most notably, millions of users now possess mobile devices 
capable of generating and storing private keys in secure enclaves (see 
Apple iCloud Keychain and Android Keystore). Millions of users might be 
able to immediately use this to start self-custodying bitcoin, except this 
hardware only supports P256 signatures, which is incompatible with the 
secp256k1 curve that Bitcoin currently uses.

Reading through old discussions, it appears that the primary concern the 
community had with P256 is the possibility of a NIST backdoor. Putting the 
likelihood of this aside, it seems reasonable to me that in 2025, users 
should at least have the option of using P256, if they wish. Native HSM 
support would significantly improve the onboarding experience for new 
users, increase the security and accessibility of hot wallets, and 
potentially reduce the cost of collaborative multisigs. Meanwhile, the 
community can continue to use secp256k1 as the ideal curve for private keys 
secured in cold storage.

At a technical level, Tapscript makes P256 mechanically straightforward to 
adopt, because it has built-in support for new types of public keys. For 
example, we could define a 33-byte public key as one requiring a P256 ECDSA 
signature, while continuing to use 32-bytes for keys requiring Schnorr 
signatures over secp256k1.

A secondary concern that I came across is that P256 can be 2-3x slower to 
validate than secp256k1. Assuming this cannot be improved, we can account 
for slower validation by doubling or tripling the validation weight cost 
for a P256 signature. Users can then pre-commit in their script to this 
additional weight or commit to it in the annex, as intended by BIP341 
<https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki>.

P256 support would grant apps the ability to use platform APIs to access 
the secure HSM on user's mobile devices, but alone, P256 is insufficient 
for non-custodial WebAuthn / passkey-based wallets. To verify a WebAuthn 
signature, we'd additionally need CSFS and CAT, so we can compute a 
WebAuthn message from a sighash and the necessary WebAuthn data on the 
stack. Alternatively, we could create a dedicated WebAuthn opcode to verify 
a WebAuthn message without enabling recursive covenants. Regardless, the 
ability to verify a P256 signature would be an important primitive.

In summary, *given the widespread hardware adoption and industry usage, is 
it worth revisiting adding P256 support to Bitcoin?*

Josh Doman

-- 
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/8fbe1fe3-425d-4056-8387-993f6ecc1been%40googlegroups.com.

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

A brief search on <a href=3D"https://gnusha.org/pi/bitcoindev/?q=3Dsecp256r=
1">gnusha.org</a> suggests that it's been over 10 years since the Bitcoin c=
ommunity last discussed adding secp256r1 support (also known as P256). The =
most in-depth discussions I found were on BitcoinTalk in <a href=3D"https:/=
/bitcointalk.org/?topic=3D2699.0">2011</a> and <a href=3D"https://bitcointa=
lk.org/index.php?topic=3D151120.0">2013</a>.<br /><br />Since then, P256 ha=
s gained widespread adoption across the modern internet and on mobile. Most=
 notably, millions of users now possess mobile devices capable of generatin=
g and storing private keys in secure enclaves (see Apple iCloud Keychain an=
d Android Keystore). Millions of users might be able to immediately use thi=
s to start self-custodying bitcoin, except this hardware only supports P256=
 signatures, which is incompatible with the secp256k1 curve that Bitcoin cu=
rrently uses.<br /><br />Reading through old discussions, it appears that t=
he primary concern the community had with P256 is the possibility of a NIST=
 backdoor. Putting the likelihood of this aside, it seems reasonable to me =
that in 2025, users should at least have the option of using P256, if they =
wish. Native HSM support would significantly improve the onboarding experie=
nce for new users, increase the security and accessibility of hot wallets, =
and potentially reduce the cost of collaborative multisigs. Meanwhile, the =
community can continue to use secp256k1 as the ideal curve for private keys=
 secured in cold storage.<br /><br />At a technical level, Tapscript makes =
P256 mechanically straightforward to adopt, because it has built-in support=
 for new types of public keys. For example, we could define a 33-byte publi=
c key as one requiring a P256 ECDSA signature, while continuing to use 32-b=
ytes for keys requiring Schnorr signatures over secp256k1.<br /><br />A sec=
ondary concern that I came across is that P256 can be 2-3x slower to valida=
te than secp256k1. Assuming this cannot be improved, we can account for slo=
wer validation by doubling or tripling the validation weight cost for a P25=
6 signature. Users can then pre-commit in their script to this additional w=
eight or commit to it in the annex, as intended by <a href=3D"https://githu=
b.com/bitcoin/bips/blob/master/bip-0341.mediawiki">BIP341</a>.<br /><br />P=
256 support would grant apps the ability to use platform APIs to access the=
 secure HSM on user's mobile devices, but alone, P256 is insufficient for n=
on-custodial WebAuthn / passkey-based wallets. To verify a WebAuthn signatu=
re, we'd additionally need CSFS and CAT, so we can compute a WebAuthn messa=
ge from a sighash and the necessary WebAuthn data on the stack. Alternative=
ly, we could create a dedicated WebAuthn opcode to verify a WebAuthn messag=
e without enabling recursive covenants. Regardless, the ability to verify a=
 P256 signature would be an important primitive.<br /><br />In summary, <b>=
given the widespread hardware adoption and industry usage, is it worth revi=
siting adding P256 support to Bitcoin?</b><br /><div><b><br /></b></div><di=
v>Josh Doman</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/8fbe1fe3-425d-4056-8387-993f6ecc1been%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/8fbe1fe3-425d-4056-8387-993f6ecc1been%40googlegroups.com</a>.<br />

------=_Part_1097_1344044231.1753220642283--

------=_Part_1096_1724980226.1753220642283--