Pythscan
Pyth DAO · 277 topics · updated 24m ago

Governance

Proposals, ideas, and council activity from the Pyth DAO, indexed from forum.pyth.network.

AllProposalsIdeasCouncilDiscussionsAnnouncementsReports
  1. PASSEDProposalProposalsFeb 11

    OP-PIP-93: Q1 2026 Pyth Core Fee Implementation (EVM Chains)

    Abstract Implement price feed update fees on Pyth Core across 70 EVM chains as outlined in the Q1 2026 — Pyth Core Onchain Fees discussion. Rationale Following the mandate from OP-PIP-87 and the Pyth Token Phase 2 discussion, the Pythian Council is responsible for implementing…

    0 replies73 views1 like
  2. PASSEDProposalProposalsFeb 9

    OP-PIP-92: Q1 2026 Pyth Express Relay Fee Implementation

    Abstract Implement the Q1 2026 fee structure for Pyth Express Relay across all whitelisted tokens. This proposal updates the auction server’s minimum_platform_fee_list configuration to apply protocol fees based on a three-tier pricing matrix: stablecoins at 1 bps, major tokens at…

    1 reply67 views5 likes
  3. PASSEDProposalProposalsFeb 3

    OP-PIP-91: PYTH Token Phase 2 — Purchases #3

    Abstract Transfer 33% of the current Pyth DAO Treasury to the Pythian Council (Ops Multisig) in order to execute the purchase of PYTH tokens as proposed and approved in OP-PIP-87. Description Following the distribution of the revenues from Pyth Pro for January 2026 by Douro Labs,…

    0 replies132 views
  4. PASSEDProposalProposalsJan 31

    OP-PIP-90: Upgrade Wormhole Core contract on Solana Mainnet

    Abstract Perform a governance upgrade of the Wormhole Core contract on Solana Mainnet to fix an issue with guardian set expiration handling. The upgrade enables setting a non-zero guardian set TTL (24 hours), allowing upcoming Wormhole guardian key rotations to be executed…

    0 replies55 views1 like
  5. PASSEDProposalProposalsJan 28

    OP-PIP-89: Upgrade Lazer Contract on Sui (testnet)

    Abstract Perform an test upgrade on a testnet deployment of Sui Lazer contract to ensure that the process works correctly. The update itself only changes the included version number - goal is to test whether the contract can successfully execute governance action. Rationale Sui…

    0 replies85 views1 like
  6. PASSEDProposalProposalsJan 8

    OP-PIP-88: PYTH Token Phase 2 — Purchases #2

    Abstract Transfer 33% of the current Pyth DAO Treasury to the Pythian Council (Ops Mulitsig) in order to execute the purchase of PYTH tokens as proposed and approved in the OP-PIP-87. Description Following the distribution of the revenues from Pyth Pro for December 2025 by Douro…

    1 reply321 views3 likes
  7. PASSEDProposalProposalsDec 2025

    OP-PIP-87: PYTH Token Phase 2 — $PYTH Strategic Reserve

    Abstract Following this discussion (**Pyth Token Phase 2)** and previous community interest around that topic (1, 2), this Operational Proposal aims to: Establish a DAO-owned $PYTH Strategic Reserve using the Pyth DAO Treasury as specified below Empower the Pythian Council to…

    2 replies439 views8 likes
  8. PASSEDProposalProposalsDec 2025

    OP-PIP-85: 4th Price Feed Council Election

    Abstract This proposal aims to: Approve the 5 nominees for the 4th Price Feed Council Distribute the stipend to the 3rd Price Feed Council members that have met the threshold Continue the previously approved stipend of 315,000 PYTH to be shared among Price Feed Council Members…

    1 reply208 views3 likes
  9. PASSEDProposalProposalsDec 2025

    OP-PIP-84: 4th Pythian Council Election

    Abstract This proposal aims to: Approve the 6 nominees for the 4th Pythian Council Distribute the stipend to the 3rd Pythian Council members that have met the threshold Continue the previously approved stipend of 100,000 PYTH to be shared among Pythian Council Members Description…

    1 reply126 views3 likes
  10. PASSEDProposalProposalsNov 2025

    OP-PIP 86: Set stake account for a Market Data Provider

    Abstract This proposal aims to assign stake account 8BYLDKDhAzbf6kB46Jkj86nvKBts2FUCBmPxTv63bRN6 to Market Data Provider (MDP) 5pqDy8FdBBLUVKSs6xoxXmrBvgRfhNVe1wB3vyLFTVeM in the context of Oracle Integrity Staking (OIS). Rationale When OIS launched in September 2024, most MDPs…

    0 replies54 views1 like
  11. PASSEDProposalProposalsNov 2025

    CO-PIP 9 :: Proposal to Assign Douro Labs as Administrator and Initial Distributor for Subscriptions to Pyth Data Off-chain

    Summary On the back of the discussion here,Douro Labs LLC (together, with its subsidiaries and affiliates, “Douro Labs”) formally proposes that the Pyth DAO: provide to Douro Labs certain services through the Pyth DAO’s operation of the Pyth Network, the result of which is access…

    7 replies539 views18 likes
  12. PASSEDProposalProposalsOct 2025

    OP-PIP-83: Upgrade Entropy contracts on all mainnet chains

    Abstract Upgrade the Entropy contracts to fix a bug in the callback gas handling logic. This fix ensures that callbacks are only marked as failed when sufficient gas was provided, regardless of the revert code returned. Rationale The previous implementation would mark callbacks…

    0 replies58 views1 like
  13. PASSEDProposalProposalsOct 2025

    OP-PIP-82: Upgrade Entropy contracts on all the testnet chains

    Abstract Upgrade the Entropy testnet contracts to fix a bug in the callback gas handling logic. This fix ensures that callbacks are only marked as failed when sufficient gas was provided, regardless of the revert code returned. If successful, a similar proposal will be raised for…

    0 replies52 views1 like
  14. ProposalProposalsSep 2025

    OP-PIP-82: Pythnet Upgrade to Enable Zero Value in Confidence Interval

    Abstract This proposal upgrades the Pyth oracle program to support aggregating a publisher prices with zero CI. Rationale There are some feeds that are being sourced from third-party APIs (ACRED/USD.NAV) or smart contracts (wstETH/stETH.rr) that have fixed values and because the…

    0 replies46 views2 likes
  15. ProposalProposalsSep 2025

    OP-PIP-81: Community Council Budget Request for second half of Council term

    Edit; Vote is now live! OP-PIP-81: Community Council 2nd Term | Pyth Governance** Abstract** This proposal outlines the Community Councils budget request for the last 6 months of the Council’s term. The budget is required to execute the initiatives outlined in this report. This…

    0 replies266 views6 likes
  16. ProposalProposalsJul 2025

    [DISCUSSION] CO-PIP-7: Transfer bricked locked token accounts so their legitimate owner can access them

    Abstract During the initial distribution of Pyth locked tokens and during subsequent distributions of rewards as part of the Pyth Reward Program, a Market Data Provider received locked PYTH tokens in a wallet which can’t interact with smart contracts on the Solana blockchain and…

    0 replies147 views3 likes
  17. PASSEDProposalProposalsJul 2025

    OP-PIP-80: Entropy v2 Mainnet Upgrade (Abstract)

    Abstract This is a follow up proposal from the OP-PIP-79. The last proposal successfully upgraded all Entropy mainnet contracts but the one on Abstract. Rationale The v2.0 upgrade will introduce significant quality of life improvements for all Entropy users. Description Entropy…

    0 replies63 views2 likes
  18. PASSEDProposalProposalsJul 2025

    OP-PIP-79: Entropy v2 Mainnet Upgrade

    Abstract Upgrade the Entropy contracts on mainnet to version 2.0. This follows the testnet upgrade done here. Rationale The v2.0 upgrade will introduce significant quality of life improvements for all Entropy users. Description Entropy version 2.0 introduces several developer…

    0 replies65 views3 likes
  19. PASSEDProposalProposalsJul 2025

    OP-PIP-78: Discontinue 1 Pythnet validator node

    Abstract This proposal aims to off-board (destake) one last validator from Pythnet. This is the 6th proposal for validator off-boarding. The first destaking proposal is available here. The second destaking proposal is available here. The third destaking proposal is available…

    0 replies40 views
  20. PASSEDProposalProposalsJun 2025

    OP-PIP-77: Discontinue 1 Pythnet validator node

    Abstract This proposal aims to off-board (destake) one last validator from Pythnet. This is the 5th proposal for validator off-boarding. The first destaking proposal is available here. The second destaking proposal is available here. The third destaking proposal is available…

    0 replies54 views
  21. PASSEDProposalProposalsJun 2025

    OP-PIP-76: Discontinue 1 Pythnet validator node

    Abstract This proposal aims to off-board (destake) one last validator from Pythnet. This is the 4th and last proposal for validator off-boarding. The first destaking proposal is available here. The second destaking proposal is available here. The third destaking proposal is…

    2 replies75 views3 likes
  22. PASSEDProposalProposalsJun 2025

    OP-PIP-75: Discontinue 36 Pythnet validator nodes

    Abstract This proposal aims to off-board (destake) 36 validators from Pythnet. This is the 2nd of a few upcoming proposals for validator off-boarding. The first destaking proposal is available here. The second destaking proposal is available here. Rationale As part of an ongoing…

    0 replies88 views4 likes
  23. PASSEDProposalProposalsMay 2025

    OP-PIP-74: Discontinue 30 Pythnet validator nodes

    Abstract This proposal aims to off-board (destake) 30 validators from Pythnet. This is the 2nd of a few upcoming proposals for validator off-boarding. The first destaking proposal is available here. Rationale As part of an ongoing effort to improve Pythnet reliability and reduce…

    0 replies72 views1 like
  24. PASSEDProposalProposalsMay 2025

    OP-PIP-74: Delegate PGAS to 1 new validator: Anza

    Abstract This proposal aims to onboard 1 new validatorsto Pythnet. This validator, ran by Anza, will be delegated 100,000 PGAS to operate. Rationale As part of an ongoing effort to improve Pythnet reliability and reduce the overhead costs to data publishers, a new infrastructure…

    0 replies42 views3 likes
25–48 of 128
← NewerOlder →