Open pifagorsoft opened 1 month ago
Thanks! I haven't spent much time on Raydium yet since we're standardizing the Orca and Meteora endpoints first. Will dig into issue when I come back to Raydium.
@fengtality so the solana connector in use by hummingbot will be this project? The other one will be discontinued?
Using http://localhost:3000/docs I send a GET request to the Raydium exchange: /raydium/amm/pool/{poolAddress}. In the poolAddress field I enter 3nMFwZXwY1s1M5s8vYAHqd4wGs4iSxXE4LRoUMMYqEgF - the pool ID on the exchange (see screenshot). After executing the request, an error appears:
[09:38:51 UTC] INFO: Getting Raydium pool info for address: 3nMFwZXwY1s1M5s8vYAHqd4wGs4iSxXE4LRoUMMYqEgF [09:38:51 UTC] ERROR: fetch pool info error: 3nMFwZXwY1s1M5s8vYAHqd4wGs4iSxXE4LRoUMMYqEgF reqId: "req-n" req: { "method": "GET", "url": "/raydium/amm/pool/3nMFwZXwY1s1M5s8vYAHqd4wGs4iSxXE4LRoUMMYqEgF", "hostname": "localhost:3000", "remoteAddress": "127.0.0.1", "remotePort": 35508 } res: { "statusCode": 500 } err: { "type": "Error", "message": "fetch pool info error: 3nMFwZXwY1s1M5s8vYAHqd4wGs4iSxXE4LRoUMMYqEgF", "stack": Error: fetch pool info error: 3nMFwZXwY1s1M5s8vYAHqd4wGs4iSxXE4LRoUMMYqEgF at hr.getRpcPoolInfos (/home/roman/larp/node_modules/.pnpm/@raydium-io+raydium-sdk-v2@0.1.64-alpha_bufferutil@4.0.8_encoding@0.1.13_fastestsmallesttexte_irjogltdfliyh55h5icwmlagbq/node_modules/@raydium-io/raydium-sdk-v2/lib/index.js:1:266060) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async GetPoolInfoController.getPoolInfo (/home/roman/larp/dist/connectors/raydium/amm-routes/getPoolInfo.js:9:21) at async Object.handler (/home/roman/larp/dist/connectors/raydium/amm-routes/getPoolInfo.js:41:30) } [09:38:51 UTC] INFO: request completed reqId: "req-n" res: { "statusCode": 500 } responseTime: 212.6868109999923