> For the complete documentation index, see [llms.txt](https://docs.zerowave.my.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerowave.my.id/testnet/avail-light-client.md).

# Avail - Light Client

The Avail Light Client (LC) monitors finalized blocks on the network, utilizing Data Availability Sampling (DAS) to ensure data integrity. It connects to Avail nodes via WebSocket, conducting random sampling of block matrices to retrieve data cells. If needed, it uses both DHT and RPC methods for data retrieval, enhancing data availability.

LC functionality is divided into two parts: DAS-focused LC and app client for data reconstruction. LC operates independently, persisting block confidence locally. It synchronizes with nodes on startup and exposes an HTTP API for querying block status, confidence, and application data.

The Avail LC enhances data availability and integrity through random sampling, akin to full nodes, while reducing the load on them. It enables convenient access to application-specific data through its API, ensuring the reliability of data within the Avail network.

### Requirement

#### Minimum Hardware Requirement 

* CPU : 2 core
* Memory : 2 GB
* SSD : 300 GB (recomended)

#### Software Requirement

* Operating System : Ubuntu 22.0+

### Claim Faucet

* Link Faucet : [Here](https://faucet.avail.tools/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zerowave.my.id/testnet/avail-light-client.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.