Compliance and IP Documentation

The following information serves as a quick reference to information relative to the Compliance and IP Documentation requirements. As such, the following points have been listed as an overview of FAQs:

• Wallet & Vault Implementation
• Wallets and Vaults are used interchangeably, while more precisely, Wallets (of crypto currencies) are contained within individual Vaults.
• More information on the implementation can be found under Vault & Self-Custody Module.
• Source code and documentation detailing the Hybrid-Vaults, Margin Wallets, and Rotational Wallets
• Source code repositories are segmented on a per-module/service level and stored in Atlassian Bitbucket in a protected/permissioned repo to which only a limited selection of specialists have access to. Repositories can be cloned to other secure environments upon request.
• Wallet functionalities are referenced in the following chapters:
• Hybrid-Vaults in Detail
• Margin Wallets in Detail
• Rotational Wallets in Detail
• Encryption procedures (RSA + Quantum Entropy), user flows, and any relevant onboarding guides
• Hybrid/Perpetual Chain Details
• Any node or chain software (if separate from standard blockchain nodes)
• Consensus mechanism documentation and configuration files, if applicable
• Distributed Storage (IPFS/Quantum Storage)
• Code for chunking, encrypting, and distributing data
• Disaster-recovery guidelines and backup procedures
• UI & Branding Materials
• Any front-end code, wireframes, and style or brand guidelines
• White-label customization steps or documentation
• TradingView Integration
• Any relevant code snippets, widgets, or library references
• Configuration steps for real-time data feeds or charting
• API Documentation and complete endpoint specs, including authentication flows and sample requests/responses
• The full API Documentation can be found located at https://docs.hybrid-chain.com, with a customized version (branded and business-case oriented) under https://docs.perpetuals.com.
• All endpoints are documented with request and response examples.
• Postman or OpenAPI files for easier integration
• The API Documentation is generated via Postman, an extract of the published API Endpoint documentation, including sample request and response payloads can be extracted upon request.
• Kraken (or Other Exchange) Integration
• Connector scripts or microservices for handling trades, deposits, and withdrawals
• Any security procedures or credential-handling instructions