What limitation do existing DAG-based consensus protocols have that DAGKNIGHT aims to fix?

Existing consensus protocols — including current DAG-based systems — require hardcoded parameters that assume worst-case network latency, meaning their security depends on network conditions never exceeding those assumptions. In a permissionless network, nodes are spread across the globe and message delivery times vary constantly. To stay safe, protocols like Bitcoin's Nakamoto Consensus bake fixed delay limits into their design. If the real network is slower or more variable than those built-in assumptions, the security guarantee can weaken — and because the limit is hardcoded, the protocol cannot adapt. For a beginner, this matters because it means those systems carry a hidden dependency: they stay secure only as long as the network behaves within a range the protocol's designers predicted in advance — a fragile guarantee that DAGKNIGHT was built to move beyond.