paraspell/xcm-api

LightSpell⚡️: API utilizing XCM-SDK to get you blazing fast ⚡️ XCM calls (Currently supporting 50 Parachains)

Content of this repository is still maintained.

It moved to monorepo and can be accessed here: https://github.com/paraspell/xcm-tools/tree/main/apps/xcm-api

xcm-api's Issues

Add ability to test request limit in API Playground

Add a simple API Playground demonstration that tests request limits implemented to prevent DDoS so users can find out how to use their captcha tokens and test out forms for higher request limit users.

Some Asset endpoints will change

A bug was found where certain assets would not work with our endpoints

eg: assets containing / in their name DOT/text

This will be fixed in the upcoming update, so Playground must also be set to support these changes.

3 asset endpoints will now contain query parameters

Make port an environment variable

Integrate Sentry - Performance monitoring, error tracking service

Find free analytic tool

Find a free analytics tool to analyze API usage to extract the following data:

• Different endpoints API request usage
• Specific token analysis (to analyze malicious behaviour from accounts that requested more API requests per minute)
• Overall API request count

The analytics tool must not collect any user data.

Add wallet address validation

Add wallet address validation just like in XCM SDK.

Current output:
Error 500

Expected output:
Error message: "Wallet address you entered is incorrect"

Memory Leak and Incomplete Instance Destruction with Repeated /x-transfer HTTP API calls

When our HTTP API /x-transfer endpoint is subjected to a high volume of persistent requests, the WsProvider from the Polkadot JS API is created repeatedly, leading to memory leaks. Even after calling the .disconnect() method, the instance isn't completely destroyed.

Steps to Reproduce:

1. Trigger a substantial number of continuous requests to our HTTP API endpoint /x-transfer.
2. Observe the creation of multiple WsProvider instances.
3. Execute .disconnect() but notice that memory isn't freed as expected.