About RAUM CLMM DEX

RAUM CLMM DEX is a concentrated-liquidity exchange interface designed for the Stellar ecosystem. The product focuses on practical operations for traders, liquidity providers, and protocol participants who need a single workspace for execution, monitoring, and governance context. Instead of separating these tasks into disconnected dashboards, RAUM presents route-specific tools that share consistent navigation and reporting patterns.

Concentrated liquidity allows providers to define ranges where capital remains active. This can improve capital efficiency compared with uniform liquidity models, but it also increases the need for active oversight. RAUM addresses that requirement with pool-focused position tooling, quote and slippage visibility for swaps, and monitoring surfaces that expose protocol and network state.

The public interface includes dedicated routes for Dashboard, Swap, Pools, Governance, and Terminal. Each route is maintained as part of an operational workflow: users can review context, execute actions, and validate outcomes with minimal context switching. Governance tools are provided to support transparent proposal lifecycle management and visible vote outcomes over protocol changes.

This website is maintained as production software and is intended for informed users who understand wallet security, transaction finality, and smart-contract interaction risk. RAUM does not hold user custody credentials through this interface. Users remain responsible for wallet key management and should verify transaction details before signing. The team publishes support and policy references to reduce ambiguity around operations, reporting, and acceptable use.

For support escalations and security issues, refer to the Contact page. For policy expectations and data-handling details, review the Privacy page. These pages are intentionally cross-linked so users, auditors, and integration teams can find operational context without relying on off-site references. The platform will continue to publish maintenance updates and route-level improvements as deployment and protocol requirements evolve.

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