# Asset Borrow Mapping

Each asset on Kinza Finance requires a detailed analysis to properly understand potential risk, and how a money market may be affected depending on what assets are borrowed against provided collateral. The potential risks of a collateral/borrow configuration involving collateral asset A with borrow asset B may be different than A:A or A:C.&#x20;

To address this challenge, Kinza Finance has developed the capability to exercise control over permitting and constraining borrowable reserves for a given collateral.&#x20;

### Collateral Constraint

Borrow Mapping constrains potential borrow pairs for a given collateral. For example, as an Ethereum LRT token, a user with ezETH as collateral can only borrow ETH. This is done by blocking all other reserves from being borrowed by a user who enabled ezETH as collateral. This constraint isolates the risk of ezETH to the ETH pool.&#x20;

&#x20;The impact for the user would be:

1. If you have already borrowed assets outside ETH, you cannot enable ezETH as collateral.
2. If you have enabled ezETH as collateral, you cannot borrow assets outside ETH.

Newly supported assets will undergo thorough analysis in partnership with our security partners to determine the Borrow Mapping parameters and allowable borrow pairs.&#x20;


---

# 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://docs.kinza.finance/lending-core/risk-methodology/asset-borrow-mapping.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.
