Bitcoin Forum
June 08, 2024, 10:57:23 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Malleability - Hard fork impossible?  (Read 1401 times)
Neuerung (OP)
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
February 13, 2014, 04:38:00 PM
Last edit: February 13, 2014, 05:42:47 PM by Neuerung
 #1

Hello,

i have read a while here in this forum, but this is my first post:

Lets assume that the malleability issue is only really solvable with a hard fork (for example timestamps now can´t be used either, because they are malleable too).

Some time ago these hard forks would "only" result in update of the clients and the mining-software, so this could be done (not without pain, but nevertheless).

But nowadays with ASICs, the key component for a transaction, the hashing, is done in hardware, hardwired in silicone.

Therefore should a hard fork be proposed, the majority of the whole mining capacity (now probably 99% ASICs) would decline this proposal. They would loose their whole investment in silicon, because their ASICS can´t be changed.

So a hard fork can never happen, and bitcoin can never evolve, or am i wrong?









 
Denton
Full Member
***
Offline Offline

Activity: 798
Merit: 100



View Profile
February 13, 2014, 04:44:43 PM
 #2

You are wrong, the only change that you can safely say the miners won't accept is changing the proof of work from SHA to something else.

Neuerung (OP)
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
February 13, 2014, 04:57:02 PM
 #3

You are wrong, the only change that you can safely say the miners won't accept is changing the proof of work from SHA to something else.

Thanks Denton for this answer.

But what´s happening if additional Information has to be put into the input of the SHA hashing (like timestamps, Transaction ID´s etc.) so that they are not malleable any more.

Can this be done in software or is the ASIC hardware wired in a way lets say:
Input 2000 Bytes -->Output SHA(2000Bytes), but if you need 500 bytes more for the additional information, the current ASIC hardware is not capable of doing this?

   
Denton
Full Member
***
Offline Offline

Activity: 798
Merit: 100



View Profile
February 13, 2014, 05:20:37 PM
 #4

You are wrong, the only change that you can safely say the miners won't accept is changing the proof of work from SHA to something else.

Can this be done in software or is the ASIC hardware wired in a way lets say:
Input 2000 Bytes -->Output SHA(2000Bytes), but if you need 500 bytes more for the additional information, the current ASIC hardware is not capable of doing this?

My knowledge of ASIC hardware is limited but i would say yes, it is.

Rannasha
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
February 13, 2014, 05:34:09 PM
 #5

ASICs (and other miners) hash the block header, which doesn't contain the actual transactions or tx-ids. Changing the way the tx-id is computed shouldn't affect mining at all.
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!