🎨Customization

WheelX Widget supports both functional configuration and visual customization.

If you want the fastest workflow, start from the hosted theme page:

Recommended workflow:

  1. Open the theme page

  2. Adjust colors and typography

  3. Copy the generated config

  4. Paste it into your host app

  5. Add functional restrictions such as networks or tokens

🧩 Configuration Overview

The main config type is:

Example:


πŸ”€ mode

Controls the widget flow.

Supported values:

  • bridge-and-swap Enables swap, bridge, and cross-chain routing.

  • swap Restricts the widget to same-chain swap flows.

Example:

Use swap when:

  • your product only supports a single chain

  • you want a simpler UI

  • you do not want users switching into bridge routes


πŸ’Έ referralCode

Adds your affiliate code to widget quote requests.

Good to know:

  • the value is trimmed before use

  • the widget does not need a separate UI change for referral tracking

  • the same config can be combined with theme and token restrictions

You can get your code here:


🌐 networks

Restricts which chains users can choose.

Supported forms:

  • 'all'

  • a single chain ID

  • an array of chain IDs

Examples:

Allow only Base:

Allow bridge from Ethereum or Base into Base or Polygon:

Use this when:

  • your app only supports a known list of chains

  • you want to avoid irrelevant routes

  • you want a smaller, more guided selection flow


πŸͺ™ defaultTokens

Sets the initial token selection shown in the widget.

Recommended usage:

  • prefill the most common trading pair

  • match the primary network of your product

  • reduce the number of clicks before the user gets a quote

Notes:

  • chainId and address are the real identifiers

  • symbol is optional, but helpful for readability

  • if a default token is not valid under the current restrictions, the widget falls back to the nearest valid option


πŸ” allowedTokens

Restricts the selectable tokens on a per-chain basis.

This is especially useful when:

  • your product should only expose approved assets

  • you want to guide users into a narrow route set

  • you are embedding the widget for a single token onboarding path

Behavior notes:

  • restrictions are chain-scoped

  • addresses are normalized internally

  • chains not listed remain unrestricted


πŸŽ›οΈ styles

Use styles to override the widget appearance with slot-based style objects.

Style Areas

The widget supports a broad set of visual slots. In practice, the most useful groups are:

  • Form shell formContainer, formTitleText, formFooterText

  • Token and input area sectionContainer, tokenSelector, amountInputContainer, amountInputText

  • Buttons primaryButton, primaryButtonText, quickHalfButton, quickMaxButton

  • Token modal tokenModalContent, tokenModalSearchInput, tokenModalChainPanel, tokenModalTokenPanel

  • Slippage controls slippageSettingsTrigger, slippagePopoverContent, slippageAutoButton, slippageCustomInput

  • Quote and transaction status quoteInfoContainer, quoteInfoCard, txStateCard, txStatePrimaryButton

Example: Branded Dark Theme

Last updated