Skip to content

Conversation

LLFourn
Copy link
Owner

@LLFourn LLFourn commented Jan 12, 2022

Sort of compatible with: BlockstreamResearch/secp256k1-zkp#131

relevant new code is in musig.rs the rest is just yak shaving.

We do this so we naturally get an implementation for lists of things
that do HashInto. It's hard to arrange otherwise.
To allow for using faster multi-exp algorithms now used in backend.
Nobody actually needs this!
/// Returns a reference to the public key.
pub fn public_key(&self) -> &XOnly {
&self.pk
pub fn public_key(&self) -> XOnly {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any rationale on why you go this way (by value instead ref?)

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

XOnly is Copy so I think it's conventional to not return references to Copy things. On top of that There's no reason to leak the implementation that keyPair stores an XOnly (it could store a Point<EvenY> instead).

(that comment needs to change though).

@LLFourn LLFourn merged commit 017aaf3 into master Jan 13, 2022
@LLFourn LLFourn deleted the musig2 branch January 13, 2022 04:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants