PancakeSwap

Pages: /swap

This module is the primary spot trading entry point. The /swap page exposes three order modes via buttons: “Swap”, “TWAP”, and “Limit”, indicating both immediate execution and time/price-conditional routing.

UI and interactive elements

• Token/network selectors are visible (e.g., “SOL Solana”), plus quote preview text like “~0 USD”.
• Core trade input is a numeric field (“0.00”) and a settings control for “Slippage Tolerance 0.50%”.
• Wallet gating is explicit: “Connect Wallet” / “WalletConnect”.
• Contextual help is embedded: “Need Help?” and “Quick start now on How to Swap!”, plus a “Details” button for expanded route/fee information.

What it enables

• Standard swap flow (amount in → amount out preview → submit).
• Advanced execution modes (TWAP/Limit) reduce MEV impact and allow hands-off execution; the UI suggests these are first-class modes rather than separate products.

Strategic significance

• This is the platform’s conversion funnel: it’s where network selection, wallet connection, and execution preferences are unified.
• The presence of TWAP/Limit on the same page as Swap implies a shared routing/quoting stack and a consistent approval/signing pipeline across modes.

Pages: /perp/v2/BTCUSD

This module provides decentralized perpetual futures. The instrument page is market-specific (e.g., BTCUSD) and shows a live price as the document title (e.g., “70,664.4”). The description states: “Trade Decentralized Perpetuals with up to 50x Leverage on BNB Chain”, which sets expectations on margin and network constraints.

UI and interactive elements

• Order entry fields include a size input (placeholder “0.0”) and a dedicated “Limit Price” field, indicating at least limit-order placement.
• Wallet connection is required (“Connect Wallet”), and there’s a visible Settings entry.
• Language selector is present (e.g., English, 繁體中文, 한국어, 日本語, etc.), suggesting global user targeting.
• Navigation shows this module sits alongside Swap, Liquidity, Position Manager, Staking, and Bridge, implying shared account state and multi-product session continuity.

What it enables

• Leverage trading with a dedicated order form and market context.
• Network anchoring to BNB Chain reduces fragmentation for perp liquidity/settlement.

Strategic significance

• Perps expand revenue beyond AMM swap fees into funding/spread/fee-based derivatives.
• Separate market routes (/perp/v2/:symbol) support deep linking, shareable market pages, and scalable listing management.

Pages: /liquidity/pools, /liquidity-pools

This module covers discovering pools, managing LP positions, and creating liquidity. The main LP earnings page /liquidity/pools is titled “Earn from LP” and is structured around “Liquidity Pools & Farms”.

UI and interactive elements

• Primary actions: “Create Pool”, “Add Liquidity”, plus views “All Pools” and “My Positions” (wallet-gated via “Connect Wallet”).
• Education and migration: “Learn How” and “Legacy Farm Page” suggest a transition path from older farming UX.
• Pool discovery table exposes: “FEE TIER”, “APR”, “TVL”, “VOLUME 24H”, “POOL TYPE”, “POOL FEATURE”.
• A concrete data point is visible in listings: cbETH/WETH with FEE TIER 0.01% and APR 9.73% under a highlighted block like “PANCAKE PICKS”.

/liquidity-pools appears as a complementary list view with a simpler performance table: Pool | TVL | Volume 24h | Fees 24h | APR 24h, plus a speed/priority control (“Priority: Turbo”) and extensive language switching.

Strategic significance

• Pool metrics (TVL/volume/fees/APR) are surfaced as first-class decision inputs to drive liquidity placement.
• “My Positions” makes LP state persistent across the product suite, while “Create Pool” expands long-tail asset onboarding.

Pages: /pools, /ecosystem-and-partnerships/business-partnerships/syrup-pools

The Syrup Pools module is the single-asset staking experience. /pools is titled “Syrup Pools” with headings “Just stake some tokens to earn.” and “High APR, low risk.” The UI is clearly optimized for scanning and position management.

UI and interactive elements

• Wallet gating: “Connect Wallet” / WalletConnect.
• Pool browsing controls include Live / Old, a “Staked only” filter, and sorting (visible options include Hot, APR, Earned, Total staked, and recency cues like Latest).
• The page design implies two key states: discovery (no wallet) and portfolio management (with wallet + “staked only”).

The partnership documentation page /ecosystem-and-partnerships/business-partnerships/syrup-pools complements the UI by describing an “Example of a Syrup Pool process”, positioning Syrup Pools as a distribution channel for partner tokens.

What it enables

• Users stake a token (often CAKE or another specified asset) to earn rewards without managing LP impermanent loss.
• Partners can run incentive programs with a standardized staking UX.

Strategic significance

• Syrup Pools act as the “simplest earn product,” retaining users who don’t want LP complexity.
• The existence of a business playbook indicates this is also a B2B growth module (token marketing + user acquisition).

Pages: /cakepad, /ecosystem-and-partnerships/business-partnerships/initial-far

This module handles primary token launches and allocations. /cakepad is branded “CAKE.PAD” with core sections: “How to Take Part”, “Commit $Cake”, “Claim your tokens”, and “FAQ”—a full lifecycle from participation to settlement.

UI and interactive elements

• Strong wallet gating and CTAs: “Connect Wallet” / WalletConnect.
• Discovery states: tabs/filters like “Latest” and “Finished”.
• A launch detail snapshot is visible: “Ended On Monad”, implying chain-specific launches; a “Details” button indicates a drill-down allocation page.
• Primary navigation cross-links to Trade / Earn / Play, keeping launch participation inside the main app shell.

The IFO documentation page /ecosystem-and-partnerships/business-partnerships/initial-far (IFOs) adds process framing with “Example of an IFO Process”, clarifying this is not only a UI but a repeatable partner program.

What it enables

• Allocation via committing CAKE and later claiming distributed tokens.
• A standardized listing pipeline for new projects across supported networks.

Strategic significance

• Launchpad products convert platform attention into CAKE demand and partner revenue.
• Chain-specific launches (e.g., Monad) position PancakeSwap as multichain, not just BNB-only.

Pages: /lottery, /prediction

This module provides engagement loops beyond trading/earning. /lottery is a full-featured on-chain lottery with clear round mechanics and user history.

Lottery UI and data points

• Headings emphasize urgency and state: “Get your tickets now!”, “until the draw”, “Next Draw”, “Prize Pot”, “Your tickets”, and “Finished Rounds”.
• Concrete live data is shown: “$31,103 in Prizes!” and “Next Draw #1940”.
• Primary action: “Buy Tickets” with supporting “Details”.
• Separate exploration paths: “All History” vs “Your History”; wallet required for personalized checks (“Connect your wallet to check if you’ve won!”).

Prediction UI

• /prediction currently foregrounds network correctness with “Check your network” and a “Switch network” button, indicating feature availability is chain-dependent and guarded by network checks.

Strategic significance

• Lottery drives repeat visits and small, frequent transactions, benefiting fee flow and brand stickiness.
• Strong network gating in Prediction reduces user error (wrong chain) and reflects operational constraints (oracle/market availability per chain).

Pages: /voting

This module exposes protocol governance and community decision-making. The /voting page is titled “Voting” and opens with “Have your say in the future of the PancakeSwap Ecosystem”, framing it as ecosystem-level governance.

UI and interactive elements

• Primary CTA: “Make a Proposal”, implying proposal creation is accessible from the UI (likely gated by eligibility).
• Proposal filtering is first-class: tabs “Core”, “Community”, “All”, and a state label like “Vote Now” to surface active proposals.
• There is explicit network enforcement: a “Check your network” section similar to other modules, plus wallet gating via “Connect Wallet”.
• A feedback bridge exists: “Got a suggestion?” suggests non-binding idea submission alongside formal proposals.

What it enables

• Users browse proposals, filter by category, and vote when eligible.
• Proposers can start governance workflows from a single entry point.

Strategic significance

• Governance is the coordination layer across trading, liquidity incentives, and token programs.
• Category separation (Core vs Community) signals different trust levels/process rigor, which helps manage risk and expectations for protocol changes.

Pages: /info/v3, /burn-dashboard

This module provides market transparency and CAKE supply tracking.

Info & Analytics (/info/v3)

• Headings define the scope: “PancakeSwap Info & Analytics”, “Top Tokens”, “Top Pairs”, “Transactions”.
• Cross-chain analytics is explicit via network buttons: Ethereum, BNB Smart Chain, ZKsync Era, Arbitrum One, Linea Mainnet, Base, opBNB.
• A search form “Search liquidity pairs or tokens” supports discovery by symbol/address.
• Navigation suggests multiple DEX engines under one analytics umbrella (e.g., Infinity, StableSwap, plus Overview / Pairs / Tokens).

Burn Dashboard (/burn-dashboard)

• Tokenomics summary is concrete: Total supply 343M CAKE, CAKE Burned 54.29M, Peak Supply 397M.
• The page shows a timestamp: “Last updated on: Mar 17, 2026”.
• Chart controls include denomination toggle (CAKE / USD) and time ranges (3m, 6m, 1y, Max).
• Transaction table columns expose on-chain traceability: Tx Hash | Amount | Timestamp | From | To | Type.

Strategic significance

• Analytics reduces information asymmetry for LPs and traders (top pairs/tokens, transaction activity).
• Burn transparency supports CAKE value narrative and helps users verify supply policy via raw tx records.

Pages: /bug-bounty, /developers/contributing, /readme/help/troubleshooting

This module is the platform’s “engineering surface area”: vulnerability intake, contributor onboarding, and end-user error resolution.

Bug Bounty (/bug-bounty)

• The page centers on preventing loss of user funds, spanning smart contracts, websites, and apps.
• UI elements include Search and an “On this page” TOC control, indicating a long-form policy document.
• A table with Level columns suggests tiered severity/reward structure (e.g., levels per impact).

Contributing (/developers/contributing)

• Structured onboarding with headings: “Setup your dev environment”, “Coding rules”, “Use the UIKit”, “Use the tools!”, “Some good practices”, and “Creating your pull request”.
• Doc shell includes global search (“Ask or search…”) and language dropdown, typical of a maintained documentation portal.

Troubleshooting (/readme/help/troubleshooting)

• Maps common on-chain/DEX errors to fixes: INSUFFICIENTOUTPUTAMOUNT, INSUFFICIENTAAMOUNT / INSUFFICIENTBAMOUNT, PancakeRouter: EXPIRED, Pancake: K, Pancake: TRANSFER_FAILED.
• Provides actionable steps like Approve the LP contract, Query balanceOf, and guidance for Add or Remove Liquidity.

Strategic significance

• Reduces support burden and increases user success rate during swaps/LP actions.
• Bug bounty + contributor guidelines shorten response time for security issues and standardize external contributions.