# K-of-N threshhold key generation scheme by limited shared secrets

**URL:** <https://delvingbitcoin.org/t/k-of-n-threshhold-key-generation-scheme-by-limited-shared-secrets/2623>\
**Category:** Protocol Design\
**Tags:** lightning, taproot\
**Created:** [June 20, 2026, 6:52am UTC](https://delvingbitcoin.org/t/k-of-n-threshhold-key-generation-scheme-by-limited-shared-secrets/2623 "2026-06-20T06:52:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kusudoha](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/kusudoha/32/2461_2.png) [@kusudoha](https://delvingbitcoin.org/u/kusudoha)\
**Post date:** [October 27, 2026, 3:12pm UTC](https://delvingbitcoin.org/t/k-of-n-threshhold-key-generation-scheme-by-limited-shared-secrets/2623/4 "2026-10-27T15:12:02Z")

</div>

The distinction seems to be the interface the scheme is trying to preserve: it reduces the threshold key to MuSig2 instances, so the author can rely on the existing MuSig2-in-MuSig2 proof for Taproot channels and derive shachain roots from the shared secrets. If Arctic can provide the same composition and derivation properties, the comparison should focus on setup, storage, and what security proof covers that exact use, not just threshold signing.

---

_[View the full topic](https://delvingbitcoin.org/t/k-of-n-threshhold-key-generation-scheme-by-limited-shared-secrets/2623)._