> For the complete documentation index, see [llms.txt](https://docs.increment.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.increment.fi/protocols/decentralized-money-market/market-parameter.md).

# Market Parameter

### Flow

Proposed parameters for FlowToken:

| Parameter               | Value      |
| ----------------------- | ---------- |
| Collateral Factor       | 80.0%      |
| Supply Cap              | 30,000,000 |
| Borrow Cap              | 15,000,000 |
| Liquidation Incentive   | 10.0%      |
| Liquidation CloseFactor | 0.5        |

### stFlow

Proposed parameters for stFlow:

| Parameter               | Value      |
| ----------------------- | ---------- |
| Collateral Factor       | 75.0%      |
| Supply Cap              | 30,000,000 |
| Borrow Cap              | 15,000,000 |
| Liquidation Incentive   | 10.0%      |
| Liquidation CloseFactor | 0.5        |

### USDC

Proposed parameters for USDC:

| Parameter               | Value |
| ----------------------- | ----- |
| Collateral Factor       | 90.0% |
| Supply Cap\*            | 0     |
| Borrow Cap\*            | 0     |
| Liquidation Incentive   | 10.0% |
| Liquidation CloseFactor | 0.5   |

### USDCf

Proposed parameters for USDCf:

| Parameter               | Value     |
| ----------------------- | --------- |
| Collateral Factor       | 90.0%     |
| Supply Cap              | 8,000,000 |
| Borrow Cap              | 6,000,000 |
| Liquidation Incentive   | 10.0%     |
| Liquidation CloseFactor | 0.5       |

\* USDC on Cadence will be deprecated after Crescendo mainnet upgrade and its contract would break by then. USDC market will be entering deprecation mode that only repaying / withdrawing is allowed.

\* USDCf on Cadence is a wrapped USDC token, which is fully backed by USDC on Ethereum and will keep working before & after Crescendo mainnet upgrade. Learn more [here](https://forum.flow.com/t/stablecoin-stability-through-crescendo-and-erc-20-standards-on-flow/6341).

### FUSD

Proposed parameters for FUSD:

| Parameter               | Value |
| ----------------------- | ----- |
| Collateral Factor       | 90.0% |
| Supply Cap\*            | 0     |
| Borrow Cap\*            | 0     |
| Liquidation Incentive   | 5.0%  |
| Liquidation CloseFactor | 0.5   |

\* FUSD's supply/borrow cap has been lowered to 0 on July 17 2023, <mark style="color:blue;">making this market only redeemable and repayable, but not suppliable or borrowable any more</mark>. This is a preparation for sunsetting this market as FUSD is being obsoleted due to the Prime Trust [issue](https://www.theblock.co/post/236097/nevada-regulator-says-prime-trust-cant-meet-all-client-withdrawals). &#x20;

### BLT

Proposed parameters for BloctoToken:

| Parameter               | Value   |
| ----------------------- | ------- |
| Collateral Factor       | 33.0%   |
| Supply Cap              | 100,000 |
| Borrow Cap              | 100,000 |
| Liquidation Incentive   | 20.0%   |
| Liquidation CloseFactor | 0.5     |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.increment.fi/protocols/decentralized-money-market/market-parameter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.