Stargatefinance Transfer Quote Amounts and Minimum Output

Token-unit conversion and decimal precision

A readable token quantity equals its raw amount divided by ten raised to the token’s decimal precision: readableAmount = rawAmount / 10^decimals . The denominator converts smallest units into whole tokens. It does not represent a fee, exchange rate or slippage allowance. The request’s amount uses smallest units, such as wei for ETH or lamports for SOL.

Source amounts use source-token precision. Destination amounts use destination-token precision. A matching ticker does not establish that two raw integers use the same scale.

Token metadata supplies the decimals value alongside the token’s chain and address. Those identifiers connect the quantity to a particular asset. An integration should retain that association when formatting amounts, including when the source and destination contracts differ. Decimal conversion changes the display scale; it does not calculate how much value the route transfers.

The quoted values and their interpretation limits

The amount fields describe different sides of the proposed transfer, while valuation fields express amounts in USD. Their names carry meaning that a bare number loses. Expected output, protected minimum output and a dollar valuation each answer a different question about the same quote.

The API returns these fields as strings, including token quantities, USD valuations and percentages. Their data type does not make their units equivalent. Decimal conversion applies to token quantities. Applying token decimals to a USD valuation or percentage would change its numerical meaning.

Does dstAmount confirm that tokens have arrived?

The dstAmount field expresses expected destination output and does not confirm that the recipient already holds that amount.

A quote identifier names the proposed transfer and becomes its transfer identifier after execution. The API can return multiple quotes for one request. Each identifier belongs to the route and amounts in its own quote, so output from one quote should not be attributed to another.

Transfer tracking distinguishes those later states. PENDING means initiation without processing, while PROCESSING means the cross-chain message remains in transit. SUCCEEDED reports successful completion. Stargate and OFT routes require the source transaction hash for status tracking, because the API follows those transfers from their source transactions.

Instant Guaranteed Finality concerns Stargate’s liquidity settlement and destination transaction guarantee. The credit mechanism still relies on LayerZero to deliver tokens on the destination chain. Consequently, successful source settlement and destination possession describe different moments. Neither the expected output field nor the protected minimum supplies a delivery timestamp.

Minimum output and destination token identity

The Value Transfer API defines dstAmountMin as the minimum destination amount under slippage protection. That quantity expresses the quote’s protected output boundary. The expected amount describes the anticipated output, while the minimum describes the protected lower bound. If the minimum is below the expected amount, treating it as the prediction understates expected output, while treating the expectation as the floor overstates protection. Both quantities use the same destination-token units, so their raw integers can be compared directly.

Asset identity also limits comparisons with the source quantity. A route that includes a swap can produce a different destination token. Native pool assets and Hydra’s pool-backed token representations also have distinct contract identities. A difference between source and destination integers therefore cannot, by itself, identify a fee or a loss. Pool liquidity and Hydra affect the available asset form; the destination token specified by the quote determines the holding that its output amounts describe.

Fee currency and USD totals

Each detailed fee entry identifies its payment chain and the token address associated with its amount. The fees array therefore provides information that the aggregate feeUsd field cannot convey alone. Fee entries distinguish types such as messaging charges and destination native drops. USD valuation leaves fee payment currencies unchanged. The API reference labels feeUsd a total, but its sample does not reconcile that figure with the listed messaging charge. The aggregate alone therefore does not establish that every charge is included.

An ETH-denominated messaging charge and a USDC transfer quantity describe different assets. Subtracting their raw integers would produce an amount with no meaningful token unit.

The API expresses feePercent relative to the transfer amount. That percentage describes the quoted charge, while the detailed entries separately identify charges and payment currencies. A route’s dollar fee, percentage fee and token-denominated charges are related views of costs. They do not all become deductions from the same token balance merely because one response contains them.

Source quantity before wrapper deductions

The Value Transfer API’s EVM wrapper deducts applicable transfer fees before sending the remaining token amount into the bridge. In its ERC20 flow, TransferDelegate pulls the full source token amount, including those fees. LZMulticall sends the fee portion to Treasury and bridges the remainder. The gross source quantity and the quantity entering the bridge can therefore differ. This ordering explains why the recipient’s quoted output reflects wrapper deductions even before any additional route-specific exchange affects the destination asset.

Those token deductions remain distinct from native-currency payments in the transaction. The fee breakdown and encoded transaction value describe the relevant charges more precisely than a source-minus-destination calculation. Even when both sides use the same underlying asset, their displayed difference does not automatically itemize every charge. A complete interpretation keeps the transferred token, the bridge input and any separate fee currency identifiable.

Route mechanisms behind the amounts

The Value Transfer API can quote routes involving Stargate pools, Omnichain Fungible Tokens (OFTs), Circle’s Cross-Chain Transfer Protocol (CCTP) and Aori. These mechanisms have different roles. Stargate coordinates pool liquidity, CCTP transfers native USDC through burn and mint operations and Aori supports intent-based swaps. The route segments explain which mechanism produces the quoted output. A quote through the broader API does not establish that every segment uses a Stargate liquidity pool.

Open full-size image

Stargate’s delivery policy specifies Taxi for all transactions from October 1, 2026. The API reference also lists the Bus identifier for batched transfers. That entry does not establish a currently available Bus option. Quoted charges belong to the returned route; a historical batching description cannot establish the fee for a current Taxi transfer.

What does feeTolerance measure in a transfer quote?

The API defines feeTolerance as the maximum acceptable fee variance, while dstAmountMin separately states the minimum output under slippage protection.

The fee-tolerance configuration uses the PERCENT type. Its amount accepts percentages from 0 to 100, with a documented default of 1. These values describe the tolerance setting. They do not state the route’s actual fee percentage or define a universal formula for its output minimum. The response’s minimum-output field supplies that quantity; substituting a fee-tolerance percentage for it changes the meaning of the comparison.

Destination native drops and output quantities

The optional dstNativeDropAmount configures a native gas drop on the destination chain. Its default value is 0. This option concerns native currency for destination gas, while the selected destination token identifies the asset that the transfer’s output fields describe. Native currency and a transferred ERC20 token remain different balances.

The detailed fee array can identify a DST_NATIVE_DROP charge when relevant. A native-drop configuration, a charge for providing that drop and the expected transferred-token quantity each describe a different aspect of the quote. Combining them requires their respective currencies and units. The presence of a destination-related charge alone does not make it additional units of the transferred token.

Changed inputs and quote validity

Changing the requested amount or the destination token changes the transfer that the API evaluates. Its routing considers cost, speed and liquidity, so quotes for different inputs do not describe interchangeable offers. Amount size also interacts with Stargate’s pathway credits. Insufficient credit can cause a transfer call to revert, even when the token exists on both chains. A quoted output quantity does not establish unlimited capacity for larger transfers.

Some quotes include expiresAt . An expired timestamp calls for a new quote; the absence of that field does not establish permanent validity.

For a comparison between available quotes, destination token identity and readable units come first. Use the quote for the selected route and interface to decide whether its expected output, protected minimum and fees fit the intended destination holding. Amounts retained from a different request describe different transfer terms.