Venues & Transports

CEX lanes, bridge lanes, and how to combine them

Venues & Transports

QTG supports two families of transfer lanes: CEX lanes for exchange-to-exchange transfers, and Bridge lanes for on-chain cross-chain transfers. Each lane compiles into a specific DAG shape with a known number of steps. You can combine lanes into multi-hop routes when a single lane cannot reach the destination.

CEX Lane

A CEX lane moves funds between two exchange accounts using the exchanges’ own withdrawal and deposit infrastructure. Every CEX transfer compiles into the same 3-node pipeline:

1. Withdraw — QTG calls the source exchange’s withdrawal API with the destination address, amount, and any required fields (memo, network, travel rule data).
2. Observe Withdrawal — QTG polls the source exchange until the withdrawal is confirmed as sent. This catches rejections, holds, and AML review states.
3. Observe Deposit — QTG polls the destination exchange until the deposit arrives and is credited. The transfer is not marked complete until the funds are confirmed on the receiving side.

The 3-node pipeline means QTG tracks both sides of the transfer. If an exchange holds a withdrawal for review, you will see it in the observe step rather than wondering where the funds went.

Supported CEX Venues

Venue	Implementation	Notes
Upbit	Free CEX adapter	Korean venue. Beneficiary fields required for KR compliance.
Binance	Free ordinary CEX adapter	Ordinary account balances plus external withdrawal/deposit. Privileged master-signed sub-account balance reads and provider-internal capital operations require Pro.
Coinbase	Free CEX adapter	Advanced Trade API. Address-scoped deposit observation.
Bybit	Free CEX adapter	Requires internal transfer from Unified Trading to Funding before withdrawal.
OKX	Free CEX adapter	KR travel-rule and private-wallet path support.
Bithumb	Pro CEX adapter (commercial)	XEMM/strategy balance reads; the transfer adapter ships under Pro.
Backpack	Pro CEX adapter (commercial)	ED25519-signed REST API.

Implementation status is not route-specific live evidence. An operator must still validate the configured account, credentials, allowlists, and route before moving funds.

Exchange-Specific Considerations

Different exchanges have different quirks that QTG handles transparently:

• Korean venues (Upbit, OKX) require travel rule fields: exchange name, receiver type, and receiver names in Korean and English.
• Binance sub-accounts are signed through the master account’s API key. QTG never holds sub-account trading keys.
• Bybit requires a manual internal transfer from the Unified Trading wallet to the Funding wallet before QTG can initiate a withdrawal. This is a Bybit platform requirement, not a QTG limitation.

Bridge Lane

A Bridge lane moves funds across blockchains using an on-chain protocol. Unlike CEX lanes where the exchange handles custody, bridge lanes require QTG to sign and broadcast transactions using your KMS key.

CCTP (Cross-Chain Transfer Protocol)

CCTP is Circle’s native USDC bridge. It compiles into a 5-node pipeline:

1. Burn — QTG signs and submits a USDC burn transaction on the source chain via your KMS.
2. Attest — QTG waits for Circle’s attestation service to confirm the burn.
3. Mint — QTG submits the mint transaction on the destination chain using the attestation proof.
4. Observe Receipt — QTG confirms the destination address actually received the USDC, matching amount and token contract.
5. Observe Finality — QTG waits for the mint transaction to reach finality.

CCTP is a built-in Free lane. Whether a specific chain pair is ready to operate depends on the configured route and operator evidence.

CCIP (Chainlink CCIP)

CCIP is an optional Pro bridge lane. It is unavailable in OSS and disabled unless the Pro package and its configuration enable it.

USDT0 / LayerZero

USDT0 is an optional Pro bridge product built on LayerZero V2’s OFT standard. It is unavailable in OSS and disabled unless the Pro package and its configuration enable it.

Circle Gateway

Circle Gateway provides a built-in Free balance and movement integration through Circle’s infrastructure. Installed integration is not route-specific live readiness.

Hyperliquid

Hyperliquid has a built-in CCTP-backed account integration. Configure and validate the selected route before using it to move funds.

Stargate (Pro)

Stargate is a Pro bridge lane. It is part of the Pro package, enabled through Pro configuration, and is not part of the Free distribution.

Bridge Lane Summary

Transport	Tier	Implementation	Notes
CCTP	Free	Built-in lane	USDC burn, attestation, and mint.
CCIP	Pro	Optional lane	Requires the Pro package and explicit enablement.
USDT0 / LayerZero	Pro	Optional lane	Requires the Pro package and explicit enablement.
Circle Gateway	Free	Built-in lane	Balance and movement integration.
Hyperliquid	Free	Built-in integration	CCTP-backed account flow.
Stargate	Pro	Optional lane	Requires the Pro package, configuration, and route evidence.

Choosing the Right Lane

Scenario	Recommended Lane	Why
Exchange to exchange (e.g., Upbit to Binance)	CEX	Direct withdrawal/deposit. Fastest, cheapest for supported pairs.
Chain to chain (e.g., Base USDC to Arbitrum USDC)	CCTP Bridge	Native USDC bridge. No slippage.
Exchange to chain (e.g., Binance to Base)	CEX withdrawal	Most exchanges support direct chain withdrawal.
Chain to exchange (e.g., Arbitrum to Upbit)	Depends on deposit support	Check if the exchange accepts deposits on that chain.

Multi-Hop Routes

Some transfers require combining lanes. For example, moving USDC from Upbit to Hyperliquid might require:

1. CEX lane: Withdraw USDC from Upbit to Arbitrum
2. Bridge lane: Topup Hyperliquid from Arbitrum via CCTP

QTG templates can express multi-hop routes as a single DAG. The nodes execute in dependency order — the bridge step waits for the CEX withdrawal to complete before starting.

For the full executor architecture and implementation details, see Executors Overview. For Free bridge internals, see CCTP Lane. CCIP, Stargate, and USDT0 require QTG Pro; their detailed operator material is not part of the OSS documentation artifact.