> For the complete documentation index, see [llms.txt](https://docs.aspanfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aspanfi.com/risk-management/oracle-security.md).

# Oracle Security

Technical reference for native ASPAN DeFi, an optional strategy within ASPAN Account. These mechanics do not describe all account assets or the planned external-strategy ASPAN Vaults.

ASPAN relies on valuation inputs to price collateral and calculate protocol state. Oracle security therefore includes the external price source, the collateral conversion adapter, and the contract logic that accepts or rejects an update.

### What a deployment must specify

* The BNB/USD feed and any collateral-specific conversion sources.
* Accepted price age, confidence or deviation limits, and decimal handling.
* The behavior when inputs are stale, unavailable, invalid, or inconsistent.
* Any fallback feed, its activation conditions, and the permissions to change configuration.

References to Pyth or Chainlink describe possible pricing dependencies. They do not establish an automatic fallback or a fixed 30-second staleness rule for every ASPAN deployment.

### Price accuracy is not liquidity

A valid feed can support accounting while actual collateral exits remain delayed or trade at a discount. Oracle checks do not guarantee execution at a displayed value.

### Payment conditions need separate verification

Determining a collateral price is different from determining whether a compute job or API service met its acceptance rule. The proposed conditional-payment and escrow flows need defined evidence, authorized verification, and dispute handling.

Those payment-layer mechanisms remain implementation and security-review work. Simulated approval in the demo is not an audited service-delivery oracle.
