This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Denominations | |
---|---|
Code | AVAX |
Development | |
Original author(s) | Emin Gün Sirer, Kevin Sekniqi, Maofan “Ted” Yin |
White paper | https://www.avalabs.org/whitepapers |
Initial release | 23 September 2020 |
Code repository | https://github.com/ava-labs/ |
Development status | Active |
Written in | Go, TypeScript, JavaScript, Python, Vue |
Developer(s) | Ava Labs |
Source model | Open source |
Ledger | |
Block explorer | https://explorer.avax.network/ |
Website | |
Website | https://avax.network/ |
Avalanche is a decentralized, open-source proof-of-stake blockchain with smart contract functionality. AVAX is the native cryptocurrency of the platform.
Avalanche was conceptualized as a consensus protocol that operates efficiently in a network of unreliable machines, addressing both crash-faults and Byzantine faults.[1] The foundations of Avalanche were first shared in May 2018 through the InterPlanetary File System (IPFS) by a pseudonymous group known as "Team Rocket".[2]
Avalanche was later developed by researchers from Cornell University, led by Emin Gün Sirer and doctoral students Maofan "Ted" Yin and Kevin Sekniqi.[3] After the initial release phase, they founded a startup technology company to develop a blockchain network that would meet finance industry requirements.[4][5][3] In March, 2020, the AVA codebase, part of the Developer Accelerator Program or AVA DAP) for the Avalanche consensus protocol, was released as open-source and made publicly available.[6]
In September 2021, the Ava labs foundation secured a $230 million from a consortium including Polychain Capital and Three Arrows Capital through the purchase of the AVAX cryptocurrency.[7]
In November 2021, following an agreement with Deloitte to improve U.S. disaster-relief funding, the Avalanche blockchain entered the top 10 cryptocurrencies by market capitalization.[8]
In August 2022, the whistleblower group "Crypto Leaks" published a report alleging that Ava Labs had entered secret agreements with the Roche Freedmen law firm with the intent to legally undermine Avalanche's competitors. Emin Gün Sirer, the CEO of Ava Labs, denied any involvement in illegal or unethical dealings with Roche Freedmen law firm.[9]
In January 2023, a partnership was announced between Avalanche and Amazon Web Services (AWS) to improve Avalanche's infrastructure and decentralized application ecosystem.[10] Arkham Intelligence also announced a partnership with Avalanche, allowing Arkham users to analyze the activities of wallets and entities within the Avalanche ecosystem.
In September, 2020, the company issued on X-Chain its native token Avax.[11][12]
The protocol has four basic interrelated mechanisms that compose structural support of the consensus tool. These four mechanisms are Slush, Snowflake, Snowball, and Avalanche. By using randomized sampling and metastability to ascertain and persist transactions, it represents a new protocol family. Although the original paper focused on a single protocol, namely Avalanche, it implicitly introduced a broad spectrum of voting-based, or quorum-based consensus protocols, called the Snow family.[2] While Avalanche is a single instantiation, the Snow family seems to be able to generalize all quorum-based voting protocols for replica control. Unlike prior quorum-based work, the Snow family enables arbitrarily parametrizable failure probability at the quorum intersection level. Standard quorum-based protocols define this failure probability to be precisely zero, but by introducing errors in the quorum intersection, a larger set of consensus protocol designs is available.[13]
Consensus protocols are the basis for the state machine replication problem, which aims to enable a set of machines to achieve agreement over a network even when a subset of the machines are corrupted. There are two major families of consensus protocols to date - classical consensus and Nakamoto consensus protocols.[14] The first achieves consensus through quorums, thus requiring voting. Famous instantiations of this are Paxos (in the crash-fault-tolerant environment) and PBFT[15] in the Byzantine-fault tolerant case. These protocols achieve agreement in a similar operation to a parliament: a proposal (transaction) is proposed and voted on to be accepted or rejected. If sufficient votes cast by the various replicas are accumulated (typically collected through elected leader replica), then a quorum is achieved, and thus agreement.
The second family, pioneered by Satoshi Nakamoto and Bitcoin is that of the Nakamoto consensus. Unlike quorum-based protocols, machines operating an instance of Nakamoto consensus achieve agreement on transactions by downloading the longest chain (typically called a fork). In Bitcoin, the longest chain is verified by ensuring that it is the one with the highest degree of work (or proof of work). Snow, while quorum-based, seems to be a universal generalization of all quorum-based protocols. Unlike prior work which requires that quorums be deterministic, i.e. the failure probability is precisely zero, Avalanche loosens this requirement, thus enabling quorum-based protocols to estimate global network state with errors.[13]
While the Snow family can be theoretically generalized to all classes of assumptions that quorum-based protocols have previously made, the formalization paper analyzes Avalanche under an asynchronous network in the Byzantine setting.[16][15][17] The assumptions are as follows:
Processors
Network
The Avalanche consensus algorithm is a unique approach to achieving consensus in various blockchain networks. It utilizes a randomized voting system to quickly confirm transactions, achieve high throughput, and reduce the risk of splits. This approach also allows for the creation of subnets, which can operate independently with their own validators and parameters.[18]
The consensus mechanism also involves a set of sub-protocols, including Avalanche-X, Avalanche-C, and Avalanche-P.[18]
The Snow family generalizes the typical definitions of safety and liveness encountered in quorum-based protocols. For Avalanche specifically, these properties are:
Avalanche, like other asynchronous networks, is not guaranteed to terminate and thus does not have the liveness property, during asynchrony. Like Paxos, Avalanche's goal is to ensure fault tolerance and it guarantees safety under asynchrony, but not liveness. This is in contrast to Nakamoto consensus, which guarantees liveness, and not safety under asynchrony.[15]