search

zapstore / zapstore

Permissionless app store powered by your social network
https://zap.store
MIT License
41 stars 4 forks source link

multi-sig release #80

Closed alltheseas closed 1 week ago

alltheseas commented 3 weeks ago

user story

As a team of devs developing one app, we would like to set up a multi-sig quorum to sign releases, so that we distribute signing responsibilities & risk.

acceptance criteria

  1. devs can set up quorum m of n multi-sig for signing releases

questions

  1. what happens if a dev retires, or steps away?

context

see https://njump.me/nevent1qqs8pmmae89agph80928l6gjm0wymechqazv80jwqrqy4cgk08epjacrrnpt0 see https://github.com/nickfarrow/frostr

franzaps commented 1 week ago

Shouldn't we leave these things to emerge from users? Maybe there's little demand

alltheseas commented 1 week ago

Fair. Let me add a new label - unvalidated

franzaps commented 1 week ago

Sure is there value in collecting issues that may never be implemented?

franzaps commented 1 week ago

How about having ONE issue where we add these unvalidated ideas? A lot of them adds clutter when trying to find the important stuff

alltheseas commented 1 week ago

How about having ONE issue where we add these unvalidated ideas? A lot of them adds clutter when trying to find the important stuff

OK

https://github.com/zapstore/zapstore/issues/105