Private USDT Scroll to Sui Bridge

FromScroll
ToSui
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

What you need to know

Privacy for the Scroll to Sui direction

Where offered, Private Route is intended to reduce an obvious direct association between the Scroll sending wallet and Sui receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Scroll. EVM 0x account address SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.

Scroll source-side visibility

Scroll exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a bytecode-compatible zero-knowledge EVM rollup that proves batches to Ethereum. Scroll inclusion and Ethereum proof settlement are distinct, and its token contracts must be verified independently from L1. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.

Sui destination-side visibility

Sui can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.

Scroll deposit role versus Sui receipt role

A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. Those deposit-side events remain public. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. The receipt and later activity remain public.

USDT issuer and contract context

USDT is issued through ERC-20, TRC-20, SPL, and other network-specific contracts. The ticker does not determine the token standard, contract, issuer controls, or destination address model. Both bridge sides can expose contract events, amounts, receiving services, and later transfers; a stable target value does not make those records private or interchangeable.

USDT token-standard evidence; USDT token-standard evidence

ERC-20, TRC-20, SPL, and other USDT representations expose different contract or token-account events. Issuer controls, receiving services, amount, timing, and later transfers can add context to this deposit. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. The source transfer remains public. ERC-20, TRC-20, SPL, and other USDT representations expose different contract or token-account events. Issuer controls, receiving services, amount, timing, and later transfers can add context to this receipt. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another. The destination receipt and later use remain public even when direct wallet association is reduced.

Cross-chain linkability limits

Private routing can reduce direct association across Sui objects and the other ledger account. Move object changes, gas, the other-network receipt, amounts, timing, and later transfers remain public. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

Verification status is separate from privacy status

Support for the exact Sui coin type or object-side asset, other network representation, amount, and region is evaluated by the live provider. Privacy intent does not establish no-KYC status. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

Private Route for USDT → USDT

Scroll wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this USDT on Scroll to USDT on Sui path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Sui hexadecimal account address with an object-based asset model; it does not hide either chain's public records.

  • Reduces the obvious link between the USDT deposit and USDT receipt
  • Compare standard and Private Route options for Scroll → Sui
  • Shows what remains public on Scroll and Sui before you deposit
Check Private Route availability →

Related routes

Private USDT Scroll to Sui Bridge FAQs

What must be verified for a private USDT Scroll to Sui bridge?

Check the exact USDT representations, live privacy status, provider, amount, region, source gas, destination address, fees, and any verification request. Standard bridge support is not proof of private availability.

Which Scroll bridge records remain public?

Scroll exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a bytecode-compatible zero-knowledge EVM rollup that proves batches to Ethereum. Scroll inclusion and Ethereum proof settlement are distinct, and its token contracts must be verified independently from L1. The deposit, gas funding, representation, confirmations, amount, and sending-address history remain observable.

Which Sui records remain public after receipt?

Sui can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. Delivery and later activity remain observable even if the provider path reduces direct wallet association.

Does bridging USDT privately hide its contract activity?

No. USDT contract events, issuer controls, amounts, timing, receiving-service deposits, and later transfers can remain public on both networks.

Which USDT events remain visible on this private bridge?

The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another. Both the deposit and receipt remain ledger records.

Does private Scroll to Sui bridging guarantee no KYC?

Support for the exact Sui coin type or object-side asset, other network representation, amount, and region is evaluated by the live provider. Privacy intent does not establish no-KYC status. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

View all Help Center FAQs →