So as of right now, the nostr protocol does not allow multiple signatures on one note. There are some fancy ways around this, but if for a variety of reasons you wanted to allow multiple people to sign or ack a note, how would you do it?
Separating the signature from the note segwit style would probably be protocol breaking and probably not compatible with current relays
Implementing an "ack" note, would be a separate event that references the main event, is more bandwidth, makes it harder for potentially lost notes, relies on some client side magic to work well.
Seperate signature from the note33.3%
Implement an "ack" note66.7%
3 votes \ poll ended
A threshold signature
Would require first a one-time attestation to membership, but all forward events would be verifiably linked to your key
This is probably the hard, but right way. Although I would assume at the cost of more rounds. Can you send me some documentation you'd recommend I look into?
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
I have a Delay Tolerant design bias so I personally want less rounds lol.
There's some nonsense I'm cooking up that may be best described as:
But I'm going to try to make it as not cursed as I can think of lol.
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'll be posting a Request for Comment. At this rate maybe a couple of RFCs. It'll be a stacker news post (as well as in the NIP repo), but I'll ping you when its ready.
This is very interesting idea.
What is a ack?
I can imagine a whitepaper with the signature of the individuals who worked on it.
Ack means acknowledged. Since its winning, some more details about how it might work.
The main note is posted by the proposer of the event. The event proposer can specify a threshold of signers for the event to be valid. The note will not show in unspecified user's feed until it reaches the threshold of signatures from specified npubs.
Specified npubs will get a notification similar to if they had been tagged. They will then co-sign the event in a way that I would imagine to be similar to reacting to a note.
This kind would have a timeout so that clients and relays know they can safely discard a note that does not reach its threshold.
If a note does not specify npubs, then anyone can co-sign