import { LenderCrossPoolMeta, UserData } from '../utils/types';
/**
 * Returns a [converter, expectedCallCount] tuple for Silo v3 user data.
 *
 * v3 reuses the v2 read interface byte-for-byte, so this parser is a
 * structural mirror of `silo-v2/userCallParse.ts` — only the registry
 * lookup (`getSiloV3MarketEntry`) and the per-pair lender key prefix
 * differ. See [silo-v2/README.md](../silo-v2/README.md) for the
 * `LenderCrossPoolMeta` field audit; the same audit applies verbatim to
 * v3.
 *
 * Result layout (10 slots per pair, 5 per side):
 *   [collateralShares0, protectedShares0, collateralRate0, protectedRate0, maxRepay0,
 *    collateralShares1, protectedShares1, collateralRate1, protectedRate1, maxRepay1]
 *
 * Deposits are computed off-chain per deposit type with separate rates:
 *   collateralAssets = collateralShares * collateralRate / 10^decimals
 *   protectedAssets  = protectedShares  * protectedRate  / 10^decimals
 *   totalDeposits    = collateralAssets + protectedAssets
 *
 * Rates differ because collateral deposits accrue borrower interest while
 * protected deposits don't.
 *
 * `collateralEnabled` is set to `true` when the silo has deposits and its
 * `lt > 0` (its side can back borrows on the other silo).
 *
 * Aggregation goes through `createBaseTypeUserState` using config mode `'0'`.
 */
export declare const getSiloV3UserDataConverter: (lender: string, chainId: string, account: string, metaMap?: LenderCrossPoolMeta) => [(data: any[]) => UserData | undefined, number];
//# sourceMappingURL=userCallParse.d.ts.map