Emergency Deployment of SegWit as a partial mitigation of CVE-2017-9230 [combined summary]



Individual post summaries: Click here to read the original discussion on the bitcoin-dev mailing list

Published on: 2017-05-31T06:17:59+00:00


Summary:

The discussion on the bitcoin-dev mailing list revolves around the impact of the ASICBOOST patent on Bitcoin mining. It is debated whether blocking ASICBoost would decrease everyone's hashrate by the same amount, and if an ASIC patent would have the same formulation as an ASICBoost patent. The conversation concludes that an unblockable mining patent advantage may arise in the future. The possibility of a state licensing regime for miners is also discussed, with concerns raised about license fees and unequal access to optional technology. The defense against a patent is to ignore it and focus on risk-sharing and decentralization. However, it is acknowledged that Bitcoin cannot prevent state patent/licensing/tax regimes and needs to find solutions to cope with them.In another email exchange, the impact of patents on Bitcoin mining is discussed. It is suggested that 67% of miners are using ASICBOOST instead of signaling for SegWit due to a patent owned by former Bitcoin Core developer Sergio Lerner. The feasibility of blocking ASICBOOST is analyzed, and concerns are raised about the potential monopoly and lack of decentralization in Bitcoin mining. There are also discussions about the Bit4 MASF proposal for increasing the block size limit, skepticism about its feasibility, and concerns about miners not signaling for SegWit.Cameron Garnham claims that ASICBOOST is the primary reason for the refusal of 67% of miners to signal for SegWit. Tom Zander questions this assumption and suggests that miners are open to disabling ASICBOOST. The use of SegWit as a partial-mitigation for the security vulnerability ASICBOOST is proposed, along with alternative solutions. The trade-offs of deploying a quick partial-mitigation versus a slower but more conservative approach are debated.A severe security vulnerability called ASICBOOST (CVE-2017-9230) is actively being exploited in the Bitcoin network. It is proposed to use SegWit as a partial-mitigation of ASICBOOST, and there is intense debate over the security trade-offs of deploying a quick partial-mitigation versus a slower approach. Gregory Maxwell proposes an alternative solution to defuse covert ASICBOOST with a segwit-like commitment to the coinbase. The politicization of ASICBOOST is criticized for potentially damaging Bitcoin development and security.The active exploitation of the security vulnerability ASICBOOST (CVE-2017-9230) in the Bitcoin network is discussed. SegWit is proposed as a partial-mitigation for ASICBOOST, and there are debates over the security trade-offs of deploying a quick partial-mitigation versus a slower approach. An alternative proposal by Gregory Maxwell to defuse covert ASICBOOST with a segwit-like commitment to the coinbase is also considered. Concerns are raised about politicizing the issue and potential damage to Bitcoin development and security.Overall, the discussions revolve around the impact of the ASICBOOST patent on Bitcoin mining, the feasibility of blocking ASICBOOST, the use of SegWit as a partial-mitigation, the skepticism towards the Bit4 MASF proposal, and concerns about miners not signaling for SegWit. There is intense debate over the security trade-offs and the need to find solutions to cope with patent/licensing/tax regimes. The context also highlights the severity of the security vulnerability ASICBOOST and the potential risks it poses to Bitcoin.


Updated on: 2023-08-01T20:47:32.222970+00:00