Review AVA Platform

What is AVA?

Developers working with AVA can easily create powerful, reliable and secure applications, as well as customizable blockchain networks with complex sets of rules, or run them based on existing private and public subnets.

Discussion of the Avalanche platform begins with the core component which powers the platform: the consensus engine. Background Distributed payments and — more generally — computation, require agreement between a set of machines. Therefore, consensus protocols, which enable a group of nodes to achieve agreement, lie at the heart of blockchains, as well as almost every deployed large-scale industrial distributed system. The topic has received extensive scrutiny for almost five decades, and that effort, to date, has yielded just two families of protocols: classical consensus protocols, which rely on all-to-all communication, and Nakamoto consensus, which relies on proof-of-work mining coupled with the longest-chain-rule.

While classical consensus protocols can have low latency and high throughput, they do not scale to large numbers of participants, nor are they robust in the presence of membership changes, which has relegated them mostly to permissioned, mostly static deployments. Nakamoto consensus protocols, on the other hand, are robust, but suffer from high confirmation latencies, low throughput, and require constant energy expenditure for their security.

Mechanism and Properties The Snow protocols operate by repeated sampling of the network. Each node polls a small, constant-sized, randomly chosen set of neighbors, and switches its proposal if a supermajority supports a different value. Samples are repeated until convergence is reached, which happens rapidly in normal operations. We elucidate the mechanism of operation via a concrete example. First, a transaction is created by a user and sent to a validating node, which is a node participating in the consensus procedure. It is then propagated out to other nodes in the network via gossiping. What happens if that user also issues a conflicting 4 Kevin Sekniqi, Daniel Laine, Stephen Buttolph, and Emin G¨un Sirer transaction, that is, a doublespend?

To choose amongst the conflicting transactions and prevent the doublespend, every node randomly selects a small subset of nodes and queries which of the conflicting transactions the queried nodes think is the valid one. If the querying node receives a supermajority response in favor of one transaction, then the node changes its own response to that transaction. Every node in the network repeats this procedure until the entire network comes to consensus on one of the conflicting transactions.

▶️ Website: https://ru.avalabs.org
▶️ Whitepaper: https://ru.avalabs.org/whitepapers
▶️ Twitter: https://twitter.com/avalabsofficial
▶️ Reddit: https://www.reddit.com/r/ava
▶️ Telegram: https://t.me/avacoin_official
▶️ Facebook: https://www.facebook.com/AvaLabsOfficial