[fees] Prismapad: add v3 launchpad#8392
Conversation
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>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Summary by CodeRabbit
WalkthroughThe Prismapad adapter adds v3 launchpad metadata, scans v2 and v3 ChangesPrismapad v2/v3 support
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
Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 13 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (13 passed)
✨ Finishing Touches✨ Simplify 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. Comment |
|
The prismapad adapter exports: |
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.
0x7c1628681c18884a1a90977fdae034282892c842, deploy block329766950xa96d9eadc4d6eed50fa408a33585c5f1df039db5(unchanged)0xdcb881fc8b472eb7797687b237e6cb123c425ff7(unchanged)Both direct-to-DEX generations emit the identical
TokenCreatedshape, so they are collected into oneDEX_LAUNCHPADSlist and their pools pooled together. No change to the fee math, thedoublecountedflag, or the metric labels — only the methodology strings were updated to say v2/v3 where they said v2.Tested with
npm test fees/prismapad:🤖 Generated with Claude Code