What you are doing
You are evaluating what can go wrong even when automation behaves exactly as designed.
Why it matters
A strategy can be profitable over one period and lose in another. Leverage, sustained trends, gaps, liquidity, fees, funding and exchange failures can materially change outcomes.
Before you start
Only use capital you can afford to expose to derivatives risk. Understand that unrealized loss is economically real even before a position closes.
Step by step
- 01Inspect maximum drawdown, not only ending return.
- 02Inspect liquidation distance and how it changes after each DCA.
- 03Confirm commissions, funding and executable price rules are included.
- 04Check how long cycles remain underwater and whether capital becomes unavailable.
- 05Consider exchange/API outages and protection-order failure.
- 06Keep the full required collateral on the dedicated subaccount while positions are open.
What you should see
Results should state the period, starting capital, fees, funding, drawdown, cycles and liquidations. Claims must distinguish historical replay from live performance.
What happens in a bad month?
A bad month can show little or no realized profit while an open cycle carries an unrealized loss. Capital may remain tied up for longer than the usual cycle, funding and exchange fees continue to matter, and the account equity can fall substantially before recovery. Historical Replay reports realized and unrealized results separately; it does not convert an open loss into a zero merely because the core position has not closed.
When Shield cannot protect you
Shield can reduce net directional exposure only after its defined trigger and only to the configured size. It cannot guarantee an execution price, prevent exchange liquidation, replace collateral, repair an invalid API key, operate through missing market data, remove basis and funding costs, or protect against every price gap, liquidity event, exchange outage or configuration error. If required telemetry is stale or incomplete, HEDGERON must show UNKNOWN and pause risk-sensitive actions rather than claim protection.
If market or exchange data fails
Do not remove reserve capital or manually fight the strategy while the state is uncertain. Verify the position directly on Bybit, follow the Status page, revoke the API key first if compromise is suspected, and contact support with the incident time and bot identifier but never with passwords, API secrets or 2FA material.
Security check
Risk control begins with account isolation and minimum API permissions; it does not end there.
Common problems
Reducing reserve capital during drawdown
This can increase margin pressure at the worst time.
Assuming 0 historical liquidations means liquidation-proof
It does not. Future paths and exchange conditions can differ.
Ignoring funding and commissions
High turnover can turn a theoretical edge into a weak or negative result.
Next step
Create and secure a dedicated Bybit account environment.
Privacy note
HEDGERON Help analytics must never collect API credentials, passwords, private account values or secret-bearing URLs.