The Trustware SDK includes WalletConnect support out of the box via the Reown AppKit Universal Connector. A built-in project ID and sane defaults are provided, so in most cases you do not need to touchDocumentation Index
Fetch the complete documentation index at: https://docs.trustware.io/llms.txt
Use this file to discover all available pages before exploring further.
walletConnect at all. This page covers when and how to override those defaults.
WalletConnectConfig type
Properties
Your WalletConnect Cloud project ID. The SDK ships with a built-in project ID
for convenience, but you should supply your own in production to avoid
hitting shared rate limits and to have visibility into your usage in the
WalletConnect dashboard.
The primary chain IDs the connector will support. Defaults to
[1]
(Ethereum mainnet). Wallets will be prompted to switch to one of these chains
when connecting.Additional chain IDs that the connector advertises as optional. Wallets that
support these chains can switch to them without being required to at
connection time.
dApp metadata shown inside the wallet during a WalletConnect session. If
omitted, the connector uses generic Trustware defaults.
The display name of your dApp shown in the wallet.
A short description of your dApp.
The canonical URL of your dApp. Must be a valid https URL.
An array of icon URLs for your dApp. The wallet will use the first icon in
the list.
Override the WalletConnect relay server URL. Defaults to WalletConnect’s
public relay. Only change this if you are running a private relay.
Controls whether the SDK renders its built-in QR modal when initiating a
WalletConnect session. Set to
false if you want to handle the QR display
yourself.Set to
true to disable WalletConnect entirely. The connector will not be
initialized and will not appear as a connection option in the widget. Useful
when your app already owns wallet state and you are using the host wallet
integration pattern.When to configure vs leave as default
Leave as default when:- You are prototyping or building an internal tool.
- You are using the drop-in widget pattern and want the shortest path to production.
- You are shipping to production and want your own WalletConnect project ID for rate limit isolation and usage analytics.
- Your app targets chains other than Ethereum mainnet (
[1]). - You want your dApp name and icon to appear correctly inside connected wallets.
- You are using the host wallet integration pattern and want to disable WalletConnect to avoid duplicate connection UI.
WalletConnect via Reown AppKit
WalletConnect is handled internally through the Reown AppKit Universal Connector. The connector is initialized once whenTrustwareProvider mounts. You do not need to install or configure AppKit directly — the SDK manages the integration for you.
All WalletConnect behavior in the current SDK version goes through the
Reown AppKit Universal Connector. You do not need to install or configure
AppKit separately.
