Pages: /dashboard (H1: MOMENTUM; tagline: Move Central Liquidity Engine)

This module is the platform’s home surface that combines protocol health, market context, and an immediate trade entry.

What it does / key features

• Acts as a consolidated landing page for navigation: Dashboard, Trade, veMMT, Liquidity, xSUI, Vaults, Portfolio, Bridge.
• Shows protocol-wide metrics and “Trending” prices to contextualize activity before trading.
• Embeds a simplified Swap panel that mirrors the dedicated Trade page flow.

Concrete UI data points observed

• Global metric shown: TVL 45,012,273.89.
• “Trending” list includes tokens and prices/changes such as SUI 0.9386, MMT 0.1133, ETH 2121.4600 (-1.96%), wBTC 69954.0609 (-1.43%).

Interactive elements

• Top-right Connect Wallet entry point.
• Swap widget controls: 1M, 50%, MAX, and primary CTA Get Started.
• Token rows display on-chain identifiers (e.g., 0x2:...:SUI, 0xdb...USDC) plus indicative USD values (e.g., USDC showing $0.99), suggesting token metadata resolution and balance reading.

Strategic significance

• The dashboard is designed to reduce time-to-first-swap by pairing TVL + market context with a ready-to-use trade panel.
• Surfacing on-chain token IDs and balances hints the app is built for multi-asset routing on Move/Sui-like primitives, not just a static token list.

Pages: /trade (H1: trade)

This module is the primary execution surface for swaps, with an explicit “Swap Aggregator mode” label indicating route selection across sources (or internal pools) rather than a single AMM.

What it does / key features

• Provides a two-asset swap flow with asset selection and balance awareness.
• Exposes an aggregator toggle/state; the UI shows “Swap Aggregator mode” with a small on control, implying a feature-flag style switch.

Interactive elements

• Wallet gating via Connect Wallet.
• Amount helpers: 50% and MAX on the “From” side.
• Token selector shows an on-chain-style address label (e.g., 0x2:...:SUI) and a second asset line (e.g., 0xdb...USDC).
• Balance readout is present (“Bal: …”), and the panel displays estimated USD values (e.g., $0.00 for zero input, and $0.99 on USDC), suggesting pricing integration.

Notable constraints / gaps from the routes

• Several trade sub-routes are not live: /trade/swap, /trade/trade, /trade/earn, /trade/farm, /trade/portfolio all return 404. This implies either legacy routing, unfinished features, or a mismatch between nav expectations and deployed pages.

Strategic significance

• The “aggregator mode” positioning is key for competitive execution on SUI/Move ecosystems where liquidity is fragmented.
• Consolidating swap on a single /trade route also simplifies wallet permissions and quote caching, but the broken sub-routes reduce discoverability for users expecting separate Swap/Farm/Earn surfaces.

Pages: /liquidity (H1: liquidity)

This module is the discovery and entry point for LP provisioning, combining a searchable pool list with performance indicators.

What it does / key features

• Lists available pools and their key KPIs so LPs can choose where to deploy capital.
• Provides an “add liquidity” entry flow from the index.

Tables / fields / actions

• Search input: “Search pools”.
• Filter button: All.
• Primary action: Add Liquidity.
• Pool table columns: Pools | TVL | Volume(24H) | Fees(24H) | APR | Rewards | Action.

Concrete data points observed

• Protocol roll-up shown again: Liquidity Pools $45,012,273.89.
• Example pool row (stable-ish pair): SUI / USDC with Vol $723.49K, fee tier shown as 0.175%, TVL $3.33M, APR 15.85%, Fees(24h) $1.27K, and rewards listed as SUI, USDC, xSUI.
• Additional rows indicate varying fee tiers and smaller TVLs (e.g., an xBTC row with 0.2%, TVL around $92.96K, APR 14.72%; an MMT row with 0.25%, TVL around $230.85K, APR 3.7%).

Strategic significance

• Exposing fee tiers next to volume and fees makes the product’s “central liquidity engine” claim tangible: users can compare monetization vs. risk.
• Showing Rewards alongside APR suggests emissions/boosting is integrated (not purely fee APR), likely tied to veMMT governance incentives and/or xSUI/vault programs.

Pages: /ve-mmt (H1: ve-mmt and Bond for veMMT; H2: Bond Duration)

This module provides vote-escrow style locking where users bond MMT to receive veMMT, which typically represents governance weight and incentive direction.

What it does / key features

• Lets a user choose a Bond Amount in MMT and set a Bond Duration.
• Promotes a max-lock mechanic: “Max Bond for 4 years for highest vote power,” implying linear or increasing vote power by time.
• Offers automation: Enable Auto-Max bond. The description indicates when enabled it keeps the unlock time at maximum until disabled.

Interactive elements

• Wallet gating: Connect Wallet.
• Amount helpers: 50% and MAX next to Bond Amount.
• Toggle control: on next to Auto-Max bond.
• Balance readout: “Bal:” appears next to MMT amount, consistent with other modules.

Strategic significance

• veMMT is the coordination layer for the rest of the product: LP rewards (seen on /liquidity), vault incentives, and potentially referral/fee sharing can all be governed by ve-voting.
• The “Auto-Max bond” toggle is a practical UX optimization: it reduces ongoing management for users who want persistent maximum voting power, and hints the protocol expects long-term lockers to be a core constituency.

Pages: /portfolio (H1: portfolio)

This module consolidates user-owned objects: LP positions, veMMT bonds, pending rewards, and referral tracking. With no connected wallet it displays empty states, but the structure reveals the intended feature set.

What it does / key features

• My positions: LP inventory and yield status.
• My veMMTs: bonded positions with governance/voting attributes.
• Pending Rewards: a unified reward counter area.
• My Referrals: referral code/link and attribution stats.

Tables / columns / actions

• Positions table columns: Pools | Liquidity | Pending Yield | APR | Price Range | Action.
• veMMT-related columns appear in the same surface: ID | Bond Amount | Volume | Duration | Voting Power (suggesting each bond is an NFT-like or object-ID based position).
• A batch action button exists: Merge All (likely merges multiple veMMT objects/locks or consolidates positions to reduce object count and improve manageability).

Observed state

• With no wallet connected: $0.00 and “No results.” empty table.
• Referral section exposes Referral Code and Referral Link fields/labels, plus aggregate metrics placeholders such as Referred TVL and Referred Volume.

Strategic significance

• This is the retention module: after trading and LPing, users need a single place to monitor yield, lock status, and governance power.
• “Merge All” implies the chain/account model can create multiple discrete position objects; consolidation reduces user friction and may lower transaction overhead.

Pages: /vaults, /xsui

This module appears intended to host managed strategies (“Vaults”) and an xSUI-related product line, but it is currently incomplete / unstable.

Vaults (/vaults)

• Page header: vaults with minimal visible content beyond navigation and Connect Wallet.
• No tables, forms, or CTAs are exposed in the captured view, implying either: (a) gated content after wallet connect, (b) content still under development, or (c) a rendering issue.

xSUI (/xsui)

• The page fails with an error boundary style message: > Something Went Wrong > “We’re currently experiencing an unexpected issue that caused this page to crash. Please try refreshing… Our team is already looking into it.”
• This indicates a runtime exception in the xSUI route (component crash), not a missing route.

Strategic significance

• Vaults typically complement liquidity pools by offering auto-compounding, curated risk, or strategy abstraction; the presence of “Vaults” in top nav suggests Momentum wants a full earn stack beyond manual LP.
• xSUI being a first-class nav item and also listed as a Rewards token on /liquidity (e.g., SUI/USDC rewards include xSUI) implies xSUI is central to emissions or yield packaging. The current crash blocks that loop, and should be treated as a priority stability issue.

Pages: /trade/earn, /trade/farm, /trade/portfolio, /trade/swap, /trade/trade (all 404)

This module isn’t a “product feature” but is still functional surface area: how the app handles invalid or legacy routes directly affects usability and SEO.

What it does / current behavior

• Each listed route renders a generic not-found page:
  • H1: 404
  • H2: This page could not be found.
  • Still includes global navigation and Connect Wallet, which is good for recovery.

Why it matters

• The naming strongly suggests these were intended sub-pages under Trade (separate Swap, Farm/Earn, and Portfolio views). Their absence creates expectation mismatch, especially if external links or older docs reference them.
• From a frontend architecture perspective, this indicates either:
  • routes removed without redirects,
  • a deployment config missing nested routes,
  • or a feature flag not backed by route-level protection.

Strategic significance

• Fixing these should be approached as a product module hygiene task: add redirects to /trade or implement the missing pages.
• Keeping nav and wallet controls on the 404 page is a solid baseline; next step is to include contextual suggestions (e.g., “Go to /trade”) to prevent user drop-off.