This page explains how Solana MM Pro works and how to operate it safely: creating clients, funding per-client MM wallets, configuring strategies, routing via Jupiter v6 & Pump.fun, and reading your PnL metrics.
MM Pro is a non-custodial console for Liquidity-as-a-Service on Solana. Each client runs in an isolated wallet. You fund those wallets, attach strategies, and the engine handles the buy/sell execution.
Solana MM Pro is a multi-client market making console for Solana. It is built to run per-client strategies across:
You do not connect MetaMask / Phantom directly to this UI. Instead, you:
A client represents a project, token, founder, or private account. Each client has:
A strategy is the configuration that controls:
A client can run multiple strategies (e.g. different tokens or behaviors).
The engine loops over strategies, reads client balances, fetches prices, and sends trades via:
Go to Clients & Limits view → fill in Client name, Telegram, Twitter, fee bps, min deposit, daily cap → click Save client.
MM Pro generates an MM wallet for this client. Copy it and send SOL + your token there.
From your own wallet (Phantom, etc.) send:
Do not send funds to MM Pro directly. You always fund client wallets you control.
Back in the MM Monitor view, fill in the strategy form:
In Active strategies, hit Start for your new strategy.
Watch trades, equity, volume & fee PnL in real time. If you want to stop activity, click Pause or delete the strategy.
Each client gets a unique Solana wallet that MM Pro uses for trading. You see:
If a client is deleted, strategies linked to that client are unbound and must be re-assigned.
After saving, the client card shows the MM wallet. Copy it and fund before starting any strategies.
So111... (SOL) or a stable (USDC/USDT).These fields control the randomized trade size as a % of available balance:
The engine uses these ranges, volatility and alpha to decide how aggressive each trade is.
auto — use Jupiter when available, fallback to Pump.fun when needed.jup — always route via Jupiter v6.pump — always use Pump.fun (requires SOL quote).When router = jup (or auto with good liquidity), MM Pro:
Use this for tokens with established pools on Raydium / other Solana DEXes.
When router = pump (or auto with no JUP liquidity), MM Pro uses Pump.fun local transactions:
amountSol, sells via sellPercentage of the bag.Ideal for tokens still on bonding curve or early Pump.fun phases.
No. MM Pro never asks for your private key or Phantom connection. You only send funds to client MM wallets that the engine controls for execution.
Go to Clients & Limits → each client card shows: volume, LiMiT fee, trades, today volume, last active timestamp.
1. Pause or delete the strategies bound to that client in Active strategies.
2. Optionally withdraw remaining funds from the client MM wallet back to your own wallet.
That depends on your router config and available liquidity. With
auto, MM Pro prefers Jupiter v6 when quotes are healthy, and falls back to Pump.fun
when JUP is not suitable or base/quote pair is curve-only.