Skip to Content
SupraNova (Bridge)Quote Fees and Limits

Quote Fees and Limits

The admin of each chain sets the fee parameters and limits, and can change them. Read them from the contracts before you send a transfer. The SupraNova application shows the same values before you confirm a transfer. Fees and Transfer Limits explain how fees and limits work.

Fee for an amount

cast call <TOKEN_BRIDGE> \ "inboundTokenFee(uint64,uint256,address)(uint64,uint64,uint64,uint256)" \ <DEST_CHAIN_ID> <AMOUNT> <TOKEN> --rpc-url <RPC_URL>

The call returns finalAmount, feeCutToService and relayerReward, normalized to the destination chain’s maximum token decimals (maxTokenDecimals), and dust in the token’s decimals. feeCutToService includes the relayer reward.

Vault limits

For tokens locked in the vault, read the lock limits and the release limits from the TokenVault. The lock limits are the per-lock minimum and maximum and the global cap. The release limits are the per-release minimum and maximum.

cast call <TOKEN_VAULT> "lockLimits(address)((uint256,uint256,uint256))" <TOKEN> --rpc-url <RPC_URL> cast call <TOKEN_VAULT> "releaseLimits(address)((uint256,uint256))" <TOKEN> --rpc-url <RPC_URL>

A global cap of 0 means no cap. lockedTokenBalance(address) returns the amount the vault has recorded as locked.

Wrapped-token limit

On SupraEVM Devnet, the TokenBridge checks each send of a wrapped token against a wrapped-token limit. Read the limit from the last field of inboundTokenInfo on the TokenBridge:

cast call <TOKEN_BRIDGE> \ "inboundTokenInfo(uint64,address)((bool,bool,address,bool,bool,uint256,uint256,uint256,(uint256,uint256)))" \ <DEST_CHAIN_ID> <TOKEN> --rpc-url <RPC_URL>

The last field holds the minimum and maximum, in the token’s decimals. A limit of 0 to 0 means the token cannot be sent. The TokenBridge contracts on Ethereum Mainnet and Sepolia have no wrapped-token limit.

For contract and package addresses, see Contract Addresses.

Last updated on