LI.FI Swidge Configuration

Configure LifiSwidgeProtocol with a WDK EVM account when you need execution, account-address-based quotes, or status lookups. Without an account, the module supports quotes and discovery when config.provider is supplied.

import { WalletAccountEvm } from '@tetherto/wdk-wallet-evm'
import { LifiSwidgeProtocol } from '@lifi/wdk-protocol-swidge-lifi'

const account = new WalletAccountEvm(seedPhrase, "0'/0/0", {
  provider: 'https://mainnet.infura.io/v3/YOUR_KEY'
})

const swidge = new LifiSwidgeProtocol(account, {
  integrator: 'my-app',
  order: 'RECOMMENDED',
  maxNetworkFeeBps: 100,
  maxProtocolFeeBps: 50
})

Constructor

new LifiSwidgeProtocol(account?, config?)

When account is omitted, config.provider is required for quoteSwidge(). Accountless quote requests omit fromAddress.

Configuration Options

Per-Call Overrides

Pass a config object to swidge(options, config) to override fee caps or execution settings for one operation.

const route = {
  fromToken: '0xdAC17F958D2ee523a2206206994597C13D831ec7',
  toToken: '0xdAC17F958D2ee523a2206206994597C13D831ec7',
  toChain: 'arbitrum',
  fromTokenAmount: 10_000_000n
}

await swidge.swidge(route, {
  maxProtocolFeeBps: 20,
  maxNetworkFeeBps: 75
})

Route Filtering

By default the module applies no extra route filtering: denyBridges is not set, allowDestinationCall is not forwarded (LI.FI's server-side default of true applies), and quotes that require native token value execute as-is. This gives the widest route coverage and matches LI.FI SDK behavior.

For gasless integrations — for example ERC-4337 where a paymaster covers source-chain gas but the LI.FI route transaction itself must not require separate native token value — opt in explicitly:

import {
  LifiSwidgeProtocol,
  NATIVE_VALUE_BRIDGE_DENY_LIST
} from '@lifi/wdk-protocol-swidge-lifi'

const swidge = new LifiSwidgeProtocol(account, {
  denyBridges: NATIVE_VALUE_BRIDGE_DENY_LIST, // filter native-value bridges at quote time
  allowNativeValue: false                     // reject any quote whose tx still needs native value
})

NATIVE_VALUE_BRIDGE_DENY_LIST is the maintained list of bridges known to require native token value in the source transaction. denyBridges replaces (does not append to) any default, so denyBridges: ['across'] denies only across.

Set allowDestinationCall: false to exclude routes that require a destination-chain call, such as a swap after bridging, which can leave the user holding an intermediary token if the destination call fails.

With allowNativeValue: false, execution rejects any quote whose transaction request requires native token value before sending approvals or the route transaction, even if a native-value bridge was not filtered out at quote time.

Contract Validation

The module always validates returned transaction data before forwarding it to the wallet. Enable trustedContracts when the integration also needs an allowlist check against LI.FI Diamond deployments and Permit2.

const swidge = new LifiSwidgeProtocol(account, {
  trustedContracts: true
})

To extend the built-in allowlist for a chain, pass chain IDs mapped to one or more extra trusted addresses:

const swidge = new LifiSwidgeProtocol(account, {
  trustedContracts: {
    137: [trustedPolygonContractAddress]
  }
})

trustedPolygonContractAddress must be a validated EVM address for the additional contract your integration trusts.

Security Notes

• Do not expose LI.FI API keys in browser clients.
• Use explicit fee caps when routing user funds.
• Validate route choices with getSupportedChains() and getSupportedTokens() before quoting.
• Ask for user confirmation before calling swidge().