Before it was officially named, the problem was already there.

It's not a lack of functionality, nor insufficient performance—the root cause lies in an inherent blind spot in on-chain systems. No matter how meticulously the contract is written, a single slip with external data can cause the entire system to collapse. Price delays, slippage impacts, data manipulation behind the scenes—trust can crumble in an instant. Anyone who has worked on protocols has encountered this pitfall.

This isn't the product of a sudden burst of inspiration.

To put it simply, it's a solution developed after a group of people were repeatedly frustrated by data issues. The backgrounds are quite diverse: some come from traditional finance, some from data engineering, and others have been deeply involved in blockchain at the foundational level. The only commonality is—everyone has been severely burned by "bad data."

Code and logic may be correct, but the system stubbornly stalls at the data link.

So in the early days, the discussion wasn't about "how to speed things up." The problem was more painful: should or shouldn't oracles just be messengers? If the data itself can't be trusted, then no matter how fast, it's just efficient error propagation.

Gradually, the idea started to become more radical: oracles shouldn't just be pipelines—they need to become a "judgment layer."

The progress has been extremely slow. No large funding, no marketing hype. A lot of time has been spent on trial and error: what verification mechanisms are feasible, what would increase costs, what simply doesn't work in real-world scenarios. The solutions pile up: some are too complex, some are overly centralized, some are too expensive for anyone to afford.

The only reason to persist is—this problem is just too real, and ignoring it will only lead to an eventual explosion.