Ricerca verificata da fonti: Bybit / OKX

Verified source facts

1. Bybit says a standard subaccount's profit and loss is segregated from the main account and that standard subaccounts support API trading. 2. Bybit says standard subaccounts cannot make external deposits or withdrawals; those operations must be performed through the main account. 3. OKX says standard users can create up to five subaccounts and can select the intended main account or subaccount during API-key creation. 4. OKX documents separate Read, Trade and Withdraw permissions and recommends binding API keys to trusted IP addresses. 5. OKX says a Trade or Withdraw API key without an IP binding expires after 14 days of inactivity; demo-trading keys are excluded from that inactivity rule.

Comparison at a glance

1. Compare account capacity on the same job

A platform comparison becomes useful only when both venues are measured against one job. For account capacity, that job concerns number and type of subaccounts. Marketing pages frequently describe broad capability while the actual decision lives in a specific pair, contract, network, entity, or account tier. Build two evidence rows from the same timestamp, then match the operating structure. Until that check is complete, neither venue earns the point.

The comparison should distinguish a published ceiling from an executable outcome. A fee table does not reveal slippage; a product menu does not prove regional eligibility; a security feature page does not prove the control is enabled on the reader's account. Record the route from public statement to authenticated evidence. The unresolved variable is VIP-specific limits, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For account capacity, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how number and type of subaccounts changes the entry, exit, monitoring, or fallback decision, and make the operator match the operating structure. The remaining uncertainty—VIP-specific limits—belongs in the dated scorecard. That produces a job-specific preference instead of a permanent winner.

2. Compare p&l isolation on the same job

For p&l isolation, that job concerns separate accounting by strategy. Build two evidence rows from the same timestamp, then verify exports and statements.

The unresolved variable is cross-margin linkage, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For p&l isolation, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how separate accounting by strategy changes the entry, exit, monitoring, or fallback decision, and make the operator verify exports and statements. The remaining uncertainty—cross-margin linkage—belongs in the dated scorecard.

3. Compare external deposits on the same job

For external deposits, that job concerns where blockchain deposits arrive. Build two evidence rows from the same timestamp, then use the documented account path.

The unresolved variable is asset-specific behavior, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For external deposits, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how where blockchain deposits arrive changes the entry, exit, monitoring, or fallback decision, and make the operator use the documented account path. The remaining uncertainty—asset-specific behavior—belongs in the dated scorecard.

4. Compare external withdrawals on the same job

For external withdrawals, that job concerns which account can send outward. Build two evidence rows from the same timestamp, then keep withdrawal authority narrow.

The unresolved variable is regional controls, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For external withdrawals, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how which account can send outward changes the entry, exit, monitoring, or fallback decision, and make the operator keep withdrawal authority narrow. The remaining uncertainty—regional controls—belongs in the dated scorecard.

5. Compare internal transfers on the same job

For internal transfers, that job concerns main-to-sub and sub-to-main movement. Build two evidence rows from the same timestamp, then map every allowed direction.

The unresolved variable is processing restrictions, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For internal transfers, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how main-to-sub and sub-to-main movement changes the entry, exit, monitoring, or fallback decision, and make the operator map every allowed direction. The remaining uncertainty—processing restrictions—belongs in the dated scorecard.

6. Compare api ownership on the same job

For api ownership, that job concerns key belongs to the selected account. Build two evidence rows from the same timestamp, then label and inventory each key.

The unresolved variable is operator confusion, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For api ownership, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how key belongs to the selected account changes the entry, exit, monitoring, or fallback decision, and make the operator label and inventory each key. The remaining uncertainty—operator confusion—belongs in the dated scorecard.

7. Compare permissions on the same job

For permissions, that job concerns read, trade and withdrawal scope. Build two evidence rows from the same timestamp, then grant least privilege.

The unresolved variable is future permission changes, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For permissions, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how read, trade and withdrawal scope changes the entry, exit, monitoring, or fallback decision, and make the operator grant least privilege. The remaining uncertainty—future permission changes—belongs in the dated scorecard.

8. Compare ip binding on the same job

For ip binding, that job concerns trusted network restriction. Build two evidence rows from the same timestamp, then bind stable egress addresses.

The unresolved variable is cloud failover addresses, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For ip binding, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how trusted network restriction changes the entry, exit, monitoring, or fallback decision, and make the operator bind stable egress addresses. The remaining uncertainty—cloud failover addresses—belongs in the dated scorecard.

9. Compare login and recovery on the same job

For login and recovery, that job concerns account switching and security controls. Build two evidence rows from the same timestamp, then test recovery without secrets.

The unresolved variable is device loss, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For login and recovery, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how account switching and security controls changes the entry, exit, monitoring, or fallback decision, and make the operator test recovery without secrets. The remaining uncertainty—device loss—belongs in the dated scorecard.

10. Compare audit trail on the same job

For audit trail, that job concerns orders, transfers and key usage. Build two evidence rows from the same timestamp, then retain redacted evidence.

The unresolved variable is history retention, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For audit trail, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how orders, transfers and key usage changes the entry, exit, monitoring, or fallback decision, and make the operator retain redacted evidence. The remaining uncertainty—history retention—belongs in the dated scorecard.

Decision scenarios

Scenario 1: when account capacity becomes decisive

Consider a reader whose main constraint is number and type of subaccounts. The correct response is not to infer a universal platform or product winner. It is to match the operating structure, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when p&l isolation becomes decisive

Consider a reader whose main constraint is separate accounting by strategy. It is to verify exports and statements, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when external deposits becomes decisive

Consider a reader whose main constraint is where blockchain deposits arrive. It is to use the documented account path, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when external withdrawals becomes decisive

Consider a reader whose main constraint is which account can send outward. It is to keep withdrawal authority narrow, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when internal transfers becomes decisive

Consider a reader whose main constraint is main-to-sub and sub-to-main movement. It is to map every allowed direction, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when api ownership becomes decisive

Consider a reader whose main constraint is key belongs to the selected account. It is to label and inventory each key, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Bybit Standard Subaccount FAQ
• Bybit API Key Guide
• OKX Subaccounts and API Connections FAQ
• OKX API Guide

Product availability, fees, controls, and legal terms can vary by entity, region, account tier, and time.