> 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.md).
# Chapter 2: The LiveArt Tokenization Engine
With over 100,000 asset fractions deployed across 17+ blockchains, LiveArt is showing the world what the next era of ownership looks like: programmable, tradable, and powered by AI.
Tokenization isn’t just the future of collecting—it’s the next big frontier in programmable finance. And cultural assets are finally part of the equation.
#### **How It Works**
The process is seamless from vault to blockchain. Physical assets are sourced, authenticated, and locked in secure storage. Then, LiveArt fractionalizes and tokenizes them—minting ERC-20 tokens that represent real ownership, backed by real-world provenance.
> *Figure: Simplified architecture of the LiveArt tokenization ecosystem.*
Everything runs through the Tokenization Engine:
* Off-chain processes like market value and authentication
* Smart contracts for issuance, transfers, and buyouts
* AI and oracles feeding real-time price data
Once minted, tokens circulate across supported blockchains (Ethereum, Base, BNB Chain, Polygon, and more), ready for DeFi trading, staking, and governance.
---
# 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.md?ask=&goal=
```
`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.