Meteora DLLM icon

Meteora DLLM

Meteora DLLM operations
Join our community

Actions4

Overview

This node interacts with the Meteora decentralized liquidity management module on the Solana blockchain. It supports operations such as opening a position in a Meteora pool, closing all positions, getting user positions, and claiming all rewards. The 'Open position' operation allows users to open a new position in a specified Meteora pool using a chosen pool strategy and bin ID offsets. This node is useful for users managing liquidity positions in Meteora pools on Solana, enabling automated and programmatic control over their liquidity management strategies.

Use Case Examples

  1. Opening a new liquidity position in a Meteora pool with a specific strategy and bin ID offsets.
  2. Closing all open positions in a Meteora pool to manage risk or rebalance portfolio.
  3. Claiming all accumulated rewards from Meteora liquidity positions.

Properties

Name Meaning
Pool Address The Meteora pool address to open a position for, specified as a string representing the Solana public key of the pool.
Pool strategy The Meteora pool strategy to use when opening a position. Options include various imbalanced and balanced strategies such as SpotImBalanced, CurveImBalanced, BidAskImBalanced, SpotBalanced, CurveBalanced, and BidAskBalanced.
Min Bin Id Offset The minimum bin ID offset to use when opening the position, specified as a number.
Max Bin Id Offset The maximum bin ID offset to use when opening the position, specified as a number.

Output

JSON

  • positionId - Identifier of the opened position in the Meteora pool.
  • transactionSignature - The Solana blockchain transaction signature confirming the position opening.
  • poolAddress - The address of the Meteora pool where the position was opened.
  • strategy - The pool strategy used to open the position.
  • binIdRange - The range of bin IDs (min and max offsets) used for the position.

Dependencies

  • @meteora-ag/dlmm (Meteora decentralized liquidity management module)
  • bs58 (Base58 encoding/decoding for Solana keys)
  • @solana/web3.js (Solana blockchain interaction)

Troubleshooting

  • Ensure the Solana API credentials (RPC URL, WebSocket endpoint, and private key) are correctly configured and valid.
  • Verify that the pool address provided is a valid Solana public key and corresponds to an existing Meteora pool.
  • Check that the pool strategy selected is supported and correctly spelled.
  • Make sure the min and max bin ID offsets are valid numbers and within acceptable ranges for the pool.
  • Common errors may include connection failures to the Solana RPC endpoint, invalid keypair errors from incorrect private key format, or transaction failures due to insufficient funds or invalid parameters.

Links

Discussion