Transfer Limits
Every transfer must fall within per-request limits, and each vault has a cap on the total amount it holds. These limits bound how much value any single transfer, and any vault in total, can move.
| Limit | Applies to | Enforced by |
|---|---|---|
| Per-request limit | The minimum and maximum amount of each lock and each release | The vault on the asset’s origin chain |
| Global cap | The total amount of each asset the vault will hold. It applies to locks only. | The vault on the asset’s origin chain |
| Wrapped-token limit | The minimum and maximum amount of each send of a wrapped token | token_bridge_service on SupraMVM, TokenBridge on SupraEVM |
| Fee coverage | The amount must be larger than the fee charged on the source chain | The fee operator on the source chain |
The Ethereum TokenVault enforces the limits of Ethereum-native assets. The SupraMVM token_vault enforces the limits of SupraMVM-native assets, such as SUPRA.
Lock limits and the wrapped-token limit apply to the amount that is locked or burned, not to the amount you enter. That amount is the amount you send, less any dust and the Token Bridge’s share of the service fee. The locked or burned amount includes the relayer reward.
Wrapped tokens
A wrapped token is burned rather than locked when it is sent, so it never passes through a vault. Its limits depend on where it is sent from:
- Sent from SupraMVM. The wrapped-token limit takes the place of the vault’s lock limit.
token_bridge_servicechecks it against the amount that is burned. Until a wrapped token’s limit is configured, the token cannot be sent from SupraMVM. - Sent from Ethereum. The
TokenBridgecontracts on Ethereum Mainnet and Sepolia have no wrapped-token limit. A wrapped token sent from Ethereum, such as the SUPRA ERC-20 token, has one bound only: the release limits of the vault on its origin chain, applied on delivery. - Sent from SupraEVM. The
TokenBridgeon SupraEVM Devnet checks a wrapped-token limit against the amount that is burned, in the same way astoken_bridge_serviceon SupraMVM. - Minted on delivery. No separate cap applies to minting. The vault limits on the asset’s origin chain bound the amount minted.
Current values
The tables below list the limits configured on the deployed contracts, for each direction of each route. The admin of each chain can change them, so read the current values from the contracts before you send a transfer. See Quote Fees and Limits.
The maximum per transfer is the smallest of the maximums checked in that direction. The contract minimum for every lock, release and wrapped-token send is 1 base unit of the asset, unless a table lists another minimum. The amount must also be larger than the fee. See Fees.
A global cap of “None” means that no global cap applies: the asset is burned rather than locked, or the vault has no cap configured.
Mainnet
Ethereum → SupraMVM
ETH, WETH, USDC, USDT, WBTC and SolvBTC are locked in the Ethereum TokenVault, which checks its lock limits and global cap. Native ETH is wrapped into WETH before it is locked, so the WETH limits apply to it. The SUPRA ERC-20 token is burned on Ethereum, so only the release limits of the SupraMVM token_vault apply, on delivery. Ethereum does not check this limit when you send, and a transfer above it is not delivered until the limit allows it.
| Asset you send | Maximum per transfer | Global cap |
|---|---|---|
| ETH, WETH | 3.888 WETH | 19.44 WETH |
| USDC | 9,000 USDC | 45,000 USDC |
| USDT | 3,800 USDT | 19,000 USDT |
| WBTC | 0.00166 WBTC | 0.0083 WBTC |
| SolvBTC (disabled in app) | 0.00166 SolvBTC | 0.0083 SolvBTC |
| SUPRA (ERC-20) | 50,000,000 SUPRA | None |
The caps are sized in USD terms with fixed reference prices, not live prices. The reference prices are $1 for USDC and USDT, $1,800 for WETH, $60,000 for WBTC and SolvBTC, and $0.00025 for SUPRA. The admin adjusts the caps as the bridge builds operating history.
Related
- Supported Tokens — token addresses on each network
- Token Transfer Models — why vault balances bound every release
- Security Model