Can we please get threshold ECDSA signing support for secp256r1 (P-256) on ICP?

[yinks002]

Following up on the icert post ICert , Decentralized Cetificate Authority

ICP really needs threshold ECDSA support for secp256r1 (P-256).

secp256k1 works for Bitcoin/Ethereum, but P-256 is the universal standard for X.509/TLS and browser trust.

We’ve heard this is already being worked on , please prioritize and complete implementation, as it’s the only way projects like iCert can achieve real-world adoption as a decentralized CA.

[ilbert]

Cross-posting as it’s the same topic:

Plans for secp256r1 (P-256) threshold ECDSA support?

I’m not sure if there are any technical blockers with adding secp256r1 (P-256) to the supported threshold ECDSA curves, but I’ve been hitting limitations trying to implement web standards that require it. Most OAuth 2.0 implementations and JWT libraries default to ES256 signatures, which need the P-256 curve specifically - this includes things like OAuth DPoP, AT Protocol, and pretty much any modern identity/auth system. Right now I can only use secp256k1, which works great for blockchain stuff…