Borrow or payback

Mon, 01 Jan 0001 00:00:00 +0000

This is the complete body of the function we are analyzing.

Construction is similar to the supply or withdraw flow, but the code is simplified because we don’t have decay amounts.

We first perform validation:

uint256 userBorrowData_ = _userBorrowData[msg.sender][token_];

if (userBorrowData_ == 0) {
 revert FluidLiquidityError(ErrorTypes.UserModule__UserNotDefined);
}
if ((userBorrowData_ >> LiquiditySlotsLink.BITS_USER_BORROW_IS_PAUSED) & 1 == 1) {
 revert FluidLiquidityError(ErrorTypes.UserModule__UserPaused);
}

User presence check. We revert if the user is not defined
If user borrow is paused

Then we extract the borrow amount and calculate the current borrow limit by calling the function we explained on the previous page:

Borrow limits

Mon, 01 Jan 0001 00:00:00 +0000

Just like withdrawal limits, Fluid imposes restrictions on borrow amounts for protocols using the liquidity layer.

Borrow limit is the maximum amount that can be borrowed, and like withdrawals, this amount can expand over some time duration by a predefined percentage.

There is also a base borrow limit, which users can freely borrow up to. Up to the base limit, no limits are applied.

And one addition to this borrow limit is the hard cap value, which is the absolute maximum one user can have as borrow amount. After this value, no expansion is possible. This can be viewed as a hard cap in some other protocols.

Operate: Borrow or payback on

Borrow or payback

Borrow limits