crossChainPermits, not per function. Each entry whitelists a source/destination pair and the limits the session has to stay within.
Basic usage
Restrict a session to only bridge USDC from Base to Arbitrum:| Field | Description |
|---|---|
from | Source chain + token (+ optional maxAmount cap). Omit for no source-token restriction. |
to | Destination chain + token (+ optional recipient pin). Omit for no destination-token restriction. |
Guardrails
Tighten a permit with optional bounds:maxAmounton a source leg caps how much of that token the session can pull (a spending limit).validAfter/validUntilbound the permit deadline. Both accept aDate.fillDeadlinebounds the fill window per destination chain.
Recipient safety
By default a cross-chain permit enforces bridge-to-self on-chain: the destination recipient must be the smart account itself. This stops a leaked session key from routing funds to an attacker-controlled address. Opt out explicitly only when you need to bridge to a different recipient:Settlement layers
A permit allows any supported settlement layer by default. PasssettlementLayers to narrow it to a subset: