What it does

The /trade page is the execution surface for swapping/converting assets. The UI is oriented around fast preset sizing and a single-step action.

Visible functionality and UI affordances

• Page title: “Trade”.
• Global navigation buttons present: Earn, Analytics, Connect (wallet gating for execution).
• Amount presets: $1, $5, $10, $50 — suggests the trade widget can size orders by USD notionals (likely mapped to input token quantity).
• Primary action button: “Convert” — indicates this flow may be framed as a converter/aggregated swap rather than an orderbook.
• Form fields shown: “0.00” and “10” (two numeric inputs). This implies a two-asset panel (pay/receive) with editable amount(s) and potentially a default or previously selected amount of 10.

Data points (what is and isn’t visible)

• No price impact, minimum received, route, fee tier, slippage controls, token selectors, or pair metadata are explicitly visible in the notes.
• The presence of USD preset buttons implies a price feed is used somewhere, even if not shown in the surface snapshot.

Strategic significance

This module is the conversion funnel for the entire protocol: it generates fee flow that can later be reflected in /dashboard rewards and incentivized by /points or campaign pages. The minimal visible controls suggest a simplified UX that reduces friction, while wallet connection via Connect enforces on-chain execution permissions.

What it does

The /liquidity page is the LP management surface: discovering pools and adding liquidity across multiple AMM generations.

Visible functionality and UI affordances

• Page title: “Liquidity”.
• Global navigation: Earn, Analytics, Connect.
• Version tabs: V2, V3, V4 — indicates parallel liquidity systems (classic constant-product, concentrated liquidity, and a newer iteration) with separate pool registries and position formats.
• Primary action: “Add Liquidity” — entry point into LP creation / position minting.
• Search field: “Search…” — implies a pool list/table exists behind it (token symbol, pool address, fee tier, TVL, etc.), even if the row data isn’t shown in the snapshot.

Data points (what is and isn’t visible)

• No explicit TVL, APR, fee tier labels, or pool counts are visible from the notes.
• The version segmentation itself is a strong functional signal: users likely must choose the correct LP model before depositing.

Strategic significance

Liquidity provisioning is the supply-side backbone for /trade execution quality (depth, spread, price impact). Supporting V2/V3/V4 suggests Hybra is maintaining backward compatibility and multiple market structures: V2 for simplicity, V3 for capital efficiency, and V4 for newer features (often hooks/advanced routing in modern designs). The Search… affordance indicates pool discovery is expected to scale beyond a small curated set.

What it does

The /dashboard page is the user’s portfolio and rewards control center, consolidating LP exposure, emissions, and token holdings.

Visible functionality and UI affordances

• Page headline value: “$0.00” shown both as the document title and an

  $0.00 — a top-level portfolio valuation or earnings balance.

• Section headers:

  • My Pools — expected to list active LP positions across V2/V3/V4.

  • Rewards — expected to show claimable incentives by pool/program.

  • HYBRA Holdings — token balance/vesting/utility view.

• Buttons:
  • Connect — gating all account-bound reads.
  • Claim All — batch claim across reward sources.
  • Claim — per-item claim action (implies a list of reward lines).
  • Buy HYBRA — on-ramp into the native token, likely routing to swap/convert or an external venue.

Data points (what is and isn’t visible)

• The visible balance is $0.00, implying either a disconnected wallet, empty account, or default state.
• No APR/APY, per-pool reward rates, or claimable token quantities are shown in the notes.

Strategic significance

A unified dashboard reduces operational friction: users can manage positions and harvest rewards without hopping between /liquidity and external claim contracts. Claim All is particularly important for gas/UX optimization when incentives are fragmented across multiple pools and campaign programs (potentially including /carnival and /points accrual).

What it does

The campaign layer spans /carnival and /points, providing incentive programs beyond baseline swap fees—typically points accumulation, LP deposit campaigns, and community conversion.

/carnival: visible functionality

• Navigation buttons include Earn, Analytics, Connect and an additional Connect Wallet (suggesting a campaign widget may embed its own connect prompt).
• Primary campaign action: Deposit LP — indicates participation requires depositing an LP position/token into a program contract.
• Community CTA: Join the discord — operationally used for support, announcements, allowlists, or dispute handling.

/points: visible functionality

• Page exists as /points with title “Hybra Finance” but no additional controls were captured, suggesting either a minimal shell or content that renders after wallet connect.

Data points (what is and isn’t visible)

• No explicit points balances, tiers, leaderboard ranks, emission schedules, or campaign end dates are visible from the notes.
• The presence of Deposit LP strongly implies a separable accounting system (deposited balance, lock duration, multipliers) even if not displayed.

Strategic significance

Campaign modules are used to bootstrap liquidity and trading volume without permanently inflating base emissions. Deposit LP programs can enforce stickiness (lockups) and align incentives toward deeper markets that improve the /trade experience. A dedicated /points page signals potential retroactive rewards, partner quests, or season-based scoring that can later be converted into HYBRA utility or airdrop eligibility.

What it does

The /bridge page is an entry point for cross-network asset movement, enabling users to bring capital into the Hybra trading and liquidity environment.

Visible functionality and UI affordances

• Page title: “Hybra Finance” (no explicit “Bridge” title in the notes, but the route indicates purpose).
• Buttons: Earn, Analytics — notably missing an explicitly captured Connect button in the notes, which may mean the bridge UI handles connection differently or the top nav differs on this page.

Data points (what is and isn’t visible)

• No chain selectors, token selectors, bridge provider branding, fees, estimated time, or status panels are visible from the snapshot.
• Absence of visible interactive fields suggests either a simplified landing surface or content dependent on runtime state.

Strategic significance

Bridging is a growth and retention primitive: it reduces the friction of onboarding liquidity from other chains, which directly supports /liquidity depth and /trade execution. Even when implemented via a third-party bridge, a first-party /bridge route is important for funnel control (tracking, safety messaging, recommended routes) and for coordinating campaigns (e.g., points for bridged TVL feeding into /points and /carnival).