The immutable auditable record
Posted: Tue May 20, 2025 7:52 am
Funding Rates/Index Prices: Specific to derivatives, real-time rates and index prices impacting perpetual contracts.
2. User and Account Data: This highly sensitive category forms the core of user identities and their financial relationships with Bitget:
* User Profiles: Personal identifiable information (PII) such as names, addresses, contact information, and linked financial accounts.
* KYC/AML Documentation: Scanned government IDs, proof of address, and other verification documents required for regulatory compliance.
* Authentication Data: Hashed passwords, 2FA settings, API key configurations, and session management tokens.
* Wallet Balances: Precise records of user holdings across all nursing homes email list supported cryptocurrencies and fiat currencies, including segregation by spot, futures, margin, and funding wallets.
3. Transactional and Historical Data: of all financial and trading movements:
* Deposits and Withdrawals: Detailed logs of all fund movements into and out of user accounts.
* Order History: A comprehensive record of every order placed, including its full lifecycle (pending, partially filled, filled, canceled, expired).
* Trade History: An immutable record of every executed trade, linked to specific users and timestamps.
* Copy Trading Records: Detailed logs of copy trading relationships, copied orders, and performance data.
4. Operational and System Data: Internal data for platform health, security, and auditing:
* System Logs: Records of server activity, application events, and error messages for troubleshooting and performance monitoring.
* Security Logs: Detailed audit trails of access attempts, suspicious activities, and security alerts.
* Configuration Data: Settings for trading pairs, fee structures, system parameters, and new product definitions.
Effectively managing these diverse datasets, ensuring their accuracy, speed, and unwavering security, is the continuous, monumental task undertaken by the "Bitget database" infrastructure.
Page 3: Architectural Choices: Relational, NoSQL
2. User and Account Data: This highly sensitive category forms the core of user identities and their financial relationships with Bitget:
* User Profiles: Personal identifiable information (PII) such as names, addresses, contact information, and linked financial accounts.
* KYC/AML Documentation: Scanned government IDs, proof of address, and other verification documents required for regulatory compliance.
* Authentication Data: Hashed passwords, 2FA settings, API key configurations, and session management tokens.
* Wallet Balances: Precise records of user holdings across all nursing homes email list supported cryptocurrencies and fiat currencies, including segregation by spot, futures, margin, and funding wallets.
3. Transactional and Historical Data: of all financial and trading movements:
* Deposits and Withdrawals: Detailed logs of all fund movements into and out of user accounts.
* Order History: A comprehensive record of every order placed, including its full lifecycle (pending, partially filled, filled, canceled, expired).
* Trade History: An immutable record of every executed trade, linked to specific users and timestamps.
* Copy Trading Records: Detailed logs of copy trading relationships, copied orders, and performance data.
4. Operational and System Data: Internal data for platform health, security, and auditing:
* System Logs: Records of server activity, application events, and error messages for troubleshooting and performance monitoring.
* Security Logs: Detailed audit trails of access attempts, suspicious activities, and security alerts.
* Configuration Data: Settings for trading pairs, fee structures, system parameters, and new product definitions.
Effectively managing these diverse datasets, ensuring their accuracy, speed, and unwavering security, is the continuous, monumental task undertaken by the "Bitget database" infrastructure.
Page 3: Architectural Choices: Relational, NoSQL