Replying to Avatar ManiMe

Thanks. I have a couple more Qs I can’t seem to find answers for … coming from a client dev :

1: does a “share signing” client have access to the “main” npub? This seems important in many ways, but I’m not clear on this in what I’ve seen of your ‘bifrost’ codebase.

2: if so … NIP07 only specifies that signers implement ‘getPublicKey()’ … which pubkey does ‘frost2x’ output ?

3: what happens with events signed by an orphaned share?

I’m sorry for being a bit dense … I guess I’m simply unclear if the ‘pubkey’ field of signed event contains the ‘main pubkey’ or the share string?
Avatar
cmd 9mo ago

Also, orphaned shares can't sign for anything. In fact, no single share can sign for anything. They can only contribute a part of the signature. You need a qurom of shares to participate in order to create a full signature. If you orphan a compromised share by deleting your other shares, then that orphan share is worthless.

Reply to this note

Please Login to reply.

Discussion

No replies yet.