What it does

• /index functions as the main landing hub for the app, exposing the primary product lines and a market list entry point.
• It surfaces three core areas via repeated headings/cards: “Leverage”, “Lend/Borrow”, and “Portfolio”, implying a unified suite (spot + lending + margin).

Visible features and UI signals

• Global navigation is consistent across pages: Explore, Bridge, Swap, Lending, Leverage, Liquidity, Stake, Vault, BNB, Farming, Airdrop, Portfolio, More plus Connect Wallet and Show Dust.
• There is a “Refer & Earn” call-to-action and copy indicating referral economics (also echoed on /swap).
• Market browsing controls appear as buttons/filters: “Featured”, “All Markets”, and a sortable metric label “APY”.
• Action buttons suggest cross-module entry points from markets: “Deposit” and “Farm Stake”.
• A settings surface is present: “Transaction Settings” with “Slippage tolerance” (the explicit numerical presets are clearer on /swap).
• Pagination exists (form fields show pagination item 1 active through item 4), suggesting multiple pages of markets.

Strategic significance

• This page is the orchestration layer: it routes users from discovery (markets/APY) into execution (deposit/stake/swap) while keeping global utilities (wallet connect, dust toggle, settings) always available.
• The presence of Deposit + Farm Stake on a markets list implies the product is designed to convert browsing into capital deployment with minimal navigation steps.

What it does

• /swap provides spot token exchange with two modes: “Swap” and “Limit” (toggle buttons visible at the top of the widget).
• It includes execution configuration and routing controls, indicating aggregation or multi-hop capability.

Concrete UI elements observed

• Primary actions: Swap, Limit, and Refer & Earn.
• Input field shows a numeric entry (form field “0.0”) for trade size.
• Settings panel includes “Transaction Settings” and “Slippage tolerance” with presets 0.1 and 0.5, plus an Advanced Routing section.
• Routing/execution options include “Custom” and a side selector labeled “Sell”.
• Balance and guardrails: the UI displays “NEAR Balance: $1.30” and an explicit requirement “Must have 0.2N or more” (a minimum threshold before swapping).

Strategic significance

• Swap is the liquidity entry point for the ecosystem; it is also where the app enforces safety rails (minimum balance) and exposes pro controls (advanced routing).
• The Limit mode signals non-trivial order logic (likely off-chain matching or on-chain conditional execution), complementing the broader “Leverage”/“Lending” positioning shown on /index.
• The embedded Refer & Earn link anchors growth directly in the trading flow, tying user acquisition to fee-generating activity.

What it does

• /stake provides staking for both the base chain token and the protocol token, plus a derivative/convert mechanism that appears to feed incentives in other modules (lending/farming boosts).

Data points and controls

• Two staking products are explicitly shown:
  • “Stake your $NEAR” with 4.64% APY.
  • “Stake your $RHEA” with 3.43% APY.
• Buttons: Stake, Unstake, and Connect Wallet.
• A numeric input is present (form field “0”) for stake amount.
• Boost integrations are called out:
  • “Lending Boost ⚡️ +Up to 50% Boost”
  • “Farming Boost ⚡️”
• Derivative/convert hints:
  • Mentions “oRhea” and “Convert Up to 100% Rate”.
  • Copy indicates: “Stake $NEAR and Receive $rNEAR (4.64%)”, implying receipt tokens for staked positions.

Strategic significance

• Staking acts as both a yield product and an account-primitive for the rest of the platform (boosting lending/farming rates, enabling composability via receipt tokens like rNEAR).
• By offering protocol-token staking (RHEA) alongside base-token staking (NEAR), the platform can align users with governance/fee capture while keeping an accessible entry point for general users.
• The explicit “boost” hooks suggest the protocol is designed to reward users who lock value, increasing stickiness across lending and farming funnels.

What it does

• /portfolio consolidates account analytics and position tables across trading and lending-style products. It reads like an operational dashboard: balances, open positions, and claimable rewards.

On-screen metrics and actions

• Top-level KPIs include: Net asset, Daily Profit, Net APY, and Unclaimed Profit with a primary Claim button.
• A Portfolio distribution section is present; the preview shows “No Data” when the wallet is empty or disconnected.
• Lending risk indicator appears as “Health Factor: 100000%” (an extreme value likely representing no borrow exposure or a placeholder when no liabilities exist).

Tables and implied data model

• Multiple tables are visible via column headers, suggesting separate tabs or stacked sections:
  • Positions table: Market | Size | Collateral/Net Value | Entry/Index Price | Liq. Price | PnL | Opening time | TP/SL Price | Action.
  • History/closed positions: Market | Size | Net value | Collateral | Entry price | Close price | Fee | PnL | Opening time | Close time | Operation.
  • Assets table: Token | Balance | Price | Value.

Strategic significance

• This module is critical for trust and retention: it exposes liquidation price, TP/SL prices, fees, and PnL in a structured way.
• The presence of both open and closed position schemas implies the platform expects active trading behavior (not just passive yield).
• The Claim flow suggests rewards accrue across modules (staking, lending, farming, trading rebates) and are unified here for one-click realization.

What it is

• Several routes that appear in the global navigation resolve to a 404 state:
  • /earn, /farm, /liquidity, /pool, /trade.
• Each shows “404” with the heading “This page could not be found.” while still rendering the full top nav (Explore/Bridge/Swap/etc.).

What’s still functional on 404 pages

• A cookie consent banner is consistently present with Accept and Reject buttons: “By clicking “Accept Cookies”, you agree to the storing of cookies…”.
• A small status element appears as a button-like label such as “lava rpc 252ms”, “lava rpc 1388ms”, “lava rpc 422ms”, etc., indicating live RPC latency/endpoint status is being surfaced even when content fails.

Strategic impact / product implications

• The nav suggests the intended product scope includes Liquidity, Farming, Earn, and possibly a separate Trade (likely perps/leverage UI). The 404 state means users cannot complete common DeFi loops (swap → add liquidity → farm) purely within the exposed routes.
• Keeping the app shell and RPC indicator visible on error pages is good operationally (users can still navigate elsewhere, and latency telemetry is available), but the broken deep links will reduce conversion from the landing hub (/index) into advanced modules.
• From an engineering standpoint, these 404s look like missing deployments or route gating rather than total app failure, because shared components (nav, cookies, RPC status) render reliably.