Crypto collateral fragmentation occurs when capital is split across exchanges, accounts or collateral types, so funds visible in a portfolio total cannot immediately support a specific obligation. Measure eligible support and required margin in each local risk pool, then check withdrawable amounts, conversion costs and deposit status. A positive aggregate balance does not create cross-exchange margin netting.
A hedge can gain on one exchange while its losing leg needs collateral on another. Both results belong in the portfolio record, but each venue evaluates the resources available to its own risk engine. The useful question is where the money can work, in which asset, and when.
Separate four balances before adding anything up
Start with the exact venue, account, product and margin mode. Then identify what each displayed balance permits.
| Balance | What it tells you | What still needs checking |
|---|---|---|
| Marked equity | Assets and position results at the reporting snapshot | Whether every component qualifies as collateral |
| Recognized margin support | Value admitted under that account's collateral rules | Requirements, open orders and available order capacity |
| Transferable funds | Amount currently permitted to leave the source account | Asset, external withdrawal rules, fees and route |
| Destination support | Amount recognized in the destination risk pool | Fresh requirements and whether the intended obligation is covered |
Bybit's Unified Trading Account FAQ distinguishes Margin Balance, Available Balance for orders, and the transferable amount. It also says unrealized profit can support trades but cannot be transferred out under the documented UTA rules. These are Bybit definitions; they illustrate why an equity number should not be relabeled as cash available elsewhere.
Collateral valuation creates another boundary. Bybit's collateral value ratio guide explains that eligible assets can receive discounted recognition and that ratios can change. A dollar of displayed asset value may therefore supply less than a dollar of margin support.
The futures margin transfer guide follows additions and removals within a position or account. Here the additional problem is funding an obligation across independent exchanges.
A $14,000 surplus with a $4,000 local shortfall
Consider this original hypothetical ledger for three independent fictional venues. All values are in reporting dollars. Assume USDC and USDT each mark at $1 and receive full collateral recognition where accepted. There are no open orders or borrowing. Maintenance requirements and the operator's chosen operating targets stay fixed for the arithmetic.
Venue A holds 20,000 USDC plus $8,000 of unrealized profit. Venue B holds 12,000 USDC with a $4,000 unrealized loss. Venue C holds 10,000 USDT without a position. A's profit supports its local account but is not withdrawable in this scenario. B accepts only USDC.
A and B's operating targets are voluntary support floors above their modeled maintenance requirements. C has no position or retained floor in this example. Falling below an operating target calls for a decision; it does not itself mean liquidation. The reported withdrawal limit is a separate platform input.
| Account | Recognized support | Maintenance requirement | Operating target | Reported outbound amount |
|---|---|---|---|---|
| A | $28,000 | $12,000 | $20,000 | 6,000 USDC |
| B | $8,000 | $6,000 | $12,000 | Not treated as a funding source |
| C | $10,000 | $0 | $0 | 10,000 USDT; conversion needed for B |
| Total | $46,000 | $18,000 | $32,000 | No single spendable total |
Combined support exceeds combined operating targets by $46,000 − $32,000 = $14,000. B nevertheless has a $12,000 − $8,000 = $4,000 target shortfall. Its current support remains $2,000 above its modeled maintenance requirement.
The aggregate also contains a positive $4,000 unrealized result: A's $8,000 gain less B's $4,000 loss. That economic offset has not paid B's collateral need. A's gain belongs to A's risk pool until a permitted movement and destination recognition occur.
C appears to have ample spare capital, but its USDT does not directly satisfy B's stipulated USDC requirement. A common dollar reporting unit cannot resolve asset eligibility. The quote currency risk guide explains why a reporting conversion and an actual payable currency need separate treatment.
Size the route from the source account
For this worksheet, cap a proposed source debit at the smaller of the platform-reported withdrawal limit and the support that can leave while retaining the chosen source target.
A has $28,000 − $20,000 = $8,000 above its target, but reports only 6,000 USDC withdrawable. The route budget is therefore the smaller amount: 6,000 USDC. This calculation is an operator's additional constraint, not an exchange withdrawal formula. Recheck both inputs immediately before acting.
Assume a withdrawal route charges a fixed 10 USDC fee deducted from the gross debit. To deliver 4,000 USDC, the gross debit must be 4,010 USDC. That fits the 6,000 limit and leaves A with $28,000 − $4,010 = $23,990 of support, or $3,990 above its target.
Debiting only 4,000 would deliver 3,990 under the assumed fee convention, leaving B $10 short. Real interfaces can quote fees differently, so record gross debit, fee asset and expected net credit separately.
C's alternative route would require a conversion. Estimate the executable conversion amount after spread, fees and any size constraints before comparing it with A's route. The quoted, effective and realized spread guide helps distinguish a displayed price from the price actually obtained. No conversion rate or cost is assumed here, so C's full $10,000 cannot be booked as a ready USDC arrival.
Give pending transfers their own ledger state
A submitted withdrawal is not yet destination collateral. For example, Kraken's cryptocurrency deposit status documentation distinguishes network processing, credited funds that may be tradable before withdrawal, successful deposits, and deposits held for manual checks. Not every asset uses every stage. Those are Kraken processing states, rather than a universal cross-exchange settlement timetable.
Continue the hypothetical A-to-B route. Ignore funding and trading fees; only the explicit 10 USDC withdrawal fee changes the combined value. C stays at $10,000 throughout.
| Route state | A support | B support | Pending transfer claim | Combined recorded value |
|---|---|---|---|---|
| Before withdrawal | $28,000 | $8,000 | $0 | $46,000 |
| A debited; B not credited | $23,990 | $8,000 | $4,000 | $45,990 |
| B recognizes the deposit | $23,990 | $12,000 | $0 | $45,990 |
The combined recorded value includes C and counts the pending claim once, assuming it remains recoverable at the stated value. It is a reconciliation total, not a promise of recovery. While pending, locally recognized support across the three accounts is only $23,990 + $8,000 + $10,000 = $41,990.
A dashboard that keeps the debited funds in A and also adds an expected arrival at B overstates support. A dashboard that removes the withdrawal without recording a pending claim can make the transfer look like a trading loss. Keep the fee, pending claim and recognized balances distinct.
When B recognizes the 4,000, move that amount out of the pending row and into B. Check the intended trading account too: a deposit into a funding wallet may require another internal allocation before supporting a position.
An offsetting hedge can still breach local maintenance
Now branch from the pending state, before B receives anything. Suppose A gains another $3,000 while B loses another $3,000. These are stipulated mark-to-market changes, not a forecast or an assumed perfect hedge under all conditions.
A's support becomes $23,990 + $3,000 = $26,990. B's falls to $8,000 − $3,000 = $5,000. The combined recorded value remains $45,990 because the gains and losses offset and the $4,000 transfer claim remains pending.
B is now $1,000 below its illustrative $6,000 maintenance requirement. The group total has not deteriorated, yet B has crossed a local threshold. This is a threshold test, not a prediction that a real exchange would leave the position open while a transfer finishes.
Deribit's platform documentation describes real-time equity and maintenance checks and says its subaccounts are margined separately. That documents a local boundary within one provider. It supplies no basis for assuming an account at an unrelated exchange receives automatic support.
Even the same owner and a combined dashboard do not establish a shared risk pool. The subaccount boundary worksheet covers account identity and authority; those details must be known before interpreting any apparent consolidation.
Use an account-and-route worksheet
Build one row per local risk pool and one record per potential funding route. Do not make a symbol or strategy name the account identifier.
| Record | Evidence to capture | Decision it supports |
|---|---|---|
| Pool identity | Venue, account, product, margin mode and observation time | Which obligations the balance actually supports |
| Collateral | Asset quantity, valuation price, eligibility and haircut | Recognized support under current rules |
| Obligations | Maintenance, initial margin, orders, borrowing and charges | Current risk state and capacity for new activity |
| Source limit | Live withdrawable amount, chosen source floor and fee convention | Maximum permissible gross debit |
| Route | Accepted token, network, destination, conversion and holds | Whether a usable arrival is possible |
| Arrival | Source debit, transaction status, destination credit and account allocation | When support can be recognized locally |
| Stress action | Local trigger and permitted response if arrival is delayed | What happens before outside funds arrive |
Use a coherent snapshot. If A's support is current but B's positions are from an earlier observation, the combined view may describe no state that ever existed. A new fill, funding charge or collateral revaluation can invalidate the route budget.
Before relying on an incoming transfer, identify what the destination can do using resources already present. Depending on the product and current permissions, that may include canceling unfilled risk-increasing orders or reducing exposure. Verify completion and the resulting risk state; a submitted cancellation or reduction is not yet a changed obligation.
Replenishing earlier, holding more locally, reducing exposure and changing collateral each carry costs and constraints. Concentrating capital can increase dependence on one venue, while splitting it requires more local funding coordination. This ledger does not select an allocation or promise that transfers will protect a position.
Finish the funding decision with three quantities: the destination's current local gap, the source's permitted gross debit after retaining its floor, and the net amount actually recognized at the destination. Until the third quantity updates, the destination must be evaluated on the collateral it already has.