/**
 * React-query hooks over the Nado gateway. Poll cadences are budgeted against
 * Nado's IP rate limit (2400 query-weight/min): an open modal spends ~10
 * weight/min on the selected product's max.
 *
 * Each hook takes the platform's logger — core has no module-scoped one.
 *
 * @see {@link https://docs.nado.xyz/developer-resources/api/rate-limits | Nado rate limits}
 */
import type { Hex } from 'viem';
import type { FunLogger } from '../../src/utils/funLogger';
/**
 * React-query owns retries (the fetch layer never retries) — up to 2 with
 * backoff, except deterministic api failures, 429s (retrying hammers the
 * limit we just tripped), and timeouts (the caller already waited 30s; the
 * next scheduled poll is the retry).
 */
export declare function shouldRetryNadoQuery(failureCount: number, error: unknown): boolean;
export declare function useNadoMaxWithdrawable(params: {
    productId: number | undefined;
    sender: Hex | undefined;
    spotLeverage: boolean;
    logger: FunLogger;
}): import("@tanstack/react-query").UseQueryResult<string, unknown>;
/**
 * Drops every cached max — prefix match, since each product and borrow state
 * holds its own entry — so a follow-up withdrawal sees the debited balance
 * rather than waiting out the refetch interval.
 */
export declare function useInvalidateNadoMaxWithdrawable(): () => void;
export declare function useNadoFeeRates(params: {
    sender: Hex | undefined;
    logger: FunLogger;
}): import("@tanstack/react-query").UseQueryResult<import("./gateway").NadoFeeRates, unknown>;
//# sourceMappingURL=hooks.d.ts.map