import { BeaconConfig } from "@lodestar/config";
import { PubkeyHex, electra } from "@lodestar/types";
import { BuilderDepositSignatureCache } from "../cache/builderDepositSignatureCache.js";
/**
 * Mutable lookup for the pending-deposit sequence used by builder-routing logic.
 *
 * This is to implement the spec's `is_pending_validator(pending_deposits, pubkey)` lazily:
 * deposits are grouped by pubkey without verifying signatures, and BLS verification is
 * deferred until a builder deposit needs to know whether the same pubkey already has a
 * valid pending validator deposit.
 *
 * Call `add()` whenever a deposit is appended to the represented sequence. A cached `true`
 * result short-circuits all subsequent checks for that pubkey; a cached `false` records
 * how many deposits were already verified, so appending a new deposit only verifies the
 * newly-appended tail rather than re-running BLS on previously-invalid entries.
 */
export declare class PendingDepositsLookup {
    private readonly depositsByPubkey;
    private readonly validationCache;
    private signaturesFromCache;
    private signaturesVerified;
    private constructor();
    /** Build an empty lookup for a sequence that will be populated incrementally. */
    static buildEmpty(): PendingDepositsLookup;
    /**
     * Append a pending deposit to the represented sequence, keyed by its (precomputed) `pubkeyHex`.
     */
    add(pendingDeposit: electra.PendingDeposit, pubkeyHex: PubkeyHex): void;
    /**
     * Returns true if any pending deposit for `pubkeyHex` has a valid BLS deposit signature.
     * Memoizes the result in `validationCache` so repeated checks for the same pubkey
     * within a block only verify deposits that have not already been checked.
     *
     * Most of the time it should hit the BuilderDepositSignatureCache so we don't have to validate
     * signatures here.
     */
    /**
     * Signature checks performed inside `hasPendingValidator()`, split by whether the pre-verify
     * cache served them. These are the scan the caller never sees: when a builder-routed deposit is
     * preceded by same-pubkey validator deposits this walk dominates, and on a `true` result the
     * caller skips its own signature check entirely.
     */
    get signatureChecks(): {
        fromCache: number;
        verified: number;
    };
    hasPendingValidator(config: BeaconConfig, pubkeyHex: PubkeyHex, cache: BuilderDepositSignatureCache): boolean;
}
//# sourceMappingURL=pendingDepositsLookup.d.ts.map