Account Model

Starbase has a slightly different market model from Deribit. Deribit has a system with main-accounts and sub-accounts. For order entry and drop copy, there is no difference between main-accounts and sub-accounts. Logical grouping of access scopes should be done on a business level. There are, however, two common exceptions: usage of a Prime Broker or a trading firm with silo-ed pods. For this reason, we are introducing two new concepts:

Concept	Description	Mapping to Deribit
Portfolio	Container for positions, funds, and balances across all currencies	1:1 with account (main- or sub-account)
Member	Group of portfolios representing a trading participant	Can span multiple subaccounts under one main account

See the table below for the Member/Portfolio setup for the three major account types.

Use Case	Description
Directly onboarded client	These clients will be set up with one member. All new and existing portfolios/sub-accounts will immediately fall under this Member.
Prime Broker clients	Clients of Prime Brokers can request their Prime Broker to set up their subaccounts as a single Member. This ensures that clients of a Prime Broker can trade completely independently of other clients of the same Prime Broker. Any new portfolios/sub-accounts will need to be added manually and by request of the Prime Broker.
Pod-based trading firms	Trading firms with multiple trading pods that act independently can request each pod to be set up as a Member. This allows pods to trade completely independently from other pods. Any new portfolio/sub-account will not immediately be part of a Member grouping.

Multi-member setups will not be allocated any higher limits than single-member setups, unless there is a good reason. An example of a good reason is a Prime Broker with two distinct Market Makers as end clients.