Executive Summary
JIL Sovereign's time-limited consensus authorization system issues 24-hour validity tokens to validators only after successful completion of both code integrity verification and identity authentication. This ensures that any node compromise, code tampering, or key rotation is detected within a single day.
Token Architecture
| Property | Specification |
|---|---|
| Format | JWT (JSON Web Token) |
| Signing | HMAC-SHA256 with fleet controller secret |
| Validity | 24 hours maximum (non-renewable) |
| Scope | Consensus participation, settlement processing |
| Revocation | Immediate via fleet controller blocklist |
| Renewal | Full re-bootstrap (Gates 1-7) required |
Security Properties
Compromise Detection Window
The 24-hour token expiry guarantees that even if a validator is compromised, it will be detected within one day when it attempts to re-bootstrap with tampered code. The integrity verification gate (Gate 3) will detect modified container images and halt the bootstrap.
Immediate Revocation
The fleet controller can immediately revoke a consensus token by adding it to a distributed blocklist. All other validators check this blocklist before accepting consensus messages from the revoked node. Revocation propagates within seconds.
Integration with Fleet Inspector
The AI Fleet Inspector monitors token expiry across all validators. If a validator's token expires without renewal (indicating bootstrap failure), the inspector flags it for investigation and may trigger automatic remediation based on the dual-policy model.