Not sure if anyone cares but the nested MuSig issue Weitse brought up today and submitted code for is really interesting… cyclical signing could be a very serious issue for MuSig on a decentralized protocol where you actually cannot easily ACK merged code among a smaller set of few distributed nodes
This creates a condition where the Master Key being disabled in a MuSig set up nests a MuSig Parent and then a MuSig child key set… the parent key set is reliant on the child and the child is reliant on the parent allowing neither to meet necessary conditions to confirm a tx in 2 of 3 sign, locking the user out of their funds completely
Brie / DagzTagz
npub14e…mcqa0
2026-02-14 01:26:10 UTC
Author Public Key
npub14expwcsvnvaqgylaqx0a06vrmfpmyzq7w956hm9hwexrxw5mllcsymcqa0Published at
2026-02-14 01:26:10 UTCEvent JSON
{
"id": "91bc7717778ece1fc83e630ea1aba9d213daa9589686da2d4e5a8520614c80a4",
"pubkey": "ae4c17620c9b3a0413fd019fd7e983da43b2081e7169abecb7764c333a9bfff1",
"created_at": 1771032370,
"kind": 1,
"tags": [],
"content": "Not sure if anyone cares but the nested MuSig issue Weitse brought up today and submitted code for is really interesting… cyclical signing could be a very serious issue for MuSig on a decentralized protocol where you actually cannot easily ACK merged code among a smaller set of few distributed nodes\n\nThis creates a condition where the Master Key being disabled in a MuSig set up nests a MuSig Parent and then a MuSig child key set… the parent key set is reliant on the child and the child is reliant on the parent allowing neither to meet necessary conditions to confirm a tx in 2 of 3 sign, locking the user out of their funds completely ",
"sig": "5c637ae6ad8b909558871a0a04c685f455ae88afac1eb3c7141c07b7eee51136a120a7b8f1c59a14a6e439f2b827debe03247bfdda6c73970fcde0dd3291c61b"
}