Maintain mesh continuity in GPS-denied environments. Drift Systems replaces timestamp-based authentication with state-based ordering, rendering replay attacks and jamming mathematically distinguishable.
The simulation below demonstrates the three core invariants of the Drift Protocol: Freshness (Sequence Validity), Timing (Latency Budgets), and Quorum (Majority Rule).
Instruction: Click "SEND CHALLENGE" to verify mesh health. Toggle "JAM" to simulate High-Power Broadband Barrage (forcing retries/latency). Click "REPLAY" to inject a valid-but-stale packet.
Note: Reactive/Follower jammers are defeated automatically by the hopping pattern and are not simulated here.
Instead of relying on shared secrets or GPS time slots, nodes generate hopping patterns using the Drift Attractor. This creates a high-entropy spread spectrum that is mathematically unpredictable to adversaries but perfectly synchronized for peers.
Drift replaces "Wall Clock Time" with "Sequence Time". Even if the local clock drifts by seconds, the arithmetic sequence ensures packet ordering. This allows for tight authentication windows without atomic clocks.
Because the state evolution $S_{t+1} = F(S_t)$ is non-invertible and path-dependent, a captured packet $P_t$ cannot be used to forge $P_{t+1}$. Replaying $P_t$ fails the freshness check immediately.
If a node is jammed, the mesh degrades gracefully. As demonstrated in the sim, if 2/3 nodes respond, the mesh remains "Operational" (Amber Status) rather than failing completely.