#### 1. General Information
Project Name: Tracking transactions made on the Deribit cryptocurrency exchange
Project Goal: To create a web application that allows traders to keep track of their trades, analyze their trading activities, and improve their trading strategy.
Target Audience: Individual traders engaged in cryptocurrency, futures, and options trading on the Deribit exchange.
#### 2. Functional Requirements
##### 2.1 Registration and Authorization, Core Functionality
Ability to register via email/password.
Implementation of two-factor authentication (at the user's discretion).
Linking the exchange API.
Adding, editing, deleting global "hedges" - name, size, date, cost, phase, status (in the money or percentage of profit/loss), relevance (in progress/completed)
Adding, editing, deleting user strategies.
Adding financial results of the "hedge" when it transitions from "In Progress" to "Completed". These financial results represent profit/loss along with trading results on the exchange.
##### 2.2 Trade Management
Receiving trade data via API:
Date and time of opening/closing.
Instrument (currency, option-date, strike, etc.).
Type of trade (buy/sell).
Entry and exit price.
Trade volume.
Commissions.
Ability to add notes (related to the global "hedge") to each trade.
Ability to batch relate trades to "hedges", where the list of trades is related to the list of "hedges" in percentage terms (Example: List of trades Y1, Y2... YN distributed among hedges A, B, and C in proportions Ax%, Bx%, Cx%).
##### 2.3 Analytics
Automatic calculation of key metrics:
Total P&L (profit and loss) for the account as a whole and for individual "hedges" and strategies (see below), as well as by intervals (year, month, week, day, specific dates).
Filters and sorting:
By trade type, instrument, date, "hedge", relevance (In Progress / Completed) and other parameters.
##### 2.4 Strategy Management
Ability to add user strategies:
Strategy name.
Description.
Linking trades to the selected strategy and/or "hedge".
Analysis of the effectiveness of each strategy in the "Analytics" section.
##### 2.5 Reminders and Notifications
Reminders about important events (for example, about the expiration of an option).
#### 3. Non-Functional Requirements
Interface: Must be intuitive, with an emphasis on minimalism and performance.
Platform Support: Web version, adapted for desktops.
Performance: Page load time - no more than 2 seconds under standard load.
Security:
Encryption of user data.
Regular backups of the database in both automatic and manual modes.
Protection against XSS and SQL injections.
#### 4. Technical Implementation
4.1 Technology Stack
Frontend: ???
Backend: ???
Database: ???
Hosting: client hosting -- functionality to be agreed upon
Integrations: API for loading data from the Deribit exchange.
#### 5. Development Stages
Analysis and Design:
Analysis/study of the Deribit API system.
Creating interface prototypes (Wireframes).
Developing MVP (minimum viable product):
Registration/authorization.
Reading and displaying trades.
Adding, editing, deleting global "hedges".
Adding, editing, deleting user strategies.
Expanding functionality:
Analytics.
Notifications.
Administration - user management and Backup.
Testing and debugging.
Release and support.
#### 6. Interface Examples
Main Page:
Trades - List of new trades that are not related to "hedges"
Overview - List of active "hedges" and metrics and performance graph.
Analytics: Reports and filters.
#### 7. Deadlines
Analysis and Design: 2 weeks.
Development of MVP: 6 weeks.
Expanding functionality: 8 weeks.
Testing and debugging: 2 weeks.
Total: ~4 months.
#### 8. Budget
Specify the approximate budget based on the scope of work and technologies used.
#### 9. Notes
Improvements and additional requirements are discussed separately.
#### 10. Further Support
In the future, it will be necessary to refine and maintain the project.
