Fetch liquidated position on

Liquidations & Factors

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

Let’s say we have 4 users opening debt positions on 4 different ticks on the ETH / USDC vault, and let’s assume 1 ETH = 2500 USDC.

Alice: 15k debt
Bob: 10k debt
Charlie: 25k debt
Eve: 12k debt

Important to note is that these examples will have one user per tick for simplicity in visuals, although every tick can have multiple positions in it. Fluid never works with individual positions during liquidations, but rather with tick data, which we will also do.

fn: fetchLatestPosition

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

We have background now, so let’s revisit the main function for fetching user positions after liquidations:

1. Fetch tick generation data

We know that the user got liquidated, partially or fully. Liquidation happened on some branch, that might be, or might not be, merged into another branch (which can also be merged with its base, etc.).

We also know that the user is part of some epoch, which we call tick ID, which can be the latest current epoch living in the tickData mapping, or an older epoch that lives in history, in the tickId mapping.

Update debt and branch data

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

There is one small piece of code left to cover to finish this section of fetching a liquidated position.

We called the fetchLatestPosition function, and now the only part left is to update final debt and branch data:

First, we check if new raw debt is bigger than previously stored dustDebtRaw. This simply ensures that net debt is bigger than zero, because we will subtract dust from new raw debt. If that’s not the case, we accumulate the difference and mark the user as fully liquidated: