⚙️Configure Widget
Flexibility at your fingertips
The LI.FI Widget supports a range of configuration options, allowing you to:
Allow or deny specific chains, tokens, bridges, and exchanges.
Preselect default source and destination chains.
Choose default tokens for both source and destination.
Set the amount of the destination token.
Specify a destination address.
Customize various LI.FI SDK settings through the
sdkConfig
configuration.
These options enable precise control over the widget's behavior and improve the user experience by adjusting it to specific needs and preferences.
Find an overview of all configuration options in Widget API Reference.
LI.FI SDK configuration
The LI.FI Widget is built on top of the LI.FI SDK, leveraging its robust functionality for cross-chain swaps and bridging. The sdkConfig
option allows you to configure various aspects of the SDK directly within the widget.
Let's look at the example of configuring private RPC endpoints using the sdkConfig
option.
In a production app, it is recommended to pass through your authenticated RPC provider URL (Alchemy, Infura, Ankr, etc).
If no RPC URLs are provided, LI.FI Widget will default to public RPC providers.
Public RPC endpoints can sometimes rate-limit users during periods of heavy load, leading to issues such as incorrectly displaying balances.
Please see other SDK configuration options in the Configure SDK section.
Preselect chains and tokens
The LI.FI Widget allows you to preconfigure default chains and tokens, making it easy to set up your desired swap or bridging parameters right from the start. Below is an example of how to configure the widget with specific default chains, tokens and amount.
By configuring these options, you can streamline the user experience, ensuring that the widget is preloaded with the desired chains and tokens for the swap or bridge. This reduces the need for manual input and helps guide users through the intended flow.
Configure allow and deny options
We provide allow
and deny
configuration options to control which chains, tokens, bridges, and exchanges can be used within your application. Here’s how you can set up and use these options:
Apart from the allow
and deny
options, the tokens
option can be configured to include other tokens or featured tokens that will appear at the top of the corresponding list of tokens.
Destination address
There are use cases where users need to have a different destination address. Usually, they can enter the destination address independently.
Still, the widget also has configuration options to pre-configure the destination address or create a curated list of wallet addresses to choose from.
Configure single destination address
Developers can use the toAddress
option to configure a single destination address. The address
and chainType
properties are required, while the name
and logoURI
properties are optional.
Configure a curated list of wallet addresses
Developers can use toAddresses
option to configure a curated list of wallet addresses.
Using this configuration, when users click on the Send to wallet
button, they will open a pre-configured list of addresses from which to choose, skipping the step where they can manually enter the address.
Last updated