Abstract
This Operational PIP proposes to:
-
Authorize Douro Labs to offer Listing as a Service (LaaS) — a commercial model for Pyth Pro to list feeds requested by Protocols and Token Issuers
-
Establish a 90/10 revenue share (DAO/Douro) for LaaS proceeds
-
Formalize reporting requirements aligned with existing Pyth Pro cadence
LaaS formalizes an existing practice that has already generated $300,000+ in listing revenue since 2025. This proposal converts ad-hoc arrangements into a formal process and a predictable, recurring revenue stream for the DAO.
Rationale
Projects wanting certain tokens supported on Pyth Lazer submit requests through the Price Feed Council. In many cases, they pay one-time fees ($20,000–$30,000) to accelerate listing and ensure ongoing support (BIO, ICON).
CO-PIP-5 authorized Douro Labs to administer the Pyth Pro (Lazer) feed catalog, but there’s no formal framework for charging listing fees. This creates ambiguity for both Douro Labs and prospective customers.
Why this matters
-
For the DAO: Additional revenue stream with 90% flowing to Treasury
-
For customers: Clear terms, professional service
-
For the ecosystem: Faster listing turnaround, better feed coverage
Key Terms
- Authorization
Douro Labs is authorized to sell Pyth Pro (Lazer) feed listings as a commercial service (“LaaS”). This includes:
-
Marketing and selling feed listings
-
Negotiating contracts with customers
-
Setting pricing based on feed complexity and support requirements
-
Managing listing lifecycle (additions, maintenance, removals)
- Pricing
Douro Labs has discretion to negotiate pricing based on:
-
Feed complexity (e.g., single price vs. multiple data points)
-
Support requirements
-
Customer size and use case
-
Market conditions
Payment options:
-
Subscription — Monthly/annual; feed removed if/when payment lapses
-
One-time — Upfront fee covering listing and defined support period
Pricing builds on proven arrangements in the $20,000–$30,000 range for standard listings. Complex or high-priority feeds may command higher pricing.
- Revenue Distribution
| Recipient | Share |
|---|---|
| Pyth DAO Treasury | 90% |
| Douro Labs | 10% |
Payments to Treasury shall be made monthly.
Rationale: For LaaS, Douro Labs provides operational support (feed maintenance, customer management) while the core value — Pyth’s aggregated price data from 120+ publishers — belongs to the network. The 90/10 split reflects this division of value.
- Service Scope
LaaS includes:
-
Listing and go-live on Pyth Lazer
-
Feed monitoring and maintenance
-
Customer support for listing-related issues
-
Standard Pyth Pro SLA coverage for end consumers of the feed
LaaS does NOT include:
-
Data access for the payor
-
Custom publisher arrangements
-
Guaranteed uptime for feeds without sufficient publisher coverage
Note: LaaS customers pay for assets to be made available through Pyth Pro (Lazer); they do not pay for access to consume those feeds. If a LaaS customer desires to consume the newly listed feed, it will need to enter into the Pyth Pro standard data-as-a-service agreement and purchase access to such feed.
- Reporting
| Metric | Description |
|---|---|
| Active subscriptions | Number of LaaS customers |
| LaaS revenue | Total revenue for the period |
| DAO share paid | Amount transferred to Treasury |
| New listings | Feeds added via LaaS |
First LaaS report due with the next scheduled Pyth Pro report following approval of this op-pip.
- Feed Removal
If a LaaS subscription lapses:
-
Grace period: 30 days from missed payment
-
Notification: Customer notified at day 0, day 14, and day 25
-
Continuity: If the feed has active Pyth Pro consumers, Douro Labs may maintain it at discretion or negotiate transfer to another paying party
Implementation Plan
| Phase | Timing | Action |
|---|---|---|
| 1 | Days 1-7 | On-chain vote on OP-PIP-98 |
| 2 | Upon passage | Douro Labs authorized to offer LaaS |
| 3 | Ongoing | Commercial operations begin |
| 4 | Next Pyth Pro report | First LaaS metrics included |