What it does

• Core swap UX for token-to-token trades with chain-aware routing and configurable execution protections.
• Same interface is exposed on multiple entry points: /swap, /avalanche/swap, /monad/swap (suggesting chain-specific defaults while keeping a shared component model).

Observed UI & controls (from /swap, /avalanche/swap, /monad/swap)

• Primary heading: “From” (h2), indicating a two-leg swap form.
• Top navigation consistently includes Tokens, Swap, Stake, Bridge, Login, plus language (English) and network shortcuts (Avalanche, Arbitrum One, Base). In the settings drawer, additional networks appear: Monad and Solana.
• Settings surface:
  • Slippage tolerance presets: 0.1% and 0.5%.
  • Transaction Deadline: shown as minutes with a visible value 30.
  • Safe Mode toggle: “Prevent high price impact trades. Disable at your own risk. Learn more.”
  • Infra toggles: Show testnets; RPC Endpoint selection with Public vs Dedicated.
• Swap form fields show sample numeric values like 0.5 and 0.0, implying input amount + output estimation behavior.
• Chain-specific token defaults are visible:
  • /avalanche/swap shows From AVAX.
  • /monad/swap shows From MON.
  • /swap shows From Select, implying no chain/token preselected.

Strategic significance

• This is the primary revenue and retention loop: a consistent swap component across chains reduces maintenance and enables rapid network expansion.
• Safe Mode + slippage + deadline controls position LFJ for both retail safety and more disciplined execution (institutional users can standardize parameters). RPC selection hints at performance optimization for latency-sensitive routing/quotes.

What it does

• /explore is a token discovery and monitoring module that functions like a lightweight screener: ranking, filtering, and surfacing liquidity/flow metrics to drive users into swaps.

Observed UI & datasets

• Page heading: “Winners trade here” (h2), explicitly positioning this as a performance-oriented discovery funnel.
• Tab-like controls: Trending, Volume, Gainers, New—four primary ranking modes.
• Time window selectors: 12h and 24h are visible, implying metric recalculation over different lookbacks.
• Filters include All Networks with explicit network options: Avalanche, Base, Monad, Solana.
• Data grid columns (table) include:
  • Token, Price, MCAP, VOL, Txns, Traders, Holders
  • Performance windows: 1h, 4h, 12h, 24h
  • Liquidity, Age
• Example row fragment demonstrates real token listing format: pippin with a shortened address “Dfh5...pump” and a displayed price $0.08438 (MCAP shown as $84.3… truncated in preview).

Interactive implications

• The presence of address + network filters suggests the table likely links into token detail and/or prefilled swap routes.
• Column selection indicates LFJ is optimizing for onchain flow signals (txns/traders/holders) rather than only price.

Strategic significance

• Explore reduces user acquisition cost by keeping discovery in-app (no need to leave for third-party screeners).
• By exposing Liquidity and Age, LFJ nudges users toward tradable and less manipulation-prone markets, complementing swap-side Safe Mode.

What it does

• The page /lfj-dex/swap/price/impact-/slippage/and/safe/mode/6735950 is a dedicated documentation module explaining swap execution risks and LFJ’s protective controls.

Observed structure & navigation

• Title and H1: “Price Impact, Slippage and Safe Mode”.
• Section headings include:
  • “#Understanding Price Impact, Slippage, and Safe Mode” (h3)
  • “#General Disclaimer” (h3)
• Left-side doc navigation shows this sits within a broader developer/user docset:
  • Welcome to LFJ, Getting Setup, Getting Started, Common FAQ and Fixes
  • LFJ DEX → Swap → How to Swap Tokens → Price Impact, Slippage and Safe Mode
  • Additional product areas are referenced in the nav: Liquidity, $JOE Token, Contracts & API, LFJ Roadmap 2026, POE (PropAMM), Liquidity Book resources.
• Interactive doc UI elements are visible:
  • Search input: “Search…”
  • Utility buttons/icons: copyCopy, collapse/expand chevrons, close controls.

How it connects to product behavior

• The swap UI explicitly includes Safe Mode and Slippage tolerance (0.1% / 0.5%); this doc page provides the rationale and risk framing behind those toggles.
• The presence of General Disclaimer suggests LFJ is aligning user education with liability boundaries and standardized warnings.

Strategic significance

• Documentation is not just support; it is part of the execution UX. Clear definitions of price impact and slippage reduce failed swaps, reduce support load, and protect the brand when volatile tokens move quickly.
• The nav’s references to Contracts & API and Liquidity Book indicate LFJ targets both end-users and integrators, even if those modules weren’t directly visible in the analyzed pages.

What it does

• /privacy is LFJ’s formal privacy and data-handling module. It defines how user data is collected, used, stored, and disclosed, covering analytics and security posture.

Observed content & sections

• Page heading: “Privacy Policy” with an explicit revision marker: “Updated 12 June 2025”.
• Section headers (h3) outline the scope and compliance surface:
  • Scope
  • Collection of Personal Data
  • Use of Personal Data
  • Disclosure of Personal Data
  • Automated Decisions
  • Cookies and Analytics
  • Children’s Privacy
  • Security
• The policy identifies the entity: El Ephjay Corp (“El Ephjay”, “LFJ”, “we”, “us”, “our”).

UI integration and localization

• The same global header appears here as on trading pages: Tokens, Swap, Stake, Bridge, Login, and language access.
• Language options are explicitly visible: English, Français, Türkçe, 中文, Tiếng Việt. This implies the compliance surface is designed to match the product’s international distribution.
• Settings elements visible globally (e.g., Theme/Language, testnet toggle, RPC endpoint selection) imply LFJ treats privacy/compliance as part of the core app shell, not a separate site.

Strategic significance

• For an onchain trading venue, privacy policy clarity affects exchange listings, institutional due diligence, and ad/analytics configuration.
• Explicit sections like Automated Decisions and Cookies and Analytics hint at tracking/experimentation needs (attribution, performance monitoring) while setting boundaries for data usage—important for a DEX aggregator and screener product.