> For the complete documentation index, see [llms.txt](https://docs.liveart.xyz/liveart/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liveart.xyz/liveart/archive/chapter-2-the-liveart-tokenization-engine/the-defi-layer.md).

# The DeFi Layer

<figure><img src="/files/sud4WEZZDUyOkMTmmEbC" alt=""><figcaption></figcaption></figure>

Tokens trade 24/7 on LiveArt’s built-in DEX. Holders can lend, borrow, stake, or combine them into custom portfolios and index products. And thanks to standard token formats (ERC-20), they plug right into external DeFi protocols too.

**Need liquidity?** Borrow against a Warhol. Want yield? Stake your share of a Patek. Every transaction—from trades to loans to payouts—is **onchain** and auditable.

Tokens aren’t static—they’re programmable. They can carry rules for buyouts, royalties, or compliance. They can represent more than value—they can move, earn, and adapt.


---

# 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.liveart.xyz/liveart/archive/chapter-2-the-liveart-tokenization-engine/the-defi-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.
