/**
 * Nado gateway failure → what went wrong, as a code each platform maps to its
 * own copy.
 *
 * - Deliberately not a message: core has no i18n, and the two SDKs namespace
 *   their keys differently (`withdrawal.nado.*` on web, `withdrawNado.*` on RN).
 * - Lives apart from `errors.ts`, which stays flow-agnostic (the codes are
 *   shared across every Nado execute and query).
 */
/**
 * Why a withdrawal failed, in terms the user can be told about. Each platform
 * owns an exhaustive map to its own translation keys, so adding a member here
 * fails their builds until they have copy for it.
 */
export type NadoWithdrawalFailure = 'generic' | 'network' | 'rateLimited' | 'exceedsBorrowLimit' | 'invalidNonce' | 'noPriorDeposit' | 'withdrawRisk'
/** Outcome unknown — the copy for this one must never invite a retry. */
 | 'unconfirmed';
export declare function toNadoWithdrawalFailure(error: unknown): NadoWithdrawalFailure;
/**
 * Whether the failure is one we have specific copy for — the input to log
 * severity (recovered → WARN, gave up → ERROR).
 *
 * Derived from {@link toNadoWithdrawalFailure} rather than its own code set, so
 * severity and messaging cannot drift apart.
 */
export declare function isExpectedNadoWithdrawalFailure(error: unknown): boolean;
//# sourceMappingURL=withdrawalErrors.d.ts.map