> 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/lazchain-components/settlement-layer.md).

# Settlement Layer

The Settlement Layer transforms AI-related data, models, and agents into tokenized assets, ensuring secure, traceable, and programmable ownership.

**Key Functionalities are as follows:**

1. **Immutable AI Asset Registration:** Training datasets, model weights, and execution parameters are permanently anchored on LazChain, ensuring provenance.
2. **Data Anchoring Token (DAT) Management:** Every issuance, transaction, ownership transfer, and access control event related to AI assets is immutably recorded on-chain.
3. **Privacy-Preserving Provenance Tracking:** Utilizes Zero-Knowledge Proofs or TEE Proofs to validate dataset authenticity while protecting sensitive AI data.

By anchoring AI assets on a decentralized ledger, the Settlement Layer guarantees integrity, accessibility, and compliance, paving the way for a trustless AI economy.


---

# 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/lazchain-components/settlement-layer.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.