Re: Daily reminder: The covert ASICBOOST scam is not fixed with segwith hardfork
None of the above posts clearly explains whether Asicboost exploit can still be used after the Frankenstein upgrade or not
I am wondering about the exact same thing, it seems weird that Jihad Wu has agreed to the Frankenstein version.
Asicboost is inacceptable so I really would like to know. Saying it is "not an issue" is just not helping.
I am wondering about the exact same thing, it seems weird that Jihad Wu has agreed to the Frankenstein version.
Asicboost is inacceptable so I really would like to know. Saying it is "not an issue" is just not helping.
1. its just more efficient method of mining. just like the GPU mining days of OpenCL vs kuda
2. asicboost is as much of an exploit as going soft is an exploit
3. to simplify it. its all about who should use the spare space of a block header.
A. asics
B. soft fork
4. if a hard consensus is needed then devs dont need the spare space to soft fork, because they are going hard so dont need cludgy code reliant on the spare block header space