Skip to content

fix(liquidity-launcher-sdk): add append-only LBP_STRATEGY_DEPLOYMENTS registry (Fixes #8051) - #688

Open
TanmayDagur wants to merge 1 commit into
Uniswap:mainfrom
TanmayDagur:fix/8051-lbp-strategy-registry
Open

TanmayDagur wants to merge 1 commit into
Uniswap:mainfrom
TanmayDagur:fix/8051-lbp-strategy-registry

Conversation

@TanmayDagur

Copy link
Copy Markdown

Description

Fixes #8051

Before:
The /launches index hard-starts at 2026-07-24 22:05 UTC (missing earlier native launches, like the liluni token on Robinhood). This happens because the SDK's LAUNCHER_ADDRESSES object only provides the most recent LBPStrategy deployment for a given chain (e.g., the v3.1.0 update on July 10). Downstream indexers that rely on this object lose visibility into auctions deployed using older, superseded strategies.

After:
This PR introduces a true append-only deployment registry for LBP strategies (LBP_STRATEGY_DEPLOYMENTS in addresses.ts), mirroring the pattern already used for INSTANT_LAUNCH_DEPLOYMENTS and AUCTION_FACTORY_DEPLOYMENTS.

It includes all 19 historical and current LBP strategies (including the legacy and v3.0.0 Robinhood addresses) across the 9 supported chains. By utilizing the newly added getLbpStrategyDeployments helper, downstream indexers can easily resolve and backfill all past native launches from all historical LBP strategy generations.

How Has This Been Tested?

  • Unit tests (bun test) - all 169 tests pass.
  • Typecheck (tsc --noEmit) - clean.
  • Added coverage in addresses.test.ts to ensure historical LBPStrategy generations are retained and properly returned by the registry helpers.

… registry (#8051)

Adds a historical deployment registry for LBP strategies to enable downstream indexers to backfill launches from older strategy deployments (e.g., Robinhood legacy deployments). This addresses the issue where earlier native launches were missing from rankings/search because the indexer was only aware of the most recent strategy.
@TanmayDagur
TanmayDagur requested a review from a team as a code owner August 10, 2026 10:22
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.

1 participant