Last year, during these few days, the pace of action by a certain oracle project was so fast that it was a bit overwhelming. First, on December 24th, they launched the OaaS product on Ethereum, then on the 28th, they deployed this system to the BNB Chain, and by the 30th, they had directly entered the Solana ecosystem. This kind of expansion speed is indeed rare in the oracle track, and each step precisely targets the pain points of the ecosystem.

What is OaaS? The full name is Oracle-as-a-Service. Simply put, it is oracle services. The project team has packaged all the complex underlying node operations, data validation, and on-chain interactions. Developers who want to use oracle functions don’t need to build infrastructure from scratch; they can directly call APIs to obtain multi-source data aggregation and on-chain verification capabilities. This is a real lifesaver for many small and medium-sized projects because the threshold for building and maintaining a reliable oracle system is too high. The costs of node operation and security audits alone can crush many teams.

It makes sense that this project focuses on Solana as the key battleground for OaaS. Solana is inherently designed for high-throughput scenarios, with theoretical TPS reaching tens of thousands, making it ideal for applications that require high-frequency data updates, such as prediction markets and on-chain exchanges. Traditional oracles often encounter bottlenecks on Solana, such as push frequency lagging behind the chain’s speed or gas costs being hard to control. The project’s solution is clever; they adopt a hybrid model that includes push mechanisms which can be flexibly adjusted based on thresholds or time intervals, ensuring data real-time performance while optimizing costs.