Orbs

Orbs are powering dLIMIT order placement, fill checks, and position exits

Orbs are the Layer-3 execution network behind dLIMIT orders integrated into decentralized exchange interfaces. To open a price-controlled spot position, connect an EVM wallet on the exchange's supported chain, choose the source and destination ERC-20 tokens, enter the source amount, set the limit price, approve the source token, and place the order. The order stays open until one eligible bid fills its single trade or the maker cancels it or its deadline passes; after a fill, the output token reaches the same wallet and becomes available for a reverse-pair exit.

A price-controlled route into an ERC-20 position

The dLIMIT workflow is a single-fill decentralized exchange order designed for traders who want a defined minimum output before converting one ERC-20 asset into another spot position. Because the entire source amount forms 1 trade segment, an eligible fill completes the specified conversion in one execution; otherwise, the order stays open until its deadline or a maker cancellation.

Wallet and chain prerequisites before placement

The prerequisite set is an EVM wallet, source tokens, native gas currency, and a dLIMIT-enabled exchange on the same chain, which together make approval and order submission possible. MetaMask and WalletConnect serve interfaces such as QuickSwap, Sushi, and PancakeSwap.

Network and gas balance

Network selection ties every token balance, allowance, order, and fill to one EVM chain. Established deployments include Sushi on Ethereum chain ID 1; PancakeSwap on BNB Chain 56, Arbitrum 42161, Base 8453, and Linea 59144; and QuickSwap on Polygon 137. Switching MetaMask from Polygon to Base changes the balances and order records the interface reads, but it does not move the original order. Keep enough native currency on the selected chain for approval, placement, cancellation, and the later exit transaction. A token bearing the same ticker on another network remains a separate contract balance.

Address, token, and allowance match

An EVM account address contains 20 bytes, normally displayed as 40 hexadecimal characters after the prefix. Match the full account before placing the order.

Token identity comes from the contract address, not from a ticker alone. The order interface should display the exact source balance and destination token before approval. Transaction and token addresses are separate: an EVM address is 20-byte, while an EVM transaction hash is 32-byte and normally renders as 64 hexadecimal characters after its prefix. Saving the placement hash gives a durable reference when a front end refreshes slowly. The allowance and source balance must belong to the same wallet on the selected chain. No balance shown on another network contributes to that order's fill.

If the source balance or allowance falls below the order amount, the recorded order cannot pass its fill checks. Execution resumes only after the same wallet restores both requirements before expiry.

Pair direction, order mode, and limit input

Pair selection is the order-definition stage where dLIMIT assigns the asset spent, the asset received, the source amount, and the minimum acceptable destination amount. Read the pair left to right: "from" leaves the wallet, and "to" enters it after the fill.

From and to tokens

USDC illustrates why token units matter. On Ethereum, USDC uses 6 decimal places, while WETH uses 18; the interface converts those base units into readable amounts. Buying WETH with USDC makes USDC the source and WETH the destination. Selling later reverses those roles. If an interface displays native ETH instead of WETH, follow the exact asset label and preview because wrapping behavior belongs to that integration.

Limit price and minimum output

dLIMIT is the 1-segment case of dTWAP, so the individual trade size equals the total order size. The limit price is the input convention; the enforceable value is the minimum destination amount derived from it. For a USDC-to-WETH order, check whether the UI quotes USDC per WETH or WETH per USDC, then read the minimum WETH line. A bid qualifies only when its net output meets or exceeds that amount. Changing the source amount recalculates the minimum, so review both figures after every edit and before the wallet confirmation. The final preview remains decisive once the maker submits the order.

How do you place a dLIMIT order?

Order placement is a two-transaction wallet workflow for an ERC-20 source token: first set the contract allowance, then submit the on-chain order with its amount, minimum output, and expiry. Each confirmed transaction has its own hash and receipt.

Approve the source token

The approval uses the EIP-20 allowance mechanism for the source token. Select an amount matching the intended order when the interface offers that control, confirm the spender and chain in the wallet, and wait for a successful receipt. A previous allowance large enough for the source amount removes the extra approval prompt, leaving only the order transaction.

Submit the order

The order transaction writes the maker's selected constraints. Before signing, compare the wallet account, source token, source amount, destination token, minimum output, and deadline with the preview. Use the transaction hash to return to the record if the order-history panel needs time to update.

1. Confirm the active wallet account and chain.
2. Select the exact source and destination tokens.
3. Enter the source amount and limit price.
4. Approve the source token if the allowance is insufficient.
5. Place the order only while the final preview matches the intended threshold.

Order states that prove placement and fill

Order status is the evidence trail linking a successful placement transaction to an open record, a winning bid, a completed fill, and the wallet's changed token balances. A closed wallet prompt alone proves only that the user responded to the request.

At receipt level, EIP-658 uses status value 1 for success and 0 for failure. A successful placement receipt proves the contract accepted the transaction, while the open-order record ties it to the maker, pair, source amount, minimum output, and deadline. Save the transaction hash or order identifier before leaving the interface.

An open state means the order exists and remains eligible under its constraints. After a fill, the history should move to filled or completed, the source-token balance should fall, and the destination-token balance should rise. One interface label may lag behind the chain, so the fill receipt and balance change provide the stronger confirmation. A completed dLIMIT fill leaves no scheduled second chunk.

The winning taker completes a dLIMIT execution through 2 on-chain transactions: one bid and one fill. The bid proposes a route and output; the fill rechecks balance, allowance, deadline, and minimum output before performing the swap. A better bid can replace the first proposal before execution. The observable spot position exists when the fill receipt succeeds and the destination token reaches the wallet.

A worked entry and exit example

The worked example is a complete spot-position lifecycle, using one dLIMIT entry and one reverse order to show how minimum outputs become observable wallet balances. It illustrates arithmetic, not a market forecast.

Every changing input in this worked example is hypothetical: the starting balance is 1,250 USDC; the entry spends 1,000 USDC; the entry preview sets a 0.500 WETH minimum; the completed entry delivers 0.505 WETH; the later exit spends all 0.505 WETH; its reverse-order preview sets a 1,060.50 USDC minimum; and the reverse fill delivers 1,070 USDC. None of these amounts represents a live quote. Both orders use the same wallet and chain, while the market movement between them is simply an illustrative condition for the two fills after the first position becomes visible.

After entry, the wallet holds 250 USDC plus 0.505 WETH. After the reverse fill, it holds the prior 250 USDC plus 1,070 USDC, totaling 1,320 USDC, and 0 WETH from the worked position. The arithmetic reaches a concrete result only because both hypothetical fills were specified; a real wallet total follows its recorded outputs.

A clean position exit through the reverse pair

Position exit is a second spot conversion in the opposite direction, where the filled destination token becomes the new source token and the chosen exit asset becomes the destination. The acquired tokens already sit in the wallet, so there is no separate dLIMIT balance to withdraw.

When immediate execution is the priority, select a standard swap on the same DEX and reverse the pair. When a minimum exit amount is the priority, create a second dLIMIT order with the acquired token as source and the chosen stablecoin or other asset as destination. Set the amount no higher than the wallet balance, approve that token when required, and submit the reverse order. The first order's approval does not automatically cover a different source token because ERC-20 allowances belong to individual token contracts.

Check the exit through the same evidence chain: a successful receipt, a filled record, a reduced source balance, and an increased destination balance. If the reverse order expires unfilled, cancel it and choose a new amount, deadline, or limit before resubmitting. The exit is complete when the balance sheet shows the chosen destination asset and zero - or consciously retained - units of the token acquired at entry.

The mechanism behind a single-fill order

The single-fill mechanism is an auction-based dTWAP order in which Orbs Guardians and other takers monitor a dLIMIT contract, compete on output, and execute through the DEX route. The published version 4 contract requires at least a 30-second bid delay and treats a bid as stale after 600 seconds. A fresh competing bid must improve the prior net output by more than 1%. The contract uses 32-bit timestamps and remains operable through 2106. QuickSwap, Sushi, PancakeSwap, SpookySwap, and THENA vary the front-end labels, while source balance, allowance, deadline, and minimum output decide the fill.