Aye the devil is always in the details. You'll probably need to build several iterations to figure out what's truly optimal. Thresholds are just one tool in the drawer.

Would be happy to take a look once you can share more. 

I have a [Delay Tolerant](https://stacker.news/items/330735) design bias so I personally want less rounds lol. 

There's some nonsense I'm cooking up that may be best described as:
![meth head gun](https://m.stacker.news/124041)

But I'm going to try to make it as not cursed as I can think of lol.


nerd2ninja

 way depending on the use-case, as it'd be over-kill and potentially have a coordination problem for ad-hoc chains of signatures where a user may only co-sign events randomly. In that setting a derivative of "boost" would probably be adequate.

It'd only be proper for regular group signatures, like for an entity or committee.

FROSTR uses these threshold sigs, could check out that project or maybe consult with 

nostr

Protocol Design

In might not be *the right* way depending on the use-case, as it'd be over-kill and potentially have a coordination problem for ad-hoc chains of signatures where a user may only co-sign events randomly. In that setting a derivative of "boost" would probably be adequate.

It'd only be proper for regular group signatures, like for an entity or committee.

FROSTR uses these threshold sigs, could check out that project or maybe consult with @bitcoinplebdev 