manime on Nostr: But wait … Does Frost allow for the “co-signing” client to gain access to the ...
But wait …
Does Frost allow for the “co-signing” client to gain access to the main “npub” (not nsec) … cause it would need to know this in order to read and write to lists, profiles, ect… let alone access to “other” users’ main pubkeys for Outbox ect…
Does Frost allow for the “co-signing” client to gain access to the main “npub” (not nsec) … cause it would need to know this in order to read and write to lists, profiles, ect… let alone access to “other” users’ main pubkeys for Outbox ect…
quoting nevent1q…h0pwAlright … now I’m just getting familiar with frost … but it looks to me like the bifrost implementation generates a unique (group_pk) pubkey for each “group” of “shares”… and it isn’t straight forward how the “main” pubkey would be obtained by a client “signer”, signing with one of the “shares”. What do you know about this?
https://github.com/FROSTR-ORG/bifrost/blob/master/src/types/group.ts#L24