REF: ADMIN_RULES // CHAPTER_2885
ADMINISTRATIVE RULES
Chapter 2885: Technical Standards for Digital Trust & Negative List Privacy
2885.0300 TOKENIZATION STANDARD
Algorithm: Argon2id (IETF RFC 9106)
64 MiB minimum
2 passes minimum
2 threads minimum
32 bytes (256 bits)
Token Construction
T = Argon2id(pass = Input Identifier, salt = Global Salt, secret = Authority Pepper)
Input Normalization
Uppercase, no whitespace, format as [Country]-[Subdivision]-[ID]
Example: "US-MN-D12345678"
2885.0400 LIFECYCLE MANAGEMENT
Pepper Rotation
Every 36 months minimum
List Regeneration
Within 24 hours of rotation
Version Control
Authorized Issuers must reject stale list versions (>24 hours)
This prevents bad actors from targeting issuers with outdated data during rotation windows.
2885.0500 PROHIBITION ON RAINBOW TABLES
PROHIBITED
Pre-computing hashes for entire populations is explicitly prohibited.
REQUIRED
Targeted hashing only—at time of transaction, for specific subject.
Privacy by Design
The Negative List architecture demonstrates that fraud prevention and privacy are not in tension:
- • No Raw Identifiers: The list stores only Argon2id tokens, not SSNs or license numbers
- • Authority Pepper: Stored in FIPS 140-3 Level 3 HSMs, rotates every 36 months
- • Version Control: Prevents replay attacks during rotation windows