/**
 * `wallets` namespace — server-side wallet display label.
 *
 * The label is the cross-machine / WEB-visible human name for a wallet (e.g.
 * "kychon"), stored server-side keyed by the wallet address and authenticated
 * by the wallet's allowance signature. It is display metadata only — never key
 * material, no custody.
 *
 * Both methods are intentionally BEST-EFFORT: they swallow errors (including a
 * not-yet-deployed endpoint / 404 / offline) and return a null/`ok:false`
 * sentinel instead of throwing. This lets `run402 wallets new|rename|import`
 * stay fully functional locally and before the gateway endpoint ships — the
 * local folder name is always the source of truth; the server label is a
 * mirror that catches up.
 *
 * Canonical call shape is the wallet-scoped handle: `r.wallet(address)` →
 * `.getLabel()` / `.setLabel(label)`. The two-string `r.wallets.setLabel(address,
 * label)` form is deprecated (see the `sdk-call-shape-conventions` change).
 */
import type { Client } from "../kernel.js";
export declare class Wallets {
    private readonly client;
    constructor(client: Client);
    /**
     * Read a wallet's server-side label, or null on any error (unset, 404,
     * offline). Public read — no auth required.
     */
    getLabel(address: string): Promise<string | null>;
}
/**
 * Wallet-scoped sub-client returned by `r.wallet(address)`. Binds the address
 * so neither label method takes it as a swappable positional. Lazy — no key or
 * network access at construction.
 */
export declare class ScopedWallet {
    private readonly client;
    private readonly address;
    constructor(client: Client, address: string);
    /** Read this wallet's server-side label, or null. */
    getLabel(): Promise<string | null>;
    /** Set this wallet's server-side label. Best-effort; never throws. */
    setLabel(label: string): Promise<{
        ok: boolean;
    }>;
}
//# sourceMappingURL=wallets.d.ts.map