Peer staleness is computed using `peer.timestamp`, which comes from the remote device’s clock. If a peer’s clock is skewed into the future, it may never be removed; if skewed into the past, it may be removed immediately. Consider tracking a local `lastSeen` (receive time) per peer and using that for cleanup instead of the sender-provided timestamp.

[algotyrnt]

Peer staleness is computed using peer.timestamp, which comes from the remote device’s clock. If a peer’s clock is skewed into the future, it may never be removed; if skewed into the past, it may be removed immediately. Consider tracking a local lastSeen (receive time) per peer and using that for cleanup instead of the sender-provided timestamp.

Originally posted by @Copilot in #1 (comment)