Orbiterfinance transfer limits by route and available liquidity
Orbiterfinance transfer limits depend on the selected route and asset, with the usable amount also constrained by available funds. A maker’s per-transaction ceiling, destination liquidity and your source balance each restrict a different part of the transfer. Use the live route quote and any amount-range message for the exact request. A threshold remembered from another route or an older integration may not apply. The minimum you can send also differs from the minimum acceptable destination output. Fees or a token conversion can change the receiving amount. Check these conditions before signing; a successful source payment alone does not prove the destination received funds.
Key takeaway: Check the receiving amount after fees even when your proposed transfer fits the route’s sending limits.
Configured ceilings and changing destination capacity
A configured maximum places a ceiling on a maker route even when additional liquidity is available. In the maker system, a maker configures the maximum allowed amount per transaction. That setting belongs to the transaction pair, so reversing the transfer direction requires its own amount check.
Destination liquidity answers whether the maker can fund the receiving payment in the required asset. The configured ceiling and the funds available for that payment describe different constraints. Your source wallet balance separately determines the funds you can spend. An amount needs to satisfy the applicable route conditions and your own funding requirements.
Refresh the request after a capacity warning or a change to its asset, direction or amount.
A quote connects the amount to a particular destination
The quote request identifies the source network, destination network, input token, output token and proposed amount. It also identifies the sending wallet and recipient. Any amount boundary needs to match that same request. A quote for another asset or the reverse direction cannot establish whether this transfer qualifies, even when both requests involve the same networks.
Execution follows the returned steps, whose operations vary with the route. Quote success describes a proposed transaction; signing, source confirmation and destination payment represent later states. The receiving token and amount must match the intended destination use.
A blocked request with a missing source fee balance
Consider a route with sender-paid source gas where the wallet reports insufficient funds despite an amount inside the displayed range. The transferable asset is present, while the balance required for the source fee is missing. The amount fits the sending range; the source transaction remains unfunded.
Funds required before the source payment
Transfer input
The selected source wallet holds the asset quantity the quote requires, expressed in that token’s correct units.
Network fee
The same wallet lacks the fee funds this route requires for its source transaction. Signing cannot repair that funding shortfall.
Read the wallet’s fee estimate and spendable source balance without broadcasting. For a transaction requiring a source-network fee payment, a balance on the destination network cannot fund that source payment. Before committing funds, the request needs these checks:
- Match the proposed amount to the selected route’s current sending bounds.
- Confirm the transferred asset is spendable in the source wallet.
- Cover the source transaction fee under the wallet’s payment method.
- Satisfy any token approval the returned steps require.
- Accept the quoted destination asset and minimum receiving amount.
Once the funding shortfall is resolved, refresh the quote before considering the source payment. If the same input still lacks a valid route, leave the transfer unsubmitted and recheck availability or another supported path. After submission, completion requires the corresponding destination payment in the intended asset, with its actual amount checked against the quoted output requirement.
Sending minimums and receiving minimums measure different amounts
A sending minimum sets the lower boundary for the route’s input quantity. Meeting it answers whether that input clears the route’s amount requirement. It does not specify the amount remaining after fees or conversion.
The quote field minDestTokenAmount represents the minimum acceptable amount received at the destination.
Read it as an output requirement in the destination token’s units. It cannot replace the minimum amount permitted on the sending side.
A route containing a swap can have different input and output tokens, so comparing their bare numerical quantities would ignore the conversion. Even with matching assets, transfer charges can reduce the receiving amount. The sending range and acceptable output therefore need their own checks.
A low input can clear a sending threshold yet leave too little destination value for the intended use.
Withholding fees affect the usefulness of smaller amounts
Maker-based transfers distinguish a withholding charge from a trading fee based on the transfer amount. The withholding charge covers the destination transfer’s gas cost. When that charge stays fixed, it consumes a larger share of a smaller input. A permitted minimum can therefore be poor value for a particular transfer without making the route technically unavailable.
Use the returned receiving quantity to assess the amount left after the quoted charges. Keep each fee in its stated denomination; a token fee and its dollar equivalent describe the same charge in different units. A route containing a swap can also quote a swap fee, so a bridge-only cost cannot stand in for that combined request.
Precision preserves the amount near a route boundary
Token amounts in the API use strings to preserve precision. A displayed decimal quantity and an integer quantity in raw token units require consistent conversion. Where an input uses raw units, apply the decimals of that particular token. The destination token can use a different precision from the source token.
Keep the full quantity during amount checks. Binary floating-point arithmetic can round a value close to a boundary, so an integration should use suitable integer or decimal arithmetic. A rounded display is useful for reading; the submitted quantity must retain the precision the selected method requires.
The direct-maker identification-code method also uses trailing payment digits to identify the destination. Preserve its generated payment amount. Independently rounding or editing that value can change the routing information, even when the visible quantity appears to remain inside the amount range.
An amount rejection needs a matching correction
An above-maximum message calls for a request fitting the permitted amount range or another supported route. A below-minimum message concerns the opposite boundary. Neither message establishes that the destination asset is unavailable in every amount. Read the returned error before treating a specific rejection as a platform-wide restriction.
A capacity warning justifies a fresh availability check. It does not establish when funds will become available or turn a temporary restriction into a permanent ceiling. An alternative path also needs to deliver the required asset to the intended network; changing the destination merely to obtain a quote changes the transfer’s purpose.
If no route accepts the required amount and destination, keep that request unsubmitted. Waiting for a new usable offer remains an option.
Older SDK amount methods have a limited scope
The older JavaScript SDK exposed getMinSendValue() and getMaxSendValue() on a router created for a selected trade pair. Those method names describe sending boundaries for that router. The SDK is marked outdated, and the supported integration direction is to obtain quotes through the API.
An old router value cannot establish the current range for a different request. Its network environment, asset selection and router context matter. Mainnet and testnet examples also describe different operating environments, so a testnet threshold needs its original scope when evaluating a mainnet amount.
The scope of the 0.005 ETH minimum
The Maker Client’s listed minimum belongs to a setup described for a whitelisted testnet. It cannot establish the minimum accepted by every live asset and route. A usable sending amount needs the conditions returned for its actual request, alongside an acceptable destination output. The minimum stated for that Maker Client setup was 0.005 ETH.
Still wondering about Orbiterfinance transfer limits?
Does a larger ERC-20 allowance increase an Orbiterfinance route’s maximum?
A larger allowance changes what a contract may spend from your token balance, not the maker route’s configured ceiling. Approval can satisfy a spending prerequisite for a contract-based transfer. The requested input must still fit the route’s amount rules and available capacity.
Can splitting an over-limit Orbiterfinance transfer make it cheaper?
Splitting an amount can repeat fixed transfer charges, so it does not automatically reduce cost. Each smaller request must qualify under its own minimum, maximum and available route conditions. Where the maker charges a withholding fee per transaction, repeated transfers incur repeated withholding charges. Compare the aggregate receiving amount and execution costs before choosing that approach.
Is a route’s sending limit expressed in dollars or token units?
Read a token-denominated sending limit in the stated asset’s units. The API quote request specifies a token quantity, while fee fields can also provide dollar equivalents. A dollar conversion does not replace the token amount required by the request. Changing market prices can alter the dollar value of an unchanged token quantity.
Will increasing slippage resolve a maximum-amount rejection?
Slippage tolerance controls acceptable price fluctuation for the quoted operation. It does not itself increase a maker’s configured transaction ceiling or supply destination liquidity. A revised tolerance can change the terms of a route involving conversion. Any revised request still needs an acceptable input amount. Treat an amount-limit error separately from an output-price constraint.
Can a manual maker payment bypass the displayed amount range?
A successful manual payment does not prove the amount qualifies for the maker’s bridge service. The source network can record a transfer without establishing that the maker will deliver the intended destination payment. Direct-maker transfers also have method-specific payment encoding. Changing the generated payment in the identification-code method can alter destination routing.
Which details help investigate a rejected transfer amount?
Keep the exact entered amount, selected asset, source network, destination network and returned error message. Include any displayed minimum or maximum, plus whether the rejection occurred during quoting or transaction submission. If a transaction reached the source network, its hash identifies a different state from an unsubmitted request.
How does a swap-before-bridge route affect amount-limit checks?
A route containing a swap before a bridge can use the converted asset for its bridge step. The original input and that intermediate asset describe different quantities. Read any bridge amount condition in the units of the asset that step uses, and retain the combined quote’s destination requirement. An unchanged source amount does not imply an unchanged intermediate token amount.
Does the quote’s gas limit cap the token amount I can bridge?
The gas limit restricts the computational work allowed for the source transaction, measured in gas units. It is separate from a sending limit measured in tokens. Raising a transaction’s gas limit does not increase a maker’s amount ceiling. A failed gas estimate also needs its actual error examined before attributing the failure to the bridge’s maximum transfer size.