Imagine you have just stepped inside a small book shop. Your first step places you on a thick woven rug. Floor-to-ceiling shelves make aisles around you. Quietly to yourself you whisper I could discover something in here, and you begin your search. For what? You’re not sure. Little potentials of discovery respond to you, pulling your eye from this shelf to that. You’re excited, alert, and open.
After a few moments taking slow steps, smelling the book shop smell, your eye rests on a thin slip of white binding smushed between two volumes. It looks out of place, homemade. The other books on the shelf are more dignified. This one is probably not supposed to be here. You reach for it.
It is very light, a paperback. You turn it over in your hand to see the front cover.
https://m.stacker.news/34095
Flipping aside the front cover reveals an inscription.
https://m.stacker.news/34096
You look up. The book shop is still there, suspended in silence. You repeat a few words, “close my mouth around the whole wide world.” You think why would you want to do that?
You turn over one more page,
Opening Remarks
You have a choice. Do you keep reading?
etc, etc, etc
you just reminded me that I wanted to create this ticket
"Do not listen to "men" with open mouth disease"
https://m.stacker.news/63743
They do have a lower footprint. Frost signatures are the same size as musig2 signatures, which are themselves the same size as "regular" schnorr signatures. That is, they are all 64 bytes.
One of the difficulties with using frost is that it doesn't support "bringing your own key." If 3 people want to generate a 2 of 3 "frost multisig" together, they cannot each independently generate a keypair and then "combine" their pubkeys together. They have to come together to generate a keypair together in a kind of "key generation ceremony." The ceremony involves doing some math that allows every keyholder to ensure everyone followed the protocol properly so that they all know for sure they'll be able to sign later.
Not only is frost not standardized yet, there is also not yet any standardized way to do the key generation ceremony. And if companies like Unchained and Hodlhodl want to support this new form of multisig, some of them will probably have to change how they do business. Any of them that ask their users to provide 2 keys and let the company provide the third can't really do that anymore. They'll have to participate in a key generation ceremony that involves interacting with both users to generate a key and do the aforementioned math to ensure it's safe.
It's all quite involved and I don't expect much fruit to come out of it anytime soon. "Regular" multisig works well so I don't see much motivation to code up the fancier version that taproot enabled. Consequently the number of people working on it is small, and progress is slow.