13 November 2026 | Author: ABF Swap Research Team
A cross-chain swap exchanges an asset on one blockchain for an asset on another, for example USDT on Tron for ETH on Ethereum. Many swaps of this kind rely on bridges, which lock funds in a smart contract on one chain and issue a wrapped copy on the other, and those contracts have been among the most frequently hacked targets in crypto. Direct swaps, solver networks and exchange-based swaps avoid holding user funds in a shared bridge vault, which removes the largest single point of failure, but each approach adds trust assumptions of its own.
Key takeaways
Risk notice:
Each blockchain keeps its own ledger and has no built-in way to verify what happens on another one. Ethereum cannot see that you sent USDT on Tron, so any cross-chain transfer needs a third party or protocol that observes one chain and acts on the other. That component is where the risk sits: whatever controls it can, in principle, release funds that were never deposited.
The Ethereum documentation on bridges divides them into two broad groups. Trusted bridges rely on an external set of verifiers, such as a multisig committee, a multi-party computation system or an oracle network, so users depend on those verifiers staying honest and secure. Trustless bridges rely on the connected blockchains themselves and add fewer new assumptions, but they are harder to build and slower. The same documentation lists smart-contract risk, systemic financial risk from wrapped assets and counterparty risk among the main concerns.
Most cross chain bridge vulnerabilities come from two sources: bugs in the smart contracts that hold and release funds, and weaknesses in the off-chain systems, keys and people that approve transfers. Because a bridge often holds the entire collateral behind every wrapped token it has issued, one flaw can expose hundreds of millions of dollars at once. According to Chainalysis research, around $2 billion was stolen in 13 bridge hacks in 2022 up to early August, about 69% of all crypto stolen in that period.
In a lock-and-mint bridge, your original tokens are locked in a contract on the source chain and the bridge mints an equivalent wrapped token on the destination chain. The wrapped token is only worth something as long as the locked collateral is there and can be redeemed. If an attacker finds a way to mint wrapped tokens without depositing anything, or to withdraw collateral without burning wrapped tokens, the backing disappears.
That is what happened to Wormhole in February 2022: the attacker spoofed the bridge's signature verification, minted 120,000 wrapped ETH without backing and swapped it for real ETH, causing a loss of about $320 million. Every holder of a wrapped token is exposed to a hack of this kind, even if they never used the bridge themselves.
Many bridges approve withdrawals when a set number of validators or multisig signers agree. That design is only as strong as the security of those keys. In March 2022, attackers gained access to the systems of Sky Mavis, the developer of the Ronin network, through a phishing email, took control of enough validator keys to approve withdrawals and drained about $625 million. The attack was later attributed to North Korea's Lazarus Group.
In July 2023, more than $125 million left the Multichain bridge after the team behind it lost control of its operations, and the project shut down. The primary risk lies in the number of trusted components required and the lack of a contingency plan if signers are compromised or unavailable.
The largest crypto bridge hacks show a clear pattern: the cause varies, but the target is always a large pool of locked funds controlled by a small number of contracts or keys.
| Incident | Date | Approximate loss | Cause | Lesson |
|---|---|---|---|---|
| Ronin | March 2022 | $625 million | Validator keys stolen after phishing | A small validator set is a single point of failure |
| Wormhole | February 2022 | $320 million | Signature verification bypassed, unbacked tokens minted | Wrapped tokens are only as good as the bridge's code |
| Nomad | August 2022 | $190 million | Faulty upgrade let anyone bypass the trust check | Upgrades can introduce critical bugs after audits |
| BNB Bridge | October 2022 | $120–130 million moved off BNB Chain | Bug in the proof verification system | Even chain-level bridges can fail |
| Multichain | July 2023 | More than $125 million | Loss of operational control | Off-chain governance can fail as badly as code |
Audits reduce risk but cannot rule out every bug, especially after upgrades. Users of wrapped tokens and bridges carry that risk whether or not they ever look at the bridge's code.
A crypto bridge swap usually combines a bridge transfer with a trade:
Each step adds a dependency: the bridge contract, the attesters, the wrapped token and the destination liquidity pool. Some issuers now offer burn-and-mint transfers for their own tokens instead. Circle's Cross-Chain Transfer Protocol, for example, burns USDC on one chain and mints native USDC on another, so users receive the issuer's own token rather than a wrapped copy.
A direct swap delivers the asset you want on the destination chain without asking you to lock funds in a bridge vault or hold a wrapped token. Someone who already holds liquidity on the destination chain, such as a liquidity provider, a solver, an exchange or the counterparty in an atomic swap, pays you there in exchange for your funds on the source chain.
The main difference is where the money sits. A lock-and-mint bridge keeps all collateral for every wrapped token in one vault. In a direct swap, liquidity providers keep separate inventories on each chain and settle trades between themselves, so there is no single vault backing tokens that thousands of people hold. If something goes wrong, the loss falls mainly on the provider's inventory and on swaps in progress at that moment.
This does not make the provider itself immune. Centralised platforms hold large hot and cold wallets of their own, and those can be targeted too: in February 2025, attackers stole about $1.5 billion in ETH from the exchange Bybit by manipulating the interface used to sign a transfer from its multisig cold wallet. The risk moves from the bridge to the operator, so the operator's security, reserves and reputation matter.
Intent-based protocols let you sign a message describing what you want, for example "100 USDC on Arbitrum in exchange for 100 USDC on Base", instead of sending a series of transactions. Competing solvers or fillers deliver the funds on the destination chain from their own inventory, usually within seconds, and are repaid on the source chain later. Any delay or risk in moving funds between chains is carried by the solver rather than by you.
Your exposure is limited to the short window between signing and being filled, and if no solver fills the order, the funds are normally returned. You still rely on the protocol's settlement contracts being free of bugs, and solvers themselves may use bridges in the background.
Receiving native assets removes one layer of risk entirely. A wrapped token depends on its bridge staying solvent; native ETH on Ethereum or native USDT on Tron depends only on that network and, for stablecoins, on the issuer. Atomic swaps take this furthest: they use hashed time-lock contracts, so that both sides of the trade either complete or are refunded automatically after a set time, without any intermediary holding funds. They are trustless but need a counterparty on the other chain and are not supported by all blockchains.
Important:
| Aspect | Lock-and-mint bridge | Intent-based (solver) swap | Atomic swap | Exchange-based swap |
|---|---|---|---|---|
| What you receive | Usually a wrapped token | Native or canonical asset | Native asset | Native asset |
| Where funds sit | In a shared bridge vault | Briefly in the protocol's contracts | In time-locked contracts on each chain | In the exchange's wallets |
| Who you trust | Bridge contracts and validators | Settlement contracts and solvers | The two blockchains' code | The exchange operator |
| Main failure mode | Contract bug or key compromise affecting all holders | Contract bug or unfilled order | Missed timeout, limited availability | Exchange hack, insolvency or freeze |
| Identity checks | None at protocol level | None at protocol level | None at protocol level | Required by regulated providers |
None of these models removes every risk. Network outages, incorrect addresses, low liquidity and software bugs remain relevant whichever route you choose.
Before you use a cross chain swap crypto service, work through these questions:
These questions matter because a cross chain crypto exchange may involve considerably more infrastructure than its interface suggests.
ABF Swap is operated by ABF Trade Connect (Pty) Ltd, a company registered in South Africa, which states that it is authorised by the FSCA under licence No. 52818. ABF Swap is not authorised by the FCA in the UK or as a crypto-asset service provider under MiCA in the EU.
ABF Swap works as an exchange: you deposit a supported asset on one network and receive another supported asset or euros, with the conversion handled on the platform rather than through a bridge contract. Verified customers can execute a cross chain swap between supported assets and networks, and the exchange-based model in the table above applies: no wrapped tokens or shared bridge vault are involved, but the platform holds your funds while the swap is processed. Before confirming, check the rate, the amount you will receive, the network and the destination address.
The same route can be used to move straight from crypto to fiat. A freelancer paid in USDT on Tron (TRC-20), for example, can sell it for euros on a platform that accepts TRC-20 deposits, without first bridging it to Ethereum (ERC-20) and paying Ethereum gas. A business receiving payments on several networks, such as Tron, Ethereum and BNB Chain (BEP-20), can convert each balance where it arrives instead of consolidating it through bridges first. In both cases, the conversion is subject to identity verification and anti-money laundering checks, so keep invoices, transaction hashes and other records that explain where the funds came from. The step-by-step cross chain setup guide on the ABF Swap website describes account creation and the verification steps.
A cross-chain swap exchanges an asset on one blockchain for an asset on another, such as USDT on Tron for ETH on Ethereum. It can be carried out through a bridge and a decentralised exchange, an intent-based protocol with solvers, an atomic swap or an exchange that holds liquidity on both networks.
A bridge swap depends on several components at once: the bridge's smart contracts, the validators or signers that approve transfers, the wrapped token it issues and the liquidity pool on the destination chain. A weakness in any of them can affect your funds, and bridge contracts have been the target of some of the largest hacks in crypto.
A bridge often holds the entire collateral behind every wrapped token it has issued in one vault. A single bug or compromised set of keys can therefore expose hundreds of millions of dollars and make wrapped tokens held by thousands of people worthless. A typical exploit of a single DEX pool affects only the liquidity in that pool.
Intent-based swaps and atomic swaps keep funds in your control or in time-locked contracts until the trade completes, and deliver native assets instead of wrapped tokens. That avoids a shared bridge vault and limits your exposure to the few seconds or minutes of the swap. You still depend on the protocol's contracts being free of bugs.
No provider can complete a transfer on a blockchain that is not producing blocks. Well-designed systems either wait until the network resumes or refund the transaction after a timeout. Before swapping, check what the provider or protocol does if one network becomes unavailable and who decides.
ABF Swap processes conversions on its own platform rather than through a bridge contract, so customers receive native supported assets or euros. Routing depends on the supported asset and network. Review the rate, network and destination details before confirming, especially during periods of network congestion or outages.
This article is for general educational purposes and does not constitute financial, investment, legal or tax advice. Cryptoassets are high-risk, their value can fall to zero, and transfers are generally irreversible. In the UK, cryptoassets are generally not protected by the FSCS, and you may not be able to complain to the Financial Ombudsman Service; in the EU, they are not covered by deposit guarantee schemes. Rules on cryptoasset services differ by country, so check whether any provider you use is authorised to serve customers where you live.





Start earning passive income from every transaction your invitees make with one of the highest rewards on the market!