# What is CarFi

CarFi is an infrastructure platform designed for the issuance and trading of Real World Assets (RWA), enabling on-chain representation, verification, and circulation of various legally enforceable real-world assets. While the platform initially focuses on the logistics sector, its long-term vision is to support standardized RWA solutions across multiple industries, chains, and asset types.<br>

At the core of CarFi lies a proprietary RWA protocol that governs the on-chain issuance and validation process. This protocol introduces a structured framework for asset evaluation based on key disclosures, legal documentation, third-party audits, and Web reputation metrics. Combined with a dynamic pricing mechanism and a flexible capital injection model, the protocol ensures that the value linkage between on-chain tokens and off-chain assets remains verifiable and adaptable. The system supports both self-service and curated issuance models, allowing integration by a wide range of asset originators with varying compliance requirements.

Beyond issuance tools, CarFi integrates a decentralized marketplace, compliance governance module, and encrypted communication system to facilitate transparent, low-friction interaction between investors, asset issuers, and regulatory service providers. Built with modularity and extensibility in mind, the platform is designed for multi-chain deployment, ensuring scalable and compliant on-chain representation of global real-world assets.


---

# 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://carfi.gitbook.io/carfi/introduction/what-is-carfi.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.