Open Price Feed is best understood as an unbundled oracle stack. Reporters author and sign data, posters submit it onchain, and view contracts decide how downstream consumers should interpret or guard it.
The repository README is explicit that Open Oracle is a standard and SDK for signed key-value data, not just one hardcoded price-feed deployment.
The governance threads matter because they explain the intended institutional role: Compound wanted to remove reliance on a single permissioned posting process while still keeping a conservative sanity-check path during migration.
OpenOraclePriceData.sol is the lowest useful mechanism layer. It authenticates source-signed messages, stores the freshest value per (source, key), and emits clear write / not-written events when updates are accepted or rejected.
UniswapAnchoredView.sol adds a distinct policy layer above authenticated data storage. It computes an onchain anchor from Uniswap cumulative prices, checks whether the designated reporter price stays within configured upper/lower anchor ratios, and only then updates the authoritative stored price.
The migration proposal makes the reporter invalidation path especially important. If the reporter key may be compromised, a signed invalidation message can switch the system into anchor-only pricing until governance chooses a replacement path.
The docs also show that decentralization here did not mean eliminating all focal trust. It meant relocating trust into a more legible combination of reporter-key control, open posting rights, immutable view configuration, and fallback anchor assumptions.
Specific source signals worth retaining
README.md: strongest concise statement of the reporter / poster / aggregate-view architecture.
OpenOraclePriceData.sol: best source for the authenticated-storage mechanism and freshness checks.
UniswapAnchoredView.sol: best source for anchor tolerance, reporter invalidation, and the protocol-facing price-selection logic.
migrating-to-the-open-price-feed thread: best source for the governance rationale, Coinbase-first deployment path, 30–60 minute Uniswap TWAP anchor, and 20% tolerance design.
open-price-feed-proposal-development thread: useful implementation and review context, especially the framing that the change removes the permissioned poster role and the note that the system was being formally reviewed and tested in the open.
Why this entry belongs in the corpus
It gives the oracle cluster a historically important baseline for signed-source feeds that do not require the data source itself to post transactions.
It strengthens comparison work across Chainlink, API3, Band, Tellor, and later protocol-owned oracle wrappers by making reporter authorship, poster openness, and view-layer policy separate analytical surfaces.
The durable insight is that oracle architecture can be decomposed into source signing, message transport, authenticated storage, and consumer-facing policy — and Open Price Feed makes that decomposition unusually explicit.