> For the complete documentation index, see [llms.txt](https://city-protocol.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://city-protocol.gitbook.io/docs/tokenization-as-a-service/overview/example-use-cases.md).

# Example Use Cases

TaaS can support multiple product templates.

***

### RWA-backed lending product

An RWA-backed lending product may tokenize exposure to a pool of secured loans or receivables. The tokenized product requires borrower reporting, collateral monitoring, reserve verification, NAV calculation, and redemption scheduling.

**Key configuration fields may include:**

· funding currency;

· collateral type;

· target collateralization ratio;

· minimum collateralization ratio;

· borrower or originator profile;

· verification partner;

· liquidity period;

· capacity;

· subscription eligibility;

· NAV reporting cadence.

***

### **Market-neutral trading strategy**

A market-neutral strategy may tokenize exposure to a strategy that seeks to capture pricing inefficiencies without taking broad directional exposure.

**Key configuration fields may include:**

· approved exchanges or venues;

· approved assets;

· maximum leverage;

· drawdown limits;

· liquidity limits;

· redemption period;

· NAV calculation method;

· management and performance fees;

· strategy reporting cadence.

***

### Tokenized treasury or cash-management product

A treasury-style product may tokenize exposure to short-duration, high-liquidity instruments. This product type places more emphasis on reserve verification, low-duration asset eligibility, NAV stability, and fast redemption.

**Key configuration fields may include:**

· eligible collateral;

· custodian or administrator;

· verification agent;

· reference rate;

· NAV update frequency;

· redemption capacity;

· jurisdictional eligibility;

· transferability policy.