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

BIP 372: Pay-to-contract tweak fields for PSBT #1293

Merged
merged 8 commits into from
Sep 29, 2022
Merged

Conversation

dr-orlovsky
Copy link
Contributor

A proposal was originally discussed in #1239 and than on a mailing list https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019761.html

@dr-orlovsky
Copy link
Contributor Author

Asking @achow101 to review

@dr-orlovsky
Copy link
Contributor Author

Kindly pining @achow101 to review. This is a stuff we briefly discussed with @apoelstra, basing also on his ideas, so his review is also highly appreciated.

@bitcoin bitcoin deleted a comment Apr 21, 2022
@apoelstra
Copy link
Contributor

concept ACK. I like this approach, it's narrow but general and clean. It could be used for hypothetical broken P2C schemes but I'm not too worried about that.

Thank you for the authorship but AFAIR this approach is not mine.

@luke-jr luke-jr added the New BIP label May 5, 2022
@luke-jr
Copy link
Member

luke-jr commented May 5, 2022

Assigned BIP number 372

@luke-jr luke-jr changed the title BIP P2C proposal BIP 372: Pay-to-contract tweak fields for PSBT May 5, 2022
@achow101
Copy link
Member

Seems fine to me. I'm not particularly familiar with p2c constructions, so can't really pass further judgement on this topic.

@dr-orlovsky
Copy link
Contributor Author

@luke-jr whom do you think we need to review this PR before getting it merged?

@kallewoof
Copy link
Contributor

@luke-jr whom do you think we need to review this PR before getting it merged?

The BIP was assigned number 372, so for starters edit the BIP to replace the "?" placeholders as appropriate. Also make sure to address the travis issues, if any.

dr-orlovsky and others added 5 commits August 21, 2022 21:43
Signed-off-by: Dr. Maxim Orlovsky <orlovsky@pandoraprime.ch>
Signed-off-by: Dr. Maxim Orlovsky <orlovsky@pandoraprime.ch>
Signed-off-by: Dr. Maxim Orlovsky <orlovsky@pandoraprime.ch>
Signed-off-by: Dr. Maxim Orlovsky <orlovsky@pandoraprime.ch>
Signed-off-by: Dr. Maxim Orlovsky <orlovsky@pandoraprime.ch>
@dr-orlovsky
Copy link
Contributor Author

@kallewoof did as you asked for.

First, I have re-based on the current master since the master I was based before contained a CI failure, which was fixed in 66aed73

I also had to fix the CI script in 2f57890 since my e-mail contains dashes, which were not allowed by CI before.

Finally I also created an entry in the README since it was required by the CI.

@kallewoof
Copy link
Contributor

Please don't use @{username} in commit descriptions. It results in a lot of spammy notifications sent to that user. (Github should really do something about that.)

@dr-orlovsky
Copy link
Contributor Author

@kallewoof ok, sorry, I didn't know

@kallewoof
Copy link
Contributor

No biggie. Github's at fault here. But yeah, do avoid in the future :)

@dr-orlovsky
Copy link
Contributor Author

@kallewoof any requirements what to do next with this PR in order to get the new BIP merged into the master?

@michaelfolkson
Copy link
Contributor

Thank you for the authorship but AFAIR this approach is not mine.

Apologies if I'm misunderstanding the context here but would you prefer to be listed in the acknowledgements rather than as a BIP co-author @apoelstra? Being listed as a co-author does seem to confer more perceived responsibility over the BIP than just being listed in the acknowledgements.

@apoelstra
Copy link
Contributor

@michaelfolkson yes, I would prefer to be listed in the acknowledgements rather than as a co-author. This is not my BIP to maintain :)

dr-orlovsky added a commit to BP-WG/bips that referenced this pull request Sep 11, 2022
@dr-orlovsky
Copy link
Contributor Author

@michaelfolkson @apoelstra fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants