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

Update to bitcoin 0.28.0 release #337

Closed
wants to merge 4 commits into from
Closed

Update to bitcoin 0.28.0 release #337

wants to merge 4 commits into from

Conversation

dr-orlovsky
Copy link
Contributor

Closes #336.

Will be un-drafted once the release is published.

@sanket1729 pls let me know will I need to squash the commits on update (they do not compile one-by-one, and I made them to simplify the review).

Copy link
Member

@sanket1729 sanket1729 left a comment

Choose a reason for hiding this comment

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

I would like these to be squashed eventually.

If possible, you can add atomic patches here. But later open another PR with a single commit.

@@ -327,7 +327,7 @@ impl<Pk: MiniscriptKey> Policy<Pk> {
/// combination of timelocks and heightlocks
pub fn is_valid(&self) -> Result<(), PolicyError> {
self.check_timelocks()?;
self.check_duplicate_keys()?;
// self.check_duplicate_keys()?;
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there any specific reason for this requirement to be removed?
This mainly concerns some algorithms the Tapscript Compiler #291 and #342 which might require changes.

@dr-orlovsky dr-orlovsky mentioned this pull request Apr 20, 2022
@dr-orlovsky
Copy link
Contributor Author

Closing due to #359

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.

Update to bitcoin 0.28 release
3 participants