System and method for blockchain interaction management

Abstract

The present invention discloses a system (100) and a method (400) for blockchain interaction management. The system (100) includes an enterprise portal (102) for managing user registration, service subscriptions, and billing, generating unique API keys for secure authentication; an API service layer (104) for enabling external system interactions with the blockchain; a blockchain layer (106) providing a Proof of Authority, PoA consensus for transaction validation, including nodes, smart contracts, and runtime pallets; and a communication framework (108) ensuring secure, authenticated transaction processing. The API service layer (104) includes modules for wallet, token, audit, and certificate management, authenticates API requests, formats them into blockchain transactions, and securely transmits them to the blockchain layer. Further, the method (400) comprises registering users and managing services (402), processing and executing incoming requests via API service layer (404) and blockchain layer (406), respectively, and transmitting data securely using a communication framework (408).

Description

[0001] SYSTEM AND METHOD FOR BLOCKCHAIN INTERACTION MANAGEMENT

[0002] FIELD OF INVENTION

[0003] The present invention relates to a system and a method for blockchain interaction management. In particular, the present invention relates to a system and a method for blockchain interaction management, that incorporates an API service layer and an enterprise portal, configured to facilitate integration between the blockchain layer and external systems.

[0004] BACKGROUND ART

[0005] Blockchain technology has revolutionized the way data and transactions are recorded, secured, and verified in a decentralized manner. Its applications have expanded beyond cryptocurrencies to include sectors such as finance, supply chain, healthcare, and governance. Innovations like Ethereum have enabled the development of smart contracts, allowing decentralized applications to execute programmable agreements directly on the blockchain. Additionally, advancements such as layer-two solutions like Polygon address issues of scalability and high transaction costs, further broadening the potential use cases of blockchain technology.

[0006] Despite these advancements, integrating blockchain into enterprise systems remains a significant challenge. Conventional blockchain platforms often require specialized knowledge of complex programming languages and protocols, making them inaccessible to businesses without dedicated technical expertise. Furthermore, while platforms like Ethereum and Polygon provide enhanced functionalities, the lack of standardized and user-friendly tools for onboarding enterprises onto blockchain networks limits the widespread adoption of this transformative technology.

[0007] One of the key challenges in current blockchain technology is its high complexity, particularly in onboarding companies and industries. Businesses face difficulties in setting up, managing, and interacting with blockchain networks due to the fragmented nature of available tools and the steep learning curve associated with blockchain-specific programming. Additionally, existing solutions lack seamless integration capabilities with external systems, hindering scalability, operational efficiency, and adoption by enterprises unfamiliar with blockchain infrastructure. These issues highlight the need for a more streamlined and accessible approach to blockchain interaction management.

[0008] Numerous systems for blockchain integration in diverse technology fields have been developed.One example of such system is disclosed in CN Patent Publication No. CN 116166280 A (hereinafter referred to as CN 280 Publication) entitled “Block chain open platform and issuing method of block chain application” having a filing date of January 17, 2019, Applicant: Hangzhou Qulian Technology Co Ltd. The CN 280 Publication discloses a blockchain open platform and a method for deploying blockchain applications, comprising a base layer for interfacing with various cloud platforms, a middle layer providing pluggable multi-blockchain service support, and a blockchain base layer offering generic blockchain services. The CN 280 Publication further discloses additional layers for one-click blockchain deployment, visual blockchain management, system services for diverse blockchain applications, and a userfacing application layer enabling access to blockchain services and the issuance of applications via the open platform.

[0009] Another example of such system is disclosed in CN Patent Publication No. CN 111262872 B (hereinafter referred to as CN 872 B Publication) entitled “Enterprise block chain service platform” having a filing date of January 20, 2020, Applicant: Brilliance Technology Co ltd. The CN 872 B Publication discloses an enterprise blockchain service platform comprising a platform management module for managing user roles, network dashboards, and platform monitoring; a blockchain management module for overseeing blockchain networks, channels, smart contracts, event messages, and agents. The CN 872 B Publication further discloses a basic resource management module for managing host resources, storage, and network environments; and a bottom support module for ensuring data security, cryptography, crosschain interaction, and pluggable consensus mechanisms.

[0010] A further example of such system is disclosed in CN Patent Publication No. CN 109743328 A (hereinafter referred to as CN 328 Publication) entitled “A kind of open cloud service platform of block chain”, having a filing date of January 17, 2019, Applicant: Hangzhou Qulian Technology Co Ltd. The CN 328 Publication discloses an open cloud service platform of block chain, that includes system of account management, certificate management, the management of block chain network, node administration, application management, O&M monitoring management, tool integration management. The CN 328 Publication further discloses that the disclosed system provides one-stop block chain technological service, visual resource layout dispatch service, visual monitoring management and operation management service by block chain open exploitation and operation maintenance personnel of the cloud platform towards enterprise-level.

[0011] As outlined above, various systems for blockchain integration have been developed. However, none of the existing systems and methods, disclose such a technology, that at least overcomes the aforementioned drawbacks.In light of the foregoing discussion, there exists a need to provide an improved blockchain interaction management system that at least overcome the above-mentioned drawbacks.SUMMARY OF INVENTION

[0012] The present invention relates to a system and a method for blockchain interaction management. In particular, the present invention relates to a system and a method for blockchain interaction management, that incorporates an API service layer and an enterprise portal, configured to facilitate integration between the blockchain layer and external systems.

[0013] One aspect of the present invention provides a system (100) for blockchain interaction management, comprising an enterprise portal (102) including a user interface configured to manage user registrations, service subscriptions, and billings based on service usage; and generate unique API keys and API secret keys for secure authentication; an application programming interface, API service layer (104), operably coupled to the enterprise portal (102), for allowing external systems to interact with blockchain architecture; a blockchain layer (106) including the blockchain architecture, operably coupled to the API service layer (104), wherein the blockchain layer (106) is configured to provide a Proof of Authority, PoA consensus mechanism for validating and confirming transactions, wherein the blockchain layer comprises a network of nodes configured to store, validate, and process distributed blockchain transactions; and at least one smart contract configured to execute programmable agreements triggered by blockchain transactions; a plurality of pallets, each pallet is configured to manage customizable runtime modules for executing a plurality of blockchain operations; a communication framework (108), interconnecting the API service layer (104) and the blockchain layer (106), configured to ensure secure and authenticated processing of transactions by facilitating the transmission of formatted transactions from the API service layer to the blockchain layer and return of responses thereof to the external systems.

[0014] Another aspect of the present invention provides that the API service layer (104) is configured to authenticate API requests using the API keys and the API secret keys generated by the enterprise portal (102); format the API requests into at least one blockchain transaction; and sign and securely transmit the at least one blockchain transaction to the blockchain layer (106) for further processing.

[0015] Another aspect of the present invention provides that the API service layer (104) comprises a plurality of service modules coupled to the blockchain layer (106) for performing specific functionalities customized to requirements of the external system, the plurality of service modules comprise at least one wallet management module (202), configured to manage wallet-related operations and manage user authentication and identity verification; at least one token management module (204), configured to handle token issuance, token transfer, and functions associated thereof; at least one audit management module (206), configured tomaintain transaction logs and support compliance; and at least one certificate management module (208), configured to issue, store, and validate digital certificates.

[0016] Another aspect of the present invention provides that the blockchain layer (106) further comprises a core client component, wherein the core client is responsible for managing network activities; a runtime component, wherein the runtime component is responsible for processing transactions and managing state transitions within the blockchain layer (106).

[0017] Another aspect of the present invention provides that the core client component and the runtime component are configured to execute a plurality of associated functions which are supported by a set of libraries, the set of libraries include at least one of network service libraries, base libraries, and runtime development framework libraries.

[0018] Another aspect of the present invention provides that the network service libraries manage network function and interactions between the networks of nodes.

[0019] Another aspect of the present invention provides that the base libraries facilitate communications between service libraries and the runtime component.

[0020] Another aspect of the present invention provides that the runtime development framework libraries are responsible for creating runtime logic and encoding / decoding data.

[0021] Another aspect of the present invention provides a method (400) for managing blockchain interactions, comprising the steps of registering users and managing services using an enterprise portal (402), wherein registering users and managing services using an enterprise portal (402) comprises method steps of (500), the method steps (500) comprising: accepting user registrations and subscriptions for blockchain-related services via the enterprise portal (502); generating unique API keys and secret keys to securely authenticate user access (504); processing incoming requests from the users via an API service layer (404); executing blockchain operations related to the external requests via a blockchain layer (406), wherein executing blockchain operations related to the external requests via a blockchain layer (406) further comprises method steps of (600), the method steps (600) comprising validating and confirming transactions using a proof of authority, PoA consensus mechanism (602); processing transactions and broadcasting confirmed transactions across a network of nodes to ensure distributed ledger consistency (604); executing programmable agreements through smart contracts triggered by the transactions (606); and enhancing runtime adaptability using customizable runtime modules managed by a plurality of pallets in the blockchain layer to execute specific blockchain operations customized to requirements of the users (608); transmitting data securely using a communication framework by transmitting formattedtransactions between the API service layer and the blockchain layer, and ensuring secure return of transaction responses to the users (408).

[0022] Yet another aspect of the present invention provides that processing external requests via an API service layer (404) further comprise method steps of (700), the method steps (700) comprising authenticating the incoming API requests using the API keys and the API secret keys (702); formatting the requests into blockchain transactions for processing (704); and signing and securely transmitting the blockchain transactions to a blockchain layer (706).

[0023] The present invention consists of features and a combination of parts hereinafter fully described and illustrated in the accompanying drawings, it being understood that various changes in the details may be made without departing from the scope of the invention or sacrificing any of the advantages of the present invention.BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS

[0024] To further clarify various aspects of some embodiments of the present invention, a more particular description of the invention will be rendered by references to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail through the accompanying drawings in which:

[0025] Figure 1 illustrates a block diagram of a blockchain interaction management system (100), in accordance with an embodiment of the present invention;

[0026] Figure 2 illustrates a block diagram of an API service layer (104), in accordance with an embodiment of the present invention;

[0027] Figure 3 is a flowchart illustrating a method (300) for integrating external systems into a blockchain interaction management system, in accordance with an embodiment of the present invention;

[0028] Figure 4 is a flowchart illustrating a method (400) for blockchain interaction management, in accordance with an embodiment of the present invention;

[0029] Figure 5 is a flowchart illustrating a method (500) for registering users and managing services using an enterprise portal (404), in accordance with an embodiment of the present invention;

[0030] Figure 6 is a flowchart illustrating a method (600) for executing blockchain operations related to the external requests via a blockchain layer (406), in accordance with an embodiment of the present invention; and

[0031] Figure 7 is a flowchart illustrating a method (700) for processing external requests via an API service layer (404), in accordance with an embodiment of the present invention.DETAILED DESCRIPTION OF THE DRAWINGS

[0032] The present invention relates to a system and a method for blockchain interaction management. In particular, the present invention relates to a system and a method for blockchain interaction management, that incorporates an API service layer and an enterprise portal, configured to facilitate integration between the blockchain layer and external systems.

[0033] Hereinafter, this specification will describe the present invention according to the preferred embodiments. It is to be understood that limiting the description to the preferred embodiments of the invention is merely to facilitate discussion of the present invention and it is envisioned without departing from the scope of the appended claims.

[0034] The present invention discloses a blockchain interaction management system that includes multiple components configured to simplify and streamline enterprise integration with blockchain technology. The system comprises an enterprise portal, an API service layer, and a blockchain layer that interact seamlessly to enable secure, efficient, and scalable blockchain operations.

[0035] The present invention addresses significant challenges faced by industries when adopting blockchain, particularly the high technical complexity, need for specialized programming expertise, and rigid infrastructure requirements. Conventional blockchains require developers to learn platform-specific languages, often making integration cost-intensive and timeconsuming. Additionally, conventional systems fail to provide the flexibility required for enterprises to customize blockchain services to their specific operational needs.

[0036] The present invention addresses these challenges by providing an API-based service layer that allows enterprises to interact with blockchain functionalities using familiar tools, eliminating the need for extensive blockchain expertise and programming knowledge. Additionally, the enterprise portal simplifies subscription management, billing, and API key generation, enabling access to blockchain resources while optimizing operational costs.

[0037] The blockchain layer, built on a customizable open-source framework, employs a Proof of Authority, PoA consensus mechanism and includes runtime modules for smart contracts, token management, and other related operations. The disclosed system ensures seamless communication between the API service layer and the blockchain layer through a secure and authenticated communication framework. By utilizing modular architecture and advanced blockchain technology, the present invention provides a practical, cost-effective, and scalable solution for enterprises to adopt blockchain without requiring in-depth technical knowledge or substantial infrastructure investments.Throughout the present invention, the term “Proof-of-Authority, PoA consensus mechanism” refers to a network consensus protocol where only a limited number of pre-authorized and verified nodes are permitted to participate in transaction validation and block creation. These nodes are rigorously vetted and granted exclusive access to critical network resources, ensuring that only trusted participants perform consensus operations. This mechanism prioritizes security and efficiency, as authority and trustworthiness, rather than computational resources, are the determining factors in block validation.

[0038] Throughout the present invention, the term “public-permissioned network” refers to a hybrid blockchain model that combines elements of public accessibility with the controlled governance of permissioned systems. In this model, selective restrictions, enforced through authentication protocols, govern administrative, operational, and governance privileges. Depending on the use case, the API service layer can be customized to operate as a fully closed system or as a publicly accessible platform where authentication ensures that only predetermined users hold elevated privileges. This configuration balances openness with stringent security measures to mitigate risks and enhance network reliability.

[0039] The PoA consensus mechanism and the public-permissioned network characteristics are functionalities of the disclosed system (100). The API layer acts as the intermediary defining and enforcing these system-wide attributes, allowing external integrations to interact with the network under the established PoA and public-permissioned principles. This architecture ensures that the system adheres to these operational paradigms while streamlining access and functionality for external applications.

[0040] Reference is made to Figures 1, where there is illustrated a blockchain interaction management system (100), in accordance with an embodiment of the present invention.

[0041] The system (100) incorporates an enterprise portal that serves as a user-facing interface, enabling enterprises to manage essential operations such as user registration, service subscriptions, and billing based on usage. This portal also generates unique API keys and API secret keys, ensuring robust authentication for external systems interacting with the blockchain.

[0042] The API service layer (104), operably coupled to the enterprise portal, acts as a critical intermediary between external systems and the blockchain layer. This layer (104) is configured to authenticate incoming API requests using the unique keys generated by the enterprise portal, format these requests into blockchain-compatible transactions, digitally sign them, and transmit them securely to the blockchain layer for processing.The authenticated API requests are formatted into a blockchain transaction and securely transmitted to the blockchain layer for processing. The blockchain layer, which is configured to validate and confirm transactions through a Proof of Authority, PoA consensus mechanism, processes these transactions accordingly. Once the transaction is processed, the blockchain layer returns a response to the API service layer. The response is thereafter forwarded back to the external system, completing the interaction cycle and enabling the external system to access the desired blockchain services.

[0043] The blockchain layer (106), operably coupled to the API service layer (104), is built on a Proof of Authority, PoA consensus mechanism, ensuring efficient and energy-conscious transaction validation and confirmation. This layer (104) comprises a network of distributed nodes that store, validate, and process blockchain transactions. In an instance, the network of nodes are interconnected computers or servers that store the blockchain's data, validate transactions, and ensure the network's security. Each node has a copy of the entire blockchain and participates in the process of confirming and processing transactions, adhering to the PoA consensus mechanism.

[0044] The blockchain layer (106) further comprises at least one smart contract for executing programmable agreements triggered by blockchain transactions. In an instance, the at least one smart contract is self-executing contracts with conditions written into code. When certain conditions are met, which is triggered by blockchain transactions, the contract automatically executes the predefined actions, automated operations.

[0045] The blockchain layer (106) further comprises multiple customizable pallets that manage runtime modules for various blockchain operations. In a specific instance, the pallets are specialized, modular components that facilitate integration and interaction with existing systems. By configuring each pallet to be adaptable and customizable, the present invention allows seamless integration into blockchain network to manage specific functions like token handling, governance, or identity verification. This modular approach ensures that integrating with external applications is straightforward and flexible, as each pallet can be tailored to meet specific operational needs. This enables a more cohesive and effective way of connecting blockchain solutions with broader enterprise systems.

[0046] The system (100) further comprises a communication framework (108) that connects the API service layer (104) with the blockchain layer (106), ensuring the secure and authenticated processing of transactions. Said framework (108) facilitates the transmission of formatted transactions from the API service layer (104) to the blockchain layer (106) while returning responses from the blockchain to the external systems, ensuring a seamless flow of data andinteractions. By combining these components, the blockchain interaction management system overcomes the complexity of blockchain technology, enabling enterprises to adopt and integrate blockchain solutions effortlessly while maintaining security, efficiency, and costeffectiveness. Such architecture is adaptable to various industries, addressing diverse use cases and providing a versatile platform for blockchain-powered applications.

[0047] In describing further to Figure 1 , reference is made to Figure 2 where there is illustrated a block diagram of an API service layer (104), in accordance with an embodiment of the present invention. The API service layer further includes specialized service modules configured to address diverse enterprise needs. These modules include a wallet management module (202) for handling wallet operations and manage user authentication and identity verification, a token management module (204) for managing token issuance and transfers, an audit management module (206) for maintaining transaction logs and ensuring compliance, and a certificate management module (208) for issuing, storing, and validating digital certificates.

[0048] In one embodiment, the API Service Layer (104) serves as the gateway for external systems, facilitating the seamless interaction with the Blockchain Layer (106). When a user or enterprise or external system requests wallet-related operations, such as creating or updating a wallet in wallet management module (202), the API Service Layer initiates by authenticating the request using API keys and secret keys generated through the enterprise portal. This ensures that only authorized operations proceed.

[0049] Upon successful authentication, the request is translated into a blockchain transaction. For example, during wallet creation, the API Service Layer formats the input parameters, such as the organization ID or user ID, into a transaction template compatible with the blockchain. This transaction is signed digitally and transmitted securely to the Blockchain Layer via the communication framework, which ensures end-to-end encryption and reliable delivery.

[0050] The Blockchain Layer, consisting of a network of nodes operating under a Proof of Authority consensus mechanism, receives the transaction and verifies its integrity. The transaction is then processed, resulting in the creation of a wallet entity on the blockchain. The wallet's metadata, including its unique address and associated attributes, is immutably stored within the blockchain, ensuring security and transparency.

[0051] For retrieval operations, such as fetching wallet details or transaction counts, the API Service Layer queries the Blockchain Layer. The blockchain responds with the requested data, ensuring that every piece of information is up-to-date and consistent with the distributed ledger. This interaction enables real-time access to wallet statuses and transaction histories.The integration between the API Service Layer and the Blockchain Layer extends to entity and certificate management. When creating entities, the API Service Layer sends formatted transactions to the smart contract and the blockchain layer, responsible for entity records. Similarly, certificate issuance and validation requests are processed securely through the blockchain, leveraging its tamper-proof storage capabilities to maintain the authenticity of digital certificates.

[0052] In light of the foregoing, the API Service Layer and Blockchain Layer deliver a comprehensive, secure, and scalable solution for managing wallets, tokens, entities, and certificates. This modular and extensible architecture ensures that enterprises can adopt blockchain technology while maintaining operational efficiency and compliance.

[0053] In an embodiment, the certificate management module (208) is configured to interact with the blockchain layer (106) to enable the secure creation, minting, transfer, and management of digital certificates, such as represented by non-fungible tokens, NFTs. The API Service Layer acts as an intermediary, facilitating seamless communication between enterprise systems and the blockchain infrastructure.

[0054] To create a new certificate smart contract, the API Service Layer receives a request containing parameters such as the wallet address, owner details, maximum supply, certificate name, symbol, image data, and a callback URL. This request is authenticated and processed to generate a transaction that is submitted to the Blockchain Layer. The blockchain executes the transaction, deploying a smart contract with the specified fields. This contract defines the rules and metadata for minting and managing certificates, with ownership initially assigned to the specified address.

[0055] When minting certificates, the API Service Layer verifies the request against the smart contract's constraints, such as the maximum supply. Upon validation, a transaction is transmitted to the Blockchain Layer to mint the certificate. The blockchain ensures that the minting operation adheres to the rules encoded in the smart contract, immutably recording the new certificate on the ledger. The minting event triggers a callback to the specified URL, providing confirmation of the blockchain update.

[0056] The transfer of certificates between wallets is facilitated by the API Service Layer, which generates and signs transactions based on user instructions. These transactions are forwarded to the Blockchain Layer, where they are validated and executed, updating ownership records in the distributed ledger. This functionality ensures secure and traceable certificate transfers.For retrieving certificate details or transaction history, the API Service Layer queries the Blockchain Layer, leveraging its decentralized data storage to fetch information. The response includes metadata, transaction logs, and current ownership details, providing a transparent and verifiable audit trail.

[0057] The module (208) also supports the transfer of smart contract ownership, allowing enterprises to reassign control of a smart contract to a different wallet. This operation is conducted through a blockchain transaction initiated by the current owner, ensuring that the ownership transfer is both secure and immutable.

[0058] By leveraging its integration with the blockchain layer, the certificate management module (208) enables robust and scalable digital certificate solutions, enhancing trust and operational efficiency for enterprise applications.

[0059] In an embodiment, the audit management module (206) ensures that all transactions conducted through the system are recorded with immutable integrity. The module interacts with the blockchain layer to store and retrieve transaction logs securely. Upon receiving a transaction request, the API Service Layer generates an audit trail comprising transaction metadata such as timestamps, involved wallet addresses, transaction type, and status. This information is submitted to the blockchain layer (106), where it is recorded as an indelible ledger entry. Said module facilitates audit retrievals, allowing enterprises to generate detailed compliance reports or conduct forensic investigations. By leveraging blockchain's immutability, the module enhances transparency and accountability.

[0060] The token management module (204) facilitates the issuance, transfer, and management of tokens. Enterprises can tokenize assets, such as loyalty points or vouchers, using this module. The API Service Layer translates user requests into transactions, which are processed by the Blockchain Layer to create and distribute tokens. Transfers between wallets are executed through blockchain transactions, ensuring traceability and reducing fraud. Additionally, the module supports token burning, freezing, and reconciliation operations, which can be initiated via the API Service Layer (104) and executed on the blockchain.

[0061] The wallet management module (202) serves as the cornerstone for creating, managing, and interacting with user and enterprise wallets. Wallet addresses and associated data are securely stored in the Blockchain Layer. The module supports operations such as wallet activation, deactivation, and transaction tracking. It also allows enterprises to categorizewallets based on operational roles, ensuring streamlined management of multi-wallet environments.

[0062] Furthermore, the wallet management module (202) manages user authentication and identity verification. In an instance, the API Service Layer interacts with enterprise systems to collect user information, which is securely hashed and sent to the blockchain layer (106) for storage. During the authentication process, the wallet management module (202) cross-verifies user credentials against the blockchain-stored records. This ensures data integrity and mitigates the risks of unauthorized access. The module (202) also supports multi-factor authentication, allowing enterprises to configure additional security layers.

[0063] Each module within the API Service Layer is integrated with the Blockchain Layer to deliver secure, scalable, and transparent functionality. This modular approach allows enterprises to adopt blockchain solutions tailored to their specific needs while leveraging the decentralized advantages of the blockchain ecosystem.

[0064] In an embodiment, the system architecture integrates the API service layer and blockchain layer. The blockchain layer (106) is composed of two primary components - the core client and the runtime. The core client is responsible for managing network activities, including peer discovery, transaction requests, consensus coordination, and responding to external RPC, Remote Procedure Call requests. This component acts as a bridge to ensure seamless communication between the blockchain and external systems. The core client supports essential operations such as storage management, peer-to-peer networking, and establishing consensus among nodes. It also facilitates remote interactions through the RPC API and gathers node metrics via built-in telemetry services.

[0065] The runtime is responsible for processing transactions and managing state transitions. When requests arrive from external sources, they pass through the core client and are handled by the runtime, which validates transactions and updates the blockchain state. The runtime environment is configured to compile into WebAssembly bytecode, which ensures several advantages. These include system upgrades without the need for hard forks, compatibility across multiple platforms, verification of runtime integrity, and the provision of validation proofs that support consensus mechanisms.

[0066] In the disclosed system (100), in accordance with an embodiment, the core client and runtime functions are supported by a set of specialized libraries that manage various aspects of their operation. These can be categorized into network service libraries, base libraries, and runtime development framework libraries.The network service libraries are crucial for managing network functions and interactions between nodes. These libraries, are prefixed with “sc_”, handle consensus, block processing, and peer-to-peer communication. For instance, the “sc_service” library ensures stable blockchain operations by handling transaction pools and network interactions.

[0067] Base libraries provide essential functions and facilitate communication between network service libraries and the runtime. Identified by the “sp_” prefix, these libraries include “sp_arithmetic” for arithmetic functions, “sp_core” for shared types, and “sp_std” for compatibility with the Rust standard library.

[0068] The runtime development framework libraries are central to creating runtime logic and encoding / decoding data. Libraries prefixed with frame_ enable runtime functionalities, with “frame_system” providing fundamental functions for component interaction, and “frame_support” defining storage, error handling, and event creation. The runtime can be expanded with additional modular libraries prefixed with “pallet_”, which add customized blockchain features tailored to specific requirements.

[0069] It will be appreciated that the present invention is built on an open-source framework, specifically leveraging the Substrate framework. This choice underpins the novel aspects of the present invention, providing a robust foundation for blockchain development that is highly modular and customizable, and provide ease of integration with the external systems.

[0070] At the core, every blockchain acts as a ledger documenting on-chain changes. In the disclosed system (100), these changes are managed by the runtime, which is often called the state transition function. Within the runtime, storage items are defined to represent the blockchain's current state, and transactions are processed to allow users to alter this state.

[0071] The outer node handles various responsibilities, including peer discovery, transaction pooling, block gossiping, consensus, and handling RPC calls from external sources. This interaction with the runtime is facilitated through the runtime API. The “sp_api” crate in Substrate is essential for building the runtime API, providing a means to create custom interfaces with the “impl_runtime_apis” macro.

[0072] The disclosed system employs a Framework for Runtime Aggregation of Modularized Entities, FRAME, that play a significant role in runtime development. It consists of a suite of modules and support libraries that simplify building runtime logic. Within Substrate, these modules, known as pallets, provide customizable business logic to integrate specific functionalities, such as staking, governance, and consensus, enabling developers to create tailored blockchain solutions efficiently.In an embodiment, the present inventionn enables advanced blockchain communication through an integrated mechanism that supports subchain or parachain architectures, facilitating efficient cross-consensus interactions. Leveraging message protocols such as Upward Message Passing, UMP, Downward Message Passing, DMP, and Cross-Consensus Message Passing, XCMP, the disclosed system (100) ensures vertical and horizontal communication between connected chains. These protocols are bolstered by a robust message format, XCM that supports asynchronous, agnostic, and ordered message execution across diverse consensus systems, enhancing interoperability. Furthermore, the present invention approach employs a Cross-Consensus Virtual Machine, XCVM to process these messages efficiently, updating relevant system states and managing transactional details with precision.

[0073] It will be appreciated that the execution of cross-consensus communication functions involves two primary components: the blockchain layer and the API service layer.

[0074] The blockchain layer facilitates the consensus-driven communication protocols, including Upward Message Passing, UMP, Downward Message Passing, DMP, and Cross-Consensus Message Passing, XCMP. It processes messages according to the XCM format, ensuring secure and ordered execution within the Cross-Consensus Virtual Machine, XCVM. This layer also manages the states and transactions of interconnected chains.

[0075] The API service layer interacts with the blockchain layer to handle external requests and coordinate message transmission. It acts as the interface through which message instructions are structured, formatted, and executed across diverse chains. This layer also integrates with the XCVM to dynamically interpret instructions, update internal states, and synchronize communication among chains. Together, these components deliver facilitate sub-chain and cross-chain interoperability.

[0076] In an embodiment, the API service layer, when interacting with the blockchain layer, achieves consensus in two main phases - block authoring and block finalisation. Block authoring involves the process of creating new blocks, which is carried out by nodes authorised according to the consensus model employed.

[0077] Block finalisation is performed to resolve forks, which occur when multiple blocks reference the same parent, creating a potential divergence in the blockchain. The block finalisation mechanism applies a fork choice rule, enabling the network to select the best chain to extend and maintain a single canonical chain.In an embodiment, the transaction pool in the blockchain layer governed by open source framework is configured to validate each incoming transaction based on rules defined in the runtime environment. This ensures that only valid transactions, which meet specific criteria, are queued for potential inclusion in a block. The process includes verifying the transaction's index, i.e., nonce, to ensure it is correct and matches the expected sequence for the signing account. Additionally, the system checks that the account has sufficient funds to cover the fees associated with the transaction. The signature accompanying the transaction is also validated to confirm authenticity. The transaction pool performs these checks before the initial inclusion, and it revalidates transactions periodically to maintain the accuracy and integrity of the pool. Transactions found to be invalid or expired are promptly removed to prevent issues with block formation.

[0078] Once a transaction is verified as valid, it is added to one of two distinct transaction queues. The "Ready Queue" holds transactions that can be included in the next block without delay. These transactions must be processed in the order they were placed in the queue to maintain consistency. The “Future Queue,” on the other hand, stores transactions that are not yet valid due to their nonce being too high. These transactions wait until the necessary number of prior transactions have been included in the chain, at which point they can transition to the ready state.

[0079] Invalid transactions are handled differently. If a transaction is deemed invalid during any verification stage, it is rejected and removed from the pool. Several reasons can lead to this rejection, including if the transaction has already been included in a block, rendering it obsolete. An invalid or improperly formed signature also causes immediate rejection. In cases where a transaction's size exceeds the block's capacity, it is returned to the transaction pool for consideration during future block formation cycles.

[0080] T o manage the ordering of transactions for block creation, nodes utilize a priority system. This disclosed system (100) ranks transactions from high to low priority based on their respective weights, and the block author includes transactions in the block until the maximum allowed block size or weight is reached. The runtime assigns transaction priority based on a calculated metric provided by a specialized pallet, ensuring that transactions with lower computational costs are processed first. In addition, inherents, which are predefined transactions essential for block creation, are prioritized above others, using a trait called “EnsurelnherentsAreFirst” to maintain their precedence.

[0081] Reference is made to Figure 3, where there is illustrated a method (300) for integrating external systems into a blockchain interaction management system, in accordance with an embodimentof the present invention, the method for integrating external systems into a blockchain interaction management system initiates with step (302) that comprises receiving, through an enterprise portal, a service request from an external system that seeks to access blockchain services. Further, at step (304), the method (300) comprises receiving a user selection related to a set of services identified via the external system, that correspond to the external system’s request and specific use case, presenting an overview of the services and their functionalities for user selection. This process allows users to select the services that best fit their needs and gain a clearer understanding of the potential applications.

[0082] Following the selection process, at step (306), the method (300) comprises conducting a user survey through Know Your Customer, KYC and Know Your Business, KYB procedures within the enterprise portal. Once the survey is complete, the method (300) proceeds to step (308) that comprises linking a user’s payment method for the processing of subscription fees and service usage charges.

[0083] Upon successful account registration, the external system is subscribed to the selected services. At step (310), the method (300) comprises generating unique API keys and API secret keys for authentication process via the enterprise portal. These keys serve as secure access credentials that enable the external system to interact with the blockchain services without risk of unauthorized access.

[0084] Furthermore, at step (312), the method comprises providing comprehensive documentation detailing the available service endpoints, specifications, and integration requirements via the API service layer. This documentation serves as a valuable guide for the external system's developers to ensure a smooth and efficient integration process. Thereafter, at step (314), the method comprises initiating the incoming API requests from the client or external system once the API keys and secret keys have been provided. At step (316), the method (300) comprises authenticating the incoming API requests using the generated API keys and API secret keys at the API service layer.

[0085] Reference is made to Figure 4, where there is illustrated a method (400) for managing blockchain interactions, in accordance with an embodiment of the present invention. The method (400) initiates by registering users and managing services through an enterprise portal at step (402).

[0086] In describing further on Figure 4, reference is made to Figure 5, where there is illustrated a method (500) for registering users and managing services through an enterprise portal. The method (500) comprises accepting user registrations and subscriptions for blockchain-relatedservices at step (502) and generating unique API keys and secret keys for secure user authentication at step (504).

[0087] Subsequent to step (402), the method (400) comprises processing incoming requests from the users via an API service layer at step (404), and executing blockchain operations related to the external requests via a blockchain layer at step (406).

[0088] In describing further on Figure 4, reference is made to Figure 6 where there is illustrated a method (600) of executing blockchain operations related to the external requests via a blockchain layer, in accordance with an embodiment of the present invention. The method (600) comprises validating and confirming transactions using a proof of authority, PoA consensus mechanism at step (602), processing transactions and broadcasting confirmed transactions across a network of nodes to ensure distributed ledger consistency at step (604), executing programmable agreements through smart contracts triggered by the transactions at step (606), and enhancing runtime adaptability using customizable runtime modules managed by a plurality of pallets in the blockchain layer to execute specific blockchain operations customized to requirements of the users, at step (608).

[0089] Thereafter, the method (400) comprises transmitting data securely using a communication framework by transmitting formatted transactions between the API service layer and the blockchain layer, and ensuring secure return of transaction responses to the users, at step (408).

[0090] In describing further on Figure 4, reference is made to Figure 7, where there is illustrated a method of processing external requests via an API service layer (404) further comprise method steps of (700), in accordance with an embodiment of the present invention. The method steps (700) comprise authenticating the incoming API requests using the API keys and the API secret keys, at step (702), formatting the requests into blockchain transactions for processing, at step (704), and signing and securely transmitting the blockchain transactions to a blockchain layer, at step (706).

[0091] Throughout this specification, unless the context requires otherwise, the word “comprise”, or variations such as “comprises” or “comprising”, will be understood to imply the inclusion of a stated step or element or integer or group of steps or elements or integers, but not the exclusion of any other step or element or integer or group of steps, elements or integers. Thus, in the context of this specification, the term “comprising” is used in an inclusive sense and thus should be understood as meaning “including principally, but not necessarily solely”.

Claims

CLAIMS1 . A system (100) for blockchain interaction management, comprising:an enterprise portal (102) including a user interface configured to:manage user registrations, service subscriptions, and billings based on service usage; andgenerate unique API keys and API secret keys for secure authentication;an application programming interface, API service layer (104), operably coupled to the enterprise portal (102), for allowing external systems to interact with blockchain architecture;a blockchain layer (106) including the blockchain architecture, operably coupled to the API service layer (104), wherein the blockchain layer (106) is configured to provide a Proof of Authority, PoA consensus mechanism for validating and confirming transactions, wherein the blockchain layer comprises:a network of nodes configured to store, validate, and process distributed blockchain transactions; andat least one smart contract configured to execute programmable agreements triggered by blockchain transactions;a plurality of pallets, each pallet is configured to manage customizable runtime modules for executing a plurality of blockchain operations;a communication framework (108), interconnecting the API service layer (104) and the blockchain layer (106), configured to:ensure secure and authenticated processing of transactions by facilitating the transmission of formatted transactions from the API service layer to the blockchain layer and return of responses thereof to the external systems;2. The system (100) according to Claim 1 , wherein the API service layer (104) is configured to:authenticate API requests using the API keys and the API secret keys generated by the enterprise portal (102);format the API requests into at least one blockchain transaction; andsign and securely transmit the at least one blockchain transaction to the blockchain layer (106) for further processing.

3. The system (100) according to Claim 1 , wherein the API service layer (104) comprises a plurality of service modules coupled to the blockchain layer (106) for performing specificfunctionalities customized to requirements of the external system, the plurality of service modules comprise:at least one wallet management module (202), configured to manage wallet-related operations and manage user authentication and identity verification;at least one token management module (204), configured to handle token issuance, token transfer, and functions associated thereof;at least one audit management module (206), configured to maintain transaction logs and support compliance;at least one certificate management module (208), configured to issue, store, and validate digital certificates.

4. The system (100) according to Claim 1, wherein the blockchain layer (106) further comprises:a core client component, wherein the core client is responsible for managing network activities;a runtime component, wherein the runtime component is responsible for processing transactions and managing state transitions within the blockchain layer (106).

5. The system (100) according to Claim 4, wherein the core client component and the runtime component are configured to execute a plurality of associated functions which are supported by a set of libraries, the set of libraries include at least one of network service libraries, base libraries, and runtime development framework libraries.

6. The system (100) according to Claim 5, wherein the network service libraries manage network function and interactions between the networks of nodes.

7. The system (100) according to Claim 5, wherein the base libraries facilitate communications between service libraries and the runtime component.

8. The system (100) according to Claim 5, wherein the runtime development framework libraries are responsible for creating runtime logic and encoding / decoding data.

9. A method (400) for managing blockchain interactions, comprising the steps of:registering users and managing services using an enterprise portal (402), wherein registering users and managing services using an enterprise portal (402) comprises method steps of (500), the method steps (500) comprising:accepting user registrations and subscriptions for blockchain-related services via the enterprise portal (502);generating unique API keys and secret keys to securely authenticate user access (504);processing incoming requests from the users via an API service layer (404); executing blockchain operations related to the external requests via a blockchain layer (406), wherein executing blockchain operations related to the external requests via a blockchain layer (406) further comprises method steps of (600), the method steps (600) comprising:validating and confirming transactions using a proof of authority, PoA consensus mechanism (602);processing transactions and broadcasting confirmed transactions across a network of nodes to ensure distributed ledger consistency (604);executing programmable agreements through smart contracts triggered by the transactions (606); andenhancing runtime adaptability using customizable runtime modules managed by a plurality of pallets in the blockchain layer to execute specific blockchain operations customized to requirements of the users (608);transmitting data securely using a communication framework by transmitting formatted transactions between the API service layer and the blockchain layer, and ensuring secure return of transaction responses to the users (408).

10. The method (400) according to Claim 9, wherein processing external requests via an API service layer (404) further comprise method steps of (700), the method steps (700) comprising:authenticating the incoming API requests using the API keys and the API secret keys (702);formatting the requests into blockchain transactions for processing (704); and signing and securely transmitting the blockchain transactions to a blockchain layer (706).

Images