-
Notifications
You must be signed in to change notification settings - Fork 495
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
Partially signed transactions should use OP_0 as placeholder #74
Comments
I agree that there should be a standard placeholder, but my gut feeling has been to put a 0000...0 signature the same length of a standard signature. This way, a partially signed transaction is exactly the same length as the final transaction, which makes it a bit easier to calculate the required transaction fees. I think this is better than OP_0 even though it doesn't match the defacto "standard" that others have adopted. What do you think? |
Well, you have an excellent point about fees. By the way, right now, the signature is not all zeros. Anyway, if you want to try to champion another standard, I support that. I agree, OP_0 is not exactly the best placeholder. However, if the majority of users settle on OP_0, that is what you should go with. |
I had this same issue trying the cryptocorp api and had to monkey patch pycoin to make it work |
Sebastian, can I take a look at your patch? |
If using 0.53 from GitHub, then the following code works well: |
We endup fixing the input and redeem script
|
As of d09b5e0, you should be able to pass in |
I believe many multisig wallets (CoinVaut, BitGo) use the convention that OP_0 is used as a placeholder for missing signatures. I am not sure if it is a standard, but it does appear to be used in many places. Can ScriptMultisig._dummy_signature please be changed to return "\x00" instead? Thanks.
The text was updated successfully, but these errors were encountered: