feat: add Pyth Express Relay, Core, and Pro fee adapters

[pythia-assistant]

Summary

Adds fee tracking adapters for three Pyth Network products:

Pyth Express Relay

• website: https://www.pyth.network/
• Category: MEV
• Chain: Solana
• Data Source: Tracks SOL and USDC received by DAO address 69ib85nGQS2Hzr4tQ8twbkGh76gKFUfWJFeJfQ37R3hW
• Methodology: All auction fees from Express Relay MEV protection accrue to the Pyth DAO

Pyth Pro (formerly Lazer)

• website: https://www.pyth.network/pyth-lazer
• Category: Oracle (subscription service)
• Chain: Solana
• Data Source: Tracks USDC transfers from Douro Labs (C6G3jRs1SD7GSNxvKNHJZy7aSar7eZiLioPpDRFFtKTf) to Pyth DAO (5Unq3fgfSNdyeGjiq2Pu5XAQUJWo2rauKGErbUyxqUGe)
• Methodology: Douro Labs (official data distributor) pays 60% of subscription revenue to the DAO

Pyth Core

• website: https://defillama.com/protocol/pyth-network
• Category: Oracle (price feeds)
• Chains: Ethereum, Arbitrum, Optimism, Base, Polygon, Avalanche, BSC, Blast, Linea, Mantle, Scroll, Manta, Mode, zkSync, Polygon zkEVM, Fantom, Celo, Gnosis
• Data Source: Tracks PriceFeedUpdate events on Pyth contracts
• Methodology: Fees paid by users to update price feeds on-chain

Related

• These adapters correspond to the protocol listings in Add Pyth Express Relay, Pyth Core, and Pyth Pro protocol listings defillama-server#11285

Summary by CodeRabbit

• New Features

  • Multi-chain Pyth Core adapter to report on-chain fee-based revenue across many EVM and non-EVM networks.
  • Solana Express Relay adapter aggregating DAO fee income (SOL & USDC) and reporting daily fees/revenue.
  • Pyth Pro Solana adapter to track USDC revenue transfers to the DAO.

• Notes

  • Adapters mark methodology for Fees/Revenue, depend on Allium, and include chain start dates.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds three new Pyth fee adapters: a multi-chain on-chain adapter (Pyth Core) computing per-update fees across many EVM and non‑EVM chains, plus two Solana adapters (Pyth Express Relay, Pyth Pro) that aggregate SOL/USDC receipts to report daily fees and revenue.

Changes

Cohort / File(s)	Summary
Multi-chain On-chain Adapter fees/pyth-core/index.ts	New adapter implementing evmChainConfig, feePerUpdateByChain, DEFAULT_FEE, PRICE_FEED_UPDATE_ABI, and fetch handlers for EVM and non‑EVM chains (fetchEvm, fetchSolana, fetchSui, fetchAptos, fetchNear). Builds per-chain adapter entries, exports default adapter (version: 1), marks isExpensiveAdapter, depends on Dependencies.ALLIUM, and documents methodology.
Solana Express Relay fees/pyth-express-relay/index.ts	New Solana adapter using getSolanaReceived to sum SOL/USDC received at a DAO address; returns dailyFees and dailyRevenue (equal), exports default adapter (version: 1), start: 2024-01-01, depends on ALLIUM.
Solana Pyth Pro fees/pyth-pro/index.ts	New Solana adapter querying Allium for USDC transfers (Douro Labs → Pyth DAO), accumulates amounts into dailyRevenue and dailyFees, handles query errors, and exports default adapter (version: 1), start: 2024-01-01, depends on ALLIUM.

Sequence Diagram(s)

sequenceDiagram
  participant Client
  participant Adapter
  participant Fetcher as ChainFetcher
  participant Data as Blockchain/Allium
  Client->>Adapter: request fees (chain, timestamp)
  Adapter->>Fetcher: invoke chain-specific fetch
  Fetcher->>Data: query logs / Allium / RPC / events
  Data-->>Fetcher: return events / transfers / balances
  Fetcher-->>Adapter: dailyFees / dailyRevenue (or zeros on error)
  Adapter-->>Client: return result

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

🐇 I hopped through ledgers, logs, and light,
Counting updates by day and night.
SOL and USDC, fees in a row,
Core, Relay, Pro — numbers grow.
A tiny hop, a revenue glow. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 60.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding three fee adapters (Express Relay, Core, and Pro) for the Pyth Network, matching the changeset content.
Description check	✅ Passed	The description comprehensively covers all three adapters with relevant details (website, category, chain, data source, methodology) and is well-organized, though it deviates from the template since this is an adapter PR rather than a new protocol listing.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@fees/pyth-core/index.ts`:
- Around line 38-40: The early return and catch block return a raw number object
instead of the required FetchResult with Balances; update both the config check
and the catch handler to return an object shaped like { dailyFees: { value: 0 },
dailyRevenue: { value: 0 } } (or the correct Balances shape used in this module)
so they match the Promise<FetchResult> signature and the success path; locate
the returns near the config check and the catch block (referenced by FetchResult
and Balances in this file) and replace the numeric literal returns with properly
structured Balances objects.
- Around line 20-25: Duplicate chain entry: CHAIN.ZKSYNC duplicates CHAIN.ERA
causing double counting; remove the obsolete CHAIN.ZKSYNC entry from the
mapping. Locate the object that maps chain constants (contains CHAIN.ZKSYNC and
CHAIN.ERA with contract "0xf087c864AEccFb6A2Bf1Af6A0382B0d0f6c5D834") and delete
the CHAIN.ZKSYNC key-value pair so only CHAIN.ERA remains as the canonical
zkSync Era configuration.

🧹 Nitpick comments (5)

fees/pyth-express-relay/index.ts (1)

9-14: Consider filtering to SOL and USDC explicitly.

The comment states "Track all tokens (SOL and USDC)" but getSolanaReceived is called without a mints filter, meaning all tokens received at the DAO address will be counted. If only SOL and USDC auction fees should be tracked, consider adding the mints parameter:

const dailyFees = await getSolanaReceived({
  options,
  target: EXPRESS_RELAY_DAO_ADDRESS,
  mints: [ADDRESSES.solana.SOL, ADDRESSES.solana.USDC], // filter to expected tokens
});

If tracking all received tokens is intentional, update the comment to reflect that.

fees/pyth-pro/index.ts (2)

6-10: Remove unused USDC_MINT constant.

USDC_MINT is defined on line 10 but never used — line 32 uses ADDRESSES.solana.USDC instead. Either use the constant consistently or remove it.

♻️ Suggested fix

 // Douro Labs is the official Pyth Pro data distributor
 // They pay 60% of subscription revenue to the Pyth DAO
 const DOURO_LABS_ADDRESS = "C6G3jRs1SD7GSNxvKNHJZy7aSar7eZiLioPpDRFFtKTf";
 const PYTH_DAO_ADDRESS = "5Unq3fgfSNdyeGjiq2Pu5XAQUJWo2rauKGErbUyxqUGe";
-const USDC_MINT = "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v";

---

46-56: Consider adding isExpensiveAdapter: true for consistency.

The pyth-express-relay adapter marks itself as isExpensiveAdapter: true since it queries Allium. This adapter also queries Allium, so consider adding the same flag for consistency.

♻️ Suggested addition

 const adapter: SimpleAdapter = {
   version: 1,
   fetch,
   chains: [CHAIN.SOLANA],
   start: "2024-01-01",
   dependencies: [Dependencies.ALLIUM],
+  isExpensiveAdapter: true,
   methodology: {

fees/pyth-core/index.ts (2)

31-32: Remove unused GET_UPDATE_FEE_ABI constant.

GET_UPDATE_FEE_ABI is defined but never used. If there's a plan to call the contract to get actual fee amounts (which would be more accurate than the hardcoded estimate), consider implementing it; otherwise remove the dead code.

♻️ Suggested fix

 // Event emitted when price feeds are updated
 const PRICE_FEED_UPDATE_ABI = "event PriceFeedUpdate(bytes32 indexed id, uint64 publishTime, int64 price, uint64 conf)";
-
-// ABI to get update fee
-const GET_UPDATE_FEE_ABI = "function getUpdateFee(bytes[] calldata updateData) external view returns (uint feeAmount)";

---

57-62: Fee estimation is a rough approximation.

The hardcoded feePerUpdate of 0.0001 native token applies uniformly across all chains despite the comment noting "varies by chain." This estimation may significantly diverge from actual fees paid, especially on chains with different gas cost structures.

Consider:

1. Using chain-specific fee estimates in chainConfig
2. Calling the getUpdateFee contract method (the ABI is already defined) to get actual fee amounts
3. Alternatively, documenting this limitation in the methodology

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@fees/pyth-core/index.ts`:
- Around line 149-171: The fetchSui function is over-counting by summing
ABS(amount); instead identify the Pyth fee receiver (fee vault) and change the
SQL to only sum positive inflows into that address (e.g., WHERE
recipient_address = '<PYTH_FEE_VAULT>' AND amount > 0) instead of using
ABS(amount), then use that summed value when calling dailyFees.addCGToken("sui",
total_fees / 1e9). Update or add a constant for the Pyth fee vault (referenced
alongside SUI_PYTH_PACKAGE) and adjust the query in fetchSui to filter by that
recipient and positive amounts so only actual fee inflows are counted.

[llamabutler]

The pyth-core adapter exports:

> adapters@1.0.0 test
> ts-node --transpile-only cli/testAdapter.ts fees pyth-core

🦙 Running PYTH-CORE adapter 🦙
---------------------------------------------------
Start Date:	Fri, 30 Jan 2026 00:00:00 GMT
End Date:	Sat, 31 Jan 2026 00:00:00 GMT
---------------------------------------------------

------ ERROR ------
Error: Invalid chain labels: undefined
    at _runAdapter (/home/runner/work/dimension-adapters/dimension-adapters/adapters/utils/runAdapter.ts:141:11)
    at runAdapter (/home/runner/work/dimension-adapters/dimension-adapters/adapters/utils/runAdapter.ts:93:29)
Invalid chain labels: undefined

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@fees/pyth-core/index.ts`:
- Around line 149-166: fetchSui is summing positive balance_changes for
SUI_FEE_RECIPIENT without restricting to SUI coin types and is using date-only
strings which lose intraday precision; update the SQL built in fetchSui (the
query passed to queryAllium) to (1) add a coin type filter (e.g. coin_type =
'0x2::sui::SUI' or the project’s canonical SUI coin_type) alongside owner =
SUI_FEE_RECIPIENT, and (2) replace the date-only comparisons with full-timestamp
comparisons using TO_TIMESTAMP_NTZ() on the UNIX timestamps derived from
options.startTimestamp/options.endTimestamp so checkpoint_timestamp windowing
preserves time-of-day; ensure dailyFees.addCGToken("sui", ...) still converts
the returned sum from base units as before.
- Around line 176-191: The SQL in fetchAptos currently sums all
fungible_asset_activities for APTOS_PYTH_CONTRACT and can overcount non-APT
tokens; update the query string (variable query in function fetchAptos) to
include the asset filter AND asset_type = '0x1::aptos_coin::AptosCoin' (keeping
the existing owner/address, activity_type, and timestamp filters) so that
dailyFees.addCGToken("aptos", res[0].total_fees / 1e8) only uses APT deposits
between options.startTimestamp and options.endTimestamp.

[llamabutler]

The pyth-core adapter exports:

> adapters@1.0.0 test
> ts-node --transpile-only cli/testAdapter.ts fees pyth-core

🦙 Running PYTH-CORE adapter 🦙
---------------------------------------------------
Start Date:	Sun, 01 Feb 2026 00:00:00 GMT
End Date:	Mon, 02 Feb 2026 00:00:00 GMT
---------------------------------------------------

------ ERROR ------
Error: Invalid chain labels: undefined
    at _runAdapter (/home/runner/work/dimension-adapters/dimension-adapters/adapters/utils/runAdapter.ts:141:11)
    at runAdapter (/home/runner/work/dimension-adapters/dimension-adapters/adapters/utils/runAdapter.ts:93:29)
Invalid chain labels: undefined

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@fees/pyth-core/index.ts`:
- Around line 7-79: evmChainConfig contains entries using undefined chain
constants (e.g., CHAIN.BITTENSOR, CHAIN.GNOSIS, CHAIN.SKATE, CHAIN.SUPERSEED,
CHAIN.SWELL, CHAIN.VICTION, CHAIN.WORLDCHAIN) which produce undefined keys and
break adapter validation; fix by either adding those missing CHAIN constants to
helpers/chains.ts (with the canonical string labels used across the codebase) or
by removing/renaming the corresponding entries from evmChainConfig so only
defined CHAIN.* symbols remain, and then run validation to confirm no "Invalid
chain labels: undefined" errors.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Extract CHAIN keys from fees/pyth-core/index.ts and helpers/chains.ts, then compare

python3 << 'PY'
import re
import pathlib

# Read the fees/pyth-core/index.ts file
config_file = pathlib.Path("fees/pyth-core/index.ts")
if not config_file.exists():
    print("ERROR: fees/pyth-core/index.ts not found")
    exit(1)

config_text = config_file.read_text()

# Extract all CHAIN.* references from the config file
used_chains = sorted(set(re.findall(r'\[CHAIN\.([A-Z0-9_]+)\]', config_text)))
print("=== CHAIN keys used in fees/pyth-core/index.ts ===")
print(f"Total unique chains: {len(used_chains)}")
print("Chains:", used_chains[:10], "..." if len(used_chains) > 10 else "")

# Read the helpers/chains.ts file
helpers_file = pathlib.Path("helpers/chains.ts")
if not helpers_file.exists():
    print("\nERROR: helpers/chains.ts not found")
    exit(1)

helpers_text = helpers_file.read_text()

# Extract CHAIN enum/constant definitions
# Look for patterns like: ETHEREUM = "...", or enum CHAIN { ETHEREUM = "..." }
defined_chains = set(re.findall(r'^\s*([A-Z0-9_]+)\s*[=:]', helpers_text, re.MULTILINE))
print(f"\n=== CHAIN keys defined in helpers/chains.ts ===")
print(f"Total defined chains: {len(defined_chains)}")

# Find missing chains
missing = sorted([k for k in used_chains if k not in defined_chains])
print(f"\n=== Missing chains ===")
if missing:
    print(f"Count: {len(missing)}")
    print("Missing chains:", missing)
else:
    print("None - all chains are defined!")

# Show some context for the first few chains
print(f"\n=== Sample verification (first 3 used chains) ===")
for chain in used_chains[:3]:
    status = "✓ DEFINED" if chain in defined_chains else "✗ MISSING"
    print(f"{chain}: {status}")
PY

Repository: DefiLlama/dimension-adapters

Length of output: 582

---

Resolve 7 undefined chain labels in evmChainConfig.

The config references these chains that are not defined in helpers/chains.ts: BITTENSOR, GNOSIS, SKATE, SUPERSEED, SWELL, VICTION, and WORLDCHAIN. These undefined constants create undefined keys in the mapping, causing the adapter validation error "Invalid chain labels: undefined". Either add the missing constants to helpers/chains.ts or remove/rename these entries from the config.

🤖 Prompt for AI Agents

In `@fees/pyth-core/index.ts` around lines 7 - 79, evmChainConfig contains entries
using undefined chain constants (e.g., CHAIN.BITTENSOR, CHAIN.GNOSIS,
CHAIN.SKATE, CHAIN.SUPERSEED, CHAIN.SWELL, CHAIN.VICTION, CHAIN.WORLDCHAIN)
which produce undefined keys and break adapter validation; fix by either adding
those missing CHAIN constants to helpers/chains.ts (with the canonical string
labels used across the codebase) or by removing/renaming the corresponding
entries from evmChainConfig so only defined CHAIN.* symbols remain, and then run
validation to confirm no "Invalid chain labels: undefined" errors.