> For the complete documentation index, see [llms.txt](https://docs.wagon.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wagon.network/products/wagon-asset-tokenization.md). # Wagon Asset Tokenization Wagon Asset Tokenization transforms real-world logistics assets — like trucks, heavy equipment, and infrastructure — into fractional tokens. Through this model, investors can buy, hold, and trade asset-backed tokens while earning stable monthly yields from rental income. *** ### 🚚 What is Tokenized? Each tokenization program represents a specific productive asset, such as: * Trucks for logistics companies * Excavators or trailers for construction * Cold storage, barges or specialized vehicles Wagon acquires these assets upfront and rent them to vetted logistics businesses under transparent, on-chain agreements. *** ### 💰 What Do Investors Get? By purchasing tokens, you: * Own **fractional rights** in real-world trucks and equipment * Earn **monthly rental yields** from the asset * **Trade tokenized asset** in the secondary market for liquidity * Get your **principal repaid at maturity** * Track the asset performance on-chain, in real-time *** ### 🔐 How Is It Structured? * A **Special Purpose Vehicle (SPV)** legally owns each asset. * The SPV enters into a **rent agreement** with the logistics operator. * A **smart contract** issues and manages tokens, distributes rental income, and supports secondary trading. *** ### 🛡 What About Security? Wagon protects both investors and operators through: * **Asset insurance** (vehicle, fire, accident, theft) * **Revenue tracking** and on-chain payment records * **Escrow-controlled disbursements** * **SPV legal structure** ensuring separation and investor protection --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.wagon.network/products/wagon-asset-tokenization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.