What it does

• Provides a single connection flow that gates stateful modules (notably /vote, /locks, /incentivize) behind an authenticated wallet session.
• Standardizes navigation across the product suite: header includes Dashboard, Swap, Liquidity, Vote, Lock, Incentivize, Connect and outbound links like Documentation, Security, Superswaps, Velo Launch, Analytics, Support, Website Mirrors.

Concrete UI evidence

• /dash (Title: Connect) is a dedicated onboarding screen with headings “Swap, deposit,take the lead” and “Connect”, and the message: “You’ll need an Ethereum Wallet to continue.”
• Wallet options are explicitly enumerated as buttons: Browser Wallet, WalletConnect, Coinbase Wallet, Binance Wallet.
• In connected contexts (seen on /index and /swap), the top bar exposes chain and balance primitives: “OP Mainnet”, “Balance 0.0 ETH” next to token selector ETH, and “Balance 0.0 VELO” next to token selector VELO. This implies a shared session store feeding token balances + chain selection.

Strategic significance

• Centralizes wallet integration and reduces duplicated logic: once connected, all modules can assume an account, chain, and token balance context.
• The consistent shell makes it easy to expand surface area (e.g., Superswaps, Velo Launch) without fragmenting UX, and supports compliance/ops links (e.g., Legal Disclaimer, Legal Disclosures visible in /swap footer alongside build/version info).

What it does

• Implements the core spot swap workflow: select sell token, select buy token, connect wallet, and execute a swap on the selected network.
• Provides an embedded swap experience both as a full page (/swap) and as a primary CTA widget on the landing/dashboard page (/index), indicating swaps are the primary conversion funnel.

Concrete UI evidence

• /swap is titled “Swap” with a primary heading

  Swap.

• The swap form exposes token rows labeled “Sell” and “Buy” (visible on /index preview), and a network selector showing “OP Mainnet”.
• Token selection is explicit and balance-aware: “Balance 0.0 ETH” with token ETH, and “Balance 0.0 VELO” with token VELO. These labels imply live wallet querying and pre-trade validation (e.g., insufficient balance states).
• Primary action is Connect when not authenticated (button label: Connect), consistent with wallet gating.
• /swap footer surfaces operational metadata: “2026 v5.0.0+1df3ed”, plus Legal Disclaimer and Legal Disclosures, which matters for institutional audit trails and release tracking.

Strategic significance

• The swap UI is the “always available” product entry point, while more complex value-capture (liquidity/voting) sits elsewhere.
• Showing chain and balances upfront reduces failed transaction attempts and anchors users to the intended execution environment (OP Mainnet), which is critical for a DEX positioned as a “central liquidity hub” on Optimism.

What it does

• Provides a pool marketplace and liquidity provisioning workflow: users can browse pools/tokens, evaluate TVL/fees/volume, and create or join liquidity positions.
• Acts as the supply-side counterpart to the swap module, with explicit messaging about emissions-based incentives.

Concrete UI evidence

• /liquidity includes the directive: “Provide liquidity to enable low-slippage swaps and earn VELO emissions.” This ties LP actions to both execution quality and rewards.
• The page exposes analytic tabs/metrics selectors: Volume, Fees, TVL, plus listing pivots Pools and Tokens (all visible as top-level toggles).
• A pool creation entry point is present: “Launch pool” (button), which connects to the broader launch tooling.
• Discoverability is built around a structured filter bar:
  • Chain: All chains
  • Token: Listed & Emerging
  • Type: Any
  • Autopilot: Inactive
  • Advanced: Inactive
  • Sort: TVL
  • Filters: Default
• Search is supported via a form field placeholder: “Symbol or address…”, indicating direct contract-address discovery.

Strategic significance

• The filter set suggests Velodrome is operating beyond a single deployment context (multi-chain awareness) while maintaining a consistent LP surface.
• Explicit Sort: TVL and segmented Pools/Tokens views indicate an intent to serve both retail browsing and professional liquidity allocation workflows.
• The inclusion of Autopilot implies optional managed behaviors (even if currently “Inactive” in the default view), positioning the LP module for future automation without changing core UX.

What it does

• Aggregates the protocol’s control plane: token locking (ve-style governance weight), voting over liquidity incentives, and targeted incentive management.
• These modules are wallet-dependent and appear intentionally gated to reduce confusion for unconnected users.

Concrete UI evidence

• /vote, /locks, and /incentivize all resolve to the same wallet-gated Connect screen when unauthenticated, with headings “Swap, deposit,take the lead” and “Connect”.
• The gating copy is explicit: “You’ll need an Ethereum Wallet to continue.” with wallet buttons Browser Wallet, WalletConnect, Coinbase Wallet, Binance Wallet.
• Navigation includes distinct entries Vote, Lock, and Incentivize, indicating three separate flows rather than a single governance page.

Strategic significance

• Separating Lock from Vote typically maps to distinct onchain actions and risk profiles (time-locked positions vs. periodic voting), which is cleaner for power users and integrators.
• A dedicated Incentivize surface suggests Velodrome targets not only passive LPs but also protocols/teams that want to direct liquidity via incentives; gating ensures only authenticated users see parameters tied to balances, allowances, and onchain approvals.
• The consistent connect-gate across these pages reduces edge cases (e.g., partially-rendered governance state without an account) and hints at a shared “account-required route” pattern in the frontend router.

What it does

• Provides a launch-oriented module focused on creating initial liquidity and improving discoverability for new tokens/projects.
• Positions Velodrome not just as a DEX, but as an onchain distribution channel for the “Superchain” ecosystem.

Concrete UI evidence

• /launcher is titled “Launch ahead” and brands the module as “Velo Launch”.
• Feature bullets are explicit and productized:
  • “Launch your liquidity” with subpoints “100% permissionless”, “Lock liquidity”, “Earn fees”.
  • “Get noticed” and “Launch your way” (implying configurable launch paths).
  • “Join the ranks of successful Superchain launches.” and “Activate the flywheel” (go-to-market framing tied to liquidity + trading loops).
• CTA consistency: Connect and Website Mirrors are present, matching the app shell conventions.
• The liquidity page reinforces the launcher link via “Launch pool” on /liquidity, implying a shared pool-creation backend with multiple entry points.

Strategic significance

• This module expands the addressable user from traders/LPs to token teams and ecosystem partners.
• “Permissionless” plus “Lock liquidity” suggests an intended pathway for safer launches (lockups) while still benefiting from fee generation, which aligns incentives between projects and traders.
• By embedding pool launch into the same app where swapping and liquidity discovery live, Velodrome shortens the path from creation → liquidity → volume → incentives.

What it does

• Introduces a cross-chain swapping experience marketed as “swap tokens across the Superchain, all in one app,” implying routing and interoperability beyond a single chain context.
• Serves as a product layer targeting wallets and integrators, not just end-users.

Concrete UI evidence

• /superswaps headline: “Introducing Superswaps” with the description: “Swap tokens across the Superchain, all in one app.”
• Primary CTA: “Try Superswaps”, indicating a dedicated execution flow beyond the informational page.
• “What’s new” section enumerates design goals:
  • “Better UX at no extra cost”
  • “Lightweight and more secure”
  • “For onchain builders”
• A dedicated block “Built for Wallets” signals SDK/embedding orientation rather than only web usage.

Strategic significance

• Superswaps positions Velodrome as a cross-domain liquidity access layer for the Superchain, which can increase order flow without requiring users to understand chain boundaries.
• The emphasis on being “lightweight” and “more secure” suggests a deliberate attempt to reduce integration complexity for wallets while maintaining trust assumptions.
• Functionally, this module complements the standard /swap: /swap anchors single-chain execution (e.g., OP Mainnet), while /superswaps markets interoperability and aggregation, broadening the funnel and partner surface.

What it does

• Provides protocol-level documentation (mechanism design, emissions, versioning) and a dedicated security overview (bug bounties, emergency processes, release history).
• Supports institutional diligence: governance/economic design on one side, operational risk posture on the other.

Concrete UI evidence

• /docs is titled “About Velodrome” and includes major headings:
  • About Velodrome
  • Tokenomics with Initial Distribution breakdown headings: Community, Protocols, Grants, Foundation, Optimism, Genesis Liquidity Pools
  • Emissions
• A table is present with at least one column labeled “VELO”, implying token-specific quantitative details are rendered in tabular form.
• /security is titled “Security Overview” with headings:
  • Bug Bounty Programs
  • Emergency Council
  • Releases, with named milestones: v1 Release, v2 and Relay v1 Releases, Slipstream Release, Superchain Release, Pool Launcher
• Both pages include navigation aids like Index and Website Mirrors, and a Connect button in the top shell.

Strategic significance

• Tokenomics documentation underpins the incentives ecosystem (LP emissions, voting power) and is necessary context for /liquidity and governance modules.
• Security overview plus release milestones provide a changelog-like map that helps counterparties assess upgrade cadence and historical scope changes (notably “Slipstream,” “Superchain,” and “Pool Launcher”).
• “Website Mirrors” suggests operational resilience: alternate frontends are treated as a first-class UX element rather than an afterthought.