LayerSwap Swidge Configuration

Each source adapter accepts (account, config?). The protocol reads the provider configuration when it constructs its HTTP client. The sending account keeps its own chain provider.

Protocol fields

A nonempty API key is forwarded to apiUrl; choose that destination before supplying credentials. The HTTP client does not enforce HTTPS for an overridden endpoint.

The request timer is cleared after fetch returns, before the body is read. The client has no automatic retry loop. An execution request that fails ambiguously must be reconciled before creating or sending another deposit.

Source network and providers

fromChain is an operation option, not a constructor configuration field. With it omitted, the adapter detects a network from its bound account. With it supplied, use a provider network name from discovery.

Account, provider and selected network must agree. Source network identity is cached on adapter instances. Create a new instance after switching the account's provider or network. Some checks are skipped when a provider is absent, and Solana's explicit-network check cannot identify every cluster. An explicit fromChain is not independent proof of the account's network.

Amounts, slippage and addresses

• Use positive integer amounts in the source token's base units. The examples choose bigint; declared amount fields accept number | bigint.
• minAmountOut is in destination-token base units. Set a positive value appropriate to your accepted output.
• Swidge slippage is a fraction: 0.005 means 0.5%. The legacy bridge() adapter instead takes a percentage string such as '0.5'.
• Supply recipient for the intended destination address and refundAddress for an address you control on the source network. Validate both address formats and chains in your application.
• refuel requests a provider-supported native-gas drop on the destination. Availability depends on the selected route.
• referenceId is an application-supplied reference included when the provider swap is created.

Without an explicit recipient, execution uses the account's address only when source and destination networks have the same provider VM type. The refund address defaults to the source account's address.

Fee limits and units

The provider's service fee and destination network fee are deducted from the source amount. Their entries have included: true and use source-token units. Separate source gas has included: false and uses the source chain's native units. Do not add amounts across different tokens.

Execution configuration overrides the constructor's fee fields for that call. For ERC-4337 accounts, the EVM adapter also forwards the supported wallet configuration overrides when estimating and sending the deposit.

To inherit a constructor fee limit, omit that property from the per-call configuration. Passing it as undefined overwrites the constructor value and removes that limit for the call.

If the create-swap response lacks a quote, execution uses empty fees and zero output fields. A positive minAmountOut rejects that response before broadcast. Without such a minimum, missing quote data does not itself stop execution. Empty fees do not prove a zero-cost route.

Chain-specific settings

Bitcoin accepts options.feeRate in sat/vB for one operation. It overrides fee-rate estimation for PSBT construction. The resulting transaction includes the required reference output, which contributes to its fee. See Bitcoin Deposits.

EVM standard accounts receive one transaction. ERC-4337 accounts receive a one-item transaction array and applicable per-call wallet configuration. Solana uses a decoded provider transaction template with a refreshed blockhash. TON uses a message built from the provider action and has separate hash tracking.

Next Steps

---

Need Help?