Here is a VERY rough draft for a FROST signing NIP.
I'd love to hear feedback and potential security concerns from anyone knowledgeable on the subject.
https://github.com/nostr-protocol/nips/pull/1400
Login to reply
Replies (8)
Frosty nip
why does it have to be a NIP
It doesn't have to be, but would be good. to establish some consensus across clients
can't the frost providers just answer like normal nip46 servers?
The handshake between them is a bit different because nonce commitments and partial signatures need to be communicated
Question: would it be possible to do time based delegation? To be more clear, I mean say you have a nostr webapp that you'd like to use, so you create some delegated keys, those keys are stored in the browser (think JWT tokens) and eventually expire. And a new fresh pair can be renegotiated later. This would allow users to sign/send events using the app but without needing constant approval from the remote signer (I'm think a chat app that uses your nostr keys, it would be a pain to have to constantly use my remote signer as opposed to just using it once for a session). Is this kind of scheme possible or even advisable?
why? can't the bunker perform the signing ritual with different peers and just return the signed event to the nip46 client?
Oh someone's working on FROST nostr already!
nostr:nevent1qqszlav4jw5wxl6mpn7n4w42la42en88ttzh3a4kjmzwy5jqtjtsseqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqhw9adf5sw9fp9eks2yx2kyjs2ffeufa5htuttzkflepl6gmedtqpsgqqqqqqs46rfr5