Abstract’s documented gas model combines a fixed offchain component for L2 state storage and zero-knowledge proof generation with a variable onchain component for publishing state and verifying proofs on Ethereum. Ethereum gas prices affect that variable component. If you’re paying gas directly in ETH, a balance in USDC.e or USDT doesn’t establish that you have the ETH needed for that transaction.

The amount sent with a contract call is separate from its gas charge. In Abstract’s writeContract interface, value specifies the native-token amount sent, measured in wei. Treat the asset amount and transaction fees separately when working out the cost.

A supported bridge, swap, or transfer route can involve an independent provider’s charges alongside network fees. Some routes also require a destination-chain claim or another transaction, with its own fee. Include that component when the selected route requires it.

View full-size image

The Migration Hub and existing bridge interface may support different routes and have different availability periods. For the same input amount, compare routes that support the same asset and destination using their complete disclosed costs and minimum received. A lower Abstract gas estimate can coexist with higher provider or destination charges.

For a route that converts assets, slippage is the difference between the expected trading price and the actual execution price. Keep that price effect separate from gas, and compare the amount received in the same destination asset.

A paymaster can pay a contract transaction’s ETH gas fee when configured for that transaction. An approval-based implementation can charge the user in an ERC-20 token that it supports. That arrangement applies to the configured transaction; it doesn’t establish sponsorship of a provider’s charge or a later transaction on another network.

An authorized Abstract Global Wallet session’s feeLimit can cap gas spending or leave it unlimited. LimitType.Lifetime applies over the session’s lifetime, while LimitType.Allowance applies per configured time period. A spending cap doesn’t state the actual transaction charge or supply a funded ETH balance.

View full-size image

Worked Example: Fees Across Two Networks

Consider a hypothetical supported Abstract-to-Ethereum withdrawal that requires an Ethereum claim. All fee amounts and the claim requirement in this example are hypothetical. Assume the three charges are separate, paid by the user, and additional to the asset amount being moved.

Total fee budget (ETH): 0.000882 ETH. Abstract gas (ETH): 0.000135; Provider fee (ETH): 0.000284; Ethereum claim gas (ETH): 0.000463. Formula: abstract_gas + provider_fee + claim_gas .

The Ethereum claim accounts for 0.000463 ETH of the total; holding that amount only on Abstract doesn’t establish that the destination transaction can be paid. Changing the claim fee changes the total by the same amount. If the actual route requires no claim, that component drops out. A fee already included in another quoted charge mustn’t be counted twice.

Network or provider fees can be incurred for failed transactions and may not be refundable. Check a transaction’s status before retrying, since another submission can duplicate a transfer or add fees.

View full-size image

Cube, Inc.’s Terms of Service dated October 6, 2026 distinguish source-chain confirmation from transfer completion. Any supported completion process continuing after discontinuation follows its own disclosed terms and deadline; it doesn’t enable a new withdrawal of assets left on Abstract.