5. Hybrid-Platform Architecture
On a system’s level, the Hybrid-Chain Platform is constructed using multiple core-components that allow for optimal redundancy, resiliency, security, and performance.
These modules are listed as follows (from an outside to inbound view):
The Hybrid-Chain Core system consists of interconnecting multiple peripheral systems to enable its core features.
It acts as a master gateway that forwards and redirects requests to the required resources or generates them accordingly.
Allows for external connections to be made in order to request resources. These resources can be web-based (accessible via browser), or via API commands (for machine-to-machine interfacing).
A multi-processing front-end service handles these requests in a redundant and fail-over safe manner.
The Front-End and API System connect to the Hybrid-Chain Core to provide information about wallet balances, profile data, etc. and allow for execution of trades, transactions, etc. to be requested and ordered by users (via the browser) and machines (via API endpoints).
Other functionality is also accessed via the Front-end System (such as Data Streaming services, Quantum Entropy, Payment Gateway Functionality, NFT Tokenization Functions, and CRM/User Management related activities).
The Chain Indexer is a stand-alone service that connects to multiple block-chain nodes and scans their individual transactions and blocks for events that are relevant to the wallets and data vaults in the Hybrid-Chain Core System. Deposits and other information is automatically picked up by the Indexer by querying blocks in real-time, decoding and matching them against known public keys within the infrastructure.
Notifications are made in real-time, informing the Core system of a new balance change event (for instance).
Full natively run blockchain nodes are an integral part of the Hybrid-Chain system. For performance reasons, full nodes are run close to or on the same infrastructure premise which allow the Chain Indexer and other components to interact with the blockchain’s native functionality (transaction monitoring, generation, broadcasting, etc.). These nodes must be synchronized and fully made available on high-performance hardware and redundant storage infrastructures.
Currently, Bitcoin, Bitcoin Cash, Litecoin, Ethereum and others are supported natively. Tron, Solana, Polygon, and others are in the integration pipeline.
This environment connects to the Block-Chain nodes that are connected to the open internet in order to manage deposits and generate transactions (generation is not equal to signing). Broadcasting of transactions after being signed in the Cold-Wallet Environment takes place on the warm side of the infrastructure.
This environment is isolated from any on-line resource, meaning no internet connection or third-party system can access this closed-off and locked cold-environment. It hosts parts of RSA asset and vault keys (which can only be decrypted by the user’s Master Password, which is set at Vault Generation in the early on-boarding process).
Generated Transaction requests are signed in this environment, with the produced signature on the transaction gets forwarded back to the warm environment where the transaction gets broadcasted, effectively generating a valid transaction on the corresponding blockchain. No synchronization systems are needed for this signature process.
The Distributed Storage solution is connected to the Hybrid-Chain Core and allows for Object and Key-Value based data to be stored in a distributed fashion.
Leveraging the Warm/Cold Vault technology paradigm, files are uploaded (encrypted before upload), sharded and distributed via individual IPFS nodes.
These Nodes are co-located in various regions across the world to provide optimal redundancy and delivery performance. Using the same decryption mechanism as the Wallet system does – files can be downloaded or shared across various web-frameworks after user’s leverage their Master-Password to decrypt or re-delegate permissions to the receiver.
These nodes are integral to allowing the closed-user group of dedicated IPFS Clusters to synchronize uploaded and secured file-based assets of clients. They automatically distribute and pin important files while regulating their resource allocation and availability.
They communicate directly with the Hybrid-Chain Core system to synchronize and update files that need to be kept in storage. Download/Data Distribution takes place via the IPFS network, effectively minimizing data-transfer overhead and inefficiencies.
In order to secure keys and data against current and future attack vectors of weak key generation processes (current standard), the Hybrid-Chain system enriches its entropy during the key-generation ceremony (RSA Keys) with Quantum-Resilient entropy.
A proprietary mix of specialized, NIST certified hardware and specialized redistribution software allows for globally co-located Hybrid-Chain datasystems to source entropy in real-time and without latency.
These Quantum Entropy Nodes can be operated on-premises or in the cloud (with Entropy Caching), providing a great layer of redundancy and flexibility to deployments and consumers.
Last updated
Was this helpful?