Node reference
Add Raydium CPMM liquidity
Deposit a balanced token pair into a CPMM pool
Add Raydium CPMM liquidity deposits into an existing constant-product pool. You choose one token amount, and the pool’s ratio determines the paired amount.
Try it step by step#
- Inspect the pool with Get Raydium pool and confirm it is CPMM.
- Choose the wallet and pool. Set Amount Token to Mint A or Mint B, then enter Amount in that token’s units.
- Review the paired-token funding and slippage before execution. Inspect the operation output and transaction signature.
What to expect#
A successful deposit changes your liquidity position in that pool. Amount refers to the selected token, not a combined value for the pair.
Things to check#
- Selecting Mint A does not make this a single-token deposit; the other token is still needed.
- Use CLMM position nodes for concentrated-liquidity pools.
- Check the pool’s mint ordering when reusing an amount from an earlier step.
Keep learning#
Network setup: This node uses solana. See connections for RPC setup and Test mode for network selection.
Parameters#
| Setting | Default | What it does |
|---|---|---|
| RPC URL | {{global.chains.solana.rpcUrl}} | Configured for Solana in workspace RPC settings. |
| Commitment | confirmed | How far a Solana block must be confirmed before its data is used. |
| Wallet | {{global.main_wallet}} | Wallet that owns the assets or position and signs this operation. |
| Raydium API URL | — | Optional Raydium data API URL. Leave empty to use the configured network endpoint. |
| Compute Unit Limit | 600000 | Maximum compute units requested for the transaction. |
| Priority Fee Ceiling (micro-lamports/CU) | 100000 | The locally audited transaction may never exceed this price. |
| Signing Layer | auto | Signing provider to use. Auto selects an available provider for this run. |
| Skip Preflight | false | Skip the RPC preflight check before sending. Keep this off while learning. |
| Confirm | false | Wait for transaction confirmation after submission. |
| Pool | — | Address identifying the pool for this operation. |
| Amount Token | MintA | Token whose units are used for Amount. The paired amount is calculated from the pool and position. |
| Amount | — | Decimal deposit amount for the selected Amount Token, Mint A or Mint B. |
| Slippage (%) | 0.5 | Maximum tolerated execution change in percent; 0.5 means half a percent. |
| On failure | stop | Choose whether a failed execution stops the workflow or only ends this path. |
| Retry attempts | 0 | How many additional attempts to make after the first failure. |
RPC URL: Available under More options.
Commitment: Choices: Processed (processed), Confirmed (confirmed), Finalized (finalized). Available under More options.
Raydium API URL: Available under More options.
Compute Unit Limit: Available under More options. Limits: minimum 1; maximum 1400000.
Priority Fee Ceiling (micro-lamports/CU): Available under More options.
Signing Layer: Choices: Auto (auto), Application (executable), Extension (extension), Web Vault (web). Available under More options.
Skip Preflight: Available under More options.
Confirm: Available under More options.
Amount Token: Choices: Mint A (MintA), Mint B (MintB).
On failure: Choices: Stop workflow (stop), Continue (continue). Available under More options.
Retry attempts: Available under More options. Limits: minimum 0.
Inputs#
| Port | Value | Description |
|---|---|---|
in | any | Payload to preserve with the Raydium result. |
Outputs#
| Port | Value | Description |
|---|---|---|
out | object | The locally built, audited, signed, and submitted Raydium operation. |
out fields#
| Field | Type |
|---|---|
operation | string |
poolAddress | string |
positionAddress | string |
positionNftAddress | string |
transactionSignature | string |
validation | object |