Skip to main content

Advanced config

These pages cover behavior that is not just a single field in Configuration—for example how the widget shares or replaces wallet connection when it lives inside your app.

Main topic: wallet management​

Most teams care about one thing here: whether the widget drives connect itself, or plugs into the wallet UX you already ship.

  • Standalone — use the widget’s built-in connect UI; no extra wallet wiring.
  • Embedded in a dApp — mount BlinqWidget under your existing WagmiProvider (RainbowKit, Dynamic, Reown AppKit, etc.) so EVM accounts and chain switching stay in sync with the rest of your app.
  • Host override — set config.wallet.onConnectClick when you want the widget to always open your connect flow (custom modal or non‑EVM stacks).

→ Full guide: Wallet management