LaaS — Listing as a Service for Pyth Pro (Lazer)

Ideas Bank
1

Summary

We propose formalizing Listing as a Service (LaaS) — a commercial model where projects may pay (via subscription or one-time fee) to have their price feeds listed and supported on Pyth Lazer.

This formalizes an existing practice: since 2025, the Pyth DAO has received over $300,000 in listing payments through the Price Feed Council. This interest has continued into 2026, with Douro Labs receiving requests for multiple listings into the Lazer data system. LaaS would formalize this revenue stream into a predictable, recurring model while giving Douro Labs the operational flexibility to scale the Pyth Pro (Lazer) feed catalog efficiently.

Background

What’s happening today:

Projects wanting their 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. This has generated meaningful revenue as $3,000+ have been accumulated by the Pyth DAO so far.

The gap:

While CO-PIP-5 authorized Douro Labs to manage the Lazer feed catalog, there’s no formal framework for charging listing fees. This creates ambiguity for both Douro Labs and prospective customers.

What we’re proposing:

Explicit authorization for Douro Labs to sell Lazer listings as a subscription service, with clear terms and revenue sharing.

Proposal

  1. Authorize Douro Labs to Sell LaaS Subscriptions

Douro Labs would be authorized to:

  • Market and sell price feed listings on Pyth Lazer

  • Negotiate subscription contracts with customers

  • Set pricing based on feed complexity and support requirements

  • Manage listing lifecycle (additions, maintenance, removals)

  1. Pricing

Pricing builds on successful prior arrangements, where listings have typically closed in the $20,000–$30,000 range (see Background above). Douro Labs has discretion to negotiate pricing based on:

  • Feed complexity (single price vs. multiple data points)

  • Support requirements

  • Customer size and use case

  • Market conditions

Payment Options:

  • Monthly subscription — Ongoing support, feed removed if payment lapses

  • One-time payment — Upfront fee covering listing and support period

Both models are available. Douro Labs negotiates the structure that best fits each customer’s needs.

Continuity: Existing Pyth Pro subscribers using a feed are handled case-by-case to ensure service continuity if the listing customer churns.

  1. Revenue Share
Recipient Share
Pyth DAO Treasury 90%
Douro Labs 10%

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.

  1. Service Scope

What 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 the feed

What LaaS does NOT include:

  • Data access for the payer (requires separate Pyth Pro subscription)

  • Custom publisher arrangements

  • Guaranteed uptime for feeds without sufficient publisher coverage

Note: LaaS customers pay for their asset to be available on Lazer — they may not consume the data themselves. Example: A protocol pays to list their governance token so DeFi integrators can access the price feed.

Reporting

LaaS revenue will be included in Douro Labs’ monthly reporting to the DAO, alongside Pyth Pro metrics:

  • Number of active LaaS subscriptions

  • Total LaaS revenue

  • DAO share paid

  • New listings added (if approved by the customer)

Open Questions

  1. Pricing floor/ceiling: Should the DAO set guardrails on pricing, or leave it fully to Douro’s discretion?

  2. Reporting cadence: Monthly (like Pyth Pro) or quarterly?

  3. Grace period: How long before a feed is removed for non-payment? 30 days? 60 days?

  4. Bundling: Should LaaS include Pyth Pro access for the paying customer, or keep them separate?

Next Steps

  1. Community feedback on this proposal

  2. Address open questions

  3. If supported, draft formal OP-PIP for vote

6 Likes
2

It’s a massive yes from me. Another big step toward consolidating revenue streams for the DAO and further establishing Pyth as a premium service within the world of DeFi.

In response to the open questions;

1 - I would lean towards at least initially letting Douro Labs handle price negotiations to get a feel for the general market consensus with the aim of eventually deciding on a floor for pricing. I don’t think a ceiling is necessary as this will essentially be decided by the market itself.

2 - Monthly, aligned with Pyth Pro. This keeps all reporting uniform and gives more transparency to how things are tracking.

3 - 30 days. Anything longer opens Pyth up to missing out on substantial revenue if payment never comes and there is really no reason for anyone to be over 30 days late in this day and age. If a protocol were to reach out as they are reaching the 30 day deadline, Douro labs could handle that case by case at their discretion.

4 - Seperate, unless this was done by creating a ‘bundle’ package. I don’t think one alone should be the price of admission for the other though.

All in all, big yes from me. Great work guys

3 Likes
3

Agree with this proposal!!!

Responses to open questions:

  1. I think allowing Douro Labs to decide pricing without DAO approval initially for a 6-month period is a smart move. Considering this shift in direction, it may be best to allow Douro Labs to find the market equilibrium based on their findings as this change is rolled out. Perhaps we can re-approve this authority on a 6/12 month basis?

  2. Monthly reporting to align with Pyth Pro and treasury would great. Also allow for greater transparency.

  3. 30 days.

  4. Separate. Perhaps offering a 20% discount off Pyth Pro as enticement?

3 Likes
4

@zenyas ,

Another great proposal. Listing as a Service is definitely a strong approach. Formalizing the listing procedure is an important step toward further commercializing Pyth Lazer / Pyth Pro.

In the longer term, it would also be interesting to see a more automated listing process. For example, a website where projects can directly subscribe to the service or make a one-off payment (e.g., via Stripe or recurring USDC payments).

1. Pricing floor / ceiling
As @lowkeigh also mentioned, during the initial phase, it likely makes sense for Douro Labs to negotiate listings to discover the appropriate market price for assets on Pyth Lazer. Over time, these deals could help establish a benchmark for future listings.

2. Reporting cadence
Monthly reporting makes the most sense, ideally aligned with existing Pyth Pro reporting and revenue sharing. (And AMA please)

3. Grace period
A 30-day grace period seems reasonable before removing a feed for non-payment.

4. Bundling
I generally agree with the sentiment shared by another community member that LaaS and Pyth Pro access should remain separate rather than bundled. However, listing partners could potentially receive a preferential discount when subscribing to existing Pyth Pro tiers.

For example, projects that pay to list their asset on Lazer could receive discounted access to tiers such as PYTH CRYPTO+ (1ms update frequency) or PYTH PRO (1ms all-asset data). This could incentivize projects to both list their assets and become Pyth Pro customers, while ensuring premium data access remains a separate service.

From SCP with Love.

4 Likes
5

@Derrp ,

Haha you beat me by 2 minutes — my precious #2 spot is gone now :grinning_face_with_smiling_eyes:. Glad we’re thinking along the same lines though.

SCP

1 Like
6

All aboard :fire:

Massive work feom u SCP

WE APPRECIATE U :ok_hand:

1 Like
8

Dear Skyz,
This post is written by @zenyas :blush: He is the hero

1 Like
9

Always seen your post for forum and assuming its yours :joy: .

Tnx again for reminders in dC
:heart:

1 Like
10

@lowkeigh @Derrp @scp covered it so good that I have nothing to say and only to support the proposal!

4 Likes