10. Compliance & IP FAQ

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

1. Wallet & Vault Implementation:

a. Wallets and Vaults are used interchangeably, while more precisely, Wallets (of crypto currencies) are contained within individual Vaults.

b. More information on the implementation can be found under Vault & Self-Custody Module.

2. Source code and documentation detailing the Hybrid-Vaults, Margin Wallets, and Rotational Wallets:

a. 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.

b. Wallet functionalities are referenced in the following chapters:

i. Hybrid-Vaults in Detail

ii. Margin Wallets in Detail

iii. Rotational Wallets in Detail

3. Encryption procedures (RSA + Quantum Entropy), user flows, and any relevant onboarding guides:

a. General Entropy Injection is referenced in the Chapter Next-Generation Wallets and Vaults.

b. More information about the custodial aspect (and therefore the onboarding guides implicitly) are found in the Chapter Hybrid-Chain Access Control Plane

4. Hybrid/Perpetual Chain Details:

a. Details are found across this Whitepaper document, with Chapter Platform Architecture describing the overall architecture and layout of the infrastructure.

5. Any node or chain software (if separate from standard blockchain nodes):

a. There are no third-party tools, software, or programs used for the Hybrid-Chain system.

b. Actual wallets are standard and open-source project related wallets (BTC, ETH, etc.)

6. Consensus mechanism documentation and configuration files, if applicable:

a. Consensus is established via the hashes of the underlying first layer transactions (where proof of work, or proof of stake, etc.) has already established valid transactions.

b. Signatures for internal Layer-2 transactions on Hybrid-Chain are based on the most robust and proven blockchain to date: Bitcoin.

7. Distributed Storage (IPFS/Quantum Storage):

a. Distributed Storage is used to securely store the most private and important data in a non-modifiable (immutable) way, which protects data integrity and makes ransomware attacks useless.

b. Besides that, the encryption framework is strengthened with Quantum Entropy on a per-file basis.

c. More information can be found in the Chapter Native Quantum Resiliency

8. Code for chunking, encrypting, and distributing data:

a. This information is provided in Bullet Point 2 of this Chapter.,

9. Disaster-recovery guidelines and backup procedures:

a. As described throughout this document.

10. UI & Branding Materials:

a. Banding Materials have not been fully established yet.

11. Any front-end code, wireframes, and style or brand guidelines:

a. This is not applicable – The Hybrid-Chain Eco-System does not come with an UI or Front-end.

b. A System and Service Architecture Map is available.

12. White-label customization steps or documentation:

a. See point 11.

13. TradingView Integration:

a. Trading View is integrated in the Front-end systems that connect to the Hybrid-Chain infrastructure.

b. There is no direct integration of Trading View within Hybrid-Chain, as there is no UI.

14. Any relevant code snippets, widgets, or library references:

a. See Section 2 of this Chapter.

15. Configuration steps for real-time data feeds or charting:

a. See Section 11 and 13 of this Chapter.

16. API Documentation and complete endpoint specs, including authentication flows and sample requests/responses:

a. 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.

b. All endpoints are documented with request and response examples.

17. Postman or OpenAPI files for easier integration:

a. 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.

18. Kraken (or Other Exchange) Integration:

a. Liquidity Provider Integrations have been custom-built for Perpetuals/PMX and are property of Perpetuals/PMX.

19. Connector scripts or microservices for handling trades, deposits, and withdrawals:

a. See section 2 and 18 of this Chapter. Liquidity Provider Integrations (and the code therefore) are property of Perpetuals/PMX

b. Additional code can be made available for code-reviews where required and applicable.

20. Any security procedures or credential-handling instructions:

a. As documented in the API Documentation (See Section 16 of this Chapter)