/**
 * pop zkemail status — ZK Email invite module state for an org.
 *
 * Surfaces the two states that silently break claims:
 *   - no module at all (org deployed without ZK Email)
 *   - module deployed but DORMANT (merkleRoot == 0 → every claim reverts AllowlistNotActive)
 * and cross-checks the committed root (indexed from ActiveAllowlistSet) against the root
 * declared inside the pinned allowlist file, which catches a swapped/unpinned CID before a
 * member hits it. Still two independent sources — chain event vs IPFS document — though
 * `pop zkemail allowlist --verify` is the stronger check: it recomputes the root from the
 * file's merkle tree rather than trusting the value the file declares.
 */
import type { Argv, ArgumentsCamelCase } from 'yargs';
interface StatusArgs {
    org?: string;
    chain?: number;
}
export declare const statusHandler: {
    builder: (yargs: Argv) => Argv<{}>;
    handler: (argv: ArgumentsCamelCase<StatusArgs>) => Promise<void>;
};
export {};