the last lightning dev meetup we had in zurich back in october, it's generally agreed upon at the spec layer that it's something we'd all like to implement at some point. the real blocker here, afaict is the inclusion of MuSig2 into the "mainline" libsecp256k1 branch -- that or bitcoin-core etc adopting the -zkp branch that currently hosts it.
it'll happen, it's just a matter of time. last i heard the LND team is pushing ahead really hard with this -- laolu's been tweeting about reimplementing MuSig2 into his go-backed version of a bitcoin client, btcd, which i think speaks to the importance of MuSig2 adoption
reply
why do you need MuSig2 at all?
afaiu with just 2p / interactivity there are some much simpler variants that work fine...
reply