On the account settings page the general settings for the account can be viewed, and some can be edited.
The profile details will show:
-
User ID
-
Which entity of Deribit the account is onboarded with
-
Account creation date
-
Username (which can be edited here)
-
Email
It is crucial to use a unique password. If the same password is used for multiple platforms, only one of them must be hacked for the hacker to easily gain access to other ones as well. The same applies to email addresses. It is also advised to use an email address that contains the least amount of personal information possible, so hackers have more difficulties guessing possible variations for other platforms. On top of this, ensure you have two factor authentication (2FA) set up on your email account as well.
-
Press the "Forgot your password?" button on login page or click the button on the account settings page.
-
Enter the account email if the request is made from the login page. This is not required on the account settings page.
-
If the email is known by our system, an email with a confirmation link will be sent.
-
Click link in the email to reset the password. A popup will open on www.deribit.com.
-
Approve with security key with scope "Account".
Here you can choose which email notifications you would like to receive.
|
Setting |
Details |
|---|---|
|
Account parameters changed |
Notify when account parameters have been changed by Deribit (e.g. rate limits, PM configuration). |
|
Margin call notifications |
Notify when the margin balance of your account has fallen below the initial margin requirement. On the platform this will be shown as the initial margin requirements breaching 100% of the margin balance. Note that there is a limit to how often these emails will be sent. They should be considered a helpful reminder, but should not be relied upon for risk management. |
|
Liquidation notifications |
Notify when Deribit starts to incrementally reduce your positions in an attempt to keep the maintenance margin requirements below the margin balance of your account. Note that there is a limit to how often these emails will be sent. They should be considered as a helpful reminder, but should not be relied upon for risk management. |
|
Rebalance notifications |
Notify cross collateral accounts when negative equity limit is breached. Note that there is a limit to how often these emails will be sent. They should be considered a helpful reminder, but should not be relied upon for risk management. |
|
Login notifications (always enabled) |
Notify when someone logs into your account. The login notifications are only sent for email logins. These are not sent for API authentications. A notification will be sent for both successful and unsuccessful login attempts. Both will have the time in UTC and the public IP address of the machine. This authentication email has an emergency lock link, which can be used by the receiver to lock the account in the event that a login is thought to be unauthorised. |
|
Email language |
Change the language for the emails. |
Join Newsletter and Exchange Notifications
There is also a link to a page where users can subscribe to additional email newsletters. These newsletter contain information such as exchange updates, and education content.
Note
These settings can only be set on the main account and will apply on all subaccounts as well. A subaccount can not be excluded from these settings
The self matching settings define how orders behave in cases where they would cross with another order from the same client, at the individual account level or between all subaccounts. Self-matching occurs when an order to buy an instrument would match with an order to sell that same instrument on the same account or subaccount. The order that was placed first is the primary order (a resting maker or passive order), and the order that was placed later is the secondary order (a taker or aggressive order). It is possible for the secondary order to be placed by a conditional order initiated prior to the primary order.
|
Setting |
Details |
|---|---|
|
Self Match prevention |
Enabled (Active) Self matching is prevented by cancelling the primary order. With the 'Self-Match Prevention' enabled, the primary order will be automatically cancelled if crossed by a secondary order. The secondary order will be placed/executed in the orderbook. This settings applies on orders within one account, either on the main or any individual subaccount, but not across all accounts. |
|
Disabled (Inactive) Self matching is prevented by rejecting the secondary order. With the 'Self-Match Prevention' disabled the primary order will be remain in orderbook, and the secondary order will be rejected. This settings applies on orders within one account, either on the main or any individual subaccount, but not across all accounts. |
|
|
Account level Self Match prevention |
Enabled (Active) Self matching is prevented across all subaccounts. With the 'Account level Self Match prevention' enabled, the check is performed on the main and all subaccounts combined. Depending on the setting of 'Self-Match Prevention', Deribit will determine which order to cancel or reject. |
|
Disabled (Inactive) Self matching is possible between different subaccounts. With the 'Account level Self Match prevention' disabled, the check will not be performed on the main and all subaccounts combined, only on each main or subaccount separately. |
|
|
Block RFQ Self-Match Prevention |
Enabled (Active) When Block RFQ Self-Match Prevention is enabled, your account’s Identity is excluded from the list of available makers. This prevents your Block RFQ orders from being matched against your own accounts (i.e., those sharing the same Identity). Even if you use ‘Select all’ in the maker list, your own Identity will be automatically excluded. Similarly, if you target your Parent Identity, any accounts under it that share your Identity will also be excluded. |
|
Disabled (Inactive) When Block RFQ Self-Match Prevention is disabled, your account’s Identity can be included in the maker list. This means your Block RFQ orders may potentially be matched against your own accounts (those with the same Identity). Using ‘Select all’ will include your own Identity, and targeting your Parent Identity will not exclude related accounts. |
Settings to arrange the sessions security.
When enabled, any attempt to switch to a new IP address during an already established session would automatically terminate that session. When this setting is changed, the new setting is applied after a fresh login.
A default session on the user interface will expire after one week (168 hours) of inactivity on the account. Any action performed on the user interface is considered an activity. Prepared trades or conditional orders, API usage (all scopes other than login on user interface) or automated emails are not considered as activity.
If 'Safe Session Duration' is enabled the session limit is shortened to 1 hour.
If a session has expired, the account is logged out and will have to login again to perform any new actions.
In the access log, events regarding logins and security changes are logged.
The specific security key used for an action will also be shown.
-
Security keys using an authenticator will be shown as tfa (2FA)
-
Security keys using a hardware key or passkey will be shown as u2f.
|
Item |
Description |
|---|---|
|
Date |
Date and time shown in DD/MM/YYY HH:MM:ss in UTC |
|
IP |
IP used in the event |
|
Location |
Approximate location based on IP |
|
Log |
Shows the events. The most common events are detailed in the remainder of this table. |
|
Login failed |
Unsuccessful login |
|
Login success |
Successful login |
|
Authorisation of login with security key 'name' |
Security key used to confirm login |
|
Changed password |
Password was changed |
|
Authorisation of list API keys with security key name |
Security key used to open the list of API keys on the account |
|
New API key 'ClientID' |
New API key created with the specific client ID |
|
Authorization of create api key with security key "name". |
Security key used to approve the creation of an API key |
|
Changed scope "API key name" |
Specifying the clientID of the API key on which the scope changed |
|
Changed whitelist "API key name" |
Specifying the clientID of the API key on which the whitelist changed |
|
Authorization of edit api key with security key "name". |
Security key used to edit the API key |
|
removed API key "API key name" |
Specifying the clientID of the API key which is removed |
|
Authorization of remove api key with security key "name". |
Security key used to remove the API key |
|
Authorization of authorize app with security key 'name' |
Security key used to add a new app |
|
Authorization of set app key state with security key "name" |
Security key used to change the state of a current app |
|
Authorization of set email for subaccount |
Security key used to set the email for a subaccount |
|
Authorization of set password for subaccount |
Security key used to set the password for a subaccount |
|
Authorization of toggle notifications from subaccount with security key "name" |
Security key used to toggle email notifications on a subaccount |
|
Authorization of add to address book with security key "name" |
Security key used to add a new withdrawal address |
|
Authorization of remove from address book with security key "name" |
Security key used to remove an existing withdrawal address. |
|
Security keys have been removed |
All you security keys are removed. All keys will be removed clicking the confirmation link provided by Deribit in a reset procedure . |
|
Security key (name) removed and unassigned from "scopes" |
A specific key has been removed, this must be approved with a security key with account scope |
|
Authorization of deactivate security with security key "name". |
Security key used to deactivate another security key |
|
Activated security key name (assignments: scopes) |
New security key activated with scopes assigned |
|
Authorization of activate security with security key "name". |
Security key used to activate another security key |
|
Security key "name" assigned to "scope" |
Security key has a new or additional scope assigned |
|
Security key 'name" removed from scope |
Security key has a scope removed |
|
Authorization of change security key assignment with key |
Security key used to perform changes on other security keys. |
If fee discounts are applied to to the account the applied rates will be shown for each currency independently (select the currency in the header)
|
Instrument Type |
Maker fee |
Taker fee |
Blockfee |
|---|---|---|---|
|
(Asset) Future |
Shown in BPS. 1 BPS = 0.01% Negative value means receiving a rebate |
Shown in BPS 1 BPS = 0.01% |
Shown as a percentage of the regular fee. For example, 80% means the fee will be 80% of regular fees. So if the regular fee for an instrument is 0.03%, the fee paid would be 0.024% instead. |
|
(Asset) Perpetual |
Shown in BPS 1 BPS = 0.01% Negative value means receiving a rebate |
Shown in BPS 1 BPS = 0.01% |
Shown as a percentage of the regular fee. For example, 80% means the fee will be 80% of regular fees. So if the regular fee for an instrument is 0.03%, the fee paid would be 0.024% instead. |
|
(Asset) Option |
Shown as a percentage of the regular fee. For example, 80% means the fee will be 80% of regular fees. So if the regular fee for an instrument is 0.03%, the fee paid would be 0.024% instead. |
Shown as a percentage of the regular fee. For example, 80% means the fee will be 80% of regular fees. So if the regular fee for an instrument is 0.03%, the fee paid would be 0.024% instead. |
Shown as a percentage of the regular fee. For example, 80% means the fee will be 80% of regular fees. So if the regular fee for an instrument is 0.03%, the fee paid would be 0.024% instead. |