fillrfillrdocs
Launch app

fillr is a Solana protocol for pre-filling limit orders against token launches. You commit USDC, USDT, or wSOL before a target token has tradeable liquidity. When the trigger fires — Jupiter routability, a timestamp, or both — any keeper executes the swap and you receive tokens at or below your max price.

Buying into Solana token launches is a coordination problem. Either you sit at a terminal refreshing the page when the launch goes live, or you accept whatever price you can get five blocks after the pool opens. fillr lets you set your price ahead of time, walk away, and let a permissionless network of keepers execute the moment the swap becomes possible — atomically enforced under your maximum.

Funds escrow to a per-order PDA. You retain ownership until execution or cancel. The program is immutable post-deploy — there is no admin key, no upgrade path, no parameter governance. The spec the program follows is the only contract that exists.

Commitment lifecycle
Activefunds escrowedExecutedkeeper filledCancelledowner refundedExpiredpast expiry_tsexecute_commitmentcancel_commitmentexpire_commitment
Three terminal states. Each closes the PDA and refunds rent to the original payer.

How it works, in 60 seconds

  1. Create a commitment. You pick a target mint, a payment mint, a max price, and a trigger condition. Your funds escrow to a Program-Derived Address unique to your order.
  2. Wait. You can keep the tab open or close it — the PDA holds your funds and the program enforces the rules.
  3. Trigger fires. When Jupiter has a route (or your unlock timestamp passes), any keeper races to execute. The program atomically checks effective_price ≤ max_price and tokens_received ≥ min_fill before delivering target tokens to your wallet.
  4. You receive the tokens. 20bps fee on the payment leg goes to the treasury. A small SOL bounty goes to the keeper. You get tokens at or below the price you set.
Status
fillr is currently deployed to devnet for testing. Mainnet launch follows audit. Devnet flows demonstrate the create / cancel / expire paths end-to-end; the keeper-fill demo runs on mainnet because Jupiter's routing service is mainnet-only.

Where to go next

  • Quickstart — create your first commitment in three minutes.
  • Commitments — the lifecycle and how the PDA works.
  • The keeper — running a fillr keeper, profitability, MEV.
  • Architecture — Anchor program internals + the Jupiter CPI flow.