The core problem: why chains cannot see each other
Every blockchain is a self-contained ledger. Its validators agree on one shared history of balances and transactions, and they have no native ability to read another chain's state. Ethereum validators do not verify Bitcoin blocks, and vice versa. This isolation is a feature, because it keeps each network's security self-sufficient, but it means assets cannot simply hop across on their own.
A bridge solves this by coordinating two actions that happen on two separate chains and making them behave as one logical transfer. Something is locked, burned, or paid on the source chain, and in response something is minted, released, or paid out on the destination chain. The engineering challenge is guaranteeing that the second action only happens when the first one truly did, without a trusted middleman quietly cheating. Different bridge designs make different trade-offs to achieve that guarantee, and those trade-offs are what separate a robust bridge from a fragile one.
Lock-and-mint: the wrapped-asset model
Lock-and-mint is the most common design for so-called wrapped assets. When you send an asset into the bridge, it is locked in a contract or vault on the source chain. The bridge then mints an equivalent token on the destination chain that represents your locked deposit, often prefixed with a w for wrapped, such as wrapped bitcoin on Ethereum. That wrapped token is a claim on the real asset sitting in the lock.
To go back, you send the wrapped token to the bridge, it is burned, and the original asset is unlocked and returned to you on the source chain. The total supply stays balanced because every wrapped token in existence should correspond to one genuine asset held in the lock. The obvious question is who holds that lock and whether they can be trusted or compromised, which is exactly where custodial versus non-custodial designs diverge. If the locked reserves are ever drained or the peg breaks, the wrapped token can lose its backing.
Burn-and-mint and liquidity-based bridges
Burn-and-mint works differently and is common for native tokens that exist across several chains. Instead of locking, the bridge burns your tokens on the source chain, permanently removing them from that supply, and mints the same amount on the destination chain. Because the token issuer controls minting on every chain, the total supply across all networks stays constant. There is no vault of locked reserves to defend, but it requires the token to be designed for this from the start.
Liquidity-based or swap-based bridges take a third route and are closer to how TorrentSwap operates. Rather than minting a wrapped IOU, they hold pools of real assets on both chains, or route through market makers. You deposit asset A on the source chain, and the bridge pays you asset B out of an existing pool on the destination chain at a quoted rate. Nothing is wrapped; you receive the genuine native asset. This model powers many cross-chain swaps, feels instant to the user, and avoids wrapped-token peg risk, though it depends on there being enough liquidity to fill your trade at a fair price.
Custodial versus non-custodial: who holds the keys
The single most important safety distinction is who controls your funds while the bridge does its work. In a custodial bridge, a company or a small set of operators holds the locked assets and signs off on releases. You are trusting that party to stay solvent, honest, and secure. If their keys are stolen or they freeze withdrawals, your funds are at their mercy. Many of the largest bridge losses in crypto history traced back to compromised operator keys or multisignature setups.
Non-custodial bridges aim to remove that trusted party. They use smart contracts, decentralized validator sets, or cryptographic proofs so that no single entity can seize deposits, and the rules execute automatically. TorrentSwap is non-custodial: it never holds your funds, and assets move directly between chains rather than sitting in an account you have to trust. You provide only a destination address and a refund address, with no account, email, or ID required. The practical takeaway is to always know, before you bridge, whether a human could unilaterally take or block your money.
Message passing, timing, and finality
For the destination action to fire only after the source action is real, chains need a way to relay proof between them. This is message passing. Depending on the bridge, relayers, oracles, validators, or light clients observe the source chain, confirm that your deposit or burn actually happened and is final, and then authorize the payout on the destination side. The security of the whole bridge often rests on how trustworthy that messaging layer is.
Timing varies mainly because of finality, the point at which a transaction is considered irreversible. Bitcoin transactions need several block confirmations before a bridge will treat them as settled, which naturally adds minutes. Faster chains confirm sooner. A bridge waits for enough confirmations on the source chain, relays the message, and then settles on the destination chain. This is why a cross-chain move is rarely truly instant. On TorrentSwap, swaps typically complete in about ten to thirty minutes, and the expected amount and fees are shown transparently before you confirm so there are no surprises.
The main risks and how to reduce them
Bridges concentrate value and complexity, which makes them a target. The headline risks are smart-contract bugs that let attackers mint or drain funds, compromised operator or validator keys in custodial designs, and liquidity or peg failures where a wrapped token loses its backing. There is also user-side risk: sending to a wrong address, choosing an unsupported chain, or falling for a phishing clone of a real bridge site.
You reduce these risks by favoring non-custodial designs, double-checking the destination address, and understanding what happens if a transfer fails. A well-built bridge should return your funds rather than leave them stranded. On TorrentSwap, if a swap fails, funds are returned to the refund address you provided at the start, so a failed route does not mean lost money. Start with a small test amount when using any bridge for the first time, confirm the quoted rate and fees before approving, and only bridge into chains and assets the service actually supports.
How TorrentSwap bridges assets
TorrentSwap is a non-custodial, no-KYC cross-chain swap and bridge. It uses the liquidity and swap-based model rather than issuing wrapped tokens, routing your trade through Chainflip and the SwapKit API so that assets move directly between chains. You never create an account or hand over funds to be held; you supply a destination address for what you want to receive and a refund address in case anything goes wrong.
It supports Bitcoin, Ethereum, Solana, Arbitrum, and Polkadot, along with tokens including USDT, USDC, and FLIP. You can bridge into a specific network through pages like /bridge/bitcoin, /bridge/ethereum, or /bridge/solana, or swap a specific pair through the exchange pages. Before you confirm, TorrentSwap shows the fees and the expected amount you will receive, and swaps typically settle in about ten to thirty minutes. If a route cannot complete, your funds return to the refund address, keeping the process transparent and self-custodial from start to finish.