Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 77 GitHub source documents. All source documents are searchable here.
Last updated: October 7, 2025
This content is meant to be consumed by AI agents via MCP. Click here to get the MCP configuration.
Note: In rare cases it may contain LLM hallucinations.
For authoritative documentation, please consult the official GLEIF vLEI trainings and the ToIP Glossary.
The minimum number or fractional weights of signatures from the current set of authoritative keys required to be attached to a Message for that Message to be considered fully signed in KERI.
The current threshold (also known as signing threshold, rotation threshold, or witness threshold) is a fundamental parameter in KERI's key-state management that specifies the minimum number of valid signatures—or the fractional weights of signatures—from the given set of current keys required to be attached to a Message for the Message to be considered fully signed.
This threshold applies specifically to the current key set (as opposed to next or pre-rotated keys) and can be expressed as either:
The threshold determines when sufficient cryptographic authority has been demonstrated to validate a message, forming a core component of KERI's multi-signature architecture and threshold signature schemes.
The current threshold is specified in all establishment events:
kt field sets the initial signing thresholdImplementations must validate that attached signatures satisfy the current threshold specified in the most recent establishment event. For integer thresholds, this is a simple count; for fractional weights, implementations must sum the weights of signing keys and verify the total meets or exceeds the threshold.
The current threshold can only be changed through an establishment event (inception or rotation). Validators must track threshold changes across the KEL to correctly validate historical events.
When setting thresholds for multisig groups, implementations should verify the threshold satisfies the ample constraint to prevent accidental lockout scenarios where insufficient participants remain to meet the threshold.
kt field updates the threshold for the new key stateFor example, in a 2-of-3 multisig configuration, the current threshold would be set to "2", requiring any 2 of the 3 current keys to sign messages.
KERI employs a sophisticated dual-threshold system:
kt): Governs signing of non-establishment events and validation of the current establishment event itselfnt): Specifies the threshold for the next rotation event using pre-rotated keysThis separation enables partial rotation and custodial rotation patterns where signing authority and rotation authority can be independently managed.
For witnessed identifiers, the current threshold works in conjunction with witness thresholds:
wt) specifies how many witnesses must receipt an eventThis dual-threshold mechanism enables KAACE (KERI's Agreement Algorithm for Control Establishment) to achieve Byzantine fault-tolerant consensus.
KERI supports fractionally-weighted thresholds through the tholder object, enabling sophisticated governance models:
The current threshold is critical for: