Ekubo

Pages: /about-ekubo/introduction

This module is the developer/user-facing documentation hub for Ekubo Protocol. The page header shows “👋Introduction” and a clear positioning statement: “Ekubo Protocol is an open source, permissionless and free by default AMM infrastructure”. The layout is a typical GitBook-style doc shell with:

• Left navigation tree exposing product areas and guides (visible items include “Vision”, “Features”, “User Guides”, “Add liquidity”, “Dollar-cost average orders”, “Governance”, “Integration Guides”, “Extensions”, “Swapping”, “Reference Links”).
• Search input: a single field labeled “Ask or search…” indicating full-site doc search.
• On-page table of contents: “On this page” plus an “Edit” entry, implying public-source docs with an edit workflow.
• UI controls: icon buttons such as bars (sidebar toggle), xmark / circle-xmark (close), chevron-up/down/right, and sun-bright (theme switch).

Strategic significance:

• This module is the canonical place to explain advanced AMM concepts and product features (notably liquidity management, DCA, governance, and integration). It reduces support load and is essential for integrators on Starknet/EVM.
• The navigation items mirror the app’s top-level features, effectively acting as an information architecture reference when app routes are missing or changing.

Pages: /swap, /evm/swap

This is the core trading interface. Both pages share a common top navigation (Trade, Pool, Charts, Rewards, Governance) and expose order-type switching directly in the main panel.

Key UI elements observed:

• Mode tabs:
  • On /swap (Starknet context): “Swap”, “DCA”, “Limit”.
  • On /evm/swap: “Swap”, “DCA” (Limit is not shown in the captured content, suggesting feature parity may differ by chain or rollout stage).
• Token in/out selection:
  • The input header shows “From ETH” and a token button labeled “ETH”.
  • A counterpart selector reads “Select token”, indicating a token list modal/picker.
• Price context: ETH displays a live-ish USD reference (e.g., $2,155.69 on /swap, $2,134.82 on /evm/swap).
• Gas estimator banner:
  • Shows “$0.03” with text “The average gas cost of a swap.”
  • On /evm/swap, it adds: “The average gas cost of a swap on Ethereum. The current base fee is 0.107 GWEI.” (chain-specific detail).

Strategic significance:

• This module is the revenue and retention driver: it funnels users into swaps and recurring execution via DCA.
• The presence of Limit on Starknet suggests an intent to offer more advanced order types where execution costs are lower.
• Chain-aware fee messaging (USD gas + base fee) helps users decide between Starknet vs EVM execution.

Pages: /swap, /evm/swap, plus shared header on 404 routes

This module is the app-wide “session” layer: connecting a wallet and setting the active network context. It’s visible as persistent header controls and small chain cues embedded in the swap views.

Observed components:

• Network selector / indicator:
  • On Starknet-facing pages the header includes a “Starknet” button.
  • On EVM-facing pages it includes “EVM”.
  • Each environment also cross-links the other network label in the footer/info area (e.g., /swap shows “Documentation” and “EVM” nearby; /evm/swap shows “Documentation” and “Starknet”).
• Wallet connect entry point:
  • A prominent “Connect wallet” button exists across pages.
  • On /evm/swap, there is an additional compact identity button “0x”, typically used to show a connected EVM address (short form) and open an account menu.
• Network-coupled fee telemetry:
  • The swap view surfaces average gas cost $0.03 everywhere, but only the EVM page exposes base fee (0.107 GWEI), implying the fee model display is conditional on network.

Strategic significance:

• Ekubo is positioning a single interface across Starknet + EVM. This module keeps the user oriented: which chain they’re on, what wallet is required, and what execution costs look like.
• The presence of both “Connect wallet” and “0x” hints at a stateful header capable of switching between disconnected/connected UI states without changing pages.

Pages: /earn, /farm, /liquidity, /pool, /portfolio, /stake, /trade

These routes all render the same error state: Title “Page not found - Ekubo Interface” with an in-page heading “Page Not Found” and message “The URL you entered does not exist. Please check the URL and try again.” Despite the missing routes, the global app shell still loads, which reveals important functional scaffolding.

What’s present even on 404:

• Global navigation buttons are consistently rendered: Trade, Pool, Charts, Rewards, Governance.
• Network + session controls remain available: Starknet (or EVM depending on context) and Connect wallet.
• A small info strip continues to show “$0.03” and “Documentation”, plus the chain label toggle (e.g., “EVM” shown on Starknet-context 404 pages), suggesting these are app-level components rather than page-level.

Implications / strategic significance:

• The interface is built as a single-page app with robust layout composition: header + footer widgets mount even when route resolution fails.
• Several expected modules are either moved, gated, or not yet shipped at these paths:
  • Liquidity management is implied by nav (Pool) but /pool and /liquidity are not valid.
  • Yield surfaces are implied by Rewards, but /earn and /farm are not valid.
  • Account views are implied by /portfolio and /stake, but they are not valid.

From an engineering standpoint, this module highlights a routing mismatch: the product IA exists in the shell, but the route table (or redirects) does not map legacy paths to current pages.