Get rid of inaccurate ScriptSigArgsExpected #7387

1. 
   sipa commented at 12:19 PM on January 21, 2016: member

   ScriptSigArgsExpected was originally introduced to avoid a form of malleability (stuffing scriptSigs with superfluous arguments). This is no longer needed since the SCRIPT_VERIFY_CLEANSTACK and SCRIPT_VERIFY_SIGPUSHONLY cover all its use case more accurately and more efficiently.

2. jonasschnelli added the label TX fees and policy on Jan 21, 2016
3. 
   dcousens commented at 12:44 PM on January 21, 2016: contributor

   utACK 5bfec00

4. Get rid of inaccurate ScriptSigArgsExpected 52b29dca76
5. sipa force-pushed on Jan 21, 2016
6. 
   sipa commented at 12:58 PM on January 21, 2016: member

   @dcousens Some tests were failing, I updated the commit.

7. laanwj added this to the milestone 0.12.0 on Jan 21, 2016
8. 
   laanwj commented at 3:41 PM on January 21, 2016: member

   utACK

9. 
   dcousens commented at 10:58 PM on January 21, 2016: contributor

   re-ACK 52b29dc

10. 
    gmaxwell commented at 11:09 PM on January 21, 2016: contributor

    ACK 52b29dca7670c3f6d2ab918c0fff1d17c4e494ad

    Constructed effectively the same patch on my own.

11. laanwj merged this on Jan 22, 2016
12. laanwj closed this on Jan 22, 2016

    ---

13. laanwj referenced this in commit f4b2ce8ee8 on Jan 22, 2016
14. 
    laanwj commented at 1:35 PM on February 2, 2016: member

    This was cherry-picked into master via 5d74309 (#7453)

15. MarcoFalke locked this on Sep 8, 2021

Milestone
0.12.0