March 21, 2026
One key to rule? Not this thread
Why One Key Shouldn't Rule Them All: Threshold Signatures for the Rest of Us
Team-Key Hype vs “Just Use a Lockbox” Brigade
TLDR: A new “team key” approach called DKLS23 promises faster, safer signatures without a single point of failure, but the crowd is split: HSM defenders say hardware lockboxes already solve this, critics slam the post as too shallow, and skeptics fear handing power to a committee is a governance nightmare.
A new post pitched threshold signatures — think “team key” where a few people must cooperate to unlock — as the fix for the classic single secret that can sink everything. The star of the show is DKLS23, a newer recipe that cuts the back-and-forth and speeds things up so signatures can happen fast, even on shaky phone connections. It still produces a normal-looking signature, so nothing breaks. Cue the fireworks.
The loudest clapback? “We already have hardware safes for keys.” Security ops folks rallied behind hardware security modules (HSMs), those tamper-resistant lockboxes where keys never leave. bob1029 basically said the whole “compromised server” line misses the point: if you set up the lockbox right, even the owner can’t touch the key.
Meanwhile, the vibes turned spicy when another commenter accused the write-up of being hand-wavy — “If you want a blog, write a blog” — calling for more math and fewer buzzwords. And the practicality crowd jumped in: yammosk doubts any company would let “3 out of 5” humans hold the crown jewels, comparing it to signing your paycheck with an Ocean’s Eleven crew. Governance beats math, they argue.
So the thread split into camps: crypto fans cheering fewer failure points and faster protocols, ops veterans yelling “just use the lockbox,” and skeptics asking who’s actually in that signing group — and what happens when someone’s on vacation. Heroes assemble or too many cooks? That’s the drama
Key Points
- •Threshold signatures split a private key across multiple parties, producing standard ECDSA signatures that are indistinguishable from single-signer outputs.
- •The DKLS23 protocol (2023), presented at IEEE Oakland 2024, advances threshold ECDSA by using oblivious transfer and requiring only three communication rounds.
- •Earlier protocols like GG18 and GG20 relied on homomorphic encryption and six or more rounds, increasing latency and complexity.
- •A simplified 2-of-2 setup uses DH-style key generation to derive a shared public key and combines nonce-based partial signatures into a standard ECDSA signature.
- •Threshold ECDSA is already used in production by organizations such as Coinbase and Visa, and verification works with tools like OpenSSL and Go’s crypto/ecdsa.