Standards and Improvement Proposals
Tracks the formal specifications and community proposals that define Pyth Network's core data models, such as price feed construction, confidence interval calculations, aggregation methodologies, and cross-chain messaging standards. This group is essential for protocol architects and integration engineers who need to understand the canonical data structures and the lifecycle of proposals that alter how prices are computed and consumed, distinct from the governance process that ratifies them or the operational releases that implement them.
Pyth Price Feed Specification
Canonical technical standard defining the binary structure of a Pyth price update, including price, confidence interval, exponent, and timestamp fields. Essential for any team parsing Pyth data on-chain or off-chain to avoid misinterpreting raw bytes, with direct implications for integration correctness and audit readiness.
Confidence Interval Calculation Standard
Formal specification of the aggregation methodology used to derive a single aggregate confidence interval from multiple publisher inputs. Covers the mathematical model, outlier handling, and how DeFi protocols should use this value for risk parameterization such as setting liquidation thresholds and loan-to-value ratios.
EMA Price and TWAP Calculation Standard
Specification for how Exponentially-Weighted Moving Average and Time-Weighted Average Price values are computed from the streaming aggregate price. Clarifies configurable parameters, intended use cases for different DeFi primitives, and integration requirements for protocols consuming these derived values.
Pythnet Data Model and Schema
Formal specification for data structures transmitted over the Pythnet appchain, including binary encoding of price feeds, batch updates, and governance attestations. Authoritative reference for developers building custom relayers, indexers, or low-level parsers that interact directly with the Pythnet validator network.
Cross-Chain Price Update Message Format
Standard defining how a Pyth price update is wrapped into a cross-chain message payload, including header fields and verification identifiers that make an update actionable on a destination chain. Critical for teams building custom receiver contracts or verifying Pyth data across multiple execution environments.
Hermes Relay Protocol Specification
Specification for the Hermes relayer's behavior, including subscription patterns, update aggregation logic, and submission mechanics to target chains. Covers request/response patterns, fee management, and gas estimation logic that define reliable data delivery for integrators running their own relay infrastructure.
On-Demand Pull Oracle Interface Standard
Formal definition of the pull-based oracle interface that consuming smart contracts must implement, including the updatePriceFeeds function signature, required verification steps, and expected behavior for handling stale or invalid updates. Foundational integration contract for all DeFi protocols consuming Pyth data.
Benchmarks Cross-Chain Data Standard
Specification for Pyth Benchmarks, a lightweight off-chain data format for historical prices. Details the JSON schema, query API standard, and how Benchmarks complement on-chain updates for backtesting, settlement, accounting, and risk modeling workflows.
Pyth Improvement Proposal Process
Meta-standard defining the lifecycle of a Pyth Improvement Proposal from ideation and community discussion through formal review, voting, and implementation. Canonical guide for protocol architects and governance participants seeking to propose changes to core oracle mechanics.
Aggregation Algorithm Change Proposals
Tracking page for proposals that modify core aggregation logic, such as shifting from median to weighted mean, introducing stake-weighting, or changing outlier detection parameters. Essential for risk teams monitoring how the protocol's price formation methodology evolves over time.
Publisher Stake-Weighting Standard Proposals
Topic page tracking proposals that define and refine how a publisher's stake influences their contribution to the aggregate price and confidence interval. Critical for understanding the economic security model and how changes affect oracle trust assumptions for consuming protocols.
Cross-Chain Governance Message Standard
Specification for how governance actions ratified on Pythnet are encoded into messages and executed atomically across multiple destination chains. Vital for integrators and risk teams who need to verify that governance decisions are correctly applied to all deployed oracle contracts.
New Data Type Standards
Family of proposals introducing derived data types beyond base price and confidence interval, such as realized volatility, funding rates, or other complex financial metrics. Tracks standardization of calculations that expand the oracle's surface area for DeFi protocols.
Pyth SDK API Specification
Formal specification for canonical Pyth client SDKs across Rust, TypeScript, Python, and Go. Defines standard interfaces for querying Hermes, parsing updates, and submitting transactions, ensuring consistency across developer tools and reducing integration errors.
On-Chain Verification Interface Standard
Standard interface for the on-chain Pyth receiver contract, specifying functions for verifying cross-chain messages, parsing price updates, and exposing data to consuming contracts. Forms the integration contract that all DeFi protocols must implement correctly to consume Pyth data safely.
Fallback Oracle Interface Standard
Proposed standard for a unified interface allowing DeFi protocols to seamlessly switch between Pyth and a secondary oracle. Defines abstract contract behavior for staleness checks and failover logic, promoting resilient integration patterns for lending markets and perpetual protocols.
Price Feed Identifier Standard
Specification for deterministic derivation of a Pyth price feed ID from a human-readable feed name. Critical for integrators to avoid hardcoding magic bytes and to ensure they are consuming the correct feed, reducing the risk of misconfiguration in production deployments.