Contact

This page lists official channels for RAUM CLMM DEX support and incident reporting. Use these contacts for integration questions, operational issues, and user-facing defects encountered on the production interface. Clear and structured reports improve triage quality and reduce response time, especially during periods of high network or market activity.

When submitting a support request, include relevant context: wallet type, network, route visited, transaction hash (if available), and a concise summary of expected versus observed behavior. Screenshots or logs can help reproduce issues faster. Avoid sharing private keys, recovery phrases, or other sensitive wallet credentials. RAUM support will never request those secrets.

Security reports are handled with elevated priority. If you discover a potential vulnerability, send details through the security address below and include reproducibility steps, impact estimate, and suggested mitigations if known. Responsible disclosure helps protect users and allows time for coordinated fixes, validation, and communication.

General Inquiries: support@raum.network
Security Reports: security@raum.network
Legacy Interface: v1.dex.raum.network

Related public references are available on the About and Privacy pages. The About page describes product scope and governance context, while the Privacy page explains data-handling boundaries and user expectations. Keeping these routes interconnected helps users and auditors quickly locate the right information without leaving the primary domain.

Response timing depends on issue type and severity. Security reports and production outages are prioritized ahead of general feature questions. For urgent requests, include complete reproducible details in the first message so triage can start without follow-up delays. Clear reporting helps the team classify impact, route ownership, and publish corrective actions more efficiently.

If your request references a transaction, include the hash and approximate timestamp to speed verification against network and application logs.

Published: February 12, 2026 | Last updated: February 12, 2026

Response windows vary by request type and network load.