Have you ever thought about a scenario like this: driving a supercar at high speed on the highway, but the navigation system updates traffic conditions only every 30 seconds—this delayed bottleneck feeling is the dilemma faced by many high-performance protocols today.

Take Kite as an example. These protocols that pursue extreme efficiency have requirements for data feeds that go beyond the "accuracy" category. They need not just correct data, but real-time responses akin to neuronal reactions. Looking at the Web3 market in 2025, which is abundant in liquidity, traditional oracles are like daily morning newspapers, while Kite demands 24/7 real-time pulse monitoring.

Where is the root of the problem? Most traditional oracles still rely on old methods like heartbeat mechanisms or threshold triggers—either updating only when price fluctuations exceed a certain percentage or rigidly posting on-chain at fixed intervals. This mode was barely acceptable in the slow markets of a few years ago, but in a world of sub-second trading like Kite, even a delay of a few seconds can cause lag in liquidation judgments and passive leakage of arbitrage opportunities. These profit loopholes caused by delays are called "oracle extractable value" in the industry—simply put, outdated price data is like a vampire stealing the protocol's underlying revenue.

From a technical bottom-up perspective, Kite aims for deterministic instant settlement logic. Traditional oracles, from data collection to on-chain confirmation, often require multi-node consensus, which is itself a bottleneck. In high-frequency trading environments, the delay effect of this bottleneck is amplified several times.