|
Title: Have Transaction Malleability been solved with segwit? Post by: Colorblind on November 01, 2017, 08:27:50 PM Hello, I was reading about transaction malleability and wondering if segwit solved it?
As far as my understanding of transactions in block goes, segwit's main purpose was to move signature to the different place in transaction hierarchy (from inputs section to whole new section). That effectively means that transaction ID represented by hash of transaction inputs+outputs+signature can't be tampered with anymore. Do I get it correctly? Thanks! Title: Re: Have Transaction Malleability been solved with segwit? Post by: achow101 on November 02, 2017, 12:42:59 AM Hello, I was reading about transaction malleability and wondering if segwit solved it? Segwit defines new output types which have their signatures moved to a new field called the witness. The witness is not part of the txid so the txid only consists of data that cannot be changed. Only transactions which spend from the segwit output types are non-malleable.As far as my understanding of transactions in block goes, segwit's main purpose was to move signature to the different place in transaction hierarchy (from inputs section to whole new section). That effectively means that transaction ID represented by hash of transaction inputs+outputs+signature can't be tampered with anymore. |