# About the Pythian Council **URL:** \ **Category:** Pythian Council\ **Created:** [April 22, 2024, 2:52pm UTC](https://forum.pyth.network/t/about-the-pythian-council/10 "2024-04-22T14:52:52Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Pyth-DAO](https://avatars.discourse-cdn.com/v4/letter/p/edb3f5/32.png) [@Pyth-DAO](https://forum.pyth.network/u/Pyth-DAO)\ **Post date:** [April 22, 2024, 2:52pm UTC](https://forum.pyth.network/t/about-the-pythian-council/10/1 "2024-04-22T14:52:52Z")
The [Pythian Council](https://github.com/pyth-network/governance/tree/main/docs/councils/pythian/election) is in charge of approving oracle program updates or changes to the data request fees. As defined in the adopted [Pyth DAO Constitution](https://github.com/pyth-network/governance/blob/main/docs/constitution/pyth-dao-constitution.md), the Pythian Council is made of 8 members who are signers of the Pythian Multisig Wallet. The Pythian Multisig Wallet has powers to perform actions that are delegated to it by the Pyth DAO. The Operational PIPs delegated to the Pythian Council involve: - the upgrade of the oracle program - the upgrade of the verification program for each of the blockchains where Pyth data is accessible - the setting of data request fees per blockchain, as well as other protocol or network fees - the management of PGAS allocation and delegation to validators The execution of such actions by the Pythian Council requires 7-of-9 approval (with one of the default multisig holders being the Operations Wallet itself) ---
**Author:** ![Pyth-DAO](https://avatars.discourse-cdn.com/v4/letter/p/edb3f5/32.png) [@Pyth-DAO](https://forum.pyth.network/u/Pyth-DAO)\ **Post date:** [May 9, 2024, 2:34pm UTC](https://forum.pyth.network/t/about-the-pythian-council/10/4 "2024-05-09T14:34:29Z")
Closed on May 9, 2024, 2:34pm UTC ---
**Author:** ![Pyth-DAO](https://avatars.discourse-cdn.com/v4/letter/p/edb3f5/32.png) [@Pyth-DAO](https://forum.pyth.network/u/Pyth-DAO)\ **Post date:** [May 9, 2024, 4:44pm UTC](https://forum.pyth.network/t/about-the-pythian-council/10/6 "2024-05-09T16:44:10Z")
Pinned on May 9, 2024, 4:44pm UTC ---
**Author:** ![Pyth-DAO](https://avatars.discourse-cdn.com/v4/letter/p/edb3f5/32.png) [@Pyth-DAO](https://forum.pyth.network/u/Pyth-DAO)\ **Post date:** [July 20, 2026, 11:06am UTC](https://forum.pyth.network/t/about-the-pythian-council/10/7 "2026-07-20T11:06:13Z")
**Pythian Council Ops Multisig** In addition to the main Pythian Multisig, [OP-PIP-87](https://forum.pyth.network/t/passed-op-pip-87-pyth-token-phase-2-pyth-strategic-reserve/2293) established a dedicated **Pythian Council Ops Multisig** for treasury operations: **Address:** `GAdn7TZhszf5KTfwNRx3A2nP6KCRFEWucZubgdEqbJA2` **Purpose:** Execute PYTH token purchases on behalf of the DAO Treasury. The DAO transfers funds (SOL/USDC) to this multisig, the Pythian Council executes swaps to PYTH following OP-PIP-87 guidelines (≤5% slippage), and purchased PYTH tokens are returned to the DAO Treasury. **Threshold:** 5-of-8 This operational multisig allows the Council to act as the executing arm for treasury management without requiring per-transaction governance votes, while maintaining full transparency through post-execution reporting.