How to tell if a swap service is holding your funds in a shared pool

05 September 2026

You can tell a swap service is using a shared pool when your transaction sits in a pending state for an unusually long time, or when a second send from the same address arrives before the first one finishes. A shared pool means the service collects incoming funds from many users into one wallet and processes them in batch, rather than handling each swap individually and immediately.

What a shared pool actually is

A shared pool is exactly what it sounds like. The service deposits all incoming customer funds into a single wallet address. Your coins go into a bucket that also holds coins from dozens or hundreds of other people doing the same trade. The service then runs a script that periodically sorts through the bucket and sends out the equivalent amounts on the destination chain.

This is different from the cleaner model: one dedicated wallet per swap, where the service generates a fresh receiving address for each transaction, watches it for exactly your deposit, and releases your output coins as soon as enough confirmations arrive. With a shared pool, everyone's money mixes together.

Signs that you are inside a shared pool

Delayed confirmation. If the service advertises a ten-minute swap but your transaction remains marked "received" for an hour with no output, that is a pool at work. The pool might only empty every thirty minutes, or when it reaches a certain total. You are waiting for the batch to flush.

Multiple pending swaps from one address. If you send a second deposit while the first is still uncompleted, and the service accepts both without complaint, you are almost certainly in a shared pool. A dedicated-wallet service would usually reject a second send until the first finishes, because each address is tied to exactly one swap.

No unique receiving address. When you initiate a swap, look at the address the service gives you. If the same address appears in your previous swap history, or if you can find that address in a block explorer with transactions from many different senders, the pool is shared. Dedicated services generate a fresh address for every new order.

Outputs that appear in large, regular bursts. Check the destination address on a block explorer. If the service sends funds to users in big clusters every few minutes, rather than as a steady trickle of individual transactions, the pool is flushing on a timer or a volume trigger.

Why a service might use a shared pool

Shared pools reduce operational complexity and save on ethereum-basics/ethereum-transaction-lifecycle/">transaction fees. The service can batch dozens of outgoing transfers into one larger transaction, paying one network fee instead of many. This can allow the service to offer lower swap fees or faster quoted rates. The trade-off is that you, the user, lose visibility and control. You cannot watch your specific coins move; you only see the pool's aggregate behaviour.

What to do if you suspect a shared pool

If you are in a hurry and your swap is stuck, there is little you can do except wait. Shared pools usually clear, because the service's business depends on it. But if hours pass and nothing happens, check the service's support channel or status page. Some services have a manual override that can push a single swap through the pool early.

For future swaps, you can test the service with a small amount first. A tiny test often reveals the pool's behaviour quickly. If the small swap completes instantly but a larger one stalls, that strongly confirms the pool logic is volume-sensitive.

Where this fits in the bigger picture

Swapping crypto across chains without a bridge or a centralised account relies on the service acting as a temporary custodian. Whether it uses a shared pool or dedicated addresses does not change the fundamental risk: you are trusting a third party to hold your funds for a few minutes or hours. Understanding the pool mechanism helps you predict wait times and spot problems, but it does not eliminate the trust assumption. If you want to move past that trust entirely, the subject covered on the hub page - swapping crypto across chains - is the next thing to read.

Back to ethereum