CN112214502A - User contract deployment method, device, system and storage medium of alliance chain - Google Patents
User contract deployment method, device, system and storage medium of alliance chain Download PDFInfo
- Publication number
- CN112214502A CN112214502A CN202010888952.7A CN202010888952A CN112214502A CN 112214502 A CN112214502 A CN 112214502A CN 202010888952 A CN202010888952 A CN 202010888952A CN 112214502 A CN112214502 A CN 112214502A
- Authority
- CN
- China
- Prior art keywords
- contract
- user
- deployment
- deployed
- user contract
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a user contract deployment method, a device, a system and a storage medium of a coalition chain, wherein the method not only considers whether a user contract with the same name is deployed on the coalition chain, but also considers the condition that the user contract is possibly upgraded and deployed except for name conflict if the user contract with the same name is deployed on the coalition chain, so whether the user contract is allowed to be deployed or not is determined by comparing whether the deployed user contract is consistent with a CA (certificate Authority) identifier of a client used by the user contract required to be deployed; in addition, the invention not only deploys the user contract on the alliance chain, but also records and links the deployment content of the user contract, therefore, the invention not only can avoid the conflict of the user contract names, but also can avoid the malicious upgrade deployment of the user contract.
Description
Technical Field
The present invention relates to a block chain technology, and in particular, to a method, an apparatus, a system, and a storage medium for deploying a user contract of a federation chain.
Background
Currently, user contract management of a federation chain is generally performed by a management node, and in a federation chain scenario in which a user can freely select a node to deploy a user contract, a user contract name conflict may occur. Since the blockchain transaction data generated by the user contracts are distinguished by contract names in the state library, the contract names cannot be modified once used, otherwise, the historical transaction data cannot be associated, and if the user contract names conflict, the transaction data generated between the user contracts with conflicting names is mixed up, and even the data is covered. Therefore, there is a need to design a user contract management mechanism for a federation chain to avoid user contract name conflicts.
Disclosure of Invention
In view of the above-mentioned deficiencies of the prior art, the present invention aims to: the utility model provides a user contract deployment method of alliance chain, can avoid taking place user contract name conflict.
In order to achieve the purpose, the invention provides the following technical scheme:
a federation chain user contract deployment method, the method comprising the steps of:
configuring nodes on a alliance chain, and responding to a deployment request sent by a client; wherein the deployment request includes content of a user contract requesting deployment;
when the node responds to the deployment request, whether a user contract with the same name is deployed on the alliance chain is detected; if the user contracts with the same name are not deployed, the corresponding user contracts are allowed to be deployed; if the user contracts with the same name are deployed, judging whether the deployed user contracts are consistent with CA identifications of clients used by the user contracts requesting to be deployed, and if so, allowing the corresponding user contracts to be deployed; if not, refusing to deploy the corresponding user contract;
and configuring a node on the alliance chain, and after the corresponding user contract is allowed to be deployed, deploying the user contract on the alliance chain, and recording the deployed content of the user contract in uplink.
According to a specific implementation manner, the method for deploying the user contract of the federation chain of the present invention further includes configuring a node on the federation chain, for recording the deployment content of the user contract on the uplink after allowing to deploy the corresponding user contract; wherein the deployment record includes content of the user contract and a CA identification of a client used by the user contract deployment.
Further, the CA identification is automatically generated by the client upon registration with a CA.
According to a specific implementation mode, the user contract deployment method of the alliance chain further comprises the steps of configuring a leader node of the alliance chain, and sending prompt information of contract name conflict to the client side after a node refuses to deploy a corresponding user contract.
According to a specific implementation mode, in the federation chain user contract deployment method of the present invention, the user contract is deployed on a federation chain, and the method includes the following steps:
reading the content of the user contract by calling a deployment interface of a system contract;
checking the content of the user contract by pre-compiling the user contract, and saving the content of the user contract after the pre-compiling is successful;
after the pre-compiling is successful, initiating a consensus voting for deploying the user contract, and after the consensus voting passes, regularly reading a contract deployment state record table, and checking whether the user contract is successfully deployed; if the user contract is not deployed successfully, starting a new contract container, loading the content of the user contract into the contract container after the contract container is started successfully, and initializing the running environment of the user contract; wherein the contract deployment state record table is updated by monitoring the deployment state of the user contract.
According to a specific implementation mode, in the user contract deployment method of the alliance chain, nodes on the alliance chain are also configured, and a contract deployment state query request sent by a client side is responded; and when the node responds to the contract deployment state query request, a query interface of a system contract is called, the contract deployment state record table is accessed, and a query result is returned to the client.
In another aspect of the present invention, there is provided a federation chain user contract deployment apparatus, the apparatus comprising:
the response module is used for responding to the deployment request sent by the client; wherein the deployment request includes content of a user contract requesting deployment; when the node responds to the deployment request, whether a user contract with the same name is deployed on the alliance chain is detected; if the user contracts with the same name are not deployed, the corresponding user contracts are allowed to be deployed; if the user contracts with the same name are deployed, judging whether the deployed user contracts are consistent with CA identifications of clients used by the user contracts requesting to be deployed, and if so, allowing the corresponding user contracts to be deployed; if not, refusing to deploy the corresponding user contract;
the deployment module is used for deploying the user contracts on the alliance chain after the corresponding user contracts are allowed to be deployed;
and the recording module is used for recording the uplink of the deployment content of the user contract after the corresponding user contract is allowed to be deployed.
According to a specific implementation manner, in the device for deploying user contracts in a federation chain of the present invention, the deployment module further includes:
the reading submodule is used for reading the content of the user contract by calling a deployment interface of a system contract;
the pre-compiling sub-module is used for pre-compiling the user contract to check the content of the user contract and storing the content of the user contract after the pre-compiling is successful;
the deployment initiation submodule is used for initiating the consensus voting for deploying the user contract after the pre-compiling is successful;
the timing task submodule is used for regularly reading the contract deployment state record table after the consensus vote passes, and checking whether the user contract is successfully deployed; if the user contract is not deployed successfully, starting a new contract container, loading the content of the user contract into the contract container after the contract container is started successfully, and initializing the running environment of the user contract;
and the deployment recording submodule is used for monitoring the deployment state of the user contract and updating the contract deployment state recording table.
In another aspect of the present invention, there is also provided a system for deploying a user contract of a federation chain, the system including: the client and the user contract deployment device of the alliance chain are respectively deployed on each node of the alliance chain.
In another aspect of the present invention, there is also provided a readable storage medium having one or more programs stored thereon, wherein the one or more programs, when executed by one or more processors, implement the method for deploying user contracts in a federation chain of the present invention.
Compared with the prior art, the invention has the beneficial effects that:
1. in the deployment process, the invention not only considers whether the alliance chain is deployed with the user contract with the same name, but also considers the situation that the user contract is possibly upgraded and deployed except for name conflict when the alliance chain is deployed with the user contract with the same name, so whether the user contract is allowed to be deployed or not is determined by comparing whether the deployed user contract is consistent with the CA (certificate Authority) identifier of the client used by the user contract which is requested to be deployed; therefore, the invention not only can avoid the conflict of the user contract names, but also can avoid the malicious upgrade and deployment of the user contracts.
2. The invention discloses a user contract deployment method of a alliance chain.A node on the alliance chain links a deployment content record of a user contract after allowing deployment of a corresponding user contract, and the deployment record comprises the content of the user contract and a CA (certificate Authority) identifier of a client used by the user contract in deployment. Therefore, the invention also utilizes the non-tampering characteristic of the block chain to chain the deployment records, thereby improving the safety and traceability of the user contract deployment.
Drawings
FIG. 1 is a diagram of the interaction architecture of a federation chain network and a client of the present invention;
FIG. 2 is a flow chart of the interaction between the client and the node according to the present invention;
FIG. 3 is a flow chart of a node responding to a deployment request of the present invention; (ii) a
FIG. 4 is a flow diagram of a method for deploying a user contract in accordance with the present invention;
FIG. 5 is a flowchart illustrating interaction between a client and a node according to an embodiment of the present invention;
FIG. 6 is a schematic structural view of a deployment device of the present invention;
FIG. 7 is a schematic structural diagram of a deployment module of the present invention;
fig. 8 is a schematic structural diagram of the deployment system of the present invention.
Detailed Description
The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention.
As shown in fig. 1, taking an existing federation chain scenario in which a user can freely select a node to deploy a user contract as an example, a client 10 may directly send a deployment request to any node in the federation chain, and at the same time, deployment of the user contract may be implemented by invoking a deployment interface of a system contract. However, in this open contract deployment mode, there are cases where the contract names collide to cause confusion and even loss of transaction data.
Therefore, the user contract deployment method of the alliance chain comprises the following steps:
configuring nodes on a alliance chain, and responding to a deployment request sent by a client; wherein the deployment request includes content of a user contract requesting deployment;
when the node responds to the deployment request, whether a user contract with the same name is deployed on the alliance chain is detected; if the user contracts with the same name are not deployed, the corresponding user contracts are allowed to be deployed; if the user contracts with the same name are deployed, judging whether the deployed user contracts are consistent with CA identifications of clients used by the user contracts requesting to be deployed, and if so, allowing the corresponding user contracts to be deployed; if not, refusing to deploy the corresponding user contract;
and configuring a node on the alliance chain, and after the corresponding user contract is allowed to be deployed, deploying the user contract on the alliance chain, and recording the deployed content of the user contract in uplink.
The CA (certification authority) digital certificate authority is used for automatically generating a CA identifier when a client registers in the CA. The client 10 is developed on an SDK supporting a calling system contract, and the SDK incorporates an ip address of each node, a signature algorithm, and the like.
Specifically, based on the federation chain user contract deployment method of the present invention, the interaction flow of the client and the node in the deployment process is shown in fig. 2:
performing, by the client, S100: sending a deployment request to the node 1, and after receiving the deployment request, the node 1 immediately performs S100 a: the deployment request is broadcast to other nodes on the federation chain, and then node 1 performs S200: responding to the deployment request; then, according to the response result, i.e. if the corresponding user contract is allowed to be deployed, S300 is performed by the node 1: the corresponding user contract is deployed on the federation chain.
Similarly, after receiving the deployment request, the node 2 or other nodes respond to the deployment request, and deploy the corresponding user contract on the federation chain according to the response result, that is, if the corresponding user contract is allowed to be deployed.
As shown in fig. 3, the process of the node 1 executing S200 is as follows:
s201: detecting whether a user contract with the same name is deployed on a alliance chain; if the user contracts with the same name are not deployed, the corresponding user contracts are allowed to be deployed, and the step is shifted to S203;
if the user contracts with the same name are deployed, continuing to execute S202, namely judging whether the deployed user contracts are consistent with the CA identifications of the clients used by the user contracts requesting to be deployed, and if so, allowing the deployment of the corresponding user contracts to jump to S203; if not, refusing to deploy the corresponding user contract, and jumping to S204.
As shown in fig. 4, the process of the node 1 executing S300 is as follows:
firstly, reading the content of a user contract by calling a deployment interface of a system contract;
then, a user contract is pre-compiled to check the content of the user contract, so that the grammar, the safety and the like of the user contract are ensured; if the pre-compiling is successful, the content of the user contract is stored, and if the pre-compiling is failed, the deployment is finished.
And after the pre-compiling is successful, initiating consensus voting for deploying the user contract, and after the consensus voting passes, deploying the user contract.
Considering that the user contract can not be guaranteed to be deployed successfully at one time, after the consensus vote passes, a timing task is set to check whether the user contract is successful or not at regular time, and if the user contract is not successfully deployed, the user contract is continuously deployed.
The timing task is specifically as follows: firstly, judging whether the time from the last time of reading a contract deployment state record table reaches delta t, if so, reading the contract deployment state record table, and checking whether the user contract is successfully deployed;
and if the user contract is successfully deployed, ending the deployment.
If the user contract is not deployed successfully, starting new contract containers in sequence, loading the content of the user contract into the contract container after the contract container is started successfully, and initializing the operating environment of the user contract.
Meanwhile, the contract deployment state recording table in the invention is updated by monitoring the deployment state of the user contract.
In a specific embodiment, the method for deploying user contracts of a federation chain of the present invention further includes configuring a node on the federation chain, for recording uplink deployment content of the user contract after allowing deployment of a corresponding user contract; wherein the deployment record includes content of the user contract and a CA identification of a client used by the user contract deployment.
As shown in fig. 5, after the node 1 responds to the deployment request, according to the response result, that is, if the corresponding user contract is allowed to be deployed, the node 1 performs S300 a: and linking the content of the user contract and the CA identification record of the client used for deploying the user contract. Therefore, once the user contract deployment is completed, the content of the user contract deployment and the CA identification of the client are not falsifiable, and the safety and traceability of the user contract deployment are improved.
Furthermore, the user contract deployment method of the alliance chain also configures nodes on the alliance chain, and responds to a contract deployment state query request sent by a client; and when the node responds to the deployment request, calling a query interface of a system contract, accessing the contract deployment state record table and returning a query result to the client.
Specifically, the client executes S400: sending a contract deployment state query request to the node 1, responding to the contract deployment state query request by the node 1, calling a query interface of a system contract, accessing a contract deployment state record table, and executing S500: and returning the query result to the client.
In another embodiment, the method for deploying the user contracts in the federation chain further includes configuring a leader node of the federation chain, and sending prompt information of contract name conflict to the client after a node refuses to deploy a corresponding user contract. If the leader node exists in the alliance chain, through the method, when the contract names conflict, the developer is prompted to modify the contract names.
As shown in fig. 6, the present invention provides a device for deploying a user contract of a federation chain, configured to be deployed on each node of the federation chain, where the device includes:
a response module 100, configured to respond to a deployment request sent by a client; wherein the deployment request includes content of a user contract requesting deployment; when the node responds to the deployment request, whether a user contract with the same name is deployed on the alliance chain is detected; if the user contracts with the same name are not deployed, the corresponding user contracts are allowed to be deployed; if the user contracts with the same name are deployed, judging whether the deployed user contracts are consistent with CA identifications of clients used by the user contracts requesting to be deployed, and if so, allowing the corresponding user contracts to be deployed; if not, refusing to deploy the corresponding user contract;
a deployment module 300 configured to deploy the user contracts on a federation chain after allowing deployment of the corresponding user contracts;
a recording module 200, configured to record uplink the deployment content of the user contract after allowing the corresponding user contract to be deployed.
In the apparatus for deploying user contracts in a federation chain of the present invention, if the response result obtained by the response module 100 is that the corresponding user contract is allowed to be deployed, the recording module 200 may firstly chain the deployment content record of the user contract, where the deployment record includes the content of the user contract and the CA identifier of the client used for deployment of the user contract, and then the deployment module 300 deploys the user contract on the federation chain.
Further, as shown in fig. 7, the deployment module 300 further includes:
the reading sub-module 310 is configured to read the content of the user contract by invoking a deployment interface of a system contract;
a pre-compiling sub-module 320, configured to pre-compile the user contract to check the content of the user contract, and store the content of the user contract after the pre-compiling is successful;
the deployment initiation submodule 330 is configured to initiate consensus voting for deploying the user contract after the pre-compilation is successful;
the timing task sub-module 340 is configured to read the contract deployment state record table in a timing manner after the consensus vote passes, and check whether the user contract is successfully deployed; if the user contract is not deployed successfully, starting a new contract container, loading the content of the user contract into the contract container after the contract container is started successfully, and initializing the running environment of the user contract;
and the deployment recording sub-module 350 is configured to monitor a deployment state of the user contract and update the contract deployment state recording table.
As shown in fig. 8, the present invention further provides a federation chain user contract deployment system, which includes a client 10 and federation chain user contract deployment apparatuses 20 respectively deployed at nodes of the federation chain. Wherein the number of clients 10 may be plural.
The present invention also provides a readable storage medium having stored thereon one or more programs which, when executed by one or more processors, implement the federation chain user contract deployment method of the present invention.
It should be understood that the disclosed system may be implemented in other ways. For example, the division of the modules into only one logical function may be implemented in another way, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the communication connection between the modules may be an indirect coupling or communication connection through some interfaces, devices or units, and may be electrical or in other forms.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each module may exist alone physically, or two or more modules are integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
Claims (10)
1. A user contract deployment method of a federation chain is characterized by comprising the following steps:
configuring nodes on a alliance chain, and responding to a deployment request sent by a client; wherein the deployment request includes content of a user contract requesting deployment;
when the node responds to the deployment request, whether a user contract with the same name is deployed on the alliance chain is detected; if the user contracts with the same name are not deployed, the corresponding user contracts are allowed to be deployed; if the user contracts with the same name are deployed, judging whether the deployed user contracts are consistent with CA identifications of clients used by the user contracts requesting to be deployed, and if so, allowing the corresponding user contracts to be deployed; if not, refusing to deploy the corresponding user contract;
and configuring nodes on the federation chain for deploying the user contracts on the federation chain after allowing deployment of the corresponding user contracts.
2. A federation chain user contract deployment method as claimed in claim 1 wherein a node on the federation chain is configured to chain up the deployment content records of the user contract after allowing deployment of the corresponding user contract; wherein the deployment record includes content of the user contract and a CA identification of a client used by the user contract deployment.
3. A federation chain user contract deployment method as claimed in claim 2 wherein the CA identity is automatically generated by the client registering with a CA.
4. The method for deploying user contracts in a alliance chain as claimed in claim 1, wherein a leader node of the alliance chain is configured, and when the nodes refuse to deploy corresponding user contracts, prompt information of contract name conflict is sent to the client.
5. A federation chain user contract deployment method as claimed in any one of claims 1 to 4 wherein deploying the user contract on a federation chain comprises the steps of:
reading the content of the user contract by calling a deployment interface of a system contract;
checking the content of the user contract by pre-compiling the user contract, and saving the content of the user contract after the pre-compiling is successful;
after the pre-compiling is successful, initiating a consensus voting for deploying the user contract, and after the consensus voting passes, regularly reading a contract deployment state record table, and checking whether the user contract is successfully deployed; if the user contract is not deployed successfully, starting a new contract container, loading the content of the user contract into the contract container after the contract container is started successfully, and initializing the running environment of the user contract; wherein the contract deployment state record table is updated by monitoring the deployment state of the user contract.
6. The federation chain user contract deployment method of claim 5, further configuring nodes on the federation chain, responding to a contract deployment state query request sent by a client; and when the node responds to the contract deployment state query request, a query interface of a system contract is called, the contract deployment state record table is accessed, and a query result is returned to the client.
7. A federation chain user contract deployment apparatus for deployment at each node of a federation chain, comprising:
the response module is used for responding to the deployment request sent by the client; wherein the deployment request includes content of a user contract requesting deployment; when the node responds to the deployment request, whether a user contract with the same name is deployed on the alliance chain is detected; if the user contracts with the same name are not deployed, the corresponding user contracts are allowed to be deployed; if the user contracts with the same name are deployed, judging whether the deployed user contracts are consistent with CA identifications of clients used by the user contracts requesting to be deployed, and if so, allowing the corresponding user contracts to be deployed; if not, refusing to deploy the corresponding user contract;
the deployment module is used for deploying the user contracts on the alliance chain after the corresponding user contracts are allowed to be deployed;
and the recording module is used for recording the uplink of the deployment content of the user contract after the corresponding user contract is allowed to be deployed.
8. A federation chain user contract deployment apparatus as recited in claim 7, wherein the deployment module further comprises:
the reading submodule is used for reading the content of the user contract by calling a deployment interface of a system contract;
the pre-compiling sub-module is used for pre-compiling the user contract to check the content of the user contract and storing the content of the user contract after the pre-compiling is successful;
the deployment initiation submodule is used for initiating the consensus voting for deploying the user contract after the pre-compiling is successful;
the timing task submodule is used for regularly reading the contract deployment state record table after the consensus vote passes, and checking whether the user contract is successfully deployed; if the user contract is not deployed successfully, starting a new contract container, loading the content of the user contract into the contract container after the contract container is started successfully, and initializing the running environment of the user contract;
and the deployment recording submodule is used for monitoring the deployment state of the user contract and updating the contract deployment state recording table.
9. A federation chain user contract deployment system, characterised by a client and federation chain user contract deployment means as claimed in claim 7 or claim 8 deployed on respective nodes of the federation chain.
10. A readable storage medium having one or more programs stored thereon, wherein the one or more programs, when executed by one or more processors, implement the federation chain user contract deployment method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010888952.7A CN112214502B (en) | 2020-08-28 | 2020-08-28 | User contract deployment method, device and system of alliance chain and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010888952.7A CN112214502B (en) | 2020-08-28 | 2020-08-28 | User contract deployment method, device and system of alliance chain and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112214502A true CN112214502A (en) | 2021-01-12 |
| CN112214502B CN112214502B (en) | 2023-07-07 |
Family
ID=74059483
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010888952.7A Active CN112214502B (en) | 2020-08-28 | 2020-08-28 | User contract deployment method, device and system of alliance chain and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112214502B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113159682A (en) * | 2021-04-22 | 2021-07-23 | 上海卓钢链科技有限公司 | Electronic warehouse receipt information alliance chain system |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107943950A (en) * | 2017-11-24 | 2018-04-20 | 中钞***产业发展有限公司杭州区块链技术研究院 | The method and system that data intelligence contract generates in a kind of block chain |
| CN109493072A (en) * | 2018-10-24 | 2019-03-19 | 杭州趣链科技有限公司 | A method of the privacy contract protection based on alliance's block chain |
| CN110163607A (en) * | 2019-05-10 | 2019-08-23 | 南京邮电大学 | The personal reference method of college student number based on block chain intelligence contract |
| CN110555773A (en) * | 2019-08-09 | 2019-12-10 | 腾讯科技（深圳）有限公司 | contract conflict detection method and device, readable storage medium and computer equipment |
| CN110599069A (en) * | 2019-09-29 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Application evaluation method and device based on block chain network |
| CN110990891A (en) * | 2019-11-29 | 2020-04-10 | 山东爱城市网信息技术有限公司 | Gymnasium contract proving method, equipment and medium based on block chain |
| CN111176668A (en) * | 2019-12-30 | 2020-05-19 | 支付宝(杭州)信息技术有限公司 | Predicter deployment method, device, electronic equipment and storage medium |
| US10673617B1 (en) * | 2018-04-24 | 2020-06-02 | George Antoniou | Methods, system and point-to-point encryption device microchip for AES-sea 512-bit key using identity access management utilizing blockchain ecosystem to improve cybersecurity |
| CN111353176A (en) * | 2020-05-22 | 2020-06-30 | 支付宝(杭州)信息技术有限公司 | Method and system for inquiring block chain data |
-
2020
- 2020-08-28 CN CN202010888952.7A patent/CN112214502B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107943950A (en) * | 2017-11-24 | 2018-04-20 | 中钞***产业发展有限公司杭州区块链技术研究院 | The method and system that data intelligence contract generates in a kind of block chain |
| US10673617B1 (en) * | 2018-04-24 | 2020-06-02 | George Antoniou | Methods, system and point-to-point encryption device microchip for AES-sea 512-bit key using identity access management utilizing blockchain ecosystem to improve cybersecurity |
| CN109493072A (en) * | 2018-10-24 | 2019-03-19 | 杭州趣链科技有限公司 | A method of the privacy contract protection based on alliance's block chain |
| CN110163607A (en) * | 2019-05-10 | 2019-08-23 | 南京邮电大学 | The personal reference method of college student number based on block chain intelligence contract |
| CN110555773A (en) * | 2019-08-09 | 2019-12-10 | 腾讯科技（深圳）有限公司 | contract conflict detection method and device, readable storage medium and computer equipment |
| CN110599069A (en) * | 2019-09-29 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Application evaluation method and device based on block chain network |
| CN110990891A (en) * | 2019-11-29 | 2020-04-10 | 山东爱城市网信息技术有限公司 | Gymnasium contract proving method, equipment and medium based on block chain |
| CN111176668A (en) * | 2019-12-30 | 2020-05-19 | 支付宝(杭州)信息技术有限公司 | Predicter deployment method, device, electronic equipment and storage medium |
| CN111353176A (en) * | 2020-05-22 | 2020-06-30 | 支付宝(杭州)信息技术有限公司 | Method and system for inquiring block chain data |
Non-Patent Citations (3)
| Title |
|---|
| Z. LU 等: "Bis: A Novel Blockchain Based Bank-Tax Interaction System in Smart City", 《2019 IEEE INTL CONF ON DEPENDABLE》 * |
| 袁勇 等: "区块链技术发展现状与展望", 《自动化学报》 * |
| 马宇生: "基于区块链技术的安全DNS***设计", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113159682A (en) * | 2021-04-22 | 2021-07-23 | 上海卓钢链科技有限公司 | Electronic warehouse receipt information alliance chain system |
| CN113159682B (en) * | 2021-04-22 | 2023-05-05 | 上海卓钢链科技有限公司 | Electronic warehouse information alliance chain system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112214502B (en) | 2023-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP3385590B2 (en) | Computer-readable recording medium recording a software update program for use when updating a computer program through a computer network | |
| US6202207B1 (en) | Method and a mechanism for synchronized updating of interoperating software | |
| US7013462B2 (en) | Method to map an inventory management system to a configuration management system | |
| US20100318968A1 (en) | Catalog-based software component management | |
| US20050262501A1 (en) | Software distribution method and system supporting configuration management | |
| CN111367659B (en) | Resource management method, equipment and medium for nodes in Kubernetes | |
| WO2016116013A1 (en) | Software upgrade method and system | |
| WO2022095844A1 (en) | Elastic block service mounting method and apparatus thereof | |
| CN108228197B (en) | Method and device for installing software in cluster | |
| CN112214502A (en) | User contract deployment method, device, system and storage medium of alliance chain | |
| CN104111862A (en) | Method and system for obtaining IP (Internet Protocol) address of virtual machine in cloud computing platform | |
| CN105744511B (en) | Android system adaptation module dynamic updating method, client and server | |
| CN110308914B (en) | Upgrade processing method, device, equipment, system and computer readable storage medium | |
| CN113076248B (en) | Application processing method, device and equipment and readable storage medium | |
| CN112148379B (en) | User contract unloading method, device and system of alliance chain and storage medium | |
| CN112738181A (en) | Method, device and server for cluster external IP access | |
| CN114721699B (en) | Mirror image upgrading method and device, electronic equipment and storage medium | |
| CN113687915B (en) | Container running method, device, equipment and storage medium | |
| CN112131266B (en) | Method, device, system and storage medium for supporting block chain complex query | |
| CN106657265A (en) | Service framework system | |
| KR102350333B1 (en) | Method for upgrading of software and pbx for the same | |
| CN117632307A (en) | Calling method and device for storage procedure, electronic equipment and storage medium | |
| CN117032818A (en) | BIOS (basic input output system) option configuration method and device | |
| CN116015651A (en) | Automatic key management method and device, electronic equipment and storage medium | |
| CN116204224A (en) | Configuration management method, device and system based on blockchain and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |