[ad_1]
The proposed prohibition for ASIC miners on the Ethereum network (ETH) seems to generate controversy in the market. The mining company Linzhi, based in Shenzhen, has issued a statement rejecting the proposal to block specialized mining hardware for the ETH network.
The new implementation aims to introduce ProgPoW. This would optimize mining activities and allow GPU hardware to work better. In the statement issued by Linzhi, the company said it was "shocked" by the proposal made by the developers of ETH.
On the question, the company wrote:
"We reject the arbitrary application of the rules and demand that clear and equal guidelines be established for all hardware manufacturers.Today we ask the developers of ethereum to publish rules and requirements for what constitutes a good producer of the ProgPoW ASIC."
Wolfgang Spraul, director of operations at Linzhi, commented that these rules could include more transparency or monthly checks on hardware companies. Already on Friday, ETH discussed the problem and shared their views on the ProgPoW proposal.
Linzhi is currently working on a new chip for the Ethereum mining algorithm that should improve the performance of other ASIC projects for Ethereum. The company has spent $ 4 million on its production. Spraul has also confirmed that they will study the feasibility and will start building the ProgepoW ASIC miners for Ethereum.
With a ProgPoW mining algorithm, GPU hardware would become competitive with ASIC hardware.
Linzhi has recently been targeted by the Ethereum Classic (ETC) community as being behind the 51% attack on its network. Linzhi and Spraul denied all charges saying they would never try the ASIC miners on a main network.
Ethereum is also trying to move from a Proof-of-Work (PoW) consent algorithm to a Proo-of-Stake (PoS). On January 16, Ethereum is expected to perform a network update called Constantinople that will reduce mining premiums from 2 ETH to 3ETH. This would allow miners to prepare for a transition to a full OP. Other opcodes will also be included in the next hard fork.
[ad_2]
Source link