Key Revocation
Pronunciation: kee rev-uh-KAY-shuhn
Also known as: Cryptographic Key Revocation
Definition
Key revocation is the formal action of declaring that a cryptographic key must no longer be trusted for future authorization, signing, decryption, or identity claims. It may follow compromise, loss, personnel change, policy expiry, or migration. Because blockchains preserve historical signatures, revocation usually changes future acceptance rules rather than erasing valid past transactions.
Overview
Meaning and scope
Key revocation is the formal action of declaring that a cryptographic key must no longer be trusted for future authorization, signing, decryption, or identity claims. It may follow compromise, loss, personnel change, policy expiry, or migration. Because blockchains preserve historical signatures, revocation usually changes future acceptance rules rather than erasing valid past transactions.
Mechanism and operation
Key revocation removes trust from a key before or at the end of its authorized lifetime. The action can update an on-chain authority, certificate status, validator registry, access-control list, or wallet policy. Historical transactions signed while the key was valid remain part of the chain and continue to verify cryptographically. Revocation changes whether new signatures or claims should be accepted after a defined time or block. Systems must therefore record the revocation point and distinguish signatures created before and after it. Clock ambiguity can be reduced by using block numbers or finalized timestamps.
Practical payment example
After a signing credential is exposed, a service revokes its authority and rotates dependent secrets; the old key remains part of the incident record.
Operational checks
Some allow an Account Authority to replace keys, while immutable single-key accounts may have no protocol-level revocation path. In those cases, funds must be transferred to a new account before compromise, or the key remains effective for as long as assets or permissions remain associated with it.
Distinctions and limits
Merely deleting a local private key is not revocation because other systems may continue accepting signatures from the corresponding public key unless they receive an authoritative status change. An incident plan should combine revocation with Key Rotation, notification, monitoring for unauthorized signatures, and review of dependent systems.
Related reading
Related definitions: Account Authority, Key Rotation.
Example
After a signing credential is exposed, a service revokes its authority and rotates dependent secrets; the old key remains part of the incident record.
Comparison
Merely deleting a local private key is not revocation because other systems may continue accepting signatures from the corresponding public key unless they receive an authoritative status change. When applying Key Revocation, teams should separate directly observed protocol facts from interpretation. key revocation changes future trust in a key; it does not erase historical signatures or help unless every relying system enforces the new status.
Key Takeaway
Key revocation changes future trust in a key; it does not erase historical signatures or help unless every relying system enforces the new status.
Sources
- Recommendation for Key Management: Part 1 — NIST (2026-08-02)
- Nodes and Clients — Ethereum.org (2026-08-02)