# DAT Token Lifecycle

The LazAI AI Data Economy is built around programmable AI licensing, ownership trading, and dataset/model composability. 

#### Token Minting & Ownership Structure

DAT tokens can be minted by AI data contributors, model creators, or AI agents via a structured issuance process:

1. **AI Data Submission:** The data provider submits dataset metadata to LazAI Flow.
2. **Validation & Anchoring:** The Quorum-based verification process confirms authenticity, generating a hashed dataset fingerprint.
3. **Token Minting:** The system mints a DAT token, encoding: Ownership rights, Usage-based pricing models, Access control permissions
4. **Revenue Distribution Rules:** The DAT contract automatically distributes revenue when datasets/models are used.

#### AI Data & Model Exchange

DAT supports AI dataset licensing and model trading through fractional ownership and dynamic pricing mechanisms.

<table data-header-hidden><thead><tr><th width="255.9140625"></th><th></th></tr></thead><tbody><tr><td><strong>Feature</strong></td><td><strong>Implementation</strong></td></tr><tr><td>Fractional Ownership Trading</td><td>Users can sell or trade partial ownership of datasets without full asset transfer.</td></tr><tr><td>AI Model Evolution</td><td>Developers can fork datasets/models while ensuring original contributors retain revenue-sharing rights.</td></tr><tr><td>Permission-Based Dataset Licensing</td><td>Data owners set usage conditions (read-only, trainable, composable), enforced via on-chain access control.</td></tr><tr><td>Dynamic AI Marketplace</td><td>AI models and datasets are tokenized &#x26; exchanged as DAT, enabling seamless monetization of AI assets.</td></tr></tbody></table>


---

# Agent Instructions: 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.lazai.network/lazai-workflow-and-runtime/dat-specifications-and-flow/dat-token-lifecycle.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.