Skip to content
Fast
SDK References / Core SDK Execution

Supported EVM ↔ Fast deposits, withdrawals, and intents with @fastxyz/allset-sdk

@fastxyz/allset-sdk provides supported EVM ↔ Fast bridge workflows. Install it with npm install @fastxyz/allset-sdk and use the package README for exact parameters and runnable examples. Fast-only transfers and account queries use @fastxyz/sdk.

Workflow SDK entry point What the return value establishes
EVM → Fast deposit executeDeposit() The source-chain deposit transaction was submitted; Fast credit is a later step.
EVM → Fast smart deposit smartDeposit() A supported EIP-7702/UserOperation route was submitted; sponsorship and chain configuration must be available.
Fast → EVM withdrawal executeWithdraw() The Fast-side transfer/intent was submitted; destination delivery is asynchronous.
Custom Fast → EVM intent executeIntent() The requested intent was submitted; destination execution must be tracked separately.

The SDK also exports wallet/client helpers, deposit builders, intent builders, and address utilities. createEvmExecutor() recognizes the chain IDs listed in the package README, including Ethereum, Polygon, Arbitrum, Base, Arc, and supported testnets. Availability of a chain in the client map does not establish that a bridge route, contract deployment, token, relayer, or sponsorship policy is live for every environment. Supply and verify the correct chain-specific addresses and endpoints.

For operator-managed Fast multisig withdrawals, see the CLI 1.7.0 two-round withdrawal guide. It uses a local recovery journal and independent signers; the SDK entry-point table above does not describe that CLI orchestration.

Deposits and withdrawals are not atomic across both networks. A source transaction hash, Fast certificate, or returned order ID is not proof that the destination side completed. Persist the workflow identity and check source and destination status before retrying. Repeating an uncertain withdrawal with a new nonce can move funds again.

For ERC-20 deposits, executeDeposit() checks allowance and may submit an approval before the deposit transaction. smartDeposit() can pay gas in the deposited token on supported routes, but needs a working bundler/paymaster policy; it is not a universal gasless guarantee. Never send funds to an address merely because an EVM wallet is auto-linked to a Fast account: the bridge requires the documented deposit flow.

Withdrawal claims default to legacy encoding in the current package. The optional allset/intent/v1 encoding must be selected explicitly and should only be used with compatible deployed cross-sign and app components. See the claim encoding section for its validation and deployment constraints.

For production integrations, define a journal of source transaction, Fast transaction, recipient, amount, chain, and destination outcome. Treat an indeterminate response as unknown, not failed, and reconcile it before issuing another money-moving operation.