/**
 * Veilo network coordinates are protocol configuration, not integrator input.
 * Keep them behind the public package entry points.
 */
export declare const VEILO_RELAYER_URL = "https://relayer-server.onrender.com";
export declare const VEILO_RELAYER_PUBLIC_KEY = "utVxnA7zax09qJCZ7UJsa8PAOoWLRcCwOkdxg/ZGmD4=";
/**
 * Internal construction options. Overrides exist only for isolated tests.
 *
 * ⚠ `baseUrl` MUST NOT be promoted to the public API. Two invariants depend on
 * it staying internal:
 *
 *   1. The privacy pool gates every spend on an on-chain relayer allowlist
 *      (`RelayerNotAllowed`). Only deposits are permissionless. A request sent
 *      to any other host cannot land on chain, so the option would be a
 *      footgun that fails late rather than a feature.
 *   2. These request bodies carry note spending keys (`TransactNote.privateKey`,
 *      and `claimantSecretKey` on position close/merge). A caller-settable
 *      destination is a caller-settable exfiltration target for user funds.
 *
 * Only `internal.ts` may construct these options, and it builds the object
 * literal itself — no caller-supplied object is ever forwarded here. To verify
 * that still holds:
 *
 *   grep -rn "createInternalRelayerClient(\|new VeiloRelayerClient(" src
 *
 * Whitelisted partners who run their own relayer are handled out of band, not
 * by a config flag. See README → "Submission always targets Veilo's relayer".
 */
export interface InternalRelayerClientOptions {
    authToken?: string;
    apiKey?: string;
    baseUrl?: string;
    encryptionPublicKey?: string;
    fetch?: typeof fetch;
}