Transaction malleability

aka5

Active Member
Foundation Member
Mar 22, 2015
17
5
103
Our favorite troll just told us that we don't have SEGWIT and for that our transactions are malleable.

From what i know thats wrong, and transactions malleability is fixed long time ago in DASH, isn't it?

The problem in bitcoin is it needs a hardfork to fix it, we had many hardforks and we fixed it in the early days, at least thats what i remember, we just didn't called that fix SEGWIT because it was long before that SEGWIT idea.

Someone has more info? Am i wrong with that?

Thanks
 

ldw

New Member
Jun 23, 2016
27
4
3
Also curious about this... Since so much of the code is shared with Bitcoin, and I don't find any source confirming Dash ever fixed it, I'd guess it's not fixed in Dash...
 

chaeplin

Active Member
Mar 29, 2014
749
356
133
https://www.dash.org/forum/threads/noob-questions.8974/#post-94378
[*]halsoActive Member
Hi,

I have a couple of beginner type questions:

1. When i back up my wallet on a mac. The format of the .dat file is VLC. Is that all good, or should i be saving in a different format?

2. Does Dash also suffer from transaction malleability?

Thanks in advance.



[*]UdjinM6Official Dash Dev
Core DeveloperModerator
Hello there,

1. Yes, it's fine. VLC thinks it's his files because of the .dat extension but internally they are completely different.
2. Bitcoin addresses malleability (more or less) in https://github.com/bitcoin/bitcoin/commit/1cea6b0. Dash 12.0 has no such fix yet but will have the same fix in 12.1.

XsV4GHVKGTjQFvwB7c6mYsGV3Mxf7iser6
12.1 has https://github.com/dashpay/dash/blob/master/src/policy/policy.h#L42-L44
 
Last edited:
  • Like
Reactions: tungfa

NewLiberty

New Member
Feb 22, 2017
1
0
1
56
Our favorite troll just told us that we don't have SEGWIT and for that our transactions are malleable.

From what i know thats wrong, and transactions malleability is fixed long time ago in DASH, isn't it?

The problem in bitcoin is it needs a hardfork to fix it, we had many hardforks and we fixed it in the early days, at least thats what i remember, we just didn't called that fix SEGWIT because it was long before that SEGWIT idea.

Someone has more info? Am i wrong with that?

Thanks
Malleability is a feature not a bug.

For example, it could be used to answer the criticism about "Lazy Masternodes".
If the test for masternodes were based on the ability to malleate a transaction then it would have to be running the full stack rather than just responding to IPNG or more simple tests.
Malleability doesn't cause problems to those that understand it, it got a bad rap from MtGox when it was blamed for MtGox's bad code, but the failure was MtGox, not the protocol.
 

juliomoros

New Member
Feb 8, 2016
33
14
8
Every crypto-currency forked from the bitcoin's transaction architecture which has not implemented segregated witness is exposed to the risk of a malleability attack. (So, NO, Dash hasn't solve the problem on malleability attack)

This is the risk that prevent cryptos to do the most needed and ordinary tradings in a decentralized fashion, by smart contracts.

In few words: as a digital signature can not "sign" itself in dash's transaction structure, the signature field in a crypto transaction can be changed without changing the transaction, threatening the operability of certain smart contracts.

This can be a problem in many, but not all smart contracts. However it seems to be the case in this problem, which IMHO is very relevant to dash community.