# \[ONGOING\] OP-PIP-136: Pyth Strategic Reserve V2
**URL:** https://forum.pyth.network/t/ongoing-op-pip-136-pyth-strategic-reserve-v2/2711
**Category:** Proposals
**Tags:** operational-pip
**Created:** [September 24, 2026, 5:02pm UTC](https://forum.pyth.network/t/ongoing-op-pip-136-pyth-strategic-reserve-v2/2711 "2026-09-24T17:02:11Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@KemarTiti](https://forum.pyth.network/u/KemarTiti)
#### Post date: [September 24, 2026, 5:02pm UTC](https://forum.pyth.network/t/ongoing-op-pip-136-pyth-strategic-reserve-v2/2711/1 "2026-09-24T17:02:11Z")
## **Abstract**
Following the discussion and positive feedback in the [Strategic Reserve V2 Ideas Bank post](https://forum.pyth.network/t/pyth-strategic-reserve-v2-aligning-pyth-accumulation-with-pyth-pro-revenue/2696), this Operational PIP proposes to update the Strategic Reserve framework established under [OP-PIP-87](https://forum.pyth.network/t/passed-op-pip-87-pyth-token-phase-2-pyth-strategic-reserve/2293).
OP-PIP-136 would:
- replace the recurring one-third-of-Treasury purchase mechanism;
- transfer the current eligible non-PYTH DAO Treasury balance to the Pythian Council Ops Multisig;
- coordinate future PYTH accumulation with eligible DAO revenue and non-PYTH Treasury assets;
- remove the need for separate monthly votes for the same mechanical activity; and
- preserve the existing execution guardrails and prohibition on selling accumulated PYTH.
This proposal does not amend the Pyth DAO Constitution or change any existing revenue share, operator assignment, or payment term.
**Realms proposal:** [OP-PIP-136: Pyth Strategic Reserve V2 | Pyth Governance](https://v2.realms.today/dao/4ct8XU5tKbMNRphWy4rePsS9kBqPhDdvZoGpmprPaug4/proposal/2qkHmHEi7r5Cz5tG2u2VNtTbD5XFmZGfdQicDhXFqAKo)
## Description
1. **Initial Treasury transfer**
Upon approval, the DAO will transfer the current eligible non-PYTH Treasury balance to the Pythian Council Ops Multisig: `GAdn7TZhszf5KTfwNRx3A2nP6KCRFEWucZubgdEqbJA2`
The current eligible balances are:
- 323,428.56 USDC
- 90 SOL
The corresponding Realms instructions will transfer:
- USDC from the DAO Treasury USDC account (`5Unq3fgfSNdyeGjiq2Pu5XAQUJWo2rauKGErbUyxqUGe`)
- SOL from the DAO Treasury wallet (`Gx4MBPb1vqZLJajZmsKLg8fGw9ErhoKsR8LeKcCKFyak`)
- to the Pythian Council Ops Multisig (`GAdn7TZhszf5KTfwNRx3A2nP6KCRFEWucZubgdEqbJA2`)
The Council must convert the eligible assets into PYTH under the approved execution rules and return all purchased PYTH to the official DAO Treasury.
1. **Ongoing Treasury management**
Following the initial transfer, future eligible non-PYTH DAO revenue and assets may be made available to the Pythian Council Ops Multisig for conversion into PYTH without requiring a separate monthly DAO vote.
Eligible revenue may include the DAO’s approved share of:
- Pyth Pro revenue;
- Listing as a Service revenue;
- Pyth Data Marketplace revenue;
- Pyth Indices revenue;
- Pyth Core fees;
- Pyth Entropy fees; and
- other DAO-owned assets once properly repatriated.
This proposal applies only to the DAO’s existing approved share and does not change any product’s commercial terms.
Direct PYTH distributions remain governed by the existing payment framework and will be held by the DAO. They are not described as open-market purchases.
1. **Execution rules**
The existing OP-PIP-87 guardrails remain unchanged:
- maximum 5% slippage per transaction;
- maximum $25,000 per transaction;
- preference for aggregators such as Jupiter;
- limit orders at least 0.1% below displayed market price; and
- public transaction proofs.
The Pythian Council and Ops Multisig act only as mechanical execution agents. They may not sell accumulated PYTH, borrow against it, use leverage or derivatives, or distribute it without a separate DAO-approved proposal.
1. **Reporting**
The Pythian Council will continue publishing monthly reports covering:
- assets received and converted;
- PYTH purchased;
- execution prices, fees, and slippage;
- transaction links;
- unconverted balances; and
- confirmation that no accumulated PYTH was sold.
## Implementation
Upon passage:
1. The initial eligible Treasury balance will be transferred to the Council Ops Multisig through the Realms instructions attached to this vote.
2. The Council will execute the conversion under the existing guardrails.
3. All purchased PYTH will be returned to the official DAO Treasury.
4. Future eligible non-PYTH DAO revenue will follow the same process.
5. No further recurring one-third purchase proposals should be required.
6. OP-PIP-136 will supersede the conflicting Treasury-management and recurring-purchase mechanics of OP-PIP-87.
**Realms proposal:** [OP-PIP-136: Pyth Strategic Reserve V2 | Pyth Governance](https://v2.realms.today/dao/4ct8XU5tKbMNRphWy4rePsS9kBqPhDdvZoGpmprPaug4/proposal/2qkHmHEi7r5Cz5tG2u2VNtTbD5XFmZGfdQicDhXFqAKo)
---
### Author:  [@scp](https://forum.pyth.network/u/scp)
#### Post date: [September 25, 2026, 6:43am UTC](https://forum.pyth.network/t/ongoing-op-pip-136-pyth-strategic-reserve-v2/2711/2 "2026-09-25T06:43:17Z")
hi @KemarTiti could you mind to look into my reply in [Pyth Strategic Reserve V2: Aligning PYTH Accumulation with Pyth Pro Revenue - #3 by scp](https://forum.pyth.network/t/pyth-strategic-reserve-v2-aligning-pyth-accumulation-with-pyth-pro-revenue/2696/3) and comment on it?
Thanks a lot. I like this update. From SCP.
---
### Author:  [@Mersault](https://forum.pyth.network/u/Mersault)
#### Post date: [September 26, 2026, 11:08pm UTC](https://forum.pyth.network/t/ongoing-op-pip-136-pyth-strategic-reserve-v2/2711/3 "2026-09-26T23:08:21Z")
Fully support OP-PIP-136. This is exactly what needs to be automated.