Skip to main content
DeFi Millionaire book on Amazon (opens in a new tab)
Auto top-up on? A glass trading vault receiving funds from a reserve.
Crypto Trading

Isolated Margin, Auto Top-Up: How Much of Your Crypto Balance Is Actually at Risk?

By

Isolated margin can receive extra funds when automatic top-ups are enabled. Map the source balance, additions and controls with DN’s Margin Reach Map.

What Matters

Isolated margin separates a position’s margin from a shared collateral pool, but the amount allocated to that position can change. Manual additions or enabled automatic replenishment can commit more money than the opening allocation. Before relying on the original figure as a risk boundary, identify every permitted source of additional margin, the product’s limits and the settings that actually apply.

DN Evidence Block

Last verified: 31 October 2026. Scope: Bybit’s Auto-Margin Replenishment and Unified Trading Account margin-mode documentation; Hyperliquid’s margining documentation. Original DN tool: Margin Reach Map, a manual control audit and synthetic allocation journal.

Decisive fact: Bybit documents automatic additions from available account balance for supported isolated-margin products when AMR is enabled. [1] Isolated margin is therefore not the same statement as “this position can never receive another unit of collateral.”

Method: documentation review and arithmetic validation only. DN did not access accounts, activate top-ups or test liquidation. The 2027 edition uses evidence reviewed in October 2026. This article does not calculate a guaranteed maximum loss or legal liability.

The useful question is where the next margin addition can come from

A trader might open a position with 500 USDT assigned to isolated margin while keeping a larger available balance nearby. The word isolated describes how the position is margined; it does not by itself explain whether another process can transfer funds into that allocation.

There are three separate questions: what is allocated now, what can be allocated later, and what account-level or custody risks exist outside the position. A clear operating plan answers all three. A lower effective leverage after adding collateral can reduce immediate liquidation pressure while increasing the capital committed to the trade.

This is not a claim that isolated margin secretly behaves as cross margin. The mechanisms differ. The point is to audit the transfer permissions surrounding the isolated position.

What automatic replenishment actually changes

Bybit’s AMR guide says the feature transfers available Unified Trading Account funds into a supported isolated position near its liquidation threshold. It identifies USDT perpetual, USDT expiry and USDC perpetual support, and describes a limit tied to the margin needed for 1× leverage. It warns that insufficient balance or market volatility can still lead to liquidation. [1]

Those are Bybit-specific rules. They are not evidence that another venue uses the same trigger, source balance, cap or supported contracts. A platform’s automatic top-up feature should be checked by its exact name and product.

Bybit’s margin-mode comparison separately lists isolated, cross and portfolio modes. It distinguishes position-specific liquidation logic from account maintenance-margin-rate logic and says AMR is disabled by default after the documented switch to isolated mode. [2] A documented default does not establish your current setting, particularly after later changes.

DN Margin Reach Map

Use this manual tool before opening a trade or when reviewing an existing one. Mark each row verified, mismatch or unknown. It does not connect to your account, move funds or forecast liquidation.

Layer Evidence to record Decision it supports
Current allocation Position ID, contract, account, currency, allocated margin and observation time What is assigned now?
Margin mode Exact mode for this position/account and current product rules Is collateral shared or position-specific?
Automatic additions Feature name, enabled state, trigger, source balance, rule-based limit Can the position draw further funds without a new manual decision?
Manual and delegated additions Authorized users, API permissions, bots or transfer workflows, where applicable Who or what can commit more capital?
Reserve boundary Where reserve funds sit and whether an authorized route can reach them Is the intended reserve operationally separate?
Addition history Confirmed top-ups, removals and transaction references Has the allocation grown beyond its original amount?
Control evidence Setting read-back, effective scope, restrictions and latest review time Is a claimed limit actually enforced?

DN decision rule: do not describe the opening margin as a fixed capital boundary while an unresolved automatic or delegated addition path remains. Treat unknown scope or source access as an evidence gap rather than assuming it is zero.

Worked example: 500 USDT becomes 1,000 USDT committed

Synthetic allocation journal, not a Bybit trigger simulation. Assume a position starts with 500 USDT allocated. Later, two confirmed margin additions of 200 and 300 USDT occur. The figures are illustrative; they do not represent a venue’s top-up sizing algorithm.

Event Allocation change Recorded cumulative allocation
Opening allocation +500 USDT 500 USDT
Confirmed addition A +200 USDT 700 USDT
Confirmed addition B +300 USDT 1,000 USDT

The journal total is 500 + 200 + 300 = 1,000 USDT, twice the opening allocation. Assuming the additions came from an available reserve and there were no other reserve movements, that reserve fell by 500 USDT. The trade can remain isolated while its allocation increases.

This ledger is not the position’s current equity or realized loss. Unrealized P&L, fees, funding, margin removals and product accounting must be reconciled separately. Adding collateral is a capital transfer, not a trading expense by itself. Do not sum the current margin field and all historical top-ups if the current field already includes those additions.

Manual reconciliation formula: opening allocation + confirmed additions − confirmed removals = net capital allocated through those events. Compare it with the provider’s corresponding allocation records, allowing for precisely identified accounting differences. Do not use the result as a liquidation-price formula.

Cross margin is a different scope, not simply “auto top-up”

Cross margin typically shares eligible collateral within a defined account scope, whereas a replenishment feature transfers funds into an isolated position under its own rules. The size and boundaries of the shared pool still need verification.

Hyperliquid’s margining documentation, for example, describes collateral sharing among cross positions and asset-specific isolation. It also says the scope across HIP-3 DEXs depends on account abstraction, and describes strict-isolated assets with constraints on margin removal. [3] Even within one system, a mode label is not enough to infer every transfer or sharing rule.

Do not switch modes impulsively as a troubleshooting step. First review the provider’s eligibility conditions, treatment of existing positions and resulting risk calculations. A mode change can alter required collateral and the applicable liquidation logic.

Audit reserves by transfer authority

A reserve is only operationally separate from a position to the extent that the relevant systems cannot automatically or discretionarily move it into that position under the permissions you have granted. A different wallet label, strategy name or subaccount display does not by itself prove that boundary.

Document the exact source account and whether an authorized user, API or automation can transfer from it. If a separate account or wallet is part of the plan, verify the actual product behavior and access controls. This article does not assert that any named venue grants a particular API permission or that any account arrangement provides legal segregation.

Keep venue custody and insolvency exposure separate from margin configuration. An isolated trading setting is not proof that assets elsewhere on a platform are protected from platform-level failure.

A written budget is useful, but it is not an enforced cap

“I will add no more than 500 USDT” is an operating policy. It becomes a technical constraint only where the actual control prevents further additions within its documented scope. A feature’s built-in limit may be based on leverage or position value rather than your preferred cash budget.

Record who can change the setting, whether changes apply to the current position or future positions, and how you confirm the effective state. A screenshot of a toggle is useful evidence of that interface at that time; it is not an end-to-end test of every automation around the account.

If you disable automatic replenishment, understand the immediate consequences for a live position. It does not close the trade or reverse additions already made. Removing a source of support can bring liquidation risk closer if the position is already stressed. No single setting eliminates market risk.

Review the map whenever the position changes

Recheck after a partial close, leverage change, account-mode change, new automation, additional deposit or manual margin transfer. Keep a dated record of the position and controlling settings. A plan approved for one state may no longer describe the next state.

If a balance movement is unexplained, reconcile its transaction reference before assuming it was a top-up. Use DN’s Balance Reconciliation Guide and Funding Bill Reconciler. For an attempted exit, check the Reduce-Only Order Audit.

Compare control requirements before choosing a venue

Use DN Pathfinder to organize requirements and the Collateral Efficiency Index to examine capital use. Capital efficiency and capital containment are different objectives; a venue suitable for one strategy may be unsuitable for another.

Affiliate disclosure: linked DN tools and reviews may include affiliate links. They are optional research pathways, and no signup is required to use this worksheet. This article does not rank venues or recommend a leveraged position.

Methodology, limitations and corrections

DN reviewed three official documents and separated mode, allocation and transfer authority into a manual audit. The worked journal was checked with decimal arithmetic. We did not validate account settings, test feature triggers or model liquidation, collection shortfalls or legal claims. The map identifies evidence required to understand capital commitment; it does not guarantee a maximum loss. Version 1.0, 31 October 2026. Report outdated guidance through DN’s contact page with a source URL, excluding credentials.

Frequently Asked Questions

Can an isolated position receive more than its opening margin?

Yes, where manual additions or a supported automatic replenishment feature are permitted. Check current settings and product rules.

Is automatic margin replenishment the same as cross margin?

No. Replenishment adds funds to an isolated allocation under its rules; cross margin shares collateral within a defined scope.

Does adding margin eliminate liquidation risk?

No. It can change the buffer and effective leverage, but volatility, losses and limited available funds can still lead to liquidation.

Does turning off top-ups remove margin already added?

Do not assume so. Disabling future automatic additions is different from removing existing collateral or closing the position.

Is the worksheet’s allocated-capital total my maximum possible loss?

No. It is a transfer reconciliation, not a complete loss, liability or liquidation model.

Primary sources

  1. Bybit: Auto-Margin Replenishment, updated 25 March 2026.
  2. Bybit: Unified Trading Account margin modes.
  3. Hyperliquid: Margining.

All sources reviewed 31 October 2026. General operational education, not individualized trading advice. Product access and rules vary.

Get the most talked about stories directly in your inbox

Join the Decentralised News briefing for independent crypto, DeFi and AI analysis. No spam, unsubscribe anytime.