> For the complete documentation index, see [llms.txt](https://docs.ledgity.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ledgity.finance/rwa-portfolio/risk-management-and-reporting.md).

# Risk Management & Reporting

Ledgity applies institutional-grade risk controls to ensure that yield is stable, withdrawals remain predictable, and capital is protected across market cycles.\
The objective is simple:

> **Stable yield → without liquidity mismatch → with full transparency.**

This is achieved through a combination of **portfolio diversification**, **liquidity buffer coverage**, **counterparty evaluation**, and **ongoing monitoring**.

***

### **1. Portfolio Construction Principles**

Ledgity’s RWA strategy is built around **short-duration, high-repayment-visibility credit**.

| Principle                      | Description                                                             |
| ------------------------------ | ----------------------------------------------------------------------- |
| **Short duration**             | Capital cycles quickly, reducing liquidity and duration risk.           |
| **Recurring cash flows**       | Yield is generated through frequent repayment schedules.                |
| **Diversification**            | Exposure is spread across multiple borrowers, sectors, and instruments. |
| **Senior secured positioning** | Contracts structured to prioritize capital protection.                  |

This avoids the liquidity mismatch risks seen in:

* **Real estate-backed lending** (multi-year repayment cycles)
* **Long-duration bonds** exposed to **rate volatility**
* **Illiquid private credit** that cannot respond to withdrawals

***

### **2. Liquidity Management & Withdrawal Safety**

Ledgity maintains a **Liquidity Buffer** on-chain to support **instant withdrawals**.

| Withdrawal Type                               | Source of Funds                              | Time to Settle                          |
| --------------------------------------------- | -------------------------------------------- | --------------------------------------- |
| **Up to available on-chain buffer**           | Direct smart contract liquidity              | **Instant**                             |
| **Standard withdrawal** (typically < 10% TVL) | Scheduled RWA repayment cycle                | **Up to 72 hours**                      |
| **Large withdrawals** (≥ 20% TVL)             | Portfolio unwinding + dedicated coordination | **1–4 weeks** (with live communication) |

This ensures:

* No forced liquidation under stress
* No redemption bans
* No unpredictable gating

Withdrawals are **predictable and transparent**, not dependent on market price movements.

***

### **3. Counterparty & Credit Evaluation**

Every RWA allocation undergoes a standardized due diligence process:

| Stage                  | Evaluation Criteria                                            |
| ---------------------- | -------------------------------------------------------------- |
| **Screening**          | Regulatory status, financial history, credibility              |
| **Risk Assessment**    | Business model, repayment predictability, collateral structure |
| **Credit Scoring**     | Quantitative & qualitative rating matrix                       |
| **Ongoing Monitoring** | Weekly repayment tracking + monthly performance review         |

In cases of deterioration:

* Exposure is gradually reduced
* Allocation is rebalanced
* Collateral claims procedures may be activated (case-dependent)

***

### **4. Custody, Legal Structuring & Asset Segregation**

Assets are held through a **qualified EU custodian**, and deployed via a **segregated SPV (Luxembourg)**.\
This ensures that:

* Assets are **legally separated** from Ledgity corporate balance sheets
* Users retain **beneficial ownership claim**
* Capital remains protected even in the event of company insolvency

This is the same structure used by **institutional asset managers** in traditional finance.

***

### **5. Reporting & Transparency**

Ledgity provides **multi-layer reporting** to ensure traceability and user confidence:

| Layer                              | Frequency       | Content                                        | Where                       |
| ---------------------------------- | --------------- | ---------------------------------------------- | --------------------------- |
| **Protocol Dashboard**             | Real-time       | TVL, yields, PPS growth, deposits/withdrawals  | App                         |
| **Monthly Portfolio Report**       | Monthly         | Allocation breakdown, performance metrics      | Documentation / Dashboard   |
| **Custodian Balance Verification** | Periodic        | Proof of segregated holdings                   | Published proofs            |
| **Proof of Reserves (PoR)**        | **In progress** | Verifiable on-chain asset collateral reporting | Via Chainlink PoR framework |

**Chainlink BUILD** supports our PoR and cross-chain transport layer:\
[https://www.chainlinkecosystem.com/ecosystem/ledgity-yield](https://www.chainlinkecosystem.com/ecosystem/ledgity-yield?utm_source=chatgpt.com)

***

### **6. Incident Response**

Ledgity maintains a **protocol-wide emergency pause mechanism**, allowing operations to be frozen across all chains if suspicious activity is detected.

Emergency actions:

* Freeze malicious actors (via GlobalBlacklist)
* Pause deposits/withdrawals temporarily (via GlobalPause)
* Execute rapid asset protection procedures

This ensures rapid containment and user fund safety.

***


---

# 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.ledgity.finance/rwa-portfolio/risk-management-and-reporting.md?ask=<question>&goal=<user_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.