Constitution updates

docs/constitution/pyth-dao-constitution.md

@@ -6,15 +6,15 @@
 - **PIP:** Pyth Improvement Proposal
 - **Pyth DAO Treasury:** all tokens held in the wallets at the following addresses: `Gx4MBPb1vqZLJajZmsKLg8fGw9ErhoKsR8LeKcCKFyak` for the native SOL token and `9HKkxg5dpqjUEW1U2r76SpQCH7uvDMciytNYxrpwMVNc` for the SPL Token, that is directly governed by the Pyth DAO via on-chain voting
 - **Pyth Forum:** the system adopted by the Pyth DAO to manage PIPs, organize the voting process and provide connectivity to the governance contract on the Solana Blockchain, located here: [https://forum.pyth.network/](https://forum.pyth.network/)
-- **Pythian Multisig Wallet:** smart contract wallet, at the following address `6oXTdojyfDS8m5VtTaYB9xRCxpKGSvKJFndLUPV3V3wT`, signed by the elected members of the Pythian Council. The Pythian Council is described in further detail below.
-- **Price Feed Multisig Wallet:** smart contract wallet, at the following address `CPUZ9njbfxjqrsx713gEk8KYatvoz1Y4hvs4a5UQKEiu` signed by the elected members of the Price Feed Council. The Price Feed Council is described in further detail below.
-- **Community Multisig Wallet:** smart contract wallet, at the following address `GKuPcXtNRJwZGrJ8tV25jSbLHZe71BUdUXVzjGLXkSt9` signed by the elected members of the Community Council. The Community Council is described in further detail below.
-- **Operations Wallets:** wallets, at the following addresses `opsLibxVY7Vz5eYMmSfX8cLFCFVYTtH6fr6MiifMpA7`, `ACzP6RC98vcBk9oTeAwcH1o5HJvtBzU59b5nqdwc7Cxy` and `Ef7AjJzDXK6Tn2gYuMvL9YdXATV29b8PwpsT1yoPokTC`, that are used by the Pythian Council, the Price Feed Council and the Community Council respectively to submit PIPs on-chain. These wallets can be used by automated processes to make proposals or by council members to propose large proposals that would otherwise require many hardware wallet signatures.
+- **Pythian Multisig Wallet:** smart contract wallet, at the following address `6oXTdojyfDS8m5VtTaYB9xRCxpKGSvKJFndLUPV3V3wT`, signed by the elected members of the Pythian Council. The Pythian Council is described in further detail below
+- **Price Feed Multisig Wallet:** smart contract wallet, at the following address `CPUZ9njbfxjqrsx713gEk8KYatvoz1Y4hvs4a5UQKEiu` signed by the elected members of the Price Feed Council. The Price Feed Council is described in further detail below
+- **Community Multisig Wallet:** smart contract wallet, at the following address `GKuPcXtNRJwZGrJ8tV25jSbLHZe71BUdUXVzjGLXkSt9` signed by the elected members of the Community Council. The Community Council is described in further detail below
+- **Operations Wallets:** wallets, at the following addresses `opsLibxVY7Vz5eYMmSfX8cLFCFVYTtH6fr6MiifMpA7`, `ACzP6RC98vcBk9oTeAwcH1o5HJvtBzU59b5nqdwc7Cxy` and `Ef7AjJzDXK6Tn2gYuMvL9YdXATV29b8PwpsT1yoPokTC`, that are used by the Pythian Council, the Price Feed Council and the Community Council respectively to submit PIPs on-chain. These wallets can be used by automated processes to make proposals or by council members to propose large proposals that would otherwise require many hardware wallet signatures
 - **PGAS:** utility token native to the Pythnet Appchain, governed by the Pyth DAO
 - **Pythnet Appchain:** blockchain instance dedicated to the production of the Pyth data, governed by the Pyth DAO
 - **Pyth Lazer:** system dedicated to the production of the Lazer data, governed by the Pyth DAO
-- **Pyth Pro:** subscription service for off-chain access to Pyth data, administered by Douro Labs on behalf of the Pyth DAO pursuant to CO-PIP-9
-- **Pyth Data Marketplace (Marketplace):** distribution platform for third-party institutional datasets, operated by Douro Labs on behalf of the Pyth DAO pursuant to CO-PIP-10. The Pyth Data Marketplace datasets is independent of Pyth Pro and thus not covered by Oracle Integrity Staking
+- **Pyth Pro:** subscription service for off-chain access to Pyth data, operated by Douro Labs on behalf of the Pyth DAO pursuant to the Pyth Pro Governance section of this Constitution
+- **Pyth Data Marketplace (Marketplace):** distribution platform for third-party institutional datasets, operated by Douro Labs on behalf of the Pyth DAO pursuant to the Pyth Data Marketplace Governance section of this Constitution. Marketplace datasets are not covered by Oracle Integrity Staking
 - **Pyth Express Relay (ER):** protocol instance that enables DeFi applications to auction off the rights to swap tokens
 - **Pyth Entropy (Entropy):** protocol instance that provides applications with provably random numbers
 - **Oracle Integrity Staking (OIS):** protocol that leverages PYTH tokens specifically staked for the purpose of improving the integrity of the pyth data
@@ -51,7 +51,7 @@ Each PIP must be labeled as Constitutional PIPs or Operational PIPs as described
     - the election of members of the Community Council
     - the management of the Pyth DAO Treasury
     - the exceptional removal and replacement of a council member
-    - the formal objection to a publisher to the Pyth Data Markeplace onboarding pursuant to the Marketplace Governance Process
+    - the formal objection to a Pyth Data Marketplace publisher onboarding pursuant to the Marketplace Governance Process
   - 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 or Lazer data are accessible
@@ -65,7 +65,7 @@ Each PIP must be labeled as Constitutional PIPs or Operational PIPs as described
     - the setting of pool capacity parameters in OIS
     - the setting of delegation fee for stake delegators in OIS
     - the determination of slashing amounts from the amount staked in OIS in compliance with the slashing rules and procedures defined by the DAO in [https://docs.pyth.network/home/oracle-integrity-staking/slashing-rulebook](https://docs.pyth.network/home/oracle-integrity-staking/slashing-rulebook)
-    - the formal objection to a publisher to the Pyth Data Markeplace onboarding pursuant to the Marketplace Governance Process
+    - the formal objection to a Pyth Data Marketplace publisher onboarding pursuant to the Marketplace Governance Process
   - Operational PIPs delegated to the Price Feed Council involve:
     - the management of the list of price feeds available through Pyth
     - the selection of publishers and the setting of the minimum number of such publishers per price feed
@@ -103,6 +103,41 @@ The Pyth DAO is able to vote directly on-chain on the submitted PIP for 7 days.
 
 The PIP is then fully executed and implemented. Any on-chain actions in the implementation plan will execute automatically in this step. The Pyth DAO LLC, council members and other service providers of the Pyth DAO LLC will take any necessary off-chain actions to implement PIPs which have passed.
 
+## Pyth Pro Governance
+
+### Operator
+
+Douro Labs is assigned as operator of Pyth Pro on behalf of the Pyth DAO. This assignment includes commercial operations, infrastructure, customer support, and related services for Pyth Pro subscriptions.
+
+**Listing as a Service (LaaS):** Douro Labs is authorized to offer Listing as a Service as a commercial model for listing feeds requested by protocols and token issuers pursuant to OP-PIP-98.
+
+### Revenue Distribution
+
+| Product | DAO Share | Operator Share |
+|---------|-----------|----------------|
+| Pyth Pro Subscriptions | 60% | 40% |
+| Listing as a Service (LaaS) | 90% | 10% |
+
+### Payment Terms
+
+Payments to the Pyth DAO Treasury shall be made monthly, within 7 days from month-end.
+
+Payments may be made in USDC, PYTH tokens, or a combination thereof, at the Operator's discretion.
+
+**When paying fully or partially in PYTH:**
+
+1. **Pricing:** The PYTH amount shall be calculated using the average daily closing price of the PYTH/USD Pyth Lazer feed across all calendar days in the payment month.
+
+2. **Minimum Value Guarantee:** The PYTH amount delivered shall not be less than the USD-equivalent value owed per the calculation above.
+
+### Reporting
+
+Douro Labs shall provide monthly reports including gross revenue, DAO share calculation, and payment currency breakdown. Reports shall be published in the Pyth Pro forum section.
+
+### Termination
+
+The Pyth DAO may revoke Douro Labs' mandate to operate Pyth Pro via a subsequent Constitutional PIP.
+
 ## Pyth Data Marketplace Governance
 
 ### Operator
@@ -117,21 +152,22 @@ Douro Labs is assigned as operator of the Pyth Data Marketplace on behalf of the
 ### Revenue Distribution
 
 Of all proceeds generated by Douro Labs from Marketplace operations:
-
 | Recipient | Share |
 |-----------|-------|
 | Pyth DAO Treasury | 60% |
 | Douro Labs | 40% |
 
-Payments shall be made monthly.
+### Payment Terms
+
+Terms are identitical to those related to Pyth Pro.
 
 ### Marketplace Governance Process (Optimistic Approval)
 
-Publisher onboardings follow an optimistic approval process — onboardings proceed unless formally objected to and blocked.
+Publisher onboardings follow an optimistic approval process - onboardings proceed unless formally objected to and blocked.
 
 **Step 1: Onboarding Notice**
 
-Douro Labs posts all new publisher onboardings in a dedicated "Marketplace Onboardings" forum section. Each notice must include:
+Douro Labs posts all new publisher onboardings in a dedicated forum section "Marketplace Onboardings". Each notice must include:
 
 - Publisher name
 - Dataset category
@@ -141,9 +177,9 @@ Douro Labs posts all new publisher onboardings in a dedicated "Marketplace Onboa
 
 Posting starts a 30-day window.
 
-**Step 2: Informal Q&A Period (Days 1-30)**
+**Step 2: Informal Discussion Period (Days 1-30)**
 
-Anyone — Council members, token holders, community — may ask questions on the forum post. Douro Labs responds and clarifies. Most onboardings resolve here with no objection.
+Anyone - Council member, token holder, community - may engage in a discussion related to the content of the forum post.
 
 **Step 3: Formal Objection**
 
@@ -154,27 +190,27 @@ If concerns are not resolved through Q&A, two objection paths exist:
 | Pythian Council | Council resolution | Super Majority (6/9) votes to object |
 | Token Holders | Operational PIP | Standard quorum + majority votes to object |
 
-The objection must pass — reach quorum and achieve majority — to pause the onboarding. A failed objection vote = onboarding proceeds as planned.
+The objection must pass - reach quorum and achieve majority - to pause the onboarding. A failed objection vote = onboarding proceeds as planned.
 
 **Step 4: Resolution Process**
 
 If an objection passes:
 
 1. Douro Labs has 14 days to present a structured response addressing concerns
 2. The same body that objected votes on the resolution:
-   - Council objected → Council votes
-   - DAO objected via OP-PIP → DAO votes via follow-up OP-PIP
+   - Council objected -  Council votes
+   - DAO objected via OP-PIP -  DAO votes via follow-up OP-PIP
 
 Possible outcomes:
-- **Approve anyway** — Concerns addressed, onboarding proceeds
-- **Reject** — Onboarding blocked
-- **Renegotiate** — Sent back with specific conditions
+- **Approve anyway** - Concerns addressed, onboarding proceeds
+- **Reject** - Onboarding blocked
+- **Renegotiate** - Sent back with specific conditions
 
 If no resolution vote occurs within 30 days of Douro's response, the objection lapses and onboarding proceeds.
 
 ### Reporting
 
-Douro Labs shall provide monthly reports on Pyth Data Marketplace operations, aligned with Pyth Pro reporting cadence. Reports shall include:
+Douro Labs shall provide monthly reports on Marketplace operations, aligned with Pyth Pro reporting cadence. Reports shall include:
 
 - Total Marketplace revenue for the period
 - DAO share paid
@@ -191,7 +227,7 @@ Douro Labs shall disclose any material financial relationship with Marketplace p
 
 ### Termination
 
-The Pyth DAO may revoke Douro Labs' mandate to operate the Pyth Data Marketplace via a subsequent Constitutional PIP.
+The Pyth DAO may revoke Douro Labs' mandate to operate the Marketplace via a subsequent Constitutional PIP.
 
 ## Council Election Process & Voting Procedures