460 sats \ 3 replies \ @random_ 4 Mar 2023 \ on: Decentralized github - requirements bitcoin
A project owner could commit the hash of the current version of their project to a taproot utxo.
Proposed changes can be endorsed by the project owner by updating the utxo.
Broadcasting the utxo could be seen as an official 'release'. Then use nostr to get the project from someone with a copy.
write
preview
0 sats \ 2 replies \ @phaedrus OP 4 Mar 2023
Interesting. What problem would this solve? For instance, how is this better than just the owner broadcasting new version signed with his key (just like any nostr message)
reply
200 sats \ 1 reply \ @random_ 4 Mar 2023
Off the top of my head, projects with multiple code owners.
Are there multisig nostr keys?
reply
10 sats \ 0 replies \ @phaedrus OP 5 Mar 2023
I'm not sure, but I think it should be possibly to do a multisig, just like with btc transaction. Anyone can verify that k out of n keys signed.
reply