/**
 * @name signer/local-keypair-signer
 * @description Local profile signer for local-dev-keypair mode.
 *
 * The hosted SAP MCP server never receives keypair bytes. Agents receive a
 * signer capability through sap_payments tools, not direct keypair access.
 * Production value flows should use a dedicated capped profile, external
 * signer, hardware wallet, or delegated session policy.
 *
 * @flow
 *   1. `createLocalKeypairSigner` loads a keypair from file via `loadKeypairFromFile`.
 *   2. Returns a `Signer` object with `publicKey`, `signTransaction`, and `signAllTransactions`
 *      that sign transactions locally using the loaded keypair.
 *
 * @module signer/local-keypair-signer
 */
import type { Signer } from './signer-types.js';
/**
 * @name createLocalKeypairSigner
 * @description Creates a local `Signer` backed by a keypair loaded from disk.
 *
 * @param walletPath — Filesystem path to the keypair JSON file.
 * @returns A `Signer` implementation that signs `Transaction` and `VersionedTransaction` objects locally.
 *
 * @usedBy `signer-resolver.ts:resolveSigner` when mode is `local-keypair`.
 */
export declare function createLocalKeypairSigner(walletPath: string): Signer;
//# sourceMappingURL=local-keypair-signer.d.ts.map