Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add checksig for vault keypair #12

Merged
merged 3 commits into from
Sep 27, 2024

Conversation

monlovesmango
Copy link
Contributor

I took a stab at adding a CHECKSIGVERIFY to the scripts which check against a keypair that the vault commits to when created. let me know if I didn't get it quite right or if there is anything you don't like about my implementation, happy to make changes!

.finalize(&secp, nums_key)
.expect("finalizing taproot spend info with a NUMS point should always work"))
}

fn x_only_public_key(&self) -> XOnlyPublicKey {
return self.keypair.unwrap().x_only_public_key().0
Copy link
Contributor

Choose a reason for hiding this comment

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

since the VaultCovenant structure has keypair as an Option, this should probably return an Option or we should require that VaultCovenant has a keypair

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have updated it so that keypair is now required for VaultCovenant

@rot13maxi rot13maxi merged commit 9e41e4d into taproot-wizards:main Sep 27, 2024
1 check passed
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