Skip to content
Fast
SDK References / Funding Abstraction

Swapper On-ramp

View as Markdown

The Fast CLI exposes several funding routes. They are not interchangeable: a hosted provider flow and an EVM → Fast bridge have different requirements and completion signals.

CLI routes

Section titled “CLI routes”
Terminal window
# Discover supported mainnet funding choices
fast fund --network mainnet --amount 50


# Bridge USDC from a supported EVM chain into Fast
fast fund usdc crypto 50 --chain arbitrum-sepolia --token USDC


# Open a hosted provider route, where available
fast fund card --network mainnet --amount 50
fast fund crypto --supplier coinbase --network mainnet

fast fund usdc crypto is the EVM bridge command. fast fund crypto is a hosted supplier route; fast fund fiat is not the documented command. On mainnet, the CLI default token is fastUSD, which does not exist on EVM source chains; select --token USDC for an EVM USDC bridge. Use fast fund usdc --network mainnet to inspect the CLI’s USDC route choices. Check fast fund --help and the CLI README for current chain and supplier support before sending funds.

SDK route

Section titled “SDK route”

Use @fastxyz/allset-sdk to build or execute a supported EVM deposit programmatically. For an ERC-20 such as USDC, the SDK may approve the bridge contract before submitting the deposit. Fast credit follows source-chain confirmation and relay; do not treat the EVM transaction hash as a completed Fast deposit.

The SDK also has smartDeposit() for supported EIP-7702 routes. That route depends on configured chain contracts and a usable bundler/paymaster sponsorship policy. If sponsorship is unavailable, it fails before a successful deposit; do not replace it with a plain transfer to an auto-linked EVM address, because that does not produce an AllSet deposit event.

Only use token addresses, bridge contracts, network IDs, and provider URLs validated for the chosen environment. The AllSet SDK README contains the current API and supported client chain IDs. Actual route availability is determined by deployment configuration, not just by a chain being listed in the SDK.