Pyth DAO · 277 topics · updated 19m ago

Governance

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

All Proposals Ideas Council Discussions Announcements Reports

PASSEDProposalProposalsMay 2024
OP-PIP-6: Upgrade Entropy contracts on all the testnet chains
Abstract Upgrade the Entropy contracts to allow users to register a callback when requesting random numbers. This callback is invoked once the request is fulfilled. Rationale The upgrade enhances the developer experience by reducing the interaction to a single transaction.…
1 reply201 views12 likes
PASSEDProposalProposalsMay 2024
OP-PIP-5: Improve usability of Pyth Solana Receiver
Abstract Upgrade the Pyth Solana Receiver on Solana to support new features. Rationale We want the Pyth Solana Receiver to support these new features to improve its usability. Moreover, these features will enable the option to build a push oracle on top of the Pyth Solana…
1 reply235 views12 likes
PASSEDProposalProposalsMay 2024
OP-PIP-4: Accept Pyth Solana receiver governance authority
Abstract Accept Pyth Solana receiver governance authority to manage the contract. Rationale The Pythian council need to accept the governance authority from the current owner of the Pyth Solana receiver contract to manage the contract. This is a requirement for official…
1 reply180 views14 likes
PASSEDProposalProposalsMay 2024
OP-PIP-3: Deactivate stake accounts
Abstract Deactivate stake accounts associated with inactive validators on Pythnet. Rationale Inactive validators interfere with block production. Description Two Pythnet validators have been offline for multiple epochs. The operators of these two validators are unable to bring…
1 reply187 views8 likes
PASSEDProposalProposalsMay 2024
OP-PIP-2: Upgrade Mode Contract
Abstract Upgrade the current Pyth oracle contract on Mode to be able to collect a share of the gas fees spent when updating a price on-chain. Rationale Collect the revenue generated from usage of the oracle by downstream applications at no extra cost to users (paid out from the…
1 reply220 views15 likes
PASSEDProposalProposalsMay 2024
OP-PIP-1: Upgrade Blast Contract
Abstract Upgrade the current Pyth oracle contract on Blast to be able to collect a share of the gas fees spent when updating a price on-chain. Rationale Collect the revenue generated from usage of the oracle by downstream applications at no extra cost to users (paid out from the…
1 reply221 views10 likes
PASSEDProposalProposalsMay 2024
CO-PIP-2: Rectify the Owner Field for Three Bricked Locked Token Accounts
Abstract During the initial distribution of Pyth locked tokens, incorrect addresses (Token Addresses) were used instead of Solana Wallet Addresses for three Token Holders due to a clerical error. This PIP would update the Staking Program to enable replacement of these Token…
1 reply253 views12 likes
PASSEDProposalProposalsMay 2024
CO-PIP-1 : Adoption of the Pyth DAO Constitution
Abstract This document ("PIP-1”) proposes the adoption of a decision framework for the Pyth DAO and the governing framework for the holders of $PYTH, the “Pyth DAO Constitution”, as formulated here: governance/docs/constitution/pyth-dao-constitution.md at…
1 reply337 views25 likes

121–128 of 128

← NewerOlder →

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

OP-PIP-5: Improve usability of Pyth Solana Receiver

OP-PIP-4: Accept Pyth Solana receiver governance authority

OP-PIP-3: Deactivate stake accounts

OP-PIP-2: Upgrade Mode Contract

OP-PIP-1: Upgrade Blast Contract

CO-PIP-2: Rectify the Owner Field for Three Bricked Locked Token Accounts

CO-PIP-1 : Adoption of the Pyth DAO Constitution