> For the complete documentation index, see [llms.txt](https://docs.lazai.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lazai.network/lazai-workflow-and-runtime/e2e-process.md).

# E2E Process

LazAI, we can divide workflows into data setup process, data usage process, and inference process according to different roles, corresponding to users who want to contribute data to obtain tokens and exchange tokens for data or models.

### Data Setup Process

<figure><img src="/files/hh6R5MSfWWKyvZxhSsLQ" alt="" width="563"><figcaption></figcaption></figure>

### Data Usage & Inference Process

<figure><img src="/files/WqkopAnsqx7GVBmcyLtN" alt="" width="563"><figcaption></figcaption></figure>

LazChain nodes not only consist of regular execution nodes and validation nodes, but also provide AI nodes (AI Execution Extension) for routine AI task execution such as model pulling and deployment, data processing, on-chain inference, and other processes.

Users provide POV and send the data to the blockchain in the form of transactions. POV is usually stored in the form of tensors and can be transmitted and stored in blocks when necessary. Users can submit publicly available tensor data or ZK proof of data to the blockchain, and provide the required model ID for subsequent inference tasks. Meanwhile, LazAI provides the Alith framework to assist users in data processing, format conversion, compression and interaction with LazChain.

When LazChain receives a POV, it will execute the corresponding contract code to request the DAO contract to perform data fingerprint verification. After verification is passed, the DAO contract can pull remote or local models to establish inference services in the AI node. The basic capabilities required for the inference services and the coprocessor acceleration are provided through AI precompile contracts.

After the user submits the POV data, they can send a data or inference request to LazChain to obtain data verification. After the data verification is completed, the data contribution is recorded and the corresponding DAT token is obtained. In addition, the LazAI network settles based on data and computing resource usage and includes a dynamic strategy for fees based on community and market conditions. For details, please refer to the settlement section.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.lazai.network/lazai-workflow-and-runtime/e2e-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.