TorrentSwap

Cross-Chain Swap Security

Cross-chain swaps coordinate transactions on more than one public blockchain. No interface can remove every network, liquidity, smart-contract, address, or user-error risk.

The safest workflow is deliberate: verify the domain, exact asset and network, destination and refund addresses, current quote, and deposit instructions before sending.

Who holds your funds, and when

TorrentSwap never holds your funds and never has access to your keys. Your deposit goes to the protocol named on your route, which holds it briefly while the swap settles: Chainflip in validator-run vaults secured by threshold signatures, NEAR Intents in its deposit service until a solver fills the order, and Flashnet at a deposit address on its settlement network.

That custody window is the main counterparty risk in any cross-chain swap, which is why every quote names the protocol and states how it holds deposits. Read the protocol pages before choosing a route for a large amount.

Connecting a wallet is optional

You can always copy the deposit address into your own wallet. If you connect a supported wallet instead, TorrentSwap reads only your public address and asks the wallet to send one exact transfer to the validated deposit address. It never requests token approvals, message signatures or permission to move anything else.

Verify the network, not only the ticker

Tokens such as USDC, USDT, and ETH can appear on multiple networks. The same ticker does not make those versions interchangeable. Confirm both the asset and network in the selector, quote, and receiving wallet.

A correctly formatted address is not proof that it belongs to the intended person or supports the selected token. Compare the full address in the wallet you control; do not rely on the first and last characters alone.

Use only current deposit instructions

Quotes and deposit instructions are route-specific and time-sensitive. Send only the requested asset and exact amount to the displayed deposit address, and do not reuse an address from an earlier swap.

If the interface says a quote is stale or expired, request a new one. Never copy a rate, minimum, timing estimate, or address from an article or screenshot.

Understand the refund address

A source-network refund address is collected before transaction creation so a refundable route has a defined return destination. Use an address from a wallet you control and can access later.

A refund is not guaranteed for every mistake. Sending the wrong asset, wrong network, duplicate deposit, or funds to an unrelated address may require manual investigation or may be unrecoverable.

Protect wallet secrets

TorrentSwap support does not need a seed phrase, private key, wallet password, or remote access to a device. Anyone asking for those details is attempting to take control of the wallet.

Use the exact TorrentSwap domain, avoid links from unsolicited messages, and keep the source transaction hash and swap details needed for support without publishing sensitive context unnecessarily.

Public ledgers and privacy

Standard swaps do not require a TorrentSwap profile, but source and destination transactions remain visible on public ledgers. Accountless does not mean anonymous.

Review the Privacy Policy for off-chain data handling, and the tracker for the current state of a transaction already sent.

Frequently asked questions

Can TorrentSwap reverse a blockchain transfer?

No. Blockchain transfers are generally irreversible. A route may support a refund under specific conditions, but that is not the same as reversing an arbitrary transfer.

Should support ask for my seed phrase?

No. Never share a seed phrase, private key, wallet password, or remote device access with TorrentSwap or anyone claiming to provide support.

Why must the refund address use the source network?

A refund returns the source-side asset, so the address must be valid for that asset and network. A destination-network address may be formatted differently or may not support it.

Check every field before sending

Use a current quote, verify both networks and wallet addresses, and keep the source transaction hash for tracking.