Avalanche Avalanche protocol is a new generation consensus protocol Reaching consensus between a collection of distributed hosts is at the heart of many services. As of today, two significant families of protocols exist to create a solution for the afro-mentioned problem. Traditional consensus protocols rely on all-to-all communication to ensure that all correct They have been challenging to scale to large numbers of participants. The second family, Nakamoto consensus protocols have become popular with the rise of Bitcoin. These protocols are considerably expensive and insufficient. Avalanche is a new consensus protocol allows for vastly superior scalability and safety.
June 2020 Denali Test Network (Phase 2/2)
July 2020
Vérifié 0%
Attention. Il y a un risque que les membres non vérifiés ne soient pas réellement membres de l'équipe
Vérifié 0%
Attention. Il y a un risque que les membres non vérifiés ne soient pas réellement membres de l'équipe
What I like:
What I dislike:
Overall, I love it. A breakthrough consensus mechanism that finally moves away from the variations of the 30 years old research that is being implemented in current projects is a welcome change to the blockchain space. There are many ICOs that claim to be Ethereum-killers out there, but having some of the best features of all other projects out there baked on top of the most novel consensus mechanism by chef Emin Gün Sirer will surely give Ethereum a run for its money. This is something new and exciting in the blockchain world, that will both push the tech forward and has the chance to make for a great investment.
The information above is put together from a few YouTube videos, interviews and mainly the input in the project’s Telegram channel. This is way too early to rate, but Avalanche is on the top of my list of projects to watch.
Update: Perlin has announced they are working on Wavelet, a pragmatic Avalanche implementation for their distributed computing project. They quoted a number of concerns related to the original Team Rocket whitepaper which they address and implement in a way they feel is different from the Avalanche consensus. I addressedthose concerns in the Avalanche Telegram channel and got the following response from Kevin Sekniqi, who TL;DR said that the team views the concerns expressed in the article as normal issues to be tackled for actual implementation and that you are doing similar work, even if not publicly sharing the progress yet.
Rating: 91/100 (potentially even higher, but let’s wait for a proper whitepaper, code, website, etc)
