LiquidMesh Security Update

📘

user address risk scan is enabled, please update your API usages

Security Update

LiquidMesh requires the user address to be explicitly provided in API requests in order to perform address-level risk evaluation.

User address risk screening primarily targets hacker-related or flagged addresses, including:

Addresses associated with known hacking incidents Addresses marked as high-risk by security partners Addresses included in internal or third-party risk lists If the provided user address is identified as risky, the request will be rejected.

Please update your API usages

For the Quote API, the userAddress parameter is suggested.

• The Security Engine relies on this field to perform address-level risk screening
• Requests without a valid user address will not be able to conduct security scanning

For Order API and Swap API , the userAddress parameter is required.

⚠️

Important
Always pass the actual end-user address.
Using placeholder, zero, or incorrect addresses may result in request rejection.

For More detail, please reference LiquidMesh Security Overview