-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Conversation
Asking @achow101 to review |
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. |
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. |
Assigned BIP number 372 |
Seems fine to me. I'm not particularly familiar with p2c constructions, so can't really pass further judgement on this topic. |
@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. |
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>
@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. |
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.) |
@kallewoof ok, sorry, I didn't know |
No biggie. Github's at fault here. But yeah, do avoid in the future :) |
@kallewoof any requirements what to do next with this PR in order to get the new BIP merged into the master? |
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. |
@michaelfolkson yes, I would prefer to be listed in the acknowledgements rather than as a co-author. This is not my BIP to maintain :) |
@michaelfolkson @apoelstra fixed |
b3dfb4b
to
d7888e5
Compare
A proposal was originally discussed in #1239 and than on a mailing list https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019761.html