The point of an exchange sub-account is containment. If one strategy blows up, the loss stays inside the container instead of reaching the balance that funds everything else. The mechanics are simple, but the details vary by venue, and the differences matter more than the marketing suggests.

• Sub-accounts separate margin and positions, but not always the custody risk of the venue itself.
• Most venues let you scope API keys per sub-account, which limits the blast radius of a leak.
• Transfers between sub-accounts are usually internal and free, unlike withdrawals to an external chain.
• Segmentation fails if the master account keeps withdrawal rights or shared collateral enabled.

What an exchange sub-account actually isolates

It isolates margin, positions, order history and permissions. It does not isolate counterparty risk. Funds on the same venue share the same custodian, the same operational failures and the same withdrawal queue.

That distinction should drive how you use them. Sub-accounts are excellent at stopping one strategy from liquidating another. They are useless against the venue itself freezing withdrawals, and they do not protect you if the entity holding the assets fails. For that risk you need a different venue, not a different sub-account.

The four things that are separated

Balance, margin, positions and API credentials are what typically move into a sub-account. Each one has its own consequences.

• Balance — the collateral available to that container only. A loss elsewhere cannot touch it, and vice versa.
• Margin — leverage is calculated per account, so a heavily used strategy does not consume the borrowing capacity of a conservative one.
• Positions — netting happens within the container. Two opposing positions in different sub-accounts stay open instead of offsetting.
• API credentials — keys issued to a sub-account normally cannot read or trade the master account, which is the single most useful property.

What stays shared

KYC identity, fee tier treatment, deposit addresses, and the legal relationship with the venue usually remain at master level. Some venues aggregate volume across sub-accounts for fee tiers; others do not. Some allow internal transfers instantly; others batch them.

Check three settings before you rely on the structure: whether the master can withdraw from sub-accounts without approval, whether negative balances in one sub-account can be covered from another, and whether margin is shared by default. Any of these enabled quietly defeats the purpose.

Why separating risk with an exchange sub-account pays off

Because the most common account failure is not theft — it is one strategy consuming the collateral that another strategy needed.

Consider a funding-rate position that is correctly hedged but temporarily underwater, running in the same account as a directional position with a tight stop. The hedge needs margin to stay open. The directional trade’s losses reduce available margin. The venue liquidates whichever position is closest to the line, which may be the hedge you intended to keep. Two sub-accounts make that interaction impossible.

Operational separation beats mental separation

Keeping strategies apart “in a spreadsheet” is not separation. If they share one balance, one liquidation engine treats them as one portfolio. The engine does not care about your labels.

This is also why sub-accounts matter for automation. A bot with a key that can only touch its own container cannot drain the rest of your account through a bug, a bad config, or a compromised API secret. That is a real limit, not a theoretical one.

How sub-account models compare

Models differ in where the boundary sits, and the differences change what you can safely automate.

Segmentation is only real when the failure of one container cannot reach the collateral of another. Everything else is bookkeeping.

Setting one up without creating new failure modes

Setup takes minutes, and the ordering matters more than the clicks.

1. Decide the boundary first: one sub-account per strategy, per client, or per risk budget. Mixed boundaries produce containers nobody can reconcile.
2. Create the sub-account and fund it with only the collateral that strategy needs, not a round-share of your total.
3. Disable master-level withdrawal rights over the sub-account if the venue allows it, or remove withdrawal permission from every key.
4. Issue a fresh API key scoped to that sub-account, with IP allowlisting where available and no withdrawal permission.
5. Set a notional cap in your own code as well, because venue-side limits are the second line of defence, not the first.
6. Record which key belongs to which container in one place, and test the separation with a small deliberate transfer.
7. Review monthly: dormant sub-accounts accumulate balance and become an unmonitored attack surface.

A simple allocation example

Suppose 10,000 units of quote currency are split three ways: 5,000 for a spot core position, 3,000 for a hedged basis trade, 2,000 for a high-turnover experimental strategy. If the experimental container loses its entire 2,000, the other two are untouched, because the liquidation engine never saw them. In a single account, that same loss would have reduced shared margin by 20 percent and could have forced a partial unwind of the hedge at the worst moment.

The arithmetic is the argument. Containment converts an unbounded portfolio event into a bounded, pre-agreed loss.

Mistakes that quietly undo the separation

Most failures come from configuration drift rather than from the model itself.

• Shared collateral switched on for convenience, which links every container again.
• One master key reused across bots, so a single leak reaches everything.
• Sub-accounts used as a filing cabinet, with balances left idle in containers nobody watches.
• Withdrawal permission granted to a trading key “just in case”, which turns a trading bug into a full loss.

Each of these is reversible, and each is worth checking before the next deposit rather than after the next incident.

Reconciliation is the other quiet failure. Once balances live in several containers, your total exposure is no longer visible on one screen, and a position you believe is hedged may be hedged in a container that no longer holds enough collateral. Export balances on a fixed schedule and add them up yourself.

The post Sub-Accounts: Separating Risk appeared first on FogChain.

That last clause is where most confusion starts. An exchange insurance fund is not deposit insurance, it does not cover hacks, and it does not reimburse you for a bad trade. It covers one narrow gap in the derivatives plumbing, and understanding that gap tells you a lot about how liquidation actually works.

• The fund absorbs shortfalls between a liquidation price and the price the venue actually got.
• It covers the venue’s book, not your deposit, and not losses from theft or insolvency.
• Fund size is a rough buffer estimate, not a guarantee, and published figures vary in what they include.
• When the fund is exhausted, venues typically fall back to auto-deleveraging other traders’ positions.

What an exchange insurance fund is for

Liquidation is supposed to be solvent: the position is closed while collateral still covers the loss. Sometimes it is not. A fast move, a thin book, or a gap through several price levels can leave the venue holding a position that is worth less than zero after the trader’s margin is gone.

That negative balance has to land somewhere. It can land on the venue’s balance sheet, on other traders through a clawback, or on a pre-funded pool. The exchange insurance fund is the third option, and most large derivatives venues use it.

Where the money comes from

Funding rules differ by venue, but the common sources are liquidation penalties charged to the liquidated trader and any residual value left after their position is closed.

When a position is liquidated, the venue typically closes it and keeps a penalty from the remaining margin. Some of that flows into the fund. In a well-behaved liquidation where the fill is better than the bankruptcy price, the surplus goes to the fund too. The fund therefore grows in calm conditions and drains in violent ones, which is exactly the opposite of when you want a buffer to be large.

How it differs from the bankruptcy price

The bankruptcy price is the price at which the trader’s margin is exactly exhausted. Liquidation tries to close the position before that price is reached. If the market moves through it faster than the venue can close, the difference is the shortfall the fund exists to cover.

This is why the fund matters most for high-leverage positions in thin markets. Low leverage and deep books make shortfalls rare. High leverage and a gap make them routine.

What an exchange insurance fund does not cover

It does not cover theft, operational failure, insolvency, or your own losses. Those are separate risks with separate (often absent) protections.

The fund is not there to make you whole. It is there to stop one trader’s bad fill from becoming every trader’s bad fill.

Reading an exchange insurance fund’s published numbers

Published fund sizes are indicative, not audited in the way a bank balance sheet is. Read them as a rough measure of buffer, and read the methodology before you read the number.

Three questions make a figure meaningful. What is it denominated in — one stablecoin, a basket, or the venue’s own token? Does the venue publish a live figure or a periodic snapshot? And is the fund actually segregated, or is it an accounting entry the venue can draw on for other purposes?

Scale the fund against open interest, not against your feelings

A fund of any given size means little without a denominator. Compare it to open interest on the same venue, and to the venue’s typical daily liquidation volume during volatile periods. A fund that looks large relative to a quiet day can look thin relative to a cascade.

None of these ratios are published consistently across venues, and definitions vary, so cross-venue comparison is approximate at best. Treat the comparison as a sanity check on order of magnitude rather than a precise ranking.

What happens when the fund runs out

Venues need a second mechanism, because a large enough move can exhaust any pool. The common answer is auto-deleveraging, usually shortened to ADL.

ADL closes profitable positions at the bankruptcy price of the failing position, ranked by leverage and profit. You do not choose it. It happens to traders who are winning, which is the part people find surprising: a correct position can be closed early because someone else’s position went wrong.

1. Liquidation engines close the failing position and consume its margin.
2. If a shortfall remains, the fund absorbs it.
3. If the fund cannot absorb it, ADL closes opposing profitable positions at the bankruptcy price.
4. If that is still insufficient, the venue may apply a clawback or socialised loss across the book, depending on its rules.
5. Any of these steps can occur within seconds during a fast move, so read the venue’s rules before you need them.

A short worked example

A trader holds a long with 500 units of margin at 10x, so the position is 5,000 notional. The bankruptcy price is 10 percent below entry. A gap takes the market 13 percent below entry before the engine can close. The loss is 650 against 500 of margin: a shortfall of 150. The fund absorbs the 150, the trader’s margin is gone, and no other account is touched. If twenty such positions fail in the same minute, the shortfall is 3,000, and whether the fund covers it depends entirely on its size at that moment.

Using fund information sensibly

Treat fund size as one input among several, and never as a reason to increase leverage.

The more useful signal is the venue’s overall risk design: how liquidation is triggered, whether ADL is disclosed clearly, how transparent the fund’s accounting is, and whether the venue publishes open interest and liquidation data. A large fund with opaque rules is less informative than a smaller fund with clear mechanics.

For your own positions, the practical controls are lower leverage, wider distance to liquidation, and collateral you can top up quickly. Those reduce the chance that you ever become the shortfall the fund has to cover.

The post Exchange Insurance Funds: What They Cover appeared first on FogChain.