What does a swap look like when no bridge contract holds your coins

05 September 2026

You send coins on Chain A and receive different coins on Chain B, but no smart contract ever locks or escrows your tokens in between. The swap happens because the counterparty - a liquidity provider or an automated market maker - holds inventory on both chains and simply hands you coins from its own supply on the destination side.

To understand why this matters, you have to see what a bridge contract normally does. A typical bridge locks your tokens into a smart contract on Chain A, then mints a wrapped version on Chain B. That contract holds your actual coins until someone redeems them. If the contract is hacked, frozen, or mismanaged, your coins can be lost or stuck. In a swap that avoids a bridge contract, there is no central pool of locked tokens. No single contract ever holds your coins.

Here is how it works in practice. You initiate a swap through the site’s interface. You choose the amount and the target chain. The site finds a liquidity provider who has, say, Ether on Chain A and Solana on Chain B. You send your Ether to that provider’s address on Chain A. The provider, after seeing the transaction confirm, sends you an equivalent value of Solana from its own wallet on Chain B. The provider never used a bridge contract. It simply moved its own coins on both chains.

The provider takes on the risk of price movement during the few seconds between your send and its send. That is why the swap includes a small fee or a slight spread. The provider also absorbs the risk that you might be sending coins from a flagged address - though the site does not promise anonymity or immunity from law enforcement scrutiny.

The swap relies on the provider having sufficient inventory on both chains. If the provider runs low on one side, the swap fails or the site routes you to a different provider. There is no fallback pool. You either get matched or you do not.

What you never see: a lock, a mint, a redeem, or a central vault. What you do see: two independent transactions, one on each chain, with no shared contract linking them. The only connection is the provider’s willingness to honor the trade.

This design has trade-offs. It avoids the most common attack surface in crypto - the bridge contract that holds billions in user funds. But it introduces counterparty risk. You must trust that the provider will send the destination coins after receiving your source coins. The site mitigates this by selecting providers with verifiable track records and requiring collateral in some cases, but the trust is not eliminated.

If you want the full picture of how these swaps work alongside other methods, read the hub page titled "Swapping crypto across chains". It covers the different mechanisms, including atomic swaps and relayers, and explains where each approach fits.

For now, the short answer is: a swap that does not use a bridge contract looks like two separate peer-to-peer transfers, one on each chain, coordinated by a third party that holds inventory on both sides. No contract ever locks your coins. You send, the provider sends back. That is the whole shape of it.

Back to sim swaps