0.17.2rc issue (standardness change for bare multisig) #14104

1. 
   preminem commented at 8:39 am on August 30, 2018: none

   IN 0.16.2 some output type is multisig.But in 0.17.2rc this is nonstardard. Anyone know why？
2. 
   preminem commented at 8:41 am on August 30, 2018: none

   e.g. txid : fc200f9cef8faf8f76756b5d02081061a1fd22ec1d580f778c12373e12a56016
3. 
   jonasschnelli commented at 9:08 am on August 30, 2018: contributor

   0.16 did allow invalid pubkey as long as they had the right size.

   0.17 is more strict about this.

   Your tx listed above uses invalid pubkeys (a pubkey starting with 0x20 is invalid) which are now non-standard.

   This is caused by #13194

4. 
   preminem commented at 10:21 am on August 30, 2018: none

   Thinks
5. jonasschnelli renamed this:
   0.17.2rc issue
   0.17.2rc issue (standardness change for bare multisig)
   on Aug 30, 2018
6. jonasschnelli added the label TX fees and policy on Aug 30, 2018
7. laanwj added this to the milestone 0.17.0 on Aug 30, 2018
8. 
   mmortal03 commented at 1:48 pm on October 8, 2018: none

   Was this fixed by 0.17.0?
9. 
   MarcoFalke commented at 6:42 am on October 9, 2018: member

   I doubt it, it should have been added to the release notes.
10. 
    fanquake commented at 11:20 pm on October 14, 2018: member

    0.17.0 is out, so I’ve pushed this to the 0.17.1 milestone.
11. fanquake removed this from the milestone 0.17.0 on Oct 14, 2018
12. fanquake added this to the milestone 0.17.1 on Oct 14, 2018
13. 
    MarcoFalke commented at 8:11 pm on November 28, 2018: member

    Unfortunately we can’t change the release notes after the fact
14. MarcoFalke closed this on Nov 28, 2018

    ---

15. DrahtBot locked this on Sep 8, 2021

Contributors
preminem jonasschnelli mmortal03 MarcoFalke fanquake

Labels
TX fees and policy

Milestone
0.17.1