The mechanism, in full.

What LPBANK does, why, and how to verify it on-chain.

Why we exist

Thesis

Memecoins leak value. Holders take profit, creators dump rewards, liquidity providers withdraw, and the chart bleeds. LPBANK inverts that.

Every coin issued through LPBANK's launchpad locks a share of its trade fees into the LPBANK reserve. Those fees are never paid out. They are routed into permanent liquidity for the $LPBANK token. The longer it runs, the deeper the pool gets. The mission is a single ratio:

pool depth (LP value) ÷ $LPBANK market cap > 100%

How it works

Mechanism

  1. A creator issues a coin through /launch. The Pump.fun fee-sharing config is set so that N% of trade fees route to the LPBANK reserve wallet.
  2. The split is locked at issuance. Pump.fun's fee-share policy disallows further updates after the first configuration call.
  3. Every ~15 minutes the buyback cron checks the reserve. If it's above the threshold (default 0.1 SOL), it calls distribute() on any pending fee-share PDAs.
  4. The cron then takes ~50% of the reserve and routes it through Jupiter into $LPBANK.
  5. The bought $LPBANK is paired with the remaining SOL and deposited into the AMM pool via pumpAmmSdk.depositInstructions.
  6. The minted LP tokens are transferred to the burn address. Liquidity is now locked forever.
Reserve share, by tier

Tiers

When you launch a coin you pick a tier. Higher tier = more fees to the reserve = faster pool depth growth = better placement.

  • Wade30%Listed in the LPBANK directory.
  • Lap50%Promoted to all $LPBANK holders.
  • Deep End75%Liquidity support and co-marketing.
  • High Dive100%Sponsored hero slot. Max exposure.
From launch to liquidity

Coin lifecycle

Creator                LPBANK                 Pump.fun
   │                     │                       │
   │  /launch form       │                       │
   │────────────────────▶│                       │
   │                     │  TX1: createCoin      │
   │                     │──────────────────────▶│
   │                     │  TX2: setFeeShares    │
   │                     │     (locked forever)  │
   │                     │──────────────────────▶│
   │                     │                       │
   ▼                     ▼                       ▼

… time passes, trades happen, fees accrue …

LPBANK reserve         Jupiter               PumpSwap pool
   │                     │                       │
   │  cron tick          │                       │
   │  if balance > th    │                       │
   │   ┌───split SOL─────┘                       │
   │   │                                         │
   │   ▼ swap 50%                                │
   │  SOL ───────────────▶$LPBANK                │
   │                                             │
   │   ┌─pair─────────────▶ deposit              │
   │   │ remaining SOL + bought $LPBANK          │
   │   ▼                                         │
   │  LP tokens                                  │
   │   │                                         │
   │   ▼ burn                                    │
   │  1nc1nerator (locked forever)               │
   ▼
Server-side automation

Buyback cron

The cron is a serverless Next.js route at /api/cron/buyback, triggered by Vercel Cron every 15 minutes. It's protected by a bearer token (LPBANK_CRON_SECRET) and uses a server-only signing key (LPBANK_RESERVE_PRIVATE_KEY).

Running it without the signing key returns a dry-run report: it still queries Jupiter and reads the reserve balance, but signs nothing. This lets you preview exactly what the next live tick will do.

Configurable via env vars:

  • LPBANK_BUYBACK_THRESHOLD_SOL=0.1
  • LPBANK_BUYBACK_FRACTION=0.5
  • LPBANK_JUP_SLIPPAGE_BPS=150
On-chain references

Addresses

  • $LPBANK mintset NEXT_PUBLIC_LPBANK_MINT
  • Reserve walletset NEXT_PUBLIC_LPBANK_RESERVE
  • Pump AMM poolauto-derived from mint at graduation
  • Pump fees programpfeeUxB6jkeY1Hxd7CsFCAjcbHA9rWtchMGdZ6VojVZ
  • Pump AMM programpAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA
  • Pump bonding curve6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P
  • Burn address1nc1nerator11111111111111111111111111111111
Common questions

FAQ

Can the fee split be changed after launch?+
No. Pump.fun's fee-sharing config can only be set once. After the launch tx lands, neither the creator nor LPBANK can modify the split. This is enforced by Pump.fun's on-chain program.
Where do the LP tokens go?+
After deposit, the minted LP tokens are transferred to the burn address. They are permanently irrecoverable. Translation: the liquidity that backs $LPBANK is locked forever.
What if my coin doesn't trade much?+
Then it doesn't generate much fee, and the reserve doesn't grow much from your coin. You still get the tier perks (directory, co-marketing, etc.). Pool depth grows with the cumulative volume of all member coins.
Is LPBANK a custodian?+
No. The launchpad never holds your creator share. Pump.fun's fee-sharing PDA routes both shares directly to their respective wallets every time fees are distributed.
What's $LPBANK used for?+
It's a memecoin. The narrative is the mission ratio. The governance is liquidity depth. There's no off-chain claim, no presale, no team allocation reserved for sale.