import type { VanaNetworkName } from "../../core/network.js";
/** What a Personal Server needs to know about the network it serves. */
export interface LocalServerNetwork {
    name: VanaNetworkName;
    chainId: number;
    gatewayUrl: string;
    storageApiUrl: string;
    contracts: Record<string, string>;
    /** The relay frpc dials to give the server its public URL. */
    tunnel: {
        serverAddr: string;
        serverPort: number;
    };
    /**
     * Vana Web for this network, where the owner answers an MCP agent's
     * `request_scope_access`. Moksha is served by the dev deployment (its
     * gateway, storage and relay are dev's), so its page is app-dev.
     */
    webOrigin: string;
}
export declare function localServerNetwork(name: VanaNetworkName): LocalServerNetwork;
/** The pinned server release, matching runtime-pkg/package.json. */
export declare const PERSONAL_SERVER_VERSION = "1.33.8";
export declare function localServerHome(): string;
/**
 * The CLI's servers for one network. Before per-account dirs, this dir was
 * itself the one server's data dir (see data-dir.ts for the move).
 */
export declare function networkServerDir(network: VanaNetworkName): string;
/**
 * The CLI's own data dir per network and owner account: the server key, its
 * index and its data belong to one owner, so two accounts never share one.
 * Never Desktop's (`~/.vana/desktop/personal-server/...`): two processes on
 * one index and one server key would corrupt both.
 */
export declare function accountServerDataDir(network: VanaNetworkName, owner: string): string;
export declare function localServerRuntimeDir(): string;
/** Ports Desktop and the CLI both try first; the loopback approval page is port + 1. */
export declare const LOCAL_SERVER_PORTS: readonly [8080, 8082, 8084];
//# sourceMappingURL=config.d.ts.map