import { KeyEpochs, OperationKeyQuery, OperationKeyReader } from '../../clients/eth/types';
import { ParticipantKeySet } from './types';
/**
 * Resolve every participant's *current* operation key.
 *
 * Use for a peg-in being built now. Issues no epoch read, so it never touches
 * the extended `getBtcVaultProtocolInfo` ABI.
 */
export declare function resolveCurrentParticipantKeys(params: {
    operationKeyReader: OperationKeyReader;
    query: OperationKeyQuery;
}): Promise<ParticipantKeySet>;
/**
 * Resolve every participant's operation key bonded at a vault's frozen epochs.
 *
 * Use for every existing-vault path: resume, payout signing, refund. The
 * rosters in `query` must be read at the vault's frozen *membership* versions,
 * because those roster keys are the genesis the keeper/challenger getters fall
 * back to.
 */
export declare function resolveParticipantKeysAtEpochs(params: {
    operationKeyReader: OperationKeyReader;
    query: OperationKeyQuery;
    epochs: KeyEpochs;
}): Promise<ParticipantKeySet>;
//# sourceMappingURL=resolveParticipantKeys.d.ts.map