Bitcoin Forum
May 10, 2024, 06:59:15 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Have Transaction Malleability been solved with segwit?  (Read 347 times)
Colorblind (OP)
Member
**
Offline Offline

Activity: 392
Merit: 41

This text is irrelevant


View Profile
November 01, 2017, 08:27:50 PM
 #1

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!

1715324355
Hero Member
*
Offline Offline

Posts: 1715324355

View Profile Personal Message (Offline)

Ignore
1715324355
Reply with quote  #2

1715324355
Report to moderator
Activity + Trust + Earned Merit == The Most Recognized Users on Bitcointalk
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715324355
Hero Member
*
Offline Offline

Posts: 1715324355

View Profile Personal Message (Offline)

Ignore
1715324355
Reply with quote  #2

1715324355
Report to moderator
1715324355
Hero Member
*
Offline Offline

Posts: 1715324355

View Profile Personal Message (Offline)

Ignore
1715324355
Reply with quote  #2

1715324355
Report to moderator
1715324355
Hero Member
*
Offline Offline

Posts: 1715324355

View Profile Personal Message (Offline)

Ignore
1715324355
Reply with quote  #2

1715324355
Report to moderator
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
November 02, 2017, 12:42:59 AM
Merited by ABCbits (1)
 #2

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.
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.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!