Oracles

On-chain DEX oracle reading Stellar order books. One of three Reflector contracts (DEX, CEX, FX) — they share interface but route different upstream feeds.

• •No on-chain twap() or x_*() methods despite the proposal claim — we compute TWAP and cross-pair locally.
• •Three separate contracts, not one. Each has its own price set.

Reflector CEX feed — pulls aggregated CEX prices on-chain. Excluded from our VWAP at aggregator time (would import their methodology).

• •Reported alongside our prices but never priced in — the divergence worker uses it as a sanity reference, not an input.

Fiat-cross feed for chained pairs (e.g. EUR/USD, GBP/USD). Contributes to triangulation when an asset trades against EURC, MXNe etc.

• •Used during X2.5 forex-factor snap (chained-fiat aggregation) when no direct fiat market exists for the asset.

Redstone Adapter does emit events — single batched WritePrices push containing every updated feed in one transaction.

• •WritePrices body has prices + timestamps but NOT feed_ids. Feed IDs live in the InvokeContract op args (write_prices(updater, feed_ids, payload)).
• •Adapter zip-merges feed_ids and updated_feeds when their lengths match; otherwise the whole event is skipped (ErrFeedIDCountMismatch).

Band's Soroban contract emits ZERO events. We observe the relay()/force_relay() InvokeContract calls instead — same dispatcher hook used by any future event-less storage-mutating Soroban contract.

• •Band stores pair rates at E18 scale; relayed single-asset rates at E9. Decoder normalises to canonical fixed-point.
• •Topic-match alone never fires Band — match by (contract_id, function_name) using the dispatcher's ContractCallDecoder interface.