Skip to content

[fees] Prismapad: add v3 launchpad#8392

Open
quepasaquepasa wants to merge 1 commit into
DefiLlama:masterfrom
quepasaquepasa:prismapad-v3
Open

[fees] Prismapad: add v3 launchpad#8392
quepasaquepasa wants to merge 1 commit into
DefiLlama:masterfrom
quepasaquepasa:prismapad-v3

Conversation

@quepasaquepasa

Copy link
Copy Markdown
Contributor

Prismapad deployed a v3 launchpad on Stable (chain 988). It is mechanically identical to v2 — the full 1B supply is minted as single-sided liquidity into an official StableSwap (Uniswap v3) 1% pool, the position NFT is locked in the launchpad, and the 1% pool fee is split 50/50 between the token's creator and the protocol treasury. The only difference is how token addresses are derived: CREATE2 over a per-creator salt rather than the contract nonce.

v3 handles new launches. v2 stays live and keeps earning fees for the tokens already launched on it, so the adapter scans both.

  • v3: 0x7c1628681c18884a1a90977fdae034282892c842, deploy block 32976695
  • v2: 0xa96d9eadc4d6eed50fa408a33585c5f1df039db5 (unchanged)
  • v1: 0xdcb881fc8b472eb7797687b237e6cb123c425ff7 (unchanged)

Both direct-to-DEX generations emit the identical TokenCreated shape, so they are collected into one DEX_LAUNCHPADS list and their pools pooled together. No change to the fee math, the doublecounted flag, or the metric labels — only the methodology strings were updated to say v2/v3 where they said v2.

Tested with npm test fees/prismapad:

STABLE
Daily volume: 13.00
Daily fees: 0.23
Daily user fees: 0.23
Daily revenue: 0.11
Daily protocol revenue: 0.11
Daily supply side revenue: 0.11

🤖 Generated with Claude Code

Prismapad deployed a v3 launchpad on Stable. It is mechanically identical
to v2 - full supply minted as single-sided liquidity into an official
StableSwap (Uniswap v3) 1% pool, position locked in the launchpad, 1% pool
fee split 50/50 between the token creator and the protocol treasury. The
only change is how token addresses are derived (CREATE2 over a per-creator
salt instead of the contract nonce).

v3 handles new launches; v2 stays live and keeps earning fees for the
tokens already launched on it, so both are scanned.

v3: 0x7c1628681c18884a1a90977fdae034282892c842 (deploy block 32976695)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f62e9f42-bb86-4375-b6ba-9ae3a4346c65

📥 Commits

Reviewing files that changed from the base of the PR and between 6b58e3a and 19de98d.

📒 Files selected for processing (1)
  • fees/prismapad/index.ts

Summary by CodeRabbit

  • Bug Fixes

    • Improved direct-to-DEX launch tracking by including both v2 and v3 launches.
    • Ensured pool activity, swap volume, and fees are captured across both launch types.
  • Documentation

    • Updated fee and volume methodology descriptions to accurately reflect v2/v3 accounting and buy- versus sell-side valuation.

Walkthrough

The Prismapad adapter adds v3 launchpad metadata, scans v2 and v3 TokenCreated events concurrently, combines launches for downstream processing, and updates methodology descriptions to cover v2/v3 fee accounting.

Changes

Prismapad v2/v3 support

Layer / File(s) Summary
Combined launchpad discovery and methodology
fees/prismapad/index.ts
Adds v3 launchpad configuration, fetches v2 and v3 launch events concurrently, combines them for pool and swap processing, and updates fee-accounting descriptions.

Estimated code review effort: 2 (Simple) | ~10 minutes

Sequence Diagram(s)

sequenceDiagram
  participant DEX_LAUNCHPADS
  participant PrismapadFetch
  participant PoolAndSwapProcessing
  DEX_LAUNCHPADS->>PrismapadFetch: Provide v2/v3 launchpad metadata
  PrismapadFetch->>DEX_LAUNCHPADS: Fetch TokenCreated logs concurrently
  PrismapadFetch->>PoolAndSwapProcessing: Pass flattened launches
Loading

Possibly related PRs

Suggested labels: fees, methodology

🚥 Pre-merge checks | ✅ 13 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Title check ⚠️ Warning The title is relevant, but it does not match the required “[type] protocol-name - description” format. Rename it to follow the required format, e.g. “[fees] Prismapad - add v3 launchpad”.
Methodology Keys ⚠️ Warning Prismapad’s methodology object includes UserFees, which isn’t one of the allowed dimension display names in the style guide. Rename/remove UserFees in methodology so only allowed display-name keys remain (e.g. Fees, Revenue, ProtocolRevenue, SupplySideRevenue, Volume).
✅ Passed checks (13 passed)
Check name Status Explanation
Description check ✅ Passed The description gives a clear rationale, scope, testing, and implementation details, which is sufficient for this update.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Breakdown Methodology Check ✅ Passed PASS: The adapter exports breakdownMethodology, and every .add() label in fees/prismapad/index.ts is covered by its keys: Fees, Revenue/ProtocolRevenue, SupplySideRevenue.
Income Statement Compliance ✅ Passed Prismapad records full fees in dailyFees, protocol’s 50% in dailyRevenue, and creator 50% in dailySupplySideRevenue, so dailyRevenue = dailyFees - dailySupplySideRevenue.
Version 2 Required ✅ Passed Prismapad adapter exports version: 2 in the adapter object, satisfying the check.
Pullhourly Required For Version 2 ✅ Passed Prismapad is version 2 and explicitly sets pullHourly: true in the adapter object.
Dune Adapters Are Version 1 ✅ Passed Prismapad uses getLogs only, not Dune helpers; version 2 is acceptable and there are no TIME_RANGE/date-filter issues.
Income Statement Balance ✅ Passed Each fee event splits exactly into protocolShare + creatorShare, and protocolShare+creatorShare = fee for v1 and v2/v3, so dailyFees matches revenue+supply-side revenue.
Fetchoptions Usage ✅ Passed Prismapad’s fetch uses a single FetchOptions arg, has no timestamp return, and doesn’t derive time windows from raw timestamps or startOfDay.
Adapter Shape ✅ Passed Prismapad uses a single-chain adapter with one global start and no per-chain config object.
Efficiency And Error Handling ✅ Passed No flagged anti-patterns found: getLogs uses targets/readable eventAbi, there are no try/catch or api.call loops, and hardcoded constants have source comments.
✨ Finishing Touches
✨ Simplify code
  • Create PR with simplified code

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

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

The prismapad adapter exports:

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

🦙 Running PRISMAPAD adapter 🦙
---------------------------------------------------
Start Date:	Thu, 23 Jul 2026 17:00:00 GMT
End Date:	Fri, 24 Jul 2026 17:00:00 GMT
---------------------------------------------------

 (1/24) start: 5 PM - 23/07    |  
 (2/24) start: 6 PM - 23/07    |  
 (3/24) start: 7 PM - 23/07    |  
 (4/24) start: 8 PM - 23/07    |  
 (5/24) start: 9 PM - 23/07    |  
 (6/24) start: 10 PM - 23/07    |  
 (7/24) start: 11 PM - 23/07    |  volume - 13.00 | fees - 0.13 | user fees - 0.13 | revenue - 0.06 | protocol revenue - 0.06 | supply side revenue - 0.06
 (8/24) start: 12 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
 (9/24) start: 1 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(10/24) start: 2 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(11/24) start: 3 AM - 24/07    |  volume - 0.00 | fees - 0.09 | user fees - 0.09 | revenue - 0.04 | protocol revenue - 0.04 | supply side revenue - 0.04
(12/24) start: 4 AM - 24/07    |  volume - 0.00 | fees - 0.01 | user fees - 0.01 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(13/24) start: 5 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(14/24) start: 6 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(15/24) start: 7 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(16/24) start: 8 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(17/24) start: 9 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(18/24) start: 10 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(19/24) start: 11 AM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(20/24) start: 12 PM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(21/24) start: 1 PM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(22/24) start: 2 PM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(23/24) start: 3 PM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00
(24/24) start: 4 PM - 24/07    |  volume - 0.00 | fees - 0.00 | user fees - 0.00 | revenue - 0.00 | protocol revenue - 0.00 | supply side revenue - 0.00

====== TOTAL DAILY AGGREGATED (sum of slots per chain) ======

STABLE 👇
End timestamp: 1784912399 (2026-07-24T16:59:59.000Z)
Daily volume: 13.00
Daily fees: 0.23
Daily user fees: 0.23
Daily revenue: 0.11
Daily protocol revenue: 0.11
Daily supply side revenue: 0.11




FEES BREAKDOWN 👇

label                        | Daily fees | Daily supply side revenue | Daily revenue
---                          | ---        | ---                       | ---          
Token Swap Fees              | 0.2286     |                           |              
Trade fees to token creators |            | 0.1143                    |              
Trade fees to protocol       |            |                           | 0.1143       

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant