On July 29th, 2026, the Pyth DAO, via the OP-PIP-123.V2, approved the usage of 1/3 of the Pyth DAO Treasury to monthly purchases PYTH tokens. These purchases are administered and executed by the Pythian Council.
On July 29th, 2026, the Pythian Council Ops Multisig received the following from the Pyth DAO Treasury:
Subsequently, the Pythian Council, exercising no independent discretion and acting only pursuant to the DAO’s instructions within the OP-PIP parameters, executed the following transactions:
It would be good to set a fixed date for purchases and post on that date. For example, like purchasing on the 1st of every month and posting on the 1st.
Thanks for the suggestion. Just to clarify, the intention here is indeed to use a DCA approach over a longer period of time, rather than have the Council make a single discretionary purchase at some random point during the month.
The framework was established through OP-PIP-87 and the subsequent monthly purchase PIPs. The mandate gives the Council some flexibility in how the purchases are executed, with the objective of accumulating PYTH efficiently on the secondary market. This can include limit orders, smaller market orders, and standard swaps when appropriate, particularly for lower volumes. The July purchase was executed under OP-PIP-123.V2.
While the report presents the monthly activity as a consolidated purchase, the actual execution is structured around this longer-term DCA approach. All of the details are also included in the spreadsheet linked in the report.
As for the timing of the reports, I’ve been handling these reports for the past several months, and our goal is always to have them published as close as possible to the end of the month. That said, because we operate through a multisig structure, there are sometimes a few additional steps involved that can result in the report being published a few days into the following month.
Importantly, this doesn’t mean the activity is happening behind the scenes. All transactions involving the Pythian Council multisig can be followed on-chain as they happen, including the DCA executions through Jupiter DCA, which is integrated directly with the Squads multisig. So the transactions are publicly verifiable in real time, even if the consolidated report itself takes a few extra days to publish.
Thank you for your reply. I do not mean to deny your efforts. I was simply thinking it would be good to post on a fixed schedule, but your response has helped me understand. Have a nice day.