import type { DIDLog, DIDLogEntry } from '@interop/did-method-webvh';
/**
 * The rung keys attributed to each standing ladder VM, keyed by the ladder
 * VM's own `publicKeyMultibase`. A ladder the walk could not attribute
 * carries no entry at all, which is what makes an unattributed ladder refuse.
 */
export type LadderRungKeys = Map<string, Set<string>>;
/**
 * The update-key multibases that signed one log entry: the fragment of each
 * proof's `did:key:<multibase>#<multibase>` verification method.
 *
 * @param entry {DIDLogEntry | undefined}
 * @returns {Set<string>}
 */
export declare function entrySignerKeysOf(entry: DIDLogEntry | undefined): Set<string>;
/**
 * Attributes each standing ladder VM's rung keys, one snapshot per log entry:
 * the returned array is indexed by entry position, and each snapshot names
 * what the log attributes as of that version and no later one. A ladder is
 * anchored at the entry introducing its VM and climbs from there by the
 * last-position rule (the module header states both).
 *
 * A snapshot names a ladder's rungs that the version still authorizes in
 * `updateKeys`, plus any rung that signed the version's own entry -- the one
 * question the ceremony-tail license asks of this map, so a rung retired by
 * the very entry it signed still answers it. A ladder left with no such rung
 * is absent from that snapshot rather than present and empty, as is a ladder
 * the walk refuses, so a caller cannot mistake "no rung attributed" for "this
 * key signed nothing".
 *
 * @param log {DIDLog}   a resolved, caller-verified account log
 * @returns {Promise<LadderRungKeys[]>}   one snapshot per entry, in log order
 */
export declare function attributeLadderRungsPerVersion(log: DIDLog): Promise<LadderRungKeys[]>;
//# sourceMappingURL=ladderRungs.d.ts.map