Avail is a Web3 infrastructure layer that allows modular execution layers to scale and interoperate in a trust minimized way. Below, you can find a list of some of the relevant GitHub repositories.
| Name (with link) | Description |
|---|---|
| Reference Document | Document containing the overall rationale, design decisions and theoretical backgrounds |
| Avail Node | Avail node implementation repo. Built using Substrate. |
| Light Client | Light client designed to check data availability proofs on Avail. |
| Explorer | Avail explorer implementation repo. Built using Polkadot apps. |
| Bridge UI | Repository for the official Avail <-> ETH bridge UI |
| Documentation | Avail documentation hub. |
| Tests | End to end tests for Avail. |
Suggestions and feedback welcome.
There are two main components in the Avail network:
- Avail Node: This forms the blockchain layer of Avail. It is built using Substrate, with modifications to specialize it for data availability. Apart from basic blockchain operations like balance transfer, validator staking, slashing and governance, it also contains methods for applications to submit data blobs. This network is secured by the GRANDPA+BABE consensus engine, under the assumption that at least 2/3 of the validator set is honest.
- Avail Light Client: The light clients (LC) form an overlay P2P network. Individually, all LCs subscribe to (finalized) headers of the chain. It performs Data Availability Sampling (DAS) to gain high confidence of DA. The LCs also host the sampled data on the P2P so that together the P2P network can have the entire data in a highly available manner.
The Avail team has partnered with Succinct labs to develop a trust-minimized bridge between Avail DA and Ethereum. VectorX enables efficient and trust-minimized bridging of arbitrary messages between Avail DA and Ethereum, which enables use cases like token bridging. You can use the bridge through the official UI.