# Oracle Architecture

Stratium relies on a modular oracle and data stack designed to support structured products, volatility markets, and macro-linked instruments on Hyperliquid HIP-3.

Rather than depending on a single oracle provider, Stratium integrates specialized data layers, each optimized for a specific function within the protocol.

### Programmable Data Layer: SEDA

[SEDA](https://www.seda.xyz/) is used as a programmable data execution layer. Its role includes executing custom data logic and transformations off-chain, enabling composable and programmable data pipelines, and supporting non-standard data inputs required for structured products.

SEDA allows Stratium to move beyond static price feeds by enabling logic-driven data computation that aligns with complex payoff structures.

### Price Feed & HIP-3 Relayer: Pyth Network

[Pyth Network](https://www.pyth.network/) serves as the primary real-time price feed provider for core market data. Within Stratium, Pyth feeds are relayed via a HIP-3 compatible relayer, used for spot prices, mark prices, and settlement references. Optimized for low-latency and high-frequency market conditions on Hyperliquid.

Pyth is treated strictly as a price signal layer, not a valuation or risk engine.

### Data Pipeline

| Stage       | Description                                                            |
| ----------- | ---------------------------------------------------------------------- |
| Collection  | Price, volatility, and domain-specific data from specialized providers |
| Validation  | Outlier detection, staleness checks, sanity bounds                     |
| Computation | Custom transformations via SEDA for non-standard underlyings           |
| Aggregation | Weighted combination across valid sources                              |
| Delivery    | Price updates posted to Hyperliquid via HIP-3 oracle interface         |

### Operational Parameters

| Parameter      | Target                                       |
| -------------- | -------------------------------------------- |
| Price updates  | Sub-second during active markets             |
| Uptime target  | 99.9%+                                       |
| Infrastructure | Multi-region redundancy                      |
| Failover       | Automatic fallback to secondary data sources |
| Monitoring     | 24/7 alerting and incident response          |

### Design Philosophy

**Separation of concerns.** Price, volatility, and computational logic are sourced from independent, specialized providers.

**Composable data.** Feeds can be combined, transformed, or replaced without protocol redesign.

**Transparency.** All oracle dependencies are explicitly disclosed. No single provider controls pricing, valuation, or settlement logic.

### Disclaimer

Oracle providers integrated into Stratium operate independently. Stratium does not control, guarantee, or warrant the accuracy, availability, or continuity of any third-party data source. Oracle inputs are technical components within protocol logic and do not constitute financial advice or valuation guarantees.


---

# Agent Instructions: 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:

```
GET https://docs.stratium.xyz/about-stratium/oracle-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.