CN112182608B - Method and system for regularly sharing alliance chain encryption data - Google Patents

Abstract

The application relates to a method and a system for regularly sharing alliance chain encryption data, wherein the method comprises the following steps: the task users of the k level regularly disclose tasks through the common user nodes, and if the level k is greater than or equal to a set level corresponding to the tasks, 3k public keys corresponding to different common user nodes are distributed to the task users; the task user encrypts and signs the complete data content, randomly breaks the complete data into 3k parts, and transmits the 3k parts to 3k different common users, wherein the common users encrypt and sign the data; transmitting all the information of the encrypted data to an intelligent contract, and setting triggering time by a task user; and periodically checking whether the triggering time is reached in the intelligent contract, and informing the common user of the intelligent contract when the triggering time is reached, decrypting the data on the alliance chain within the specified time and disclosing the data. The method not only ensures the safety and consistency of the data in the unpublished stage, but also can ensure that the data must be publicly shared after the intelligent contract is triggered.

Description

A method and system for regular sharing of alliance chain encrypted data

Technical field

The invention relates to a method and system for regular sharing of alliance chain encrypted data, and belongs to the technical field of alliance chain.

Background technique

Blockchain is a decentralized infrastructure and distributed computing paradigm that uses encrypted chain block structures to verify and store data, uses distributed node consensus algorithms to generate and update data, and uses smart contracts to program and operate data. , the blockchain has its unique block generation, transaction generation and verification protocols, which are distributed, open and transparent, unchangeable, unforgeable, traceable and highly trustworthy. Blockchain data is stored in the form of hash data storage. The asymmetric encryption mechanism of the blockchain effectively protects account privacy and transaction data. Using the blockchain to store the encrypted form of data can effectively prevent plaintext data. With the leakage of data, data has become an important asset of the enterprise. How to effectively control the access rights of data within the enterprise and securely share data between enterprises has always been a challenge. The public sharing of data is of great significance to enterprises, academic research, etc. The distributed ledger in the blockchain can solve the above problems in some aspects, but the asymmetric encryption mechanism applied in the blockchain can only perform one-to-one Secure transmission.

Contents of the invention

In response to the above problems, the purpose of the present invention is to provide a method and system for regular sharing of alliance chain encrypted data, which not only ensures the security and consistency of the data in the undisclosed stage, but also ensures that the data must be shared publicly after the smart contract is triggered.

In order to achieve the above purpose, the present invention adopts the following technical solution: a method for regular sharing of alliance chain encrypted data, including the following steps: S1 k-level task users regularly disclose tasks through ordinary user nodes. If level k is greater than or equal to the setting corresponding to the task level, the task user is assigned the public keys corresponding to 3k different ordinary user nodes; the S2 task user encrypts and signs the complete data content, randomly scrambles the complete data, divides it into 3k parts, and transmits them to 3k different Ordinary users, 3k different ordinary users encrypt and sign their assigned data; S3 sends all the encrypted data information in step S2 to the smart contract, and the task user sets the trigger time; S4 checks regularly in the smart contract Whether the trigger time is reached, if the trigger time is reached, the smart contract notifies 3k different ordinary users, who will decrypt the data on the alliance chain within the specified time and make the data public.

Furthermore, the data in step S2 is randomly scrambled and divided into 3k parts. Among them, 3k parts can only be restored according to the randomly scrambled order of the data after more than or equal to 2k ordinary users decrypt the parts encrypted with their own public keys. Complete data content.

Further, the information of the encrypted data in step S3 includes the random shuffling order of the data content, the data distribution results and the corresponding encryption public key order.

Further, the creation steps of the smart contract in step S3 include: S3.1 receives the contract creation application submitted by the task user; S3.2 generates the contract and contract record according to the contract creation application; S3.3 sends the contract to the task user, and the task user Sign the contract; S3.4 stores the contract signed by the task user in step S3.3, and publishes the contract information in the alliance chain.

Further, in step S4, the data on the alliance chain is decrypted within the specified time. If the ordinary user discloses the data on the alliance chain within the specified time, the transaction amount will be rewarded and the user level will be improved. If the ordinary user decrypts the data in advance or still fails after timeout, If it is not decrypted, the transaction amount cannot be obtained and the user level will be reduced.

Furthermore, the initial level of an ordinary user node is level 1, and the highest level is level 5. If an ordinary user node completes smart contract tasks more than the predetermined number of times, the level will increase by 1 level. If the number of defaults exceeds the predetermined number of times, the level will decrease by 1 level.

Further, in step S1, the data decrypted by ordinary users on the alliance chain within the specified time is restored in the order of random shuffling of the data, and the restored data is compared with the complete data of the task user to determine whether the task user is different from the ordinary user. Whether the content provided by the user is consistent.

Further, the execution steps of the smart contract in step S4 include: S4.1 Set up regular inspections of all smart contracts and traverse the content of the smart contract one by one; S4.2 When the trigger time is reached, create a contract transaction record and publish the contract transaction record to the alliance In the chain, 3k different ordinary users are automatically notified to decrypt within the specified time.

Furthermore, the smart contract content includes the status, transactions and triggering conditions of the smart contract.

The invention discloses a consortium chain encrypted data regular sharing system, including: a data distribution module, used to enable k-level task users to regularly disclose tasks through ordinary user nodes. If the level k is greater than or equal to the set level corresponding to the task, then The task user allocates the public keys corresponding to 3k different ordinary user nodes; the data encryption module is used to enable the task user to encrypt and sign the complete data content, and randomly scrambles the complete data, divides it into 3k parts, and transmits them to 3k parts respectively. Different ordinary users, 3k different ordinary users encrypt and sign their assigned data; the smart contract module is used to send all the encrypted data information in step S2 to the smart contract, and the task user sets the trigger time; The decryption output module is used to regularly check whether the trigger time is reached in the smart contract. If the trigger time is reached, the smart contract notifies 3k different ordinary users, who will decrypt the data on the alliance chain within the specified time and make the data public.

Since the present invention adopts the above technical solutions, it has the following advantages:

1. In the fields of law, copyright and enterprise data applications, there are scenarios where data needs privacy protection to prevent tampering and needs to be shared publicly. By establishing a consortium chain where encrypted data is regularly disclosed, it can be ensured that the data will not be tampered with during the protection period and will not be Publicly, task users can save current real but sensitive data on the chain, and can decrypt it after ensuring that the data is triggered at a regular time.

2. By establishing smart contracts, the scheduled disclosure process is made transparent. After a certain time is triggered, the data can be decrypted through enough user nodes to share and disclose it.

Description of the drawings

Figure 1 is a flowchart of a method for regularly sharing encrypted data on a consortium chain in an embodiment of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the technical direction of the present invention, the present invention is described in detail through specific embodiments. However, it should be understood that the specific embodiments are provided only for a better understanding of the present invention, and they should not be construed as limitations of the present invention. In the description of the present invention, it is to be understood that the terms used are for the purpose of description only and are not to be construed as indicating or implying relative importance.

Embodiment 1

This embodiment discloses a method for regular sharing of consortium chain encrypted data, which includes the following steps:

Divide the alliance chain nodes into alliance nodes and ordinary user nodes, and set the level of ordinary user nodes. The initial level of an ordinary user node is level 1, and the highest level is level 5. If an ordinary user node completes smart contract tasks more than the predetermined number of times, the level will increase by 1 level. If the number of defaults exceeds the predetermined number of times, the level will decrease by 1 level.

S1 k-level task users regularly publish tasks through ordinary user nodes. If level k is greater than or equal to the set level corresponding to the task, the public keys corresponding to 3k different ordinary user nodes will be assigned to the task user.

The S2 task user encrypts and signs the complete data content, randomly scrambles the complete data, divides it into 3k parts, and transmits them to 3k different ordinary users respectively. The 3k different ordinary users encrypt and sign the assigned data. .

In step S2, the data is randomly scrambled and divided into 3k parts. Among the 3k parts, only when more than or equal to 2k ordinary users decrypt the parts encrypted with their own public keys, the complete data can be restored according to the randomly scrambled order of the data. content. This allocation can prevent the complete file from being unable to be interpreted due to a specified node expiration date that cannot be decrypted.

S3 sends all the encrypted data information in step S2 to the smart contract, and tasks the user to set the trigger time.

The information of the encrypted data in step S3 includes the random shuffling order of the data content, the data distribution result and its corresponding encryption public key order.

The creation steps of the smart contract in step S3 include:

S3.1 receives the contract creation application submitted by the task user;

S3.2 Generate contracts and contract records based on the contract creation application;

S3.3 Send the contract to the task user, and the task user signs the contract;

S3.4 stores the contract signed by the task user in step S3.3, and publishes the contract information on the alliance chain.

S4 regularly checks in the smart contract whether the trigger time is reached. If the trigger time is reached, the smart contract notifies 3k different ordinary users, who will decrypt the data on the alliance chain within the specified time and make the data public.

In step S4, the data on the alliance chain is decrypted within the specified time. If the ordinary user discloses the data on the alliance chain within the specified time, the transaction amount will be rewarded and the user level will be improved. If the ordinary user decrypts the data in advance or fails to decrypt it after timeout, Otherwise, the transaction amount cannot be obtained and the user level will be reduced.

In step S4, the data decrypted by ordinary users on the alliance chain within the specified time is restored in the order of random shuffling of the data, and the restored data is compared with the complete data of the task user to determine whether the task user and the ordinary user provide whether the contents are consistent. This can be used to determine whether the task user has placed files with inconsistent data, and it can also be used to determine whether ordinary user nodes have falsely disclosed decrypted data.

The execution steps of the smart contract in step S4 include:

S4.1 Set up regular inspections of all smart contracts and traverse the smart contract content one by one. The smart contract content includes the status, transactions and triggering conditions of the smart contract.

S4.2 When the trigger time is reached, create a contract transaction record, publish the contract transaction record to the alliance chain, and automatically notify 3k different ordinary users to decrypt within the specified time.

Embodiment 2

Based on the same inventive concept, this embodiment discloses a consortium chain encrypted data regular sharing system, including:

The data distribution module is used to enable k-level task users to regularly disclose tasks through ordinary user nodes. If level k is greater than or equal to the set level corresponding to the task, public keys corresponding to 3k different ordinary user nodes are allocated to the task user;

The data encryption module is used to enable task users to encrypt and sign the complete data content, randomly scramble the complete data, divide it into 3k parts, and transmit them to 3k different ordinary users respectively, and 3k different ordinary users will divide them into Encrypt and sign data;

The smart contract module is used to send all the encrypted data information in step S3 to the smart contract, and the task user sets the trigger time;

The decryption output module is used to regularly check whether the trigger time is reached in the smart contract. If the trigger time is reached, the smart contract notifies 3k different ordinary users, who will decrypt the data on the alliance chain within the specified time and make the data public.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those of ordinary skill in the art should understand that the present invention can still be modified. Modifications or equivalent substitutions may be made to the specific embodiments, and any modifications or equivalent substitutions that do not depart from the spirit and scope of the invention shall be covered by the scope of the claims of the invention. The above content is only a specific implementation mode of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, and all of them should be covered. within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (6)

1. A method for regular sharing of consortium chain encrypted data, which is characterized by including the following steps: S1 k-level task users regularly publish tasks through ordinary user nodes. If the level k is greater than or equal to the set level corresponding to the task, then the public keys corresponding to 3k different ordinary user nodes are assigned to the task user; The S2 task user encrypts and signs the complete data content, randomly scrambles the complete data, divides it into 3k parts, and transmits them to 3k different ordinary users respectively, and the 3k different ordinary users receive their assigned data. Perform encryption and signing; S3 sends the information about the encrypted data in step S2 to the smart contract, and the task user sets the trigger time; S4 regularly checks in the smart contract whether the trigger time is reached. If the trigger time is reached, the smart contract notifies the 3k different ordinary users, who decrypt the data on the alliance chain within the specified time and disclose the data; The information of the encrypted data in step S3 includes the random shuffling order of the data content, the data distribution results and the corresponding encrypted public key order; The creation steps of the smart contract in step S3 include: S3.1 receives the contract creation application submitted by the task user; S3.2 Generate contracts and contract records based on the contract creation application; S3.3 Send the contract to the task user, and the task user signs the contract; S3.4 stores the contract signed by the task user in step S3.3, and publishes the contract information on the alliance chain; In the step S4, the data decrypted by ordinary users on the alliance chain within the specified time is restored in the order of random shuffling of the data, and the restored data is compared with the complete data of the task user to determine whether the task user is different from the ordinary user. Whether the content provided by the user is consistent; The execution steps of the smart contract in step S4 include: S4.1 Set up regular inspections of all smart contracts and traverse the contents of smart contracts one by one; S4.2 When the trigger time is reached, create a contract transaction record, publish the contract transaction record to the alliance chain, and automatically notify the 3k different ordinary users to decrypt within the specified time. 2. The method for regular sharing of consortium chain encrypted data as claimed in claim 1, characterized in that the data in step S2 is randomly scrambled and divided into 3k parts, wherein the 3k parts can only be shared when there are greater than or equal to 2k Ordinary users can restore the complete data content according to the randomly shuffled order of the data after decrypting the part encrypted with their own public key. 3. The method for regularly sharing consortium chain encrypted data as claimed in claim 1, characterized in that in step S4, the data on the consortium chain is decrypted within a specified time. If the ordinary user discloses the consortium chain within the specified time, The data on the data will be rewarded with the transaction amount and the user level will be improved. If the ordinary user decrypts the data in advance or fails to decrypt it after timeout, the transaction amount will not be obtained and the user level will be lowered. 4. The method for regular sharing of alliance chain encrypted data as claimed in claim 1, characterized in that the initial level of the ordinary user node is level 1, the highest level is level 5, and the number of times the ordinary user node completes smart contract tasks exceeds a predetermined number of times. , the level increases by 1 level, if the number of defaults exceeds the predetermined number of times, the level decreases by 1 level. 5. The method for regular sharing of consortium chain encrypted data as claimed in claim 1, wherein the smart contract content includes the status, transactions and triggering conditions of the smart contract. 6. A consortium chain encrypted data regular sharing system, which is characterized by including: The data allocation module is used to enable k-level task users to regularly publish tasks through ordinary user nodes. If the k-level task users are greater than or equal to the set level corresponding to the task, 3k different tasks are assigned to the task users. The public key corresponding to the ordinary user node; The data encryption module is used to enable the task user to encrypt and sign the complete data content, randomly scramble the complete data, divide it into 3k parts, and transmit them to 3k different ordinary users respectively. The 3k different ordinary users Encrypt and sign the assigned data; The smart contract module is used to send all encrypted data information to the smart contract, and the user sets the trigger time for the task; The decryption output module is used to regularly check whether the trigger time is reached in the smart contract. If the trigger time is reached, the smart contract notifies the 3k different ordinary users to decrypt the data on the alliance chain within the specified time. , and make said data public; The information of the encrypted data includes the random shuffling order of the data content, the data distribution results and the corresponding encryption public key order; The steps to create smart contracts in the smart contract module include: S3.1 receives the contract creation application submitted by the task user; S3.2 Generate contracts and contract records based on the contract creation application; S3.3 Send the contract to the task user, and the task user signs the contract; S3.4 stores the contract signed by the task user in step S3.3, and publishes the contract information on the alliance chain; In the decryption output module, the data decrypted by ordinary users on the alliance chain within the specified time is restored in the order of random data shuffling, and the restored data is compared with the complete data of the task user to determine whether the task user is the same as the task user. Whether the content provided by ordinary users is consistent; The execution steps of the smart contract in the decryption output module include: S4.1 Set up regular inspections of all smart contracts and traverse the contents of smart contracts one by one; S4.2 When the trigger time is reached, create a contract transaction record, publish the contract transaction record to the alliance chain, and automatically notify the 3k different ordinary users to decrypt within the specified time.