Skip to content

feat: token launcher (pump.fun) + Newly Listed section#1

Open
adaptcom[bot] wants to merge 2 commits into
mainfrom
feat/token-launcher
Open

feat: token launcher (pump.fun) + Newly Listed section#1
adaptcom[bot] wants to merge 2 commits into
mainfrom
feat/token-launcher

Conversation

@adaptcom

@adaptcom adaptcom Bot commented Jun 24, 2026

Copy link
Copy Markdown

What this adds

A token launcher for OG DEX, plus a Newly Listed section.

Users connect Phantom, fill in token details + image, pay a flat $5 launch fee (SOL or USDC/USDT) to the existing pay wallet, and deploy a token on pump.fun straight from OG DEX. On success they get the token link + CA. Newly launched tokens are pulled by CA into our database and surfaced in the new Newly Listed section.

Per spec: launched tokens are unverified and receive no boosts — they only appear in Newly Listed until they're listed/boosted separately.

Flow

  1. Connect Phantom wallet.
  2. Enter name, symbol, description, image, optional socials + dev buy.
  3. Pay the $5 fee (SOL / USDC / USDT) to the existing pay wallet — captured automatically from the wallet.
  4. The fee tx is verified on-chain (rpc-proxy getTransaction) before recording; payment_tx is single-use.
  5. Image + metadata upload to pump.fun IPFS; create tx built via PumpPortal trade-local (pool: pump), signed by the mint keypair + Phantom, and broadcast.
  6. CA is recorded into ogdex_launches and shown in /new.

Files

  • api/launch.js — IPFS upload, PumpPortal create, and on-chain fee verification + record.
  • api/launches.js — Newly Listed feed (live price/mcap enrichment).
  • supabase/launches_migration.sqlogdex_launches table (run in Supabase SQL editor).
  • src/pages/Launch.tsx — launcher UI.
  • src/pages/NewlyListed.tsx/new section.
  • src/lib/solana.ts — Phantom + fee/transfer + create signing helpers.
  • Nav links (desktop + mobile), Store card, routes, Solana deps + vite node polyfills.

Before merge / deploy

  • Run supabase/launches_migration.sql in the Supabase project.
  • Confirm SUPABASE_SERVICE_ROLE_KEY is set in the OGDEX Vercel env (needed by dbInsert).
  • The client uses public api.mainnet-beta.solana.com for blockhash/confirm; swap to a Helius/private RPC if rate limits bite.

Notes / assumptions

  • Standard launchpad model: the user signs the create tx and owns their token (matches OG Scan's launcher). The $5 is purely the platform fee on top of the ~0.02 SOL network cost.
  • Fee verification allows a small tolerance (92% of $5) to absorb SOL price drift between quote and payment.

Build: vite build passes (1827 modules).

- Add /launch page: connect Phantom, fill token details + image, pay a flat
  $5 launch fee (SOL or USDC/USDT) to the existing pay wallet, deploy on
  pump.fun via PumpPortal, and get the token link + CA.
- Fee is verified on-chain automatically (api/launch.js -> rpc-proxy
  getTransaction) before the launch is recorded; payment_tx is single-use.
- New ogdex_launches table (migration) + api/launches.js feed.
- Add /new 'Newly Listed' section showing launched tokens. Launched tokens
  are UNVERIFIED and receive NO boosts by design.
- Wire nav links (desktop + mobile), Store card, and routes.
- Add @solana/web3.js + @solana/spl-token + node polyfills for the browser.
@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
og-dex Ready Ready Preview, Comment Jun 24, 2026 1:42pm

Vercel Hobby caps a deployment at 12 serverless functions and each file in
/api counts as one (we were at 14). Move every route into api/_routes/*.js
(underscore folder = excluded from the function count) and add a single
api/[...path].js dispatcher that routes by the first path segment.

Result: 1 serverless function total, unlimited endpoints. Frontend /api/*
URLs are unchanged. To add an endpoint: create api/_routes/<name>.js and
register it in the dispatcher.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants