Sushiswap

What it does

• Primary execution surface for trading on Sushi across multiple strategies.
• Exposes four modes directly in the top-level trade switcher: “Swap”, “Limit”, “DCA”, “Cross-Chain”.

Pages & UI entry points

• /swap and /ethereum/swap (Title: Swap) position Sushi as an aggregator: “supporting over 30 chains” and “best rates across DeFi.” Both pages share the same global navigation: Trade, Positions, network selector (Ethereum), and Connect WalletConnect.
• /ethereum/limit (Title: Limit) presents limit-order routing with the same mode switcher buttons.
• /ethereum/dca (Title: DCA) positions scheduled accumulation into tokens (“Dollar-cost average into your favorite tokens”).
• /ethereum/cross-chain-swap (Title: Cross-Chain Swap) adds cross-chain execution under the same trade shell.

Interactive elements observed

• Consistent header controls imply shared state management across routes:
  • Network context (explicitly shown as “Ethereum”).
  • Wallet connect call-to-action: “Connect WalletConnect”.
  • Mode tabs: Swap / Limit / DCA / Cross-Chain.

Strategic significance

• This module is the platform’s primary funnel: it monetizes via swap routing and aggregation while keeping users within Sushi for multiple execution styles.
• The uniform shell across /ethereum/ routes suggests a modular trading front-end: one container (wallet + network + navigation) with interchangeable strategy views, reducing UX fragmentation and enabling faster rollout of new order types.

What it does

• Lets LPs discover opportunities and manage active liquidity positions (v2, v3, and vault-style products).

Pool discovery (market browse)

• /ethereum/explore/pools (Title: Pools) is a data-heavy directory.
• Visible segmentation:
  • Heading: “🏦 Liquidity Vaults (5)”
  • Heading: “Pools (1507)”
• Action affordances and sort/filter hooks are implied by column headers and buttons:
  • Buttons: TVL, Fees (24h), APR (24h)
  • Table columns include (as displayed across views):
  • Pool name | TVL | Fees (24h) | APR (24h)
  • and a broader dataset: Name | TVL | Volume (24h) | Volume (1w) | Transactions (24h) | APR
• A persistent “Cookie Policy” header appears, indicating a site-wide compliance banner layer that may affect layout stacking.

LP position management (account state)

• /ethereum/pool and /pool (Title: My Positions) focus on owned liquidity.
• The page surfaces account emptiness clearly: heading shows “My Positions (0)Connect Wallet” when disconnected.
• Controls/buttons visible:
  • Navigation: Trade, Positions, Connect WalletConnect
  • Network indicator: NetworkEthereum
  • Product selectors: “🍣 SushiSwap v3”, “🍣 SushiSwap v2”, “🏦 Liquidity Vault”
• Positions table columns reveal the management model:
  • Name | Price Range | Position Size | Unclaimed fees

Strategic significance

• The browse page drives TVL by making yield + activity metrics legible (TVL, fees, APR, volumes, tx count).
• The positions page completes the lifecycle: LP onboarding, monitoring unclaimed fees, and switching between v2/v3/vault paradigms—critical for retaining liquidity once deposited.

What it does

• Provides SUSHI staking and basic governance-related controls (delegation / voting power).

Page & surfaced metrics

• /stake (Title: Stake) explicitly states: “Stake SUSHI in the SushiBar to earn more SUSHI.”
• Key headings indicate the information architecture:
  • “Your Voting Power”
  • “Manage”
  • “Your Balance”
  • A displayed rate: “4.43%” (presented as a headline metric; likely staking APR/APY).

Interactive elements

• Buttons/CTAs:
  • Wallet: Connect WalletConnect
  • Education: Learn More
  • Governance action: Delegate
  • Staking action: Stake
• An address-like element is shown as “0x8798...4272”, suggesting a contract address, connected account reference, or target delegation/staking contract displayed inline for verification.

Strategic significance

• This module anchors token utility beyond trading: it encourages long-term holding and aligns users with protocol governance.
• Presenting Voting Power alongside staking actions pushes users to couple economic stake with governance participation.
• The explicit rate (4.43%) functions as a conversion driver and sets expectations for rewards, while the “Manage” section implies ongoing operations (deposit/withdraw/claim flows) even if the detailed forms are not visible in the summarized page text.

What it does

• Captures demand for perpetual futures without exposing trading functionality yet.

Page behavior

• /perps (Title/Heading: Perps on Sushi Coming Soon) is a placeholder module.
• The page keeps the global app shell intact:
  • Top navigation: Trade, Positions
  • Network: Ethereum
  • Wallet CTA: Connect WalletConnect

Form & data capture

• A simple lead-capture form is present:
  • Field: “Enter your Telegram handle”
  • Button: Submit
• No pricing, leverage, margin mode, funding rate, or market list is exposed—this is not a functional perps terminal.

Strategic significance

• This page is a controlled rollout mechanism: it preserves brand continuity inside the main app while deferring risk-heavy functionality.
• Collecting Telegram handles indicates a distribution channel for beta access, announcements, or onboarding cohorts.
• Keeping the same header (wallet + chain context) suggests the perps product is intended to live inside the same session model and navigation system as spot trading and LP management when launched.

What it is

• A set of routes that currently fail to resolve or are blocked behind infrastructure/security layers, impacting discoverability and link integrity.

404 routes observed

• /earn, /farm, /liquidity, /portfolio, /trade all resolve to a 404 page:
  • Title: 404
  • Headings: “404” and “This page could not be found.”
  • Description text still advertises the broader app scope (“swap, cross chain swap, streaming, vesting, and permissionless market making”), indicating these were once valid top-level product categories or remain in marketing copy.

Security/interstitial

• /index resolves to “Vercel Security Checkpoint”, implying an edge protection layer that may trigger based on request patterns, geos, or risk signals.

Why it matters

• Broken/legacy routes degrade acquisition and partner integrations: older documentation or backlinks to /farm or /liquidity will dead-end.
• The mismatch between marketing description and available pages creates expectation gaps (e.g., “streaming” and “vesting” are mentioned but not represented in the analyzed routes).
• From a product ops perspective, these should be handled with explicit redirects (e.g., /trade → /swap, /liquidity → /ethereum/explore/pools, /earn → /stake or a consolidated “Earn” hub) to preserve SEO and reduce support load.