btc1 / bitcoin

btc1 project bitcoin implementation
MIT License
329 stars 55 forks source link

Disabling ASICBOOST #8

Closed jgarzik closed 7 years ago

jgarzik commented 7 years ago

A patented mining chip hardware feature "ASICBOOST" has been the subject of debate and controversy in the community.

This issue is raised for the WG to consider testing protocol/software changes that ban/disable/render ineffective this hardware optimization.

Quoting [with permission] one chip maker, Jihan Wu of Bitmain: "Asicboost is being repetitively mentioned in the reddit. Btc1 can take a very clear stance to help to ban it if community emotion desire it"

Suggested next steps for this issue:

--

Status: Unscoped. Process Note: This is outside the scope of the SegWit2x charter; post-Milestone1 material. This means that the SegWit2X WG, as a matter of policy, will (1) 1st pursue the originally stated goal and milestones, and then (2) 2nd consider other issues that might require additional rounds of agreement among the 70+ working group members.

jli225 commented 7 years ago

@mk229797 The principle of SegWit2X is based on the expectation that most participants come together for the long-term greater goodness of Bitcoin. I am pretty sure miners will keep their promise like they did in the past. BTW I never believed ASIcBoost was anything but propaganda and there were many technical analysis that has debunked this lie. So, if miners vote to agree on disabling ASICBoost, will you admit it's your fault to defame miners by spreading this lie?

ghost commented 7 years ago

@jli225 first at all do not twist my words, second - i'm not miner - but if miners use some technology and lets say believe that it gives them better profit obviously they will not cut the branch on which there are sitting without view for extra profit later - and no, I will not apologize if somebody changes their mind about anything - does not matter rationale or lack of it behind somebody's decision

jgarzik commented 7 years ago

OP explicitly quotes one miner (and supposed patent holder) who is ok with code changes that disable covert or overt ASICBOOST.

Closing this issue. No technique has been raised in this thread, beyond that which is intrinsically provided by SegWit itself, which is readily deployable to move the needle further in the direction of disabling ASICBOOST.

Status: Unresolved. Can re-open if a concrete technique is proposed.