scriptless-scripts VS DotNetLightning

The example you gave of a multisig output that can be spent by either Alice, or Bob after some time, is easily handled too.

[1] https://github.com/BlockstreamResearch/scriptless-scripts

​ With MuSig2, some protocols will benefit greatly, such as “scriptless script Lightning” and threshold signature. If Taproot is started, MuSig2 can be applied to a series of Blockstream products, such as Blockstream Green and c-lightning, as well as the Liquid peg mechanism. The Liquid network may activate Taproot before Bitcoin, and we can experience MuSig2 on it earlier!

With that in mind, let’s make a graphical model for Atomic swap with an adaptor signature. I won’t go into the details about the protocol.. The model will be something like

While ago, I’ve been building F# library for the Bitcoin Lightning Network (LN), DotNetLightning. After (barely) finishing my first iteration, I’ve noticed that there is a more matured library called rust-lightning for doing the same for the rustlang, and I’ve switched my efforts to its .NET binding with C# After working for both F# and C# for a decent amount of time, I noticed that it both has goodies and baddies for different domains. One particular domain I think that F# is a clear winner is for prototyping a new idea.