What it does

• The /swap page is the primary trading surface. It exposes a simple “select token + amount” flow while advertising a new liquidity backend: “✨ Adaptive Liquidity market maker is live”.
• Supports Aggregator Mode, implying routing across pools/sources rather than a single pool path.

UI/interaction details observed

• Core CTA: “Connect Wallet”.
• Amount input shows placeholder/value formatting like “0.00”.
• The quote area shows a concrete example on-screen: “0.5 SUI” → “5.46 USDC”, and a midline number “0.95” (likely price impact/route metric/fee indicator as presented).
• On first load, it presents onboarding copy: “Welcome to Magma! Simplified crypto trading experience” and instructions to pick tokens and enter an amount.

Strategic significance

• This module is the conversion funnel: it turns the platform’s liquidity inventory (ALMM/CLMM pools) into user volume.
• The “Aggregator Mode” positioning suggests Magma aims to compete on execution quality (routing, best price) rather than only pool depth.
• By anchoring the new ALMM messaging directly on the swap page, the product aligns trading growth with liquidity migration and new pool adoption.

What it does

• The pool directory surfaces available pools and their performance metrics, acting as the entry point for liquidity provision.
• Pages: /pool/list and /liquidity/deposit both present “Liquidity Pools” with similar tabbing and tables.

Data & tables

• Both pages show a table with columns: Asset | TVL | Volume(24H) | Fees(24H) | APR | Rewards | Add.
• Filters/controls observed:
  • Tabs/segments: “All”, “✨ALMM new”, “CLMM”, plus “View Legacy Pools”.
  • “Filter by token” search control.
  • On /dashboard/list sorting is explicit (“Sort by TVL”); pool pages visually emphasize TVL/volume/fees.
• Example rows shown on-screen (as displayed):
  • /liquidity/deposit: “MAGMA SUI Bin Step 400” with numbers 817.06 / 237.20 / 12.48 / 558.10 across the metric columns.
  • /pool/list: “USDC MAGMA 🎉CLMM” with numbers 0.01 / 1,162,474 / 1,155,728 / 115.6 / 3.63.
  • /pool/list also shows “suiUSDT … 0.001 / 347,933 / 842,174 / 8.42 / 12.01” and “SUI … 0.18 / 238,085 / 51,871 …”.

Interactive elements

• CTAs: “Deposit Liquidity”, per-row “Add”, and helper links like “Learn More” and “Tutorials” (on /pool/list).

Strategic significance

• This module is the discovery + decision layer for LPs. By placing APR/Rewards next to fees/volume, Magma encourages liquidity to follow activity and incentives, and clearly differentiates new ALMM from CLMM and legacy.

What it does

• /pool/select is a guided entry screen for provisioning liquidity: users choose the two tokens first, then the UI reveals eligible pools.

Form fields & states

• Search input: “Enter the token symbol or address”.
• Two selectors:
  • “Token 1 – Select a Token”
  • “Token 2 – Select a Token”
• Fee configuration is displayed as a base parameter: “Base Fee 0.2%”.
• Empty/no-result state is explicit: “No token found”.
• Alternate input path is offered: “Or you can enter Coin Type” (suggesting Sui-style type strings / on-chain identifiers).

Interactive elements

• Primary gating action: “Connect Wallet” is required before the user can progress into actual deposit/position creation.

Strategic significance

• Separating token selection from pool choice reduces cognitive load and aligns with how concentrated liquidity products work (token pair → multiple fee tiers / pool types).
• Exposing Base Fee 0.2% at selection time sets expectations early and prevents users from discovering fee-tier constraints late in the flow.
• The “Coin Type” pathway is a power-user affordance; it supports long-tail assets that might not be in a curated token list, improving composability for Sui-native assets.

What it does

• /dashboard/list is the portfolio view for liquidity positions. It separates positions by pool model and supports yield claiming.

UI structure & controls

• Top-level segmentation: “CLMM” and “ALMM” tabs.
• Discovery aids:
  • “Filter by token”
  • “Sort by TVL”
• Empty-state guidance is clear: “You don't have any positions yet. Click here to Add liquidity”.

Portfolio summary & actions

• A summary block lists at least:
  • “Total Liquidity”
  • “Pending Yield”
• Yield collection is centralized with a prominent “Claim All” button.
• Wallet gating is enforced via “Connect Wallet”.

Compliance/footer elements

• The page includes product/legal links: “Disclaimer” and “Terms of Use”.

Strategic significance

• This module is the retention layer for LPs: it turns one-time deposits into an ongoing loop of monitoring and claiming.
• Supporting both CLMM and ALMM in the same dashboard indicates Magma expects users to straddle models during transition periods (or to pick based on strategy).
• A global Claim All reduces friction and gas/ops overhead for users with multiple positions, which is especially important if the product encourages fragmented liquidity across many pools.

What it does

• /dashboard/legacy exists to unwind older pool positions and push users toward newer pools.
• The page is explicit about the reason: “Legacy ALMM pools consumed excessive gas. Please claim and rebuild positions in the new pool.”

Guided migration UX

• Calls-to-action:
  • “Add liquidity in new pools”
  • “View new pools”
• Documentation-oriented links/sections:
  • “Learn more”
  • “Migration Guide”
• The flow described is two-step: claim (from legacy) → rebuild positions (in new ALMM pools).

Strategic significance

• This module is operational hygiene. High gas consumption can kill LP profitability; explicitly routing users to a “new pools” surface protects APR perception.
• Having a dedicated legacy dashboard avoids mixing old mechanics with new ALMM/CLMM UX, which reduces support burden and UI ambiguity.
• Migration messaging also signals protocol iteration: Magma is willing to deprecate designs that don’t meet performance targets, while providing a safer, documented path rather than leaving users stranded.

What it does

• /point is an incentives dashboard tracking user “Points” across multiple activities and social channels.

User gating & primary content

• The page is wallet-gated: “Connect wallet to view your ranking” with a “Connect Wallet” button.
• It aggregates point sources under “Total Points” and breaks them down into categories:
  • LP Points
  • Swap Points
  • Daily Points
  • Social Points
  • Discord Points
  • Galxe Points
  • Twitter Points

Implications of the taxonomy

• The split between LP and Swap indicates Magma values both sides of marketplace creation: liquidity depth and trade flow.
• The presence of Daily implies streaks/check-ins or periodic tasks.
• Social integrations (Discord/Galxe/Twitter) suggest off-chain proof-of-participation tasks feeding into on-chain identity via the connected wallet.

Strategic significance

• This module is a programmable growth engine: it creates measurable behaviors that can later map to rewards (fee rebates, airdrops, boosted APR, whitelists).
• By consolidating on-chain actions and off-chain engagement into one ledger, Magma can drive coordinated campaigns (e.g., “trade + provide liquidity + complete Galxe”) without fragmenting the user experience across multiple sites.

What it does

• /airdrop is the token distribution hub for the MAGMA airdrop lifecycle, currently in a post-campaign state.

On-page status & CTAs

• Status banner/text: “Airdrop Ended” and “The Magma airdrop has concluded. Thank you for participating.”
• Primary actions:
  • “Connect Wallet” (for eligibility/claim context)
  • “View Results” (public summary)

Public metrics shown

• The page publishes campaign totals:
  • Total Claimed (MAGMA): 10,561,804
  • Participants (addresses): 23568
• Education/support link: “Read the Drop FAQ →” under a “Learn More” label.

Strategic significance

• This module closes the loop between the Points system and user acquisition: it provides credibility via transparent claimed totals and participant count.
• Keeping the page live after the event (“ended” + results) serves as a historical record and reduces support load (“where is my airdrop?”), while also acting as marketing proof for future campaigns.
• The explicit “View Results” CTA suggests Magma expects community members to share/verify outcomes, reinforcing trust in distribution accounting.