Grin Is Hard Forking Every Six Months to Keep ASICs Off the Network
The Grin community is trying to eliminate ASICs for the next two years.
Best known for its refactoring tool, MimbleWimble implementation, Grin's developers have improved both the privacy and scalability of the block chain. Recently, Grin's developers have released a technology roadmap to help prevent the use of powerful mining hardware on the network.
This plan involves changing the cryptocurrency's proof-of-work algorithm every six months, which means system-wide upgrades or hard forks each time.
Because a robust ASIC can only focus on one algorithm, changing the algorithm consistently can quickly make the ASICs generated for one algorithm outdated. In other words, hard forks have shown to be controversial about the various password communities. The result of community splitting was block-chain splitting.
According to Grin's anonymous senior developer Igno Peverell:
"What we're concerned about is the potential preemption that we can get from our early days and ASIC makers when we do equipment preparation on the first day, which will lead to an extremely centralized mining market."
Peverell's concerns are repeated by many people in the cryptocurrency community these days.
Critics regard ASIC as centralized. Not only is expensive technology generally leaping over individual GPU miners, but network groups can be made into a few mining pools, and now, only one company, Bitmain, has nearly all cryptocurrency mining ASICs.
While the cryptocurrency project is attempting to completely eliminate hardware, other communities are confronted with Chinese mining enthusiasts in hopes of racing competition. Grin, on the other hand, is only interested in limiting its use in the network in the short term.
Peverell said, "I think everyone can easily understand, and it may not be true a year ago, but the ASIC has essentially won."
Still, Peverell thinks it can resume the cryptocurrency project by allowing ASIC to take control of the mining market shortly after Grin's release (expected until the end of the year).
So he hopes that he and other Grin developers will have time every time there is a competitive ASIC market.
One by one hard fork
Part of the crypto space is doubtful about upgrading the cryptocurrency consensus algorithm every six months, but Grin developers think the network can handle it.
That's because Grin is already planning a hard fork and planning on the timeline for the first few years anyway to introduce new features into the block chain. It would not be so unnecessary to add consensus to the agreement in that way.
In other words, the developer thinks that creating a hard fork is a perpetual part of the block chain.
"We do not want to keep Grin on a regular basis for governance and policy reasons," Peverell said. "We believe that regular rigid forks will bring too much centralization pressure."
The pressure of centralization he refers to is related to the user, so it must be accompanied by support from the lead developers and the biggest players to prevent them from splitting the block chain.
The Grin developer team decided to restrict these hard forks. At the end of these two years, I ultimately want to permanently switch to the Cuckoo Cycle work proof algorithm, which is unique in that I have to machine the machine to use more memory than any other work proof algorithm.
At this point, they expect ASICs to grow better, but expect more ASIC groups built by many companies that believe they will lead to a healthy Grin ecosystem.
"[That’s] We decided to limit the Cuckoo Cycle ASIC to a reasonable period of maturity and multiple players, but it did not take long enough for the regular hard fork to become a problem," Peverell told CoinDesk .
There have been some controversies about the idea for the Grin forum, but the most active community member of cryptocurrency, "Technology", agrees that a two-year plan is the best option.
"There are still a few parameters that we need to fix before we make a decision, and we will be voting and staying at the meeting that the project developer will implement," says Peverell.
Despite all these deliberate plans, there are other concerns that "secret ASICs" can interfere with.
Siicoin's lead developer, David Vorick, told Grin developers that ASIC manufacturers are worried about changing algorithms with painless software updates to keep their networks running with changing algorithms.
Borik said that ASIC stands at the center of a drama similar to the mining of ciao exposures, while investors and future miners are looking for ASICs for Grin as part of an effort to secure a competitive advantage before the block- I was looking into making.
"It was very difficult to hear because I could not stress how serious the secret ASIC could harm coins and their mining community," Peverell said.
He added that the Grin developer team had modified the encryption algorithm based on Vorick's suggestion.
Catheryne Nicholson, CEO and co-founder of BlockCypher, e-mailed to all developers who repeat the MimbleWimble idea that Vorick believes is right. Investors actually want to make an ASIC for Grin.
It is something that Nicholson is not happy with.
"Personally, I find it disgusting," she wrote.
"We do not provide funding directly to the open source development business, but we seek to destroy the ecosystem before we have opportunities for development, and we serve ourselves free from the backdrop of those who have done it all."
Because of this, BlockCypher provides resources for Grin developers through Grinmint, a new mining pool.
Obviously I was a bit creepy about the situation. Nicholson concluded his post with the hash tag "DontBeaDick".
Shaver image with Shutterstock
CoinDesk, a leader in block-chain news, is a media outlet that pursues the highest standards of journalism and adheres to strict editorial policies. CoinDesk is an independent operating subsidiary of the Digital Currency Group, which invests in cryptocurrencies and block-chain startups.
(f.fbq) return; n = f.fbq = function () n.callMethod?
n.callMethod.apply (n, arguments): n.queue.push (arguments); if (! f._fbq) f._fbq = n;
n.push = n; n.loaded =! 0; n.version = & # 39; 2.0 & # 39 ;; n.queue = ; t = b.createElement (e); t.async =! 0;
t.src = v; s = b.getElementsByTagName (e) ; s.parentNode.insertBefore (t, s)} (window,
Document, & # 39; script & # 39 ;, & # 39; // connect.facebook.net/en_US/fbevents.js');
fbq (& # 39; init & # 39 ;, & # 39; 472218139648482 & # 39;);
fbq (& # 39; init & # 39 ;, & # 39; 239547076708948 & # 39;);
fbq (& # 39; track & # 39 ;, & # 39; PageView & # 39;);
You must log in to post a comment.