Creation and operation of a blockchain service system

Abstract

Methods and systems for creating a blockchain service system for a user. The method includes receiving user input. The user input includes configuration information associated with the blockchain service system. The method also includes creating the blockchain service system for the user based on the received user input. The blockchain service system includes a blockchain hosted in a computing network and one or more tools for operating and managing the blockchain.

Description

TECHNICAL FIELD

[0001] The present invention relates to the creation and / or operation of blockchain service systems. BACKGROUND

[0002] Blockchain technology can facilitate the digitization of transactions and records through secure, shared, and distributed ledgers, and can be used for different personal and commercial applications. Generally, the creation and deployment of blockchain systems or platforms requires the manual building, setting up, optimizing, and maintaining of various hardware and software. For some individuals and businesses, performing these manual operations can be both difficult and time-consuming. SUMMARY

[0003] In a first aspect of the invention, a method of creating a blockchain service system for a user is provided. The method includes: (a) receiving user input comprising configuration information associated with the blockchain service system, and (b) creating, based on the received user input, the blockchain service system for the user. The blockchain service system includes a blockchain hosted in a computing network and one or more tools for operating and managing the blockchain.

[0004] Optionally, step (b) includes creating, for the user, a namespace on a container orchestration platform, and creating, in the namespace, one or more containers associated with the one or more tools based on one or more predetermined images. The container orchestration platform is operable to facilitate the operation of the blockchain service system.

[0005] Optionally, the container orchestration platform comprises a Kubernetes platform.

[0006] Optionally, the one or more predetermined images comprise one or more Docker images.

[0007] Optionally, the one or more containers include a database container having one or more database modules for facilitating access to one or more databases associated with the blockchain service system. Optionally, the one or more database modules include a first database module for storing blockchain service related data and a second database module for storing API related data.

[0008] Optionally, the one or more containers include a network API container having a network service API module.

[0009] Optionally, the one or more containers include a blockchain operations container having a blockchain module, a blockchain API module, and a cryptocurrency explorer module.

[0010] Optionally, step (b) includes initializing a plurality of blockchain nodes for the blockchain based on user input, and configuring the blockchain based on the initialized blockchain nodes. The blockchain nodes can be part of a computing network.

[0011] Optionally, the configuration information includes information on a number of blockchain nodes required for the blockchain service system.

[0012] Optionally, the configuration information includes information associated with resource limitations and / or requirements of the blockchain service system. The resource limitations and / or requirements can include processor limitations and / or requirements, memory or storage limitations and / or requirements, and / or disk drive limitations and / or requirements.

[0013] Optionally, the one or more tools include one or more APIs for facilitating access to and operation of the blockchain.

[0014] Optionally, the one or more APIs are operable to facilitate one or more of uploading data to the blockchain, validating data based on data stored in the blockchain, and querying data stored in the blockchain.

[0015] Optionally, the one or more tools include a user interface for facilitating user operation and / or management of the blockchain. The user interface is operable to display data, blocks, transactions, accounts, cryptocurrencies, usage information, and / or smart contracts associated with the blockchain and / or the blockchain service system.

[0016] Optionally, the blockchain is an Ethereum-based blockchain.

[0017] Optionally, the blockchain is a private blockchain.

[0018] Optionally, the computing network includes a distributed computing network.

[0019] Optionally, the computing network includes a cloud computing network.

[0020] In a second aspect of the application, there is provided a non-transitory computer- readable storage medium storing one or more programs configured to be executed by one or more processors, the one or more programs comprising instructions for performing or facilitating the performance of the method of the first aspect.

[0021] In a third aspect of the application, there is provided a system for creating a blockchain service system for a user. The system includes one or more processors and a memory. The memory stores one or more programs configured to be executed by the one or more processors. The one or more programs comprise instructions for performing or facilitating the performance of the method of the first aspect.

[0022] In a fourth aspect of the application, a system for creating a blockchain service system for a user is provided. The system includes one or more processors configured to (a) receive user input including configuration information associated with the blockchain service system, and (b) based on the received user input, create the blockchain service system for the user. The blockchain service system includes a blockchain hosted in a computing network and one or more tools for operating and managing the blockchain.

[0023] Optionally, the one or more processors are configured to perform (b) by creating a namespace for the user on a container orchestration platform, and creating one or more containers associated with the one or more tools in the namespace based on one or more predetermined images. The container orchestration platform is operable to facilitate operation of the blockchain service system. The container orchestration platform can be operated or run by the one or more processors.

[0024] In some embodiments, the container orchestration platform is operable to facilitate operation of a plurality of blockchain service systems, each of the plurality of blockchain service systems for a different user, wherein each user has a respective namespace, blockchain, and tools.

[0025] Optionally, the container orchestration platform includes a Kubernetes platform.

[0026] Optionally, the one or more predetermined images include one or more Docker images.

[0027] Optionally, the one or more containers include a database container having one or more database modules for facilitating access to one or more databases associated with the blockchain service system. Optionally, the one or more database modules include a first database module for storing blockchain service related data and a second database module for storing API related data.

[0028] Optionally, the one or more containers include a network API container having a network service API module.

[0029] Optionally, the one or more containers include a blockchain operation container having a blockchain module, a blockchain API module, and a cryptocurrency explorer module.

[0030] Optionally, the one or more processors are configured to perform (b) by, based on the user input, initializing a plurality of blockchain nodes for the blockchain, and configuring the blockchain based on the initialized blockchain nodes. The blockchain nodes can be part of the computing network.

[0031] Optionally, the configuration information includes: information of a number of blockchain nodes required by the blockchain service system.

[0032] Optionally, the configuration information includes: information associated with resource limits and / or requirements of the blockchain service system. The resource limits and / or requirements can include processor limits and / or requirements, memory or storage limits and / or requirements, and / or disk drive limits and / or requirements.

[0033] Optionally, the one or more tools include: one or more APIs for facilitating access to and operation of the blockchain.

[0034] Optionally, the one or more APIs are operable to facilitate one or more of: uploading data to the blockchain, validating data based on data stored in the blockchain, and querying data stored in the blockchain.

[0035] Optionally, the one or more tools include: a user interface for facilitating user operation and / or management of the blockchain. The user interface is operable to display data, blocks, transactions, accounts, cryptocurrencies, usage information, and / or smart contracts associated with the blockchain and / or the blockchain service system.

[0036] Optionally, the blockchain is an Ethereum-based blockchain.

[0037] Optionally, the blockchain is a private blockchain.

[0038] Optionally, the computing network includes a distributed computing network. The one or more processors can or can not be part of the distributed computing network.

[0039] Optionally, the computing network includes a cloud computing network. The one or more processors can or can not be part of the cloud computing network.

[0040] In a fifth aspect of the application, there is provided a method of using a blockchain service system, the blockchain service system being created based on the method of the first aspect. The method includes performing an operation using the blockchain service system.

[0041] Optionally, the operation includes a data upload operation.

[0042] Optionally, the data upload operation includes: receiving data to be uploaded to the blockchain, uploading the data or a representation of the data to the blockchain, and providing a transaction hash if the data or the representation of the data is successfully uploaded to the blockchain.

[0043] Optionally, the data upload operation further comprises, prior to uploading the data or the representation of the data to the blockchain, determining a size of the data to be uploaded to the blockchain; if it is determined that the size of the data does not reach or exceed a threshold, uploading the data to the blockchain; and if it is determined that the size of the data reaches or exceeds the threshold, uploading a representation of the data to the blockchain.

[0044] Optionally, the data upload operation further comprises, if it is determined that the size of the data reaches or exceeds the threshold, determining a hash of the data; and uploading the hash (as the representation of the data) to the blockchain.

[0045] Optionally, the data upload operation further comprises, if it is determined that the size of the data reaches or exceeds the threshold, splitting the data into a plurality of data portions, wherein each data portion is within the threshold in size; and uploading the plurality of data portions (as the representation of the data) to the blockchain.

[0046] Optionally, the data upload operation further comprises, prior to uploading the data or the representation of the data to the blockchain, obtaining a token, the token being for allowing use of an API to facilitate uploading of the data to the blockchain; and only allowing use of the API to upload the data to the blockchain when the token is obtained.

[0047] Optionally, the data upload operation further comprises, prior to uploading the data or the representation of the data to the blockchain, obtaining a token, the token being for allowing use of an API to facilitate uploading of the data to the blockchain; determining validity of the token; and only allowing use of the API to upload the data to the blockchain when the token is determined to be valid.

[0048] Optionally, the operation comprises a data verification operation.

[0049] Optionally, the data verification operation comprises receiving a transaction hash and data to be verified, and determining, from the transaction hash, whether the data to be verified matches data stored in the blockchain.

[0050] Optionally, the data verification operation further comprises, if it is determined that the data does not match the data stored in the blockchain, providing a result indicating that there is a difference between the data and the data stored in the blockchain; and if it is determined that the data matches the data stored in the blockchain, providing a corresponding result or notification indicating that the data matches the data stored in the blockchain.

[0051] Optionally, the data verification operation further comprises, prior to the determining, obtaining a token, the token being for allowing use of an API to facilitate access to the data stored in the blockchain (for the determining); and only allowing use of the API to make the determining when the token is obtained.

[0052] Optionally, the data verification operation further comprises, prior to the determining, obtaining a token, the token being for allowing use of an API to facilitate access to data stored in the blockchain (for the determining); determining validity of the token; and allowing use of the API for the determining only if the token is determined to be valid.

[0053] Optionally, the operation comprises a data query operation.

[0054] Optionally, the data query operation comprises receiving a transaction hash, and determining, from the transaction hash, whether data associated with the transaction hash is stored in the blockchain.

[0055] Optionally, the data query operation further comprises, if it is determined that the data associated with the transaction hash is stored in the blockchain, providing the data associated with the transaction hash; and if it is determined that the data associated with the transaction hash is not stored in the blockchain, providing a respective result or notification indicating that the data associated with the transaction hash is not stored in the blockchain.

[0056] Optionally, the data query operation further comprises, prior to the determining, obtaining a token, the token being for allowing use of an API to facilitate access to data stored in the blockchain (for the determining); and allowing use of the API for the determining only if the token is obtained.

[0057] Optionally, the data verification operation further comprises, prior to the determining, obtaining a token, the token being for allowing use of an API to facilitate access to data stored in the blockchain (for the determining); determining validity of the token; and allowing use of the API for the determining only if the token is determined to be valid.

[0058] In a sixth aspect of the application, there is provided a non-transitory computer- readable storage medium storing one or more programs configured to be executed by one or more processors, the one or more programs comprising instructions for performing or facilitating performance of the method of the fifth aspect.

[0059] In a seventh aspect of the application, there is provided a system for using a blockchain service system, the blockchain service system being created based on the method of the first aspect. The system comprises one or more processors and a memory. The memory stores one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for performing or facilitating performance of the method of the fifth aspect.

[0060] In an eighth aspect of the application, there is provided a system for using a blockchain service system, the blockchain service system being created based on the method of the first aspect. The system comprises one or more processors configured to perform operations using the blockchain service system.

[0061] Optionally, the operation includes a data upload operation.

[0062] Optionally, the one or more processors are configured to perform the data upload operation by receiving data to be uploaded to the blockchain, uploading the data or a representation of the data to the blockchain, and providing a transaction hash if the data or the representation of the data is successfully uploaded to the blockchain.

[0063] Optionally, the one or more processors are further configured to perform the data upload operation by, prior to uploading the data or the representation of the data to the blockchain, determining a size of the data to be uploaded to the blockchain, uploading the data to the blockchain if it is determined that the size of the data does not meet or exceed a threshold, and uploading a representation of the data to the blockchain if it is determined that the size of the data meets or exceeds the threshold.

[0064] Optionally, the one or more processors are further configured to, if it is determined that the size of the data meets or exceeds the threshold, determine a hash value of the data, and upload the hash value (as the representation of the data) to the blockchain.

[0065] Optionally, the one or more processors are further configured to perform the data upload operation by, if it is determined that the size of the data meets or exceeds the threshold, splitting the data into a plurality of data portions, wherein each data portion is within the threshold in size, and uploading the plurality of data portions (as the representation of the data) to the blockchain.

[0066] Optionally, the one or more processors are further configured to perform the data upload operation by, prior to uploading the data or the representation of the data to the blockchain, obtaining a token that is used to allow use of an API to facilitate uploading of the data to the blockchain, and allowing use of the API to upload the data to the blockchain only if the token is obtained.

[0067] Optionally, the one or more processors are further configured to perform the data upload operation by, prior to uploading the data or the representation of the data to the blockchain, obtaining a token that is used to allow use of an API to facilitate uploading of the data to the blockchain, determining a validity of the token, and allowing use of the API to upload the data to the blockchain only if the token is determined to be valid.

[0068] Optionally, the operation includes a data verification operation.

[0069] Optionally, the one or more processors are configured to perform the data verification operation by receiving a transaction hash and data to be verified, and determining, from the transaction hash, whether the data to be verified matches data stored in the blockchain.

[0070] Optionally, the one or more processors are further configured to perform the data validation operation by: providing a result indicating that there is a difference between the data and the data stored in the blockchain if it is determined that the data does not match the data stored in the blockchain; and providing a respective result or notification indicating that the data matches the data stored in the blockchain if it is determined that the data matches the data stored in the blockchain.

[0071] Optionally, the one or more processors are further configured to perform the data validation operation by: prior to the determining, obtaining a token that is used to allow use of the API to facilitate access to the data stored in the blockchain (to make the determining); and allowing use of the API to make the determining only when the token is obtained.

[0072] Optionally, the one or more processors are further configured to perform the data validation operation by: prior to the determining, obtaining a token that is used to allow use of the API to facilitate access to the data stored in the blockchain (to make the determining); determining a validity of the token; and allowing use of the API to make the determining only when the token is determined to be valid.

[0073] Optionally, the operation comprises a data query operation.

[0074] Optionally, the one or more processors are configured to perform the data query operation by: receiving a transaction hash; and determining, from the transaction hash, whether data associated with the transaction hash is stored in the blockchain.

[0075] Optionally, the one or more processors are further configured to perform the data query operation by: providing the data associated with the transaction hash if it is determined that the data associated with the transaction hash is stored in the blockchain; and providing a respective result or notification indicating that the data associated with the transaction hash is not stored in the blockchain if it is determined that the data associated with the transaction hash is not stored in the blockchain.

[0076] Optionally, the one or more processors are further configured to perform the data query operation by: prior to the determining, obtaining a token that is used to allow use of the API to facilitate access to the data stored in the blockchain (to make the determining); and allowing use of the API to make the determining only when the token is obtained.

[0077] Optionally, the one or more processors are further configured to perform the data query operation by: prior to the determining, obtaining a token that is used to allow use of the API to facilitate access to the data stored in the blockchain (to make the determining); determining a validity of the token; and allowing use of the API to make the determining only when the token is determined to be valid.

[0078] Other features and aspects of the present application will become apparent from consideration of the description and drawings. In appropriate and applicable circumstances, any one or more of the features described herein in respect of one aspect or embodiment can be combined with any one or more of the other features described herein in respect of any one or more other aspects or embodiments. In appropriate and applicable circumstances, any aspect described herein can be combined with any other aspect described herein. For example, the method of the first aspect and the method of the fifth aspect can be combined. For example, the non-transitory computer-readable storage medium of the second aspect and the non-transitory computer-readable storage medium of the sixth aspect can be combined. For example, the system of the third aspect and the system of the seventh aspect can be combined. For example, the system of the fourth aspect and the system of the eighth aspect can be combined. BRIEF DESCRIPTION OF DRAWINGS

[0079] Embodiments of the present application will now be described, by way of example only, with reference to the accompanying drawings in which:

[0080] Figure 1 is a schematic diagram of a system for creating and / or operating a blockchain service system of an embodiment of the present application;

[0081] Figure 2 is a flowchart of a method for creating a blockchain service system of an embodiment of the present application;

[0082] Figure 3 is a schematic diagram of a blockchain service system creation and / or operation platform of an embodiment of the present application;

[0083] Figure 4 is a functional block diagram of a blockchain service system creation and / or operation platform of an embodiment of the present application;

[0084] Figure 5 is a schematic diagram of a blockchain service system creation and / or operation platform of an embodiment of the present application;

[0085] Figure 6 is a schematic diagram of a container in a namespace of a platform of an embodiment of the present application; Figure 5

[0086] Figure 7 is a schematic diagram of a containerized architecture of an embodiment of the present application;

[0087] Figure 8 is a schematic diagram of a blockchain service system of an embodiment of the present application;

[0088] Figure 9 is a schematic diagram of various operations that can be performed by a blockchain service system of an embodiment of the present application; Figure 8

[0089] ​​Figure 10A is a flowchart of a data upload operation that can be performed by a blockchain service system of one embodiment of the present application. Figure 8

[0090] Figure 10B is a flowchart of a data query operation that can be performed by a blockchain service system of one embodiment of the present application. Figure 8

[0091] Figure 10C is a flowchart of a data validation operation that can be performed by a blockchain service system of one embodiment of the present application. Figure 8

[0092] Figure 11 is a screenshot of a user interface of a blockchain management console of one embodiment of the present application.

[0093] Figure 12 is a screenshot of a user interface of a blockchain service console of one embodiment of the present application.

[0094] Figure 13 is a screenshot of a user interface of a cryptocurrency browser of one embodiment of the present application.

[0095] Figure 14 is a schematic diagram of an application of a blockchain service system in one embodiment of the present application.

[0096] Figure 15 is a schematic diagram of a blockchain service system creating and / or operating a platform in one embodiment of the present application; and

[0097] Figure 16 is a functional block diagram of an information processing system that can be used to implement at least a portion of the present application in one embodiment of the present application. DETAILED DESCRIPTION

[0098] Figure 1 ​​​A system 100 for creating and / or operating a blockchain service system (i.e., a blockchain service system creation and / or operation system) is shown. The system 100 can be implemented using hardware, software, or both. The system 100 is arranged to receive configuration information associated with a blockchain service system (e.g., specifications and / or requirements associated with the blockchain service system) from a user. The user can be an individual or an enterprise unit / entity that wishes to set up a blockchain service system for use. For example, the configuration information can include: a number of blockchain nodes required, information associated with resource (e.g., CPU, memory, storage, disk drive, etc.) limitations and / or requirements, etc. The system 100 is also arranged to create a blockchain service system for use by the user based on the user input. The blockchain service system created by the system 100 includes a blockchain hosted in a computing network for use by the user, and tools for the user to operate and manage the blockchain (and its related operations). In the present embodiment, the blockchain is a private, Ethereum-based blockchain hosted on a distributed computing network or a cloud computing network.

[0099] The system 100 of the present embodiment utilizes containerization technology to create a blockchain service system. In the present embodiment, the system 100 is arranged to create a namespace for the user on a container orchestration platform, and create containers associated with the tools in the namespace based on predetermined images, etc. The container orchestration platform can be used to facilitate the operation of the blockchain service system, and in the present embodiment is a Kubernetes platform. In the present embodiment, the predetermined images are Docker images. In the present embodiment, a plurality of containers are created in the namespace. These containers include: a database container, a web API container, and a blockchain operation container. The database container includes a database module associated with a database associated with the blockchain service system. In one example, the database module includes: a database module for storing blockchain service related data and another database module for storing API related data. The web API container includes a web service API module. The blockchain operation container includes a blockchain module, a blockchain API module, and a blockchain (e.g., cryptocurrency) explorer module, all of which are associated with the blockchain. In the present embodiment, the system 100 is arranged to initialize a plurality of blockchain nodes (which can be part of a computing network) for the blockchain based on the user input, and configure the blockchain based on the initialized blockchain nodes.

[0100] The tools for creating a blockchain service system can include an API for facilitating blockchain access and operations, e.g., uploading data to a blockchain, validating data based on data stored in a blockchain, querying data stored in a blockchain, etc. The tools for creating a blockchain service system can include a user interface for facilitating user operations and / or managing a blockchain. The user interface can be operable to display data, blocks, transactions, accounts, cryptocurrencies, usage information, and / or smart contracts associated with a blockchain and / or a blockchain service system.

[0101] In the present embodiment, the system 100 can be used to create a blockchain service system for different users, such that each user has their own blockchain and tools, which are preferably customized according to the needs (inputs) of the user.

[0102] Figure 2 A method 200 for creating a blockchain service system of one embodiment of the present invention is shown. The method 200 can be implemented using the system 100 or other system (which can be comprised of hardware, software, or both). The method 200 of the present embodiment is arranged to facilitate the rapid creation and deployment of a blockchain service system for use by a user. The method 200 can be performed by different users to help each of them establish their own blockchain service system. The method 200 can help reduce or eliminate complex and / or time-consuming operations that need to be performed by a user to establish a blockchain service. These complex and / or time-consuming operations include, for example, server application, environment configuration, blockchain node installation / configuration / initialization / startup, etc. By using the method 200, a user can be provided with a blockchain service system that includes a set of proprietary (i.e., user-specific) private chain networks and services, and an operator of the creation system can be provided with an interface for managing and monitoring the blockchain service systems of different users.

[0103] The method 200 begins at stage 202: information registration stage. At this stage 202, a user provides at least the following information: user information (e.g., details, particulars, etc.), the number of blockchain nodes required, resource (e.g., CPU, memory, storage) limits, other container configuration information, etc. This information can be provided by the user through a user interface of a management console of the blockchain service system creation and / or operation system (e.g., system 100). In one example, the user inputs are stored in a management console database.

[0104] After stage 202, the method 200 proceeds to stage 204: creation and launch stage. At stage 204, the blockchain service system creates and / or operates a system arranged to, for example, create a dedicated space (user-specific namespace) for the user on a Kubernetes (K8S) platform, generate a private chain account, and create and launch containers of various functional modules in the space (user-specific namespace) created for the user. Preferably, one or more of these operations are performed automatically without user intervention or substantially without user intervention. In one example, the creation and / or launch of the containers (e.g., which containers to launch, how many containers to launch, etc.) is based on the user input received at stage 202. In one example, the creation and / or launch of the containers is based on the deployment of images from the master node to the worker nodes in the Kubernetes (K8S) platform. In one example, one or more private chain accounts are created for the user, and the account address and key information are stored in the management console database.

[0105] After stage 204, the method 200 proceeds to stage 206: initialization and configuration stage. At stage 206, the blockchain service system creates and / or operates a system arranged to perform the following example operations: initialize blockchain nodes, import private chain accounts, configure private chain networks (blockchains) based on the initialized blockchain nodes, launch private chain nodes and thus blockchains, deploy smart contracts for the blockchains, and configure blockchain APIs, service consoles, and cryptocurrency browsers for the blockchains. Preferably, one or more of these operations are performed automatically without user intervention or substantially without user intervention. In one example, the initialization of the blockchain nodes (which blockchain nodes to initialize, how many blockchain nodes to initialize, etc.) is based on the user input received at stage 202. In one example, the following information / data is obtained from the management console database to facilitate automatic deployment: (1) regarding blockchain node initialization: account address and private key, node initialization section (including packaging time, chain identifier), (2) regarding blockchain API: appslog contract json, administrator account address and private key.

[0106] In one example, stage 206 includes exporting a keystore file according to the user's blockchain account address and private key and placing it in the keystore file directory of the blockchain node, and writing the account information and contract information in the management console database to the service console database. The service console database information is written to the blockchain API configuration file, and the above information is obtained from the service console database at the time of the launch of the blockchain API. After automatic deployment, the contract address, container IP address, and other information are written to the management console database.

[0107] After stage 206, the method 200 proceeds to stage 208: service delivery stage. At stage 208, the blockchain service system creation and / or operation system is arranged to check (e.g., test) the created blockchain and various tools. The blockchain service system creation and / or operation system is arranged to deliver the blockchain API, service console, and cryptocurrency explorer to the users (e.g., provide them for use by the users). Using these tools, the users can operate and manage their own blockchain.

[0108] Figure 3 is a schematic diagram of a blockchain service system creation and / or operation platform 300 according to an embodiment of the present invention.

[0109] The platform 300 includes a system 302 for creating and / or operating blockchain service systems for different users. The system 302 includes a management and monitoring center with a management console arranged in a platform management namespace for facilitating the creation and / or operation of blockchain service systems for different users. In the present embodiment, the management console can facilitate the automatic deployment of blockchain service systems for different users. Each blockchain service system can include a blockchain for a respective user and tools (e.g., API, monitoring / service console, etc.) for managing and / or operating the respective blockchain. The management console can perform at least a portion of the method 200. As shown in Figure 2 Figure 3 different users are provided with different user-specific spaces and blockchain services, each arranged in a respective namespace. The system 302 includes a Kubernetes container cluster for automatically creating, deploying, scaling, and managing containerized applications to support the creation and / or operation of blockchain service systems. The Kubernetes container cluster includes a plurality of master nodes and a plurality of worker nodes operating in a plurality of virtual machine servers. In the present embodiment, the virtual machine servers are installed with a Docker engine. The virtual machine servers can be deployed to a public cloud computing network or a private cloud computing network. The system 302 also provides a Kubernetes management platform, which can provide a user interface (e.g., GUI) for managing the Kubernetes container cluster. The system 302 can be operatively arranged in or coupled with a distributed storage system 306 for storing data, information, etc. associated with the blockchain service systems and / or the platform 300 or system 302. Various applications 304, including user interfaces (e.g., GUIs), can be operatively coupled with the system 302 for accessing the system 302. These applications 304 can include a management console (interface) allowing an operator / administrator of the platform 300 to manage the platform 300 or system 302, a blockchain service console (interface) allowing a user of a blockchain service system to manage and / or operate their own blockchain service system, and various user applications.​

[0110] Figure 4 Layers of a blockchain service system creation and / or operation platform 400 of one embodiment of the present invention are shown. The platform 400 can be adapted for the platform 300.

[0111] The platform 400 includes a resource layer that provides resources for operating the platform 400. In this embodiment, the resource layer can include a public cloud computing network, a private cloud computing network, and / or virtual machines arranged in one or more information processing systems. The platform 400 also includes a container layer that creates a Kubernetes platform for hosting and operating containers. Various services and modules are packaged into container images and deployed to the Kubernetes platform to enable container management, resource scheduling, and fast creation / deployment of blockchain service systems. The platform includes a blockchain and database layer that operates blockchains and related databases. In this embodiment, the blockchain and database layer includes an ETH private chain network and MySQL and Redis databases. Each node of the ETH private chain has a private chain ledger. The MySQL database can store data (statistics, data upload, etc.) associated with the private chain network, which can be queried through a service console. The platform 400 also includes a service application layer that provides different application modules that implement different functions. In this embodiment, the application modules include: a basic information query management module, a transaction (blockchain related) information query module, a user role management module, a customer (user) management module, a blockchain configuration management module, a token management module, a blockchain information query module, a blockchain information monitoring module, an API service module (data upload module, data query module, data verification module), etc. The platform 400 also includes a customer front-end layer that includes various customer and administrator / operator application front-ends. In this embodiment, the customer front-end layer includes a blockchain service console that facilitates management and / or operation of a blockchain by a user, a blockchain management console that facilitates management and / or operation of the platform 400 by an operator / administrator of the platform 400, an Ethereum (ETH) (cryptocurrency) browser that facilitates management and / or operation of a cryptocurrency associated with a blockchain by a user, and various user applications.

[0112] Figure 5 A blockchain service system creation and / or operation platform 500 in one embodiment of the present invention is shown. The platform 500 can be adapted for the platforms 300, 400. As shown, Figure 5 different users can have different namespaces (customer namespaces) in the Kubernetes platform. The different namespaces of different users are separated, and container operating environments and data storage are separated in virtual spaces. From Figure 5As can be seen, each user has their own set of blockchain and related tools. Specifically, each user has, in a namespace on the Kubernetes platform: a web API container with a console web API module, a database container with a service console database and a Redis database, and a blockchain container with a blockchain module, a blockchain API module (ETH API), and a cryptocurrency explorer module (ETH explorer). Through the blockchain API module, the user can upload data to the blockchain in the blockchain module, query and / or validate data in the blockchain module based on data stored in the blockchain, etc. Through the console web API module, the user can access the database container (and related modules) and the blockchain container (and related modules, e.g., through the blockchain API module) using their service console (user interface). User applications can integrate with the blockchain module to access the blockchain module. Further, an administrator or operator of the platform 500 can manage users and blockchain services through a management console, and related data can be stored in a management console database module. In some embodiments, the administrator or operator of the platform 500 can access different users’ private chains through open remote procedure call (RPC) services of the users’ private chains for querying and transfer operations.

[0113] Figure 6 The containers in one user namespace in the platform 500 are shown more clearly. As Figure 6As shown, there are three container images. The first image is an ETH node image. This image includes an ETH module, an ETH API module, and an ETH browser module, which are arranged to provide core blockchain and API services. In this embodiment, the ETH module includes an Ethereum node and is used for functions such as setting up a private chain, synchronizing a ledger, managing accounts, and deploying smart contracts. In this embodiment, the ETH API module is used to interact with the Ethereum private chain for data submission / upload, transaction query, data verification, account and ether (cryptocurrency) management. In this embodiment, the ETH browser module is used for private chain viewing of blocks, transactions, accounts, and smart contracts. Through the browser module, information associated with the blockchain, such as block data, state data, transaction details, etc., can be intuitively presented to the user. The user can use the interface to upload data onto the chain and can quickly view the chain status. The second image is a database image. In this embodiment, the database image is used to provide MySQL and Redis database services. In this embodiment, the MySQL database is for the database of the blockchain service console, and it is used to store data such as Ethereum nodes, blocks, transactions, transfers, system users, roles, access control, and API access authentication. In this embodiment, the Redis database is a database that can facilitate the saving and reading of API access tokens for API access control, etc. The third image is a web API image, which in this embodiment is used to provide or allow access to the database and ETH API module through the service console.

[0114] Figure 7 A containerization framework 700 of one embodiment of the present invention is shown. In this embodiment, each user’s blockchain service system is packaged into a Docker image, which includes a blockchain node (ETH) image, a MySQL database image, and a web API image (for the service console). In one embodiment, the master node of the Kubernetes platform is arranged to deploy the images to different worker nodes to operate different blockchain service systems for different users.

[0115] Figure 8 is a schematic diagram of a blockchain service system 800 of one embodiment of the present invention. The blockchain service system 800 can be created based on any of the embodiments described above, or in other ways. The system 800 includes a blockchain network that is accessible by users via a user application and a blockchain API.

[0116] Figure 9 Various example operations 900 that can be performed by the blockchain service system 800 of Figure 8 are shown. These example operations 900 include a data upload operation 900A, a data query operation 900B, and a data verification operation 900C.

[0117] In the data upload operation 900A of the present embodiment, a user submits data to their blockchain through the application and the blockchain API. The data is submitted to the blockchain as a transaction. The chain will process the data using a consensus mechanism (e.g. authority proof consensus mechanism) to put the transaction / data on the blockchain. If the data is successfully uploaded onto the chain, the transaction hash associated with the transaction (upload of data) will be returned to the user. The data upload operation 900A can but does not have to be performed in real-time (at the same time as the data / transaction is submitted).

[0118] In the data query operation 900B of the present embodiment, a user submits a transaction hash to their blockchain through the application and the blockchain API to query whether the data associated with the transaction hash has been previously submitted to the blockchain. The chain will process the transaction hash and determine whether the data associated with the transaction hash has been previously submitted to the blockchain. If it is determined that the transaction hash has been previously submitted to the blockchain, the transaction information (time, details, etc.) and / or the data associated with the transaction is returned to the user.

[0119] In the data verification operation 900C of the present embodiment, a user submits a transaction hash and a set of data to be verified to their blockchain through the application and the blockchain API to query whether the data to be verified corresponds to the transaction hash. The chain will process the data and the transaction hash and determine whether the data to be verified corresponds to the transaction hash. If it is determined that the data corresponds to the transaction hash, the verification information (time, details, etc.) is returned to the user.

[0120] Figure 10A A data upload operation 1000A of an embodiment of the present application is shown. The operation 1000A can be performed by the blockchain service system 800 of Figure 8 In the present embodiment, a user must obtain an API access token from the system to initiate or operate the data upload API to perform the data upload operation 1000A. If an API access token is not obtained, the user cannot perform the data upload operation 1000A. If an API access token can be obtained, the user can perform the data upload operation 1000A. In some embodiments, the API access token is further checked for validity and only initiates or operates the data upload API if it is determined that the obtained token is valid (e.g. whether it corresponds to the latest token, whether it has expired, etc.).

[0121] The data upload operation 1000A generally includes receiving data to be uploaded to the blockchain, uploading the data or a representation of the data to the blockchain, and providing / returning a transaction hash if the data or the representation of the data is successfully uploaded to the blockchain. In some embodiments, the user needs to format the data into a form suitable for uploading to the blockchain through the system. In some embodiments, prior to uploading, the system can determine the size of the data to be uploaded to the blockchain. If the size of the data does not reach or exceed a threshold, the data can be uploaded to the blockchain. If the size of the data reaches or exceeds the threshold, a representation of the data (rather than the data) can be uploaded to the blockchain. In one example, the representation of the data is a hash value of the data. In another example, the representation of the data is a compressed or downsized version of the data. In yet another example, the representation of the data is a data portion of the data (segmented from the data).

[0122] Figure 10B The data query operation 1000B of one embodiment of the present application is shown. The operation 1000B can be performed by the blockchain service system 800 of Figure 8 In this embodiment, the user must obtain an API access token from the system to initiate or operate the data query API to perform the data query operation 1000B. If the API access token is not obtained, the user cannot perform the data query operation 1000B. If the API access token can be obtained, the user can perform the data query operation 1000B. In some embodiments, the API access token is further checked for validity and only the data query API is initiated or operated if it is determined that the obtained token is valid (e.g., whether it corresponds to the latest token, whether it has expired, etc.).

[0123] The data query operation 1000B generally includes receiving a transaction hash, and determining whether the data associated with the transaction hash is stored in the blockchain according to the transaction hash. In some embodiments, if the data associated with the transaction hash is stored in the blockchain, the data associated with the transaction hash is provided or returned to the user. In some embodiments, if the data associated with the transaction hash is not stored in the blockchain, a corresponding result or notification is provided to the user.

[0124] Figure 10C The data verification operation 1000C of one embodiment of the present application is shown. The operation 1000C can be performed by the blockchain service system 800 of Figure 8The blockchain service system 800 executes. In this embodiment, a user must obtain an API access token from the system to initiate or operate the data verification API to perform the data verification operation 1000C. If an API access token is not obtained, the user cannot perform the data verification operation 1000C. If an API access token can be obtained, the user can perform the data verification operation 1000C. In some embodiments, the API access token is further checked for validity and only initiated or operated the data verification API if it is determined that the obtained token is valid (e.g., whether it corresponds to the latest token, whether it has expired, etc.).

[0125] The data verification operation 1000C generally includes receiving a transaction hash and data to be verified, and determining whether the data to be verified matches the data stored in the blockchain according to the transaction hash. In some embodiments, if the data does not match the data stored in the blockchain, a corresponding result or notification is provided to the user. In some embodiments, if the data matches the data stored in the blockchain, a corresponding result or notification is provided to the user.

[0126] Figure 11 FIG. 11 is a screenshot 1100 of a user interface of a blockchain management console of an embodiment. As described above, the blockchain management console enables an operator or administrator of the blockchain service system to manage different users or blockchains or blockchain services of the system. The blockchain management console can provide a variety of functions, such as viewing blockchain information statistics and Kubernetes platform statistics, facilitating creation of user-specific blockchain service systems, facilitating deployment of blockchain service systems, allowing user and blockchain / blockchain service management for different users, account (funds) management, etc.

[0127] Figure 12 FIG. 12 is a screenshot 1200 of a user interface of a blockchain service console of an embodiment. As described above, the blockchain service console enables each user to manage and / or operate their own blockchain service system. The blockchain service console can provide a variety of functions, such as viewing blockchain information and data upload statistics, monitoring container resource usage of the user’s blockchain service, facilitating verification and tracking of uploaded data, managing token transfers, etc.

[0128] Figure 13 FIG. 13 is a screenshot 1300 of a user interface of a cryptocurrency explorer of an embodiment. As described above, the cryptocurrency explorer (e.g., ETH explorer) enables each user to view cryptocurrency information associated with their blockchain. The cryptocurrency explorer can provide a variety of functions, such as viewing blockchain node information, block information, transaction information, blockchain account information, etc.

[0129] Figure 14is an example application 1400 of a blockchain service system of one embodiment of the present application. The blockchain service system can be created and / or operated based on any of the above embodiments. In this application 1400, the blockchain service system is integrated with a corporate travel and leave record system for recording travel and leave records of employees of a corporation.

[0130] Figure 15 is a blockchain service system creation and / or operation platform 1500 of one embodiment. The platform 1500 generally includes a container orchestration platform that operates various blockchain services (blockchain service systems) and a blockchain management console that is operatively connected with the container orchestration platform. The platform 1500 can be based on the platform 300, 400, 500, etc.

[0131] Figure 16 An example information processing system 1600 of one embodiment of the present application is shown, which can be used as a server or another type of information processing system. In some embodiments, the information processing system 1600 can be used to implement (partially or wholly) systems and / or methods of the present application. For example, the information processing system 1600 can be used as at least a portion of a blockchain service system creation and / or operation platform, at least a portion of a blockchain service system creation and / or operation system, at least a portion of a cloud computing network, at least a portion of a blockchain network, etc.

[0132] The information processing system 1600 generally includes appropriate components needed to receive, store, and execute appropriate computer instructions, commands, and / or code. The main components of the information processing system 1600 are a processor 1602 and a memory 1604. The processor 1602 can include one or more of a CPU, a MCU, a logic circuit, a Raspberry Pi chip, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and / or any one or more digital or analog circuits / circuitries configured to interpret and / or execute program instructions and / or process signals and / or information and / or data. The memory 1604 can include one or more volatile memory (e.g., RAM, DRAM, SRAM), one or more non-volatile memory (e.g., ROM, PROM, EPROM, EEPROM, FRAM, MRAM, FLASH, SSD, NAND, NVDIMM), or any combination thereof. Appropriate computer instructions, commands, code, information, and / or data can be stored in the memory 1604. Computer instructions for performing or facilitating performance of the method embodiments of the present application can be stored in the memory 1604. The processor 1602 and the memory 1604 can be integrated or separate (and operatively connected). Optionally, the information processing system 1600 further includes one or more input devices 1606. Examples of the input devices 1606 include a keyboard, a mouse, a stylus, an image scanner, a microphone, a tactile / touch input device (e.g., a touch-sensitive screen), an image / video input device (e.g., a camera), and the like. Optionally, the information processing system 1600 further includes one or more output devices 1608. Examples of the output devices 1608 include a display (e.g., a monitor, a screen, a projector, and the like), a speaker, a headphone, a headset, a printer, an additive manufacturing machine (e.g., a 3D printer), and the like. The display can include an LCD display, an LED / OLED display, or other suitable display, which can or can not be touch-sensitive. The information processing system 1600 can further include one or more disk drives 1612, which can include one or more of a solid-state drive, a hard disk drive, an optical drive, a flash drive, a tape drive, and the like. A suitable operating system can be installed in the data processing system 1600, e.g., in the disk drive 1612 or the memory 1604. The memory 1604 and the disk drive 1612 can be operated by the processor 1602. Optionally, the information processing system 1600 further includes a communication device 1610 for communicating with other devices, such as a server, a personal computer, a terminal, a tablet, a telephone, a watch, an Internet of Things (IoT) device, or other wireless computing devices.The communication device 1610 can include one or more of a modem, a network interface card (NIC), an integrated network interface, a NFC transceiver, a ZigBee transceiver, a Wi-Fi transceiver, a Bluetooth transceiver, a radio frequency transceiver, a cellular (2G, 3G, 4G, 5G, 5G+, etc.) transceiver, an optical port, an infrared port, a USB connection, or other wired or wireless communication interfaces. The transceiver(s) can be implemented by one or more devices (integrated transmitters and receivers, separate transmitters and receivers, etc.). The communication links can be wired or wireless and can transmit commands, instructions, information, and / or data. In one example, the processor 1602, the memory 1604 (and optionally the input device 1606, the output device 1608, the communication device 1610, and the disk drive 1612, if present), are connected to each other by a bus. In one embodiment, at least some of these components can be connected wirelessly, e.g., over a network such as the Internet or a cloud computing network. As will be appreciated by those skilled in the art, Figure 16 The information handling system 1600 shown in FIG. 16 is simply an example and in other embodiments the information handling system 1600 can have a different configuration (e.g., include additional components, have fewer components, etc.). In one example, the information handling system 1600 can include 3 virtual machines, 8 core CPU, 8 GB memory, 500 GB storage, network cards, a Linux CentOS 7+ operating system, and various tools such as OutSystems, GoEthereum, Ethereum-Block-Explorer (Python version), Redis database, Flask, Nodejs, MySQL database, Docker, Kubernetes, etc.

[0133] The system and method embodiments of the present application can provide various features and advantages. In some embodiments, the system and method can provide a highly integrated API. Specifically, the system and method can provide a series of integrated APIs for a blockchain service system that enable users to easily implement blockchain-based data upload, tracking, and verification functionalities. In some embodiments, the system and method can support uploading large size data to a blockchain. Specifically, the data upload API can automatically split large size data before upload to facilitate different data upload requirements. In some embodiments, the system and method can provide a convenient and flexible way to deploy and operate a blockchain service system. Specifically, the system and method can provide easy access, dynamic resource creation and scalability, and multi-dimensional security mechanisms. The system and method can also provide flexibility in terms of cost (customized for different users). In some embodiments, the system and method can provide user-specific spaces. Specifically, each user’s blockchain service system is deployed in a separate space (separated from other users), which helps to facilitate the independence and autonomy of the blockchain service users. In some embodiments, the system and method can enable fast delivery (creation and deployment) of a blockchain service system. In one example, the entire creation and deployment process can take less than 1 hour (e.g., 10 minutes) and does not require or substantially require user intervention (except for necessary user input). The system and method can facilitate simple and easy creation and deployment of a blockchain environment according to the specific needs of a user, can provide fast service delivery, and can enable a user-friendly interface (e.g., GUI) for the management and operation of the blockchain. The system and method can alleviate or eliminate the burden of users to create a blockchain or use blockchain technology. It should be noted that some embodiments of the present application can include other or further advantages not specifically mentioned here.

[0134] Although not required, the embodiments described with reference to the figures can be implemented as an application programming interface (API) or a series of libraries for use by developers or can be included in another software application (which operates in a terminal or computer operating system or portable computing device operating system, for example). In general, as will be apparent to those of ordinary skill in the art, the functions of the software application can be distributed in multiple routines, objects, and / or components to achieve the same functions described herein, as the program modules include routines, programs, objects, components, and data files that help perform particular functions.

[0135] It should also be appreciated that where the methods and systems of embodiments of the application are implemented wholly or partially by a computing system, any suitable computing system architecture can be utilized, including stand-alone computers, networked computers, special-purpose or non-special-purpose hardware devices, etc. The terms "computing system" and "computing device" (or similar terms) are intended to encompass, without limitation, computers or information processing hardware of any suitable arrangement capable of implementing the described functionality.

[0136] Those skilled in the art will appreciate that different variations and / or modifications (additions or omissions) of the application as described in the particular implementations can be made without departing from the scope of the application. Thus, the described implementations of the application are to be considered in all respects as illustrative and not restrictive. Exemplary optional features of some aspects of the application are set forth in the SUMMARY. Some implementations of the application can include one or more of these optional features (some of which are not specifically shown in the drawings). Some implementations of the application can lack one or more of these optional features (some of which are not specifically shown in the drawings). One or more features of one implementation can be combined with one or more features of another implementation to provide further implementations of the application. Some implementations of the application do not limit the container orchestration platform to the Kubernetes platform (but can be other alternatives to Kubernetes). Some implementations of the application do not limit the image or container image to the Docker image (but can be other alternatives to Docker). Some implementations of the application do not limit the blockchain to the Ethereum-based blockchain (but can be based on other cryptography or technology). Some implementations of the application do not limit the blockchain to a private blockchain (but can be a public blockchain).

Claims

1. A method of creating and / or operating a blockchain service system for users, characterized by, The method comprises: (a) receiving user input, the user input comprising configuration information associated with a blockchain service system; and (b) based on receiving the user input, creating a blockchain service system for a user, the blockchain service system comprising a blockchain hosted in a computing network and one or more tools for operating and managing the blockchain; The step (b) comprises: creating a namespace for the user on a Kubernetes container orchestration platform; creating one or more containers associated with the one or more tools in the namespace based on one or more predetermined Docker images, wherein the one or more tools comprise a user interface or one or more APIs, and wherein different namespaces for different users and their respective one or more containers are segregated; wherein the blockchain service system for each user is packaged as a unified Docker image comprising a blockchain node image, a MySQL database image, and a web API image for supporting blockchain operations, data storage, and user interface functionalities; wherein the Kubernetes container orchestration platform is operable to facilitate operations of the blockchain service system; performing operations using the blockchain service system; the operations comprising a data upload operation, the data upload operation comprising: receiving data to be uploaded to the blockchain, uploading the data or a representation of the data to the blockchain, and providing a transaction hash if the data or the representation of the data is successfully uploaded to the blockchain; prior to uploading the data or the representation of the data to the blockchain: determining a size of the data to be uploaded to the blockchain, uploading the data to the blockchain if it is determined that the size of the data does not reach or exceed a threshold, and uploading a representation of the data to the blockchain if it is determined that the size of the data reaches or exceeds a threshold; if it is determined that the size of the data reaches or exceeds a threshold: determining a hash value of the data, and uploading the hash value to the blockchain, wherein the hash value is a representation of the data; splitting the data into a plurality of data portions, each of the data portions having a size within the threshold; and uploading the plurality of data portions to the blockchain, wherein the plurality of data portions are representations of the data.

2. The method of claim 1, wherein, The one or more containers comprise one or more of: a database container having one or more database modules for facilitating access to one or more databases associated with the blockchain service system; an API container comprising a web service API module; and a blockchain operations container having a blockchain module, a blockchain API module, and a cryptocurrency explorer module.

3. The method of claim 2, wherein, The one or more database modules comprise: a first database module for storing blockchain service related data; and a second database module for storing API related data.

4. The method of claim 1, wherein, The step (b) comprises: based on the user input, initializing a plurality of blockchain nodes for the blockchain; and configuring a blockchain based on the initialized blockchain nodes.

5. The method of claim 1, wherein, The configuration information includes: information regarding a number of blockchain nodes required for the blockchain service system; and / or information associated with resource limitations and / or requirements of the blockchain service system.

6. The method of claim 5, wherein, The resource limitations and / or requirements include: processor limitations and / or requirements; memory or storage limitations and / or requirements; and / or disk drive limitations and / or requirements.

7. The method of claim 1, wherein, The one or more APIs are configured to facilitate access to and operation of the blockchain.

8. The method of claim 7, wherein, The one or more APIs are operable to facilitate: uploading data to the blockchain, verifying data based on data stored in the blockchain, and querying data stored in the blockchain.

9. The method of claim 1, wherein, The user interface is configured to facilitate user operation and / or management of the blockchain; wherein the user interface is operable to display data, blocks, transactions, accounts, cryptocurrencies, usage information, and / or smart contracts associated with the blockchain and / or the blockchain service system.

10. The method of claim 1, wherein, The blockchain is an Ethereum-based blockchain.

11. The method of claim 1, wherein, The blockchain is a private blockchain.

12. The method of claim 1, wherein, The computing network includes a distributed computing network or a cloud computing network.

13. The method of claim 1, wherein, The data upload operation further includes: prior to uploading the data or the representation of the data to the blockchain: obtaining a token for allowing use of an API to facilitate uploading the data to the blockchain; and allowing use of the API to upload the data to the blockchain only if the token is obtained.

14. The method of claim 1, wherein, The data upload operation further includes: prior to uploading the data or the representation of the data to the blockchain: obtaining a token for allowing use of an API to facilitate uploading the data to the blockchain; determining validity of the token; and allowing use of the API to upload the data to the blockchain only if the token is determined to be valid.

15. The method of claim 1, wherein, The operations include a data verification operation, the data verification operation including: receiving a transaction hash and data to be verified; and determining, based on the transaction hash, whether the data to be verified matches data stored in the blockchain.

16. The method of claim 15, wherein, The data verification operation further includes: if it is determined that the data to be verified does not match the data stored in the blockchain, providing a result indicating that there is a discrepancy between the data and the data stored in the blockchain; and if it is determined that the data to be verified matches the data stored in the blockchain, providing a corresponding result or notification indicating that the data matches the data stored in the blockchain.

17. The method of claim 1, wherein, The operations include a data query operation, the data query operation including: receiving a transaction hash; and determining, based on the transaction hash, whether data associated with the transaction hash is stored in the blockchain.

18. The method of claim 17, wherein, The data query operation further includes: if it is determined that data associated with the transaction hash is stored in the blockchain, providing the data associated with the transaction hash; and if it is determined that data associated with the transaction hash is not stored in the blockchain, providing a respective result or notification indicating that data associated with the transaction hash is not stored in the blockchain. 19.A system for creating and / or operating a blockchain service system for users, characterized by, The system comprises: one or more processors, and a memory storing one or more programs configured for execution by the one or more processors, the one or more programs comprising instructions for performing or facilitating performance of the method of any one of claims 1 to 18.

Images