Quickstart for LPs Partner

A step‑by‑step guide for partners to create an LP position on the Saros DLMM.

Things to note

  • Fees are auto‑compounded into your position and realized on withdrawal (no separate claim button).

  • Requirement for those using Squads Multisig only: your LP must be placed in a single transaction (one TX only). Design your Bin Step and price range so the total number of bins fits into one single transaction (see step 4.3 for an example). If you require additional bins (wider range), add these in separate TXs.

  • If you encounter issues using a ledger, try TXs that create 3 positions or fewer. Ensuring you sign TXs quickly can also help.

  • Need help fast? DM the Saros team.

What you’ll need

  • A Solana wallet with SOL for fees.

  • The assets of the pool you’re adding to (e.g., wBTC/mBTC or USDC/USDS).

  • A clear price range you’d like to provide liquidity within and amounts for each token.

Step 1: Create the pool (if it doesn't exist)

  1. On dlmm.saros.xyz, click Create Pool (or + New Pool) and search for your tokens. First, check the Pools page to ensure the pool doesn't already exist.

  2. Select Token A / Token B (e.g., wBTC / mBTC or USDS / USDC). Double‑check mint addresses.

  3. Set Pool parameters:

    • Shape: Spot (uniform liquidity across your selected range).

      • Why Spot for pool creation? Keeps inventory evenly spread in a tight band (e.g., 0.9992–1.0006) and avoids over‑concentration if the mark moves before TVL arrives. Also, if you’re using a multisig like Squads, it reduces chances of TX failure because bin counts are predictable and all fit into a single TX. You can still add additional Curve positions later to concentrate near the active bin price for higher fee capture.

    • Base fee: up to you but most pegged wrappers/stable pools start at 0.01%.

    • Bin Step: 1 (*Basic Fee auto = 0.01% as shown).

      • Why 1 bps? Highest price resolution for pegged pairs (BTC/BTC, stable/stable), smoother re‑pegs and tighter quotes across aggregators.

      • For those using Squads multisig only - you are limited the number of ‘positions’ you set up in a single TX (see section 4.3 for more details): At 1 bps, each bin = 0.01% with a 16‑bin cap per TX. Your initial position should cover a total span of ≤0.16% (≈ ±0.08% maximum each side). Plan your range accordingly. You can add more positions in separate TXs to get a wider range.

    • Initial price: set near 1.0000 (or current market), ensure active bin is at the middle.

  4. Click Create Pool and approve in Squad (one transaction)

Step 2: Open the pool on Saros DLMM

  1. Search and open your pool (e.g., USDS/USDC).

  2. Click Add Liquidity.

Step 3: Choose Liquidity Shape & Range

  1. Liquidity Shape: Select Spot or Curve (pegged) for assets stable in price against one another (i.e. BTC/wBTC; USDC/USDT).

  2. Bin Step: Default 1 bps (0.01%) for tight control but many bins

  3. Range: for a tight 1:1 example, set 0.9992 – 1.0006 (≈ ±0.07% around 1.00).

Step 4: Allocate Liquidity

  1. Select Both sides (recommended for pegged pairs) or Single‑sided if topping up one token.

  2. Enter token amounts. For BTC/BTC or stable/stable, providing roughly balanced amounts is simplest.

  3. For multisig users only: Check the # of positions shown by the UI (see image below for example). If it’s >1, reduce the per‑tx coverage (narrower sub‑range - typically 16 bins or less, or a higher bin step), then add remaining bins in separate TXs afterwards.

Example: Adding liquidity between ranges 0.9936 -> 1.0032 using a multisig: TX 1: 1.0017 -> 1.0032 TX 2: 1.0000 -> 1.0016 TX 3: 0.9984 -> 0.9999 TX 4: 0.9968 -> 0.9983 TX 5: 0.9952 -> 0.9967 TX 6: 0.9936 -> 0.9951

Click Preview to review fees, range and bins, then Add Liquidity and approve.

Step 5: Confirm & Monitor

  • Your position will immediately start earning trading fees within the active bins. Fees auto‑compound; you realize them when you withdraw (partially or fully).

  • You can adjust later:

    • Narrower range (fewer bins) → higher fee capture when price stays in‑range, fewer TXs for multisig users.

    • Wider range (more bins) → more time in range, but may require multiple transactions for multisig users.

Last updated