Execute a LayerSwap Swidge

Start with a protocol bound to the matching initialized account, as shown in Usage. Match that account's provider to the chosen source network. These examples remain subject to release availability.

Confirm a stable intent

Select network names and token identifiers from discovery. Validate the destination recipient and source refund address for their intended networks. Choose a positive minimum destination amount and all three fee limits before requesting consent.

export async function executeLayerswap({
  protocol,
  sourceNetwork,
  destinationNetwork,
  sourceToken,
  destinationToken,
  amount,
  recipientAddress,
  refundAddress,
  minAmountOut,
  limits,
  confirm
}) {
  if (typeof amount !== 'bigint' || amount <= 0n ||
      typeof minAmountOut !== 'bigint' || minAmountOut <= 0n) {
    throw new RangeError('Supply positive bigint input and minimum-output amounts')
  }
  if (typeof recipientAddress !== 'string' || recipientAddress.length === 0 ||
      typeof refundAddress !== 'string' || refundAddress.length === 0) {
    throw new TypeError('Supply the intended recipient and source refund address')
  }

  const identifiers = [sourceNetwork, destinationNetwork, sourceToken, destinationToken]
  if (identifiers.some(value => typeof value !== 'string' || value.length === 0)) {
    throw new TypeError('Supply discovered network names and token identifiers as strings')
  }

  const intent = Object.freeze({
    fromChain: sourceNetwork,
    toChain: destinationNetwork,
    fromToken: sourceToken,
    toToken: destinationToken,
    fromTokenAmount: amount,
    recipient: recipientAddress,
    refundAddress,
    minAmountOut,
    slippage: 0.005
  })
  const caps = {
    bridgeMaxFee: limits?.bridgeMaxFee,
    maxNetworkFeeBps: limits?.maxNetworkFeeBps,
    maxProtocolFeeBps: limits?.maxProtocolFeeBps
  }
  for (const value of Object.values(caps)) {
    if (typeof value !== 'bigint' || value < 0n) {
      throw new RangeError('Supply all three fee limits as non-negative bigint values')
    }
  }
  Object.freeze(caps)

  const quote = await protocol.quoteSwidge(intent)
  if (!await confirm({ intent, caps, quote })) return null

  return protocol.swidge(intent, caps)
}

confirm is your application callback. Show the source amount/token, destination token, recipient, refund address, minimum output and each fee with its denomination. The helper copies the primitive intent and limit values before awaiting consent. It requires all three limits as non-negative bigint values even though the SDK also declares numeric limits. These explicit per-call values override the constructor's fee limits; missing values are rejected before quoting or asking for consent.

Keep the bound account and its provider fixed through confirmation. If either changes, cancel the intent and construct a new matching protocol instance.

quoteSwidge() resolves the route and input amount but does not validate recipient, refundAddress or minAmountOut. Your application validates those inputs before consent, and execution applies its minimum-output check.

The preview does not lock execution terms. swidge() creates its own provider swap and evaluates the quote attached to that response. It does not expose a second application-confirmation callback between receiving those instructions and sending the source deposit.

What execution can do

1. Check the account, route and supplied integer options.
2. Create a provider swap and receive its deposit instruction and execution quote.
3. Check the minimum output and included-fee cap.
4. Prepare the source deposit and check applicable basis-point limits.
5. Submit through the source adapter, then notify the provider on a best-effort basis.

Source-specific behavior

EVM calldata receives syntax checks, but its complete effects are not decoded and independently verified. Solana reconstructs the transaction rather than independently reviewing every instruction's business intent. The provider remains responsible for its routing instructions and destination payout.

This family does not expose a separate getRequiredApproval() application flow. Follow the selected adapter's deposit path rather than copying an allowance workflow from another provider.

Keep the submission identifiers

On success, persist result.id, result.hash, the selected networks and result.transactions before starting other application work. If persistence fails after success, use the result already held by your application to reconcile the deposit; do not call execution again as a storage retry.

A source hash confirms only that the send path returned it. Destination payout or refund is separate. On an ambiguous send error, inspect source-chain state and the provider's swap before deciding whether another deposit is necessary. See Track Settlement.

Next Steps

Need Help?