> 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/dat-specifications-and-flow/dat-interaction-flow.md).

# DAT Interaction Flow

On-Chain & Off-Chain

The following diagram illustrates the full lifecycle of a DAT token, from submission to verification, trading, and AI execution.

1. **iDAO Submits AI Data & Model (LazAI Flow):** Metadata, dataset hashes, and storage locations are submitted to LazAI Flow.
2. **Verification & Token Minting:** The LazChain network validates dataset integrity and mints the DAT token.
3. **AI Dataset/Model Usage:** Users request AI training/inference access, enforced via DAT-based smart contracts.
4. **Fraud-Proof Submission & Dispute Resolution:** Challengers can submit fraud proofs if AI models are biased or invalid.
5. **Revenue Distribution:** AI data/model owners receive royalty-based revenue upon each usage.

LazAI’s Data Anchoring Token (DAT) protocol redefines AI dataset ownership, licensing, and provenance tracking by integrating semi-fungible tokenization, on-chain verification, and decentralized AI economy models.


---

# 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/dat-specifications-and-flow/dat-interaction-flow.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.