Co-authored by KemarTiti (Pythian Council, Pyth Data Association) and @zenyas (Pythian Council, Douro Labs)
Summary
Q1 fees are live and working as designed. With two months of data in hand, the Pythian Council and Douro Labs have reviewed Express Relay’s performance and want to share our findings with the DAO. This post covers what’s working, where the challenges are, and a proposed path forward.
What’s Working: X Stocks
Before diving into the numbers, worth highlighting what’s actually performing well. X Stocks account for ~45% of current volume and ~60% of fee revenue. They’ve held up better than other asset classes (-63% vs -90%+ elsewhere) because xStocks have limited onchain liquidity outside Express Relay, giving searchers better pricing power.
This is a real use case — tokenized assets with thin liquidity benefit from the Express Relay model.
1 Fees: Implementation Successful
In February, OP-PIP-92 activated protocol fees across 35 tokens. The implementation went smoothly — fees are collecting as designed.
| Month | Revenue | Context |
|---|---|---|
| Jan 2026 | $2,250 | Pre-fees (tips only) |
| Feb 2026 | $1,360 | Fees activated Feb 9 |
| Mar 2026 | $2,200 | Full month with fees |
Revenue has been steady but hasn’t grown with the fee implementation, largely due to volume shifts.
Volume Changes
| Metric | 2025 (Annual) | Post-Fee (Annualized) | Change |
|---|---|---|---|
| Total Volume | ~$600M | ~$59M | -90% |
| WSOL | $123M | $2.5M | -98% |
| USDC | $238M | $27M | -89% |
| Memecoins | $77M | $4M | -95% |
| X Stocks | ~$30M | ~$11M | -63% |
The volume decline isn’t fee-related — at 1-10 bps, protocol fees are negligible (a $10k trade costs $1-10). The primary factor: Jupiter launched their own RFQ system and, from a competitive standpoint, removed Express Relay from their aggregator. Jupiter had been the main distribution channel for spot token flow.
Economics
Running Express Relay costs between $5,000-$15,000 monthly (infrastructure, tech support). Current revenue is around $2,000/month. For every $1 Douro spends operating Express Relay, the DAO sees roughly $0.20 in revenue.
The DAO isn’t directly bearing this cost, but it raises the question of whether Douro’s resources could have more impact elsewhere.
Market Context
A few observations from looking at the broader landscape:
-
Distribution matters significantly in OEV/MEV. Products that own their flow (Jupiter) or are integrated with major existing flow (Chainlink SVR via Aave) have an advantage that’s hard to replicate through protocol improvements alone.
-
Solana aggregator dynamics changed. Jupiter’s RFQ launch shifted the competitive landscape. This wasn’t unexpected from their perspective, but it affected Express Relay’s distribution.
-
Tokenized assets remain promising. X Stocks performance shows the model works for assets with limited onchain liquidity — there may be future opportunities here even if the broader product winds down.
Proposal
Based on this review, we’re proposing an orderly wind-down of Express Relay.
What this means:
-
Douro Labs will begin a gradual sunset of Express Relay infrastructure
-
Communicate timeline to integrated protocols
-
Help current integrators transition
-
Maintain service during the transition period
-
Explore opportunities to license or sell the codebase to interested parties (AMMs, RFQ protocols, tokenized asset issuers) — any proceeds to the DAO treasury
Why: Current revenue (~$2K/mo) doesn’t justify operating costs ($5-15K/mo). Douro’s resources would have more impact on higher-traction areas like Pyth Pro and Pyth Terminal.
Timeline
| Phase | Timing | Action |
|---|---|---|
| Discussion | April 2026 | Gather DAO feedback |
| Decision | Last week of April | OP-PIP vote to confirm direction |
| Deprecation | End of Q2 2026 | Full sunset, support integrator transitions |
| Code Exploration | Ongoing | Explore licensing/sale opportunities |
Next Steps
-
Community feedback — Does this direction make sense? Anything we should consider?
-
Integrator feedback — Reaching out to protocols using Express Relay to understand their timeline needs.
-
Searcher feedback — Talking to active searchers about transition and potential interest in the codebase.