import { LenderCrossPoolMeta, UserData } from '../utils/types';
/**
 * Compound III (Comet) pricing context for interpreting user balances below.
 *
 * Each market has one borrowable base token and a dedicated base price feed
 * (`baseTokenPriceFeed`). Every listed collateral has its own feed from
 * `getAssetInfo`. Comet reads each feed via `getPrice` and combines amounts with
 * the same scaling pattern (`mulPrice`); it does not normalize answers into a
 * single quote asset inside the contract.
 *
 * Feed quote assets are deployment-specific (e.g. token/USD, token/ETH,
 * token/BTC, peg-style, or constant feeds for the base). There is no protocol
 * guarantee that all feeds for a Comet share one numeraire—only that governance
 * configures them so borrow and collateral sides are economically comparable.
 *
 * Comet does not define a named “health factor”. A HF-like scalar is the ratio
 * of total risk-adjusted collateral value to borrow value when both sides are
 * valued the way Comet does for liquidation: debt from borrow balance and the
 * base feed; per-asset collateral from balances, that asset’s feed, and
 * `liquidateCollateralFactor` (liquidation threshold, above borrow collateral
 * factor).
 */
export declare const getCompoundV3UserDataConverter: (lender: string, chainId: string, account: string, metaMap?: LenderCrossPoolMeta) => [(data: any[]) => UserData | undefined, number];
//# sourceMappingURL=userCallParse.d.ts.map