> For the complete documentation index, see [llms.txt](https://docs.kaze.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaze.fi/tigris/oracle.md). # Oracle ## The Most Innovative Oracle System ### What is a Distributed Signature-Based Oracle Network? Oracle nodes are connected to the [Pythnet](https://pyth.network) price feed. The asset prices and other related data is signed and broadcasted directly to Tigris users, which is used to place market orders. This data consists of: * Asset price * Spread * Timestamp * Node address * Market open/closed status * Oracle signature Upon placing a trade, price data and signature is included in the transaction input parameters, where the validity of the data and the signatures are verified on-chain.\ \ **What does this mean for traders?** * **Reliable prices.** The moment you click the 'Open Trade' button, the asset price is locked in. This means there is no slippage in price, **ever**. * **Instant order execution.** Unlike traditional oracle-callback solutions, which require at least two transactions (one to place an order, the other for settlement), all orders are executed instantly in only one transaction, so there is no need to wait for settlement at all. * The speed of the platform is only limited by the speed of the blockchain being used. ## Tigris order execution **Other protocols:** User places market order -> Order tx confirmed -> Keeper receives event (price stored here) -> Keeper executes order -> Order execution tx confirmed -> Position is opened **Tigris:** User sends signed order data to node off-chain -> Node places order on-chain (price stored here) -> Order tx confirmed -> Position is opened --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kaze.fi/tigris/oracle.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.