CN112214502B - User contract deployment method, device and system of alliance chain and storage medium - Google Patents
User contract deployment method, device and system of alliance chain and storage medium Download PDFInfo
- Publication number
- CN112214502B CN112214502B CN202010888952.7A CN202010888952A CN112214502B CN 112214502 B CN112214502 B CN 112214502B CN 202010888952 A CN202010888952 A CN 202010888952A CN 112214502 B CN112214502 B CN 112214502B
- Authority
- CN
- China
- Prior art keywords
- contract
- user
- deployment
- deployed
- contracts
- 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.)
- Active
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 alliance chain, wherein the method not only considers whether user contracts with the same name are deployed on the alliance chain, but also considers the situation that if the user contracts with the same name are deployed on the alliance chain, the user contracts are possibly upgraded and deployed except for name conflicts, so that whether the deployed user contracts are allowed to be deployed or not is determined by comparing whether CA identifications of clients used by the deployed user contracts and the user contracts requiring deployment are consistent or not; in addition, the invention not only deploys the user contracts on the alliance chain, but also links the deployment content records of the user contracts, so that the invention can avoid the collision of the user contract names, and can also avoid the malicious upgrade deployment of the user contracts.
Description
Technical Field
The present invention relates to blockchain technologies, and in particular, to a method, an apparatus, a system, and a storage medium for deploying user contracts of a federated chain.
Background
Currently, user contract management of a federation chain is generally performed by a management node, and in a federation chain scenario where a supporting user can freely select a node to deploy a user contract, a user contract name conflict may occur. Because the blockchain transaction data generated by the user contracts is distinguished by contract names in the state library, the contract names cannot be modified once being used, otherwise, historical transaction data cannot be associated, and if the user contract names conflict, the transaction data generated between the user contracts with the conflicting names are confused, and even the data is covered. Therefore, it is necessary to design a user contract management mechanism of the federation chain to avoid the occurrence of user contract name conflicts.
Disclosure of Invention
In view of the above-described deficiencies of the prior art, the present invention aims to: a user contract deployment method of a alliance chain is provided, which can avoid the occurrence of user contract name conflict.
In order to achieve the above object, the present invention provides the following technical solutions:
a method of user contract deployment for a federation chain, 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, detecting whether user contracts with the same name are deployed on the alliance chain; 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 deployment, and if so, allowing deployment of corresponding user contracts; if not, refusing to deploy the corresponding user contract;
and configuring nodes on the alliance chain, wherein the nodes are used for deploying the user contracts on the alliance chain after the corresponding user contracts are allowed to be deployed, and linking the deployment content records of the user contracts.
According to a specific embodiment, the user contract deployment method of the alliance chain further comprises the steps of configuring nodes on the alliance chain, and after the corresponding user contracts are allowed to be deployed, uploading deployment content records of the user contracts; wherein the deployment record includes the content of the user contract and the CA identification of the client used by the user contract deployment.
Further, the CA identification is automatically generated when the client registers with the CA.
According to a specific embodiment, the user contract deployment method of the alliance chain further comprises the step of configuring a leader node of the alliance chain, and sending prompt information of contract name conflict to the client after the node refuses to deploy the corresponding user contract.
According to a specific embodiment, in the user contract deployment method of the alliance chain, the user contract is deployed on the alliance chain, and the method comprises the following steps:
reading the content of the user contract by calling a deployment interface of the system contract;
checking the content of the user contract by precompiling the user contract, and storing the content of the user contract after precompilation is successful;
after the precoding is successful, initiating a consensus voting for deploying the user contracts, and after the consensus voting is passed, regularly reading a contract deployment state record table to check whether the user contracts are 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; 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 is responded; and when the node responds to the contract deployment state query request, a query interface of the 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 user contract deployment apparatus of a federation chain, 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, detecting whether user contracts with the same name are deployed on the alliance chain; 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 deployment, and if so, allowing deployment of corresponding user contracts; 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 linking the deployment content records of the user contracts after the corresponding user contracts are allowed to be deployed.
According to a specific embodiment, in the user contract deployment device of the federation chain of the present invention, the deployment module further includes:
the reading sub-module is used for reading the content of the user contract by calling a deployment interface of the system contract;
a precompilation sub-module, configured to precompile the user contract, so as to check the content of the user contract, and store the content of the user contract after precompilation is successful;
the deployment launching tool module is used for launching consensus voting for deploying the user contracts after the pre-compiling is successful;
the timing task sub-module is used for regularly reading the contract deployment state record table after the consensus voting is passed, 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 record sub-module is used for monitoring the deployment state of the user contract and updating the contract deployment state record 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 comprising: client and user contract deployment means of the present federation chain deployed on respective nodes of the federation chain, respectively.
In another aspect of the present invention, there is 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 user contract deployment method of the federated chain of the present invention.
Compared with the prior art, the invention has the beneficial effects that:
1. in the deployment process, not only the fact that whether the user contracts with the same name are deployed on the alliance chain is considered, but also the fact that if the user contracts with the same name are deployed on the alliance chain, besides name conflict, the user contracts are possibly upgraded and deployed is considered, so that whether the user contracts are allowed to be deployed or not is determined by comparing whether the deployed user contracts are consistent with CA identifications of clients used by the user contracts requiring deployment or not; therefore, the invention not only can avoid the conflict of the names of the user contracts, but also can avoid the malicious upgrade deployment of the user contracts.
2. According to the user contract deployment method of the alliance chain, after the corresponding user contracts are allowed to be deployed, the node on the alliance chain links the deployment content record of the user contracts, wherein the deployment record comprises the content of the user contracts and CA identification of the client used by the user contracts in the deployment. Therefore, the invention also uses the non-tamperable characteristic of the blockchain to link the deployment record, thereby improving the security and traceability of user contract deployment.
Drawings
FIG. 1 is a diagram of an interaction architecture of a federated chain network and a client in accordance with the present invention;
FIG. 2 is a flow chart of interaction between a client and a node according to the present invention;
FIG. 3 is a flow chart of a node of the present invention responding to a deployment request; the method comprises the steps of carrying out a first treatment on the surface of the
FIG. 4 is a flow chart of the deployment of a user contract in accordance with the present invention;
FIG. 5 is a flow chart illustrating interaction between a client and a node in an embodiment of the present invention;
FIG. 6 is a schematic structural view of the deployment device of the present invention;
FIG. 7 is a schematic diagram of a deployment module of the present invention;
fig. 8 is a schematic diagram of the deployment system of the present invention.
Detailed Description
Other advantages and effects of the present invention will become apparent to those skilled in the art from the following disclosure, which describes the embodiments of the present invention with reference to specific examples. The invention may be practiced or carried out in other embodiments that depart from the specific details, and the details of the present description may be modified or varied from the spirit and scope of the present invention.
As shown in fig. 1, taking the existing scenario of a federation chain in which a supporting user can freely select a node to deploy a user contract as an example, a client 10 can directly send a deployment request to any node in the federation chain, and can implement deployment of the user contract by calling a deployment interface of the system contract. However, in this open contract deployment method, there are cases where contract names collide, which may cause confusion of transaction data, or even coverage loss.
Thus, the user contract deployment method of the alliance chain of the present invention comprises 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, detecting whether user contracts with the same name are deployed on the alliance chain; 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 deployment, and if so, allowing deployment of corresponding user contracts; if not, refusing to deploy the corresponding user contract;
and configuring nodes on the alliance chain, wherein the nodes are used for deploying the user contracts on the alliance chain after the corresponding user contracts are allowed to be deployed, and linking the deployment content records of the user contracts.
The CA (certificattion authority) digital certificate authentication center and the CA identification are automatically generated when the client registers with the CA. The client 10 is developed on an SDK supporting a calling system contract, in which ip addresses of respective nodes, signature algorithms, and the like are integrated.
Specifically, according to the user contract deployment method of the alliance chain, the interaction flow of the client and the node in the deployment process is shown in fig. 2:
s100 is performed by the client: sending the deployment request to node 1, and upon receiving the deployment request, node 1 immediately executes S100a: broadcasting the deployment request to other nodes on the federation chain, then performing S200 by node 1: responding to the deployment request; then, according to the response result, i.e., if the deployment of the corresponding user contract is allowed, S300 is performed by the node 1: the corresponding user contracts are 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, i.e. if the deployment of the corresponding user contract is allowed.
As shown in fig. 3, the flow when the node 1 executes S200 is as follows:
s201: detecting whether user contracts with the same name are 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 skipped 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 CA identifications of clients used by the user contracts requesting deployment, and if so, allowing the deployment of corresponding user contracts to jump to S203; if not, the deployment of the corresponding user contract is refused, and the process goes to S204.
As shown in fig. 4, the flow when the node 1 executes S300 is as follows:
firstly, reading the content of a user contract by calling a deployment interface of the system contract;
then, pre-compiling the user contract to check the content of the user contract, thereby ensuring the grammar and the security of the user contract; if the pre-compiling is successful, the content of the user contract is saved, and if the pre-compiling is failed, the deployment is ended.
After the precoding is successful, the consensus voting for deploying the user contracts is initiated, and after the consensus voting is passed, the user contracts are deployed.
In consideration of the fact that the user contract cannot be ensured to be deployed successfully once, after the consensus voting is passed, the user contract is checked to be successful at regular time by setting a timing task, and if the user contract is not deployed successfully, the deployment is continued.
The timing task is specifically: firstly, judging whether the time from last reading of 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 deployment is successful, ending the deployment.
And if the user contract is not deployed successfully, starting a new contract container in sequence, 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.
Meanwhile, the contract deployment state record table in the invention is updated by monitoring the deployment state of the user contract.
In a specific embodiment, the user contract deployment method of the alliance chain further comprises the steps of configuring nodes on the alliance chain, and after the corresponding user contracts are allowed to be deployed, uploading deployment content records of the user contracts; wherein the deployment record includes the content of the user contract and the CA identification of the client used by the user contract deployment.
As shown in fig. 5, after the node 1 responds to the deployment request, S300a is then performed by the node 1 according to the response result, i.e., if the deployment of the corresponding user contract is allowed: the content of the user contract and the CA identification record of the client used by the user contract deployment are uplinked. Therefore, once the deployment of the user contract is completed, the content and the CA identification using the client side in the deployment process can be guaranteed to be untampered, so that the security and traceability of the deployment of the user contract are improved.
Further, 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 the client; when the node responds to the deployment 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.
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 the system contract, accessing a contract deployment state record table, and executing S500: and returning the query result to the client.
In another embodiment, the user contract deployment method of the alliance chain further comprises the step of configuring a leader node of the alliance chain, and sending prompt information of contract name conflict to the client after the node refuses to deploy the corresponding user contract. If there is a leader node in the federation chain, by the method, when contract name conflict occurs, a developer is prompted to modify the contract name.
As shown in fig. 6, the present invention provides a user contract deployment apparatus of a federation chain, for deployment on each node of the federation chain, comprising:
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, detecting whether user contracts with the same name are deployed on the alliance chain; 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 deployment, and if so, allowing deployment of corresponding user contracts; if not, refusing to deploy the corresponding user contract;
a deployment module 300, configured to deploy the user contracts on the federation chain after allowing deployment of the corresponding user contracts;
a recording module 200, configured to, after allowing deployment of the corresponding user contract, uplink the deployment content record of the user contract.
In the user contract deployment apparatus of the federation chain of the present invention, if the response result obtained by the response module 100 is that the deployment of the corresponding user contract is allowed, the deployment content record of the user contract may be first uploaded by the recording module 200, where the deployment record includes the content of the user contract and the CA identifier of the client that the user is about to use for deployment, 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:
a reading sub-module 310, configured to read the content of the user contract by calling a deployment interface of the system contract;
a precompilation sub-module 320, configured to precompile the user contract to check the content of the user contract, and store the content of the user contract after precompilation is successful;
a deployment launching tool module 330, configured to launch a consensus vote for deploying the user contract after the precoding is successful;
a timing task sub-module 340, configured to periodically read a contract deployment status record table 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;
the deployment record sub-module 350 is configured to monitor a deployment status of a user contract, and update the contract deployment status record table.
As shown in fig. 8, the present invention also provides a user contract deployment system of a federation chain, in which a client 10 and a user contract deployment apparatus 20 of the present invention of the federation chain are deployed on respective nodes of the federation chain, respectively. 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 a user contract deployment method of the federated chain of the present invention.
It should be understood that the system disclosed in the present invention may be implemented in other manners. For example, the modules may be divided into only one logic function, and there may be other manners of dividing the modules when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. In addition, the communication connection between modules may be an indirect coupling or communication connection via some interfaces, devices or units, and may be in electrical or other forms.
In addition, each functional module in the embodiments of the present invention may be integrated in one processing unit, or each module may exist alone physically, or two or more modules may be integrated in one processing unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform 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, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Claims (10)
1. A method for deploying a user contract of a federation chain, 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, detecting whether user contracts with the same name are deployed on the alliance chain; 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 deployment, and if so, allowing deployment of corresponding user contracts; if not, refusing to deploy the corresponding user contract;
and configuring nodes on the alliance chain, wherein the nodes are used for deploying the user contracts on the alliance chain after the corresponding user contracts are allowed to be deployed.
2. The method of claim 1, wherein nodes on the federation chain are configured to upload deployment content records for the user contracts after allowing deployment of the corresponding user contracts; wherein the deployment record includes the content of the user contract and the CA identification of the client used by the user contract deployment.
3. The federation-linked user contract deployment method according to claim 2, wherein the CA identification is automatically generated when registered with a CA by the client.
4. The method for deploying user contracts of a federation chain according to claim 1, wherein a leader node of the federation chain is configured to send a prompt message for contract name conflict to a client after the node refuses to deploy the corresponding user contract.
5. The method of claim 1 to 4, wherein the user contracts are deployed on the federation chain, comprising the steps of:
reading the content of the user contract by calling a deployment interface of the system contract;
checking the content of the user contract by precompiling the user contract, and storing the content of the user contract after precompilation is successful;
after the precoding is successful, initiating a consensus voting for deploying the user contracts, and after the consensus voting is passed, regularly reading a contract deployment state record table to check whether the user contracts are 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; the contract deployment state record table is updated by monitoring the deployment state of the user contract.
6. The method of claim 5, further configuring nodes on the federation chain to respond to a contract deployment status query request sent by the client; and when the node responds to the contract deployment state query request, a query interface of the system contract is called, the contract deployment state record table is accessed, and a query result is returned to the client.
7. A user contract deployment apparatus of a federation chain for deployment on respective nodes of the 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, detecting whether user contracts with the same name are deployed on the alliance chain; 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 deployment, and if so, allowing deployment of corresponding user contracts; 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 linking the deployment content records of the user contracts after the corresponding user contracts are allowed to be deployed.
8. The federation-linked user contract deployment apparatus of claim 7, wherein the deployment module further comprises:
the reading sub-module is used for reading the content of the user contract by calling a deployment interface of the system contract;
a precompilation sub-module, configured to precompile the user contract, so as to check the content of the user contract, and store the content of the user contract after precompilation is successful;
the deployment launching tool module is used for launching consensus voting for deploying the user contracts after the pre-compiling is successful;
the timing task sub-module is used for regularly reading the contract deployment state record table after the consensus voting is passed, 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 record sub-module is used for monitoring the deployment state of the user contract and updating the contract deployment state record table.
9. A user contract deployment system of a federation chain, characterized by a client and a user contract deployment apparatus of a federation chain as claimed in claim 7 or 8 deployed on respective nodes of the federation chain.
10. A readable storage medium having one or more programs stored thereon, which when executed by one or more processors, implement the user contract deployment method of the federation chain of any of claims 1-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 CN112214502A (en) | 2021-01-12 |
| CN112214502B true 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) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113159682B (en) * | 2021-04-22 | 2023-05-05 | 上海卓钢链科技有限公司 | Electronic warehouse 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 |
|---|
| Bis: A Novel Blockchain Based Bank-Tax Interaction System in Smart City;Z. Lu 等;《2019 IEEE Intl Conf on Dependable》;1008-1014 * |
| 区块链技术发展现状与展望;袁勇 等;《自动化学报》;第42卷(第4期);481-494 * |
| 基于区块链技术的安全DNS系统设计;马宇生;《中国优秀硕士学位论文全文数据库信息科技辑》(第（2018）8期);I138-368 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112214502A (en) | 2021-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20140075438A1 (en) | Method, server, and system for starting an application | |
| US11669337B2 (en) | Bare metal device management | |
| CN108696372B (en) | Method and system for keeping system configuration consistency | |
| CN110224854B (en) | Block chain node deployment method and device and storage medium | |
| US11711256B2 (en) | Autonomous server agents | |
| US20160313715A1 (en) | Method, Device and Computer Program Product for Programming a Plurality of Control Units | |
| WO2016116013A1 (en) | Software upgrade method and system | |
| CN112214502B (en) | User contract deployment method, device and system of alliance chain and storage medium | |
| CN111026436B (en) | Model joint training method and device | |
| CN111314241A (en) | Task scheduling method and scheduling system | |
| CN113076248A (en) | Application processing method, device and equipment and readable storage medium | |
| US11349928B2 (en) | Offline sideloading for enrollment of devices in a mobile device management system | |
| CN110308914B (en) | Upgrade processing method, device, equipment, system and computer readable storage medium | |
| CN115335803A (en) | Equipment upgrading method, intelligent equipment and computer readable storage medium | |
| CN112148379B (en) | User contract unloading method, device and system of alliance chain and storage medium | |
| CN110688130A (en) | Physical machine deployment method, physical machine deployment device, readable storage medium and electronic equipment | |
| CN115495107A (en) | Version deployment method and device and electronic equipment | |
| CN112738181B (en) | Method, device and server for cluster external IP access | |
| CN116009984A (en) | Security arrangement and automatic response processing method and device and electronic equipment | |
| CN108650320B (en) | Method for synchronizing configuration files of isomorphic cascading equipment in cluster environment | |
| CN111464395A (en) | Method and device for creating block chain and readable storage medium | |
| CN113687915B (en) | Container running method, device, equipment and storage medium | |
| CN115905271B (en) | Virus library updating method and device and multi-engine detection system | |
| CN114721699B (en) | Mirror image upgrading method and device, electronic equipment and storage medium | |
| CN116150197A (en) | Data acquisition method and device |
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 |