combinePubKeys should not allow for n_pubkeys==1 about secp256k1-zkp HOT 5 CLOSED

why wouldn't it? n_pubkeys = 1 is well defined and has an obvious sensible behaviour. If the interface forces more than one then a caller needs to handle an additional corner case that would otherwise just work.

from secp256k1-zkp.

Hm. You can also combine the same pubkey n times with itself. I don't have a use case for this either but it's not broken or wrong in any sense, so I tend not to put restrictions here. But you're right, it's somehow confusing. I'm indifferent.

from secp256k1-zkp.

Ok, if the current behavior is to be kept, it would be nice to document it. How about a footnote in musig.md that says that the API supports a single signer? The footnote could be referenced each time a plural like "participants" or "public keys" is used.

from secp256k1-zkp.

I'd rather not complicate the exposition for the sake of this usecase. The current text makes sense for n=1 (aside from being ungrammatical) and it never occurred to me that n=1 might not work. Though perhaps I am just too close to this.

from secp256k1-zkp.

I don't understand what's the issue here. Does the function not do exactly what you'd expect with 1 input?

Look at Python's sum function (https://docs.python.org/3/library/functions.html#sum). It also does not list a special case for only one input.

from secp256k1-zkp.