> For the complete documentation index, see [llms.txt](https://calnix.gitbook.io/aave-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://calnix.gitbook.io/aave-book/functions/common-functions/supplycap-borrowcap.md).

# SupplyCap, BorrowCap

## TLDR

**Borrow caps:** limits of how much of each asset can be borrowed, which reduces insolvency risk.

**Supply caps**: limits how much of a certain asset is supplied. Helps control excessive exposure to a certain asset and mitigate attacks like infinite minting or price oracle manipulation.

{% hint style="info" %}
If borrow/supply cap is set to 0; this sigifies that there is no cap.
{% endhint %}

{% hint style="success" %}
In case Borrow Cap of the reserve is set lower than the current totalDebt, the existing borrowers are not effected but no more borrows (stable or variable) can be initiated for that reserve.
{% endhint %}

{% hint style="success" %}
In case *Supply Cap* of the reserve is set lower than the current liquidity of the reserve, the existing suppliers are not effected but no more liquidity can be supplied to that reserve.
{% endhint %}

### How are the caps stored

Each asset has a corresponding `ReserveData` struct which outlines its key information and configuration. 

* `PoolStorage` holds mapping `_reserves` which maps asset address to `ReserveData`.

Within each`ReserveData` struct, there is a nested struct of type `ReserveConfigurationMap`. The nested struct contain a bitmap, storing the asset's configuration:

<figure><img src="https://1829638638-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0k7YXwFGMFZcsyqkM4q1%2Fuploads%2FEckMKls5WgNcrsEccgR3%2Fimage.png?alt=media&amp;token=bec6ab44-797f-4a39-8639-8c5b0af76104" alt=""><figcaption><p><code>ReserveConfigurationMap</code></p></figcaption></figure>

An asset's borrow and supply caps are defined within the bitmap, along with other relevant information.&#x20;

### getSupplyCap

To retrieve a specific asset's supply cap, we call `getSupplyCap` and pass said asset's `ReserveConfigurationMap`.

<figure><img src="https://1829638638-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0k7YXwFGMFZcsyqkM4q1%2Fuploads%2FVTJndYNSbSq1FohBEiGx%2Fimage.png?alt=media&amp;token=42340249-0988-4fac-a5ce-e4fe33f124f3" alt=""><figcaption></figcaption></figure>

```solidity
uint256 internal constant SUPPLY_CAP_START_BIT_POSITION = 116
uint256 internal constant SUPPLY_CAP_MASK = 0xFFFFFFFFFFFFFFFFFFFFFFFFFF000000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFF;
```

* Only bits 116 - 151 are set to `0` in the mask; these bits will be set to `1` after the `~` operation.
* `data & ~SUPPLY_CAP_MASK` will return a hexadecimal number in which all the characters are set to `0,`except potentially the bits representing the supply cap.
* These bits will return the hex value of the supply cap.
* If supply cap is indeed `0`, then `0x000...000` would be returned.

Numbers in Solidity are left-padded. Therefore to convert our resulting hexadecimal number to the appropriate number representation so that it can be cast as a `uint256`, right shifting by 116 bits is required.

* this will remove all the 0s on the right, from the least significant bit to the value
* left-padding will be done accordingly, to ensure 32 byte representation

{% hint style="info" %}
See more at [getReserveFactor](/aave-book/primer/bitmap-and-masks.md#getreservefactor)
{% endhint %}

### getBorrowCap

```solidity
uint256 internal constant BORROW_CAP_START_BIT_POSITION = 80
uint256 internal constant BORROW_CAP_MASK = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000000FFFFFFFFFFFFFFFFFFFF;
```

* Process is similar to getSupplyCap