BIP126: Grammar fix and review#4
BIP126: Grammar fix and review#4kristovatlas merged 2 commits intoOpenBitcoinPrivacyProject:masterfrom dcousens:patch-1
Conversation
Does this BIP also apply to non-addressable output scripts?
It seems so, might be worth making that consistent? |
Is this the total desired spend? If so, what is the value of the "desired" spend in step 2? |
By this do you mean a change in the procedure? Or do you mean the method by which the inputs are chosen must be non-deterministic for some portion of transactions created? |
|
@kristovatlas I hope you don't mind me reviewing this here, it seemed the most coherent place. But I'd be happy to take this to email or a GitHub issue if you'd prefer. |
I don't understand what you mean by either of these questions. Can you give a specific example of what you're talking about?
Yes, this does need to be clarified. If there is only one party forming the transaction, then then "spend output" and "change output" in step 3 are actually additional change outputs. In this step, "spend output" really means an output of a specified value. It's explained more precisely in the Rules section. If more than party is forming the transaction, then each party gets one output of the designated size, and (probably) one change output.
Mostly the procedure is written from the perspective of a normal wallet which is encountering unavoidable HITs as part of its normal operation. Those wallets will sometimes be capable of forming standard form transactions, and sometimes need to create alternate form transactions, and sometimes won't be able to follow this procedure at all. Clients that allow multiple parties to form HITs will usually be able to create any form they want, and only rarely be constrained. If intentional HITs always use standard form, then that means it's possible to find alternate form HITs on the blockchain and assume they are probably unintentional. To prevent this, clients that form intentional HITs should sometimes choose to make alternate form transactions even if they could have created a standard form transaction. |
|
ACK f51a8e1 |
|
ACK 05e96d2 |
|
@dcousens thanks for the review. are you still doing additional review, or is this ready to be merged? |
|
Also, this is a perfectly good place to post your feedback, I think -- thanks |
|
I've ACK'd these commits, please submit a new PR for additional changes. |
|
Thanks @kristovatlas, sorry I've been hammered at work this week. |
ping @justusranvier, I only just saw #3, so I've partially started review here. I can move the comments there if needed.