How to use sub-accounts for different crypto contract strategies?

Sub-Account Structure and Isolation Benefits

1. Each sub-account operates with independent margin, position limits, and risk parameters, enabling strict separation between distinct trading methodologies.

2. Funds transferred to a sub-account are not accessible from the master account or other sub-accounts without explicit re-transfer, eliminating cross-strategy capital leakage.

3. Leverage settings can be customized per sub-account—allowing one to run high-leverage scalping while another maintains conservative 5x exposure for swing positions.

4. Order history, PnL tracking, and liquidation triggers remain siloed, preventing performance distortion when aggregating metrics across strategies.

5. API keys assigned to sub-accounts inherit only the permissions granted at creation, reducing systemic exposure if credentials are compromised.

Allocating Sub-Accounts by Strategy Type

1. A dedicated sub-account for grid trading isolates volatility-driven drawdowns from trend-following positions held elsewhere.

2. Arbitrage sub-accounts hold minimal open interest but require rapid order execution—enabling fine-tuned latency optimization without affecting longer-term holdings.

3. Hedging sub-accounts may hold inverse perpetuals against spot positions; their margin usage does not interfere with directional strategy equity.

4. Market-making sub-accounts benefit from segregated fee tiers and rebate eligibility, often tied to volume thresholds calculated independently.

5. Copy-trading sub-accounts allow third-party signal providers to manage capital without visibility into or control over other operational accounts.

Risk Management Through Sub-Account Boundaries

1. Maximum loss caps can be enforced per sub-account via automated transfer limits or stop-out rules triggered at predefined equity thresholds.

2. Margin calls in one sub-account do not trigger margin calls elsewhere—even if the master account holds sufficient aggregate collateral.

3. Liquidation engines calculate bankruptcy price solely on the sub-account’s isolated wallet balance and open positions, removing interdependence.

4. Daily PnL reporting is generated per sub-account, supporting granular attribution analysis without manual ledger reconciliation.

5. Position size constraints can be hardcoded into sub-account configuration, blocking orders that exceed pre-approved notional values.

Operational Workflow Integration

1. Automated funding scripts push initial capital to designated sub-accounts based on strategy activation signals from external analytics platforms.

2. Real-time balance synchronization ensures sub-account equity feeds into centralized dashboards without requiring manual CSV exports.

3. Sub-account-specific webhooks deliver fill confirmations, liquidation alerts, and funding rate updates directly to corresponding strategy modules.

4. Withdrawal whitelists restrict outbound transfers to pre-authorized addresses, enforcing custody discipline across all sub-accounts.

5. Audit logs record every internal fund movement, API call, and permission change—each tagged with sub-account ID and timestamp.

Common Questions and Answers

Q: Can I share a single API key across multiple sub-accounts?A: No. Each sub-account requires its own uniquely generated API key with permissions scoped exclusively to that environment.

Q: Do sub-accounts support different trading fee tiers?A: Yes. Fee schedules are determined by the individual sub-account’s 30-day trading volume and maker/taker ratio, independent of other accounts.

Q: Is it possible to convert a sub-account into a standalone main account?A: Not natively. Sub-accounts exist as logical partitions under the master account’s KYC and compliance framework; migration would require full onboarding.

Q: Can I view aggregated PnL across all sub-accounts in real time?A: Yes. Dashboard interfaces display consolidated equity and net PnL, but underlying calculations always originate from isolated sub-account ledgers.