Dynamic modification of an Iceberg group during an open Lightning channel

Determine how much an Iceberg threshold-signing group can change its internal configuration while a Lightning channel remains open, including proactively refreshing shares, repairing the share of a member that has lost it, changing group membership, or changing the threshold, while preserving the aggregate funding key.

Background

Iceberg fixes an aggregate public key for the threshold group, and that key occupies one participant slot in the channel’s MuSig2 funding key. Consequently, changing the aggregate key would require closing and reopening the Lightning channel. The paper explicitly leaves unresolved which internal maintenance and reconfiguration operations can be performed without changing that aggregate key, including share refresh, recovery of a lost share, membership changes, and threshold changes.

References

For Lightning, a further question is how much a group can change about itself while the channel stays open: proactively refreshing its shares, repairing the share of a member that has lost it, or changing the membership or the threshold.

Enabling Threshold Custody for the Lightning Network with Nested Threshold Multi-Signatures  (2608.20705 - Gerhart et al., 21 Aug 2026) in Section 8, Conclusion and Future Work