Uniswap / Uniswap/interface

[Bug] /launches index hard-starts at 2026-07-24 22:05 UTC — earlier native launches missing from rankings/search (app.uniswap.org/launches and pools.trade)

Open
#8,051 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
5.5k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

📱 Interface Affected

Also affects pools.trade (not listed above) — both read the same launches index.


🧩 App Version

  • Version (if known): current production
  • Production build

💻 System / Environment Info

  • Browser: N/A — reproducible in any browser and directly against the API (backend data issue, not client-side)
  • OS / Platform: N/A
  • Device: N/A
  • Wallet used: N/A — reproducible without connecting a wallet
  • Network: Robinhood Chain (chain id 4663)

🔁 Steps to Reproduce

Via UI:

  1. Go to app.uniswap.org/launches (or pools.trade)
  2. Browse the ranked launches feed for Robinhood Chain, or search "liluni"
  3. Liluni (0x4a6Eec8A30b49d289B9Fc865Fd374b4D61eab8fB, ~$3.5M 24h volume, top-10 on the
    chain) never appears

Via API (root cause):

  1. POST data.v2.DataApiService/ListLaunches with
    {"launchpadId":"uniswap-bonding-curve","chainIds":[4663],"sortBy":"LAUNCHES_ORDER_BY_LAUNCHED_AT","ascending":true}
    → the oldest entry in the entire index is 2026-07-24 22:05 UTC
  2. Liluni launched 2026-07-23 22:51 UTC via the LiquidityLauncher clearing auction
    (tx 0x399c2615f26d85d8333f991196f20fb4141d2e91f8c9da2956a9b4115a27128c) — ~23h before
    the index starts

✅ Expected Behavior

All tokens launched through the LiquidityLauncher appear in the launches index regardless of
launch date.


❌ Actual Behavior

The index hard-starts at 2026-07-24 22:05 UTC. Launches before that timestamp are invisible
in rankings and search on both surfaces, while their token pages work fine by direct link
(https://pools.trade/t/0x4a6eec8a30b49d289b9fc865fd374b4d61eab8fb — tagged Crowd Launch,
full stats, live chart).


🧾 Additional Context

  • Launch mechanism is ruled out as the cause: identical clearing-auction → LBP launches
    made after the cutoff are indexed normally, e.g. SKRMP
    0x0f68BEE9880a41CDf9713C24358FfDB4756d53c2 (Aug 3) and CHWDR
    0xB358766827d7C704d3c52a57b5Cf181D1b0ffC6c (Jul 30)
  • GetToken returns full data for the affected token (safety verdict "Benign"), so only the
    launches index is missing history
  • Suggested fix: backfill the index to the LiquidityLauncher's first on-chain activity
    (~23 hours of history on Robinhood Chain)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the launches feed and search requests to data.v2.DataApiService/ListLaunches, then inspect which service owns the launches index. Reproduce the ascending Robinhood Chain query and confirm the 2026-07-24 cutoff. Done means earlier LiquidityLauncher launches, including liluni, appear in rankings and search on both surfaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.