Invariant checking is the process of verifying that a protocol’s state still obeys rules that must never be violated. In a ledger or blockchain, those rules can include supply caps, balance conservation, signature requirements, and limits on how transactions may change state. If an update would break one of those assumptions, the system should reject it.
This matters because many high-impact crypto attacks are not about stealing keys, but about making the protocol accept an impossible state. A flaw in invariant checking can let an attacker inflate supply, create invalid balances, or bypass checks that preserve consensus safety. Defenders use invariant checks in validation code, fuzzing, and formal verification to catch edge cases before release. During incident response, teams also compare on-chain behavior against protocol rules to confirm whether a reported bug is real or just a faulty claim.