Energy data distributed sharing system and method based on block chain technology

Abstract

The invention discloses an energy data distributed sharing system and method based on a block chain technology, and the method comprises the steps that a client sends an energy data transaction proposal to an endorsement node, and the transaction proposal comprises a digital signature generated by encrypting transaction content; after the endorsement node verifies the digital signature successfully, creating a container for operating a corresponding chain code; the client initiates a call request of the chain code to the endorsement node after the chain code is started, the chain code executes the intelligent contract logic of each service party and generates a read-write set object, and an endorsement result is fed back to the client; the client packages and submits a transaction proposal and an endorsement to the sorting node, the sorting node sorts transactions and packages the transactions into blocks, and the copy node stores the verified transactions into an account book by the accounting node; and the bookkeeping node obtains the sorted batch transaction block structures to check before the transaction blocks fall into a disk, and finally writes the transactions into an account book. According to the invention, the problems of insufficient data security and operation transparency in the data sharing process can be solved.

Description

Technical Field

[0001] The present invention relates to the field of energy data sharing and management, and specifically to a distributed energy data sharing system and method based on blockchain technology. Background Art

[0002] The data compliance management requirements of the energy system are relatively high, and there are technical barriers between different professions. In particular, some important power dispatching data and equipment-related production data are not shared in a good way. Traditional data sharing is done offline or in the form of internal forms, which is extremely inefficient and cannot fully release the value of data.

[0003] Moreover, in the traditional energy data management system, the centralized storage and management of data also has the risk of low security, easy tampering and attack. In addition, the real-time and transparency of the data are insufficient, which makes it difficult to meet the construction requirements of the new generation of smart grids. The present invention uses blockchain technology as the underlying architecture, so that the management of energy data has the decentralized, tamper-proof and traceable characteristics of blockchain, which can effectively solve the above problems. Summary of the invention

[0004] The present invention provides a distributed energy data sharing system and method based on blockchain technology, which helps promote energy data sharing, optimizes the business processes of energy enterprises, reduces the operating costs of energy enterprises, and improves the collaborative efficiency of energy enterprises through the "trusted" technology of blockchain.

[0005] A distributed sharing method of energy data based on blockchain technology includes the following steps:

[0006] Step S1: The client SDK sends an energy data transaction proposal to the endorsing node through broadcasting. The transaction proposal includes a digital signature generated by encrypting the transaction content.

[0007] Step S2: After receiving the broadcast message from each client, the endorsing node uses the public key sent by the client to verify whether the digital signature matches the transaction data. After the signature verification is successful, a container running the corresponding chain code is created;

[0008] Step S3: After the chain code is started, the corresponding client initiates a chain code call request to the endorsement node through gRPC. The endorsement node forwards the call request to the chain code. The chain code in the container starts to execute the smart contract logic of each business party, generates a read-write set object, and feeds back the endorsement result to the client;

[0009] Step S4: The client collects endorsement feedback results from the endorsement node, packages the transaction proposal and endorsement, and submits them to the sorting node. The sorting node sorts the transactions and packages them into blocks. The replica node verifies the transactions in the block on all nodes through the FastBFT consensus algorithm. The verified transactions are stored in the ledger by the accounting node, and the information storage object status is updated;

[0010] Step S5: The accounting node periodically obtains the sorted batch transaction block structure from the sorting node for pre-storage inspection, and finally writes the transaction into the ledger for users to publish data.

[0011] Furthermore, step S1 specifically includes:

[0012] The client SDK initiates an energy data transaction proposal to the chain code of the endorsing node, wherein the transaction proposal includes the chain code function to be executed and related parameters;

[0013] When the client sends a transaction proposal, it uses asymmetric encryption technology and the national secret SM2 digital signature algorithm to generate a public key and a private key, uses the private key to encrypt the transaction content, and generates a digital signature.

[0014] Furthermore, step S2 specifically includes:

[0015] After receiving the broadcast message, the endorsement node uses the public key sent by the client to verify the digital signature attached to the transaction. If the endorsement node verifies the digital signature successfully, it proves that the integrity of the transaction has not been destroyed during the transmission process, and the transaction is indeed issued by the private key signature corresponding to the public key, thereby confirming that the transaction is a valid transaction;

[0016] The endorsement node obtains the chain code files corresponding to different business parties from the local chain code package

[0017] The chaincode file is compiled using the corresponding compiler to generate an executable file, which is packaged into a Docker image. The Docker image is then used to create a container that runs the corresponding chaincode.

[0018] Furthermore, step S3 specifically includes:

[0019] After the chain code is started, the client and the endorsing node communicate via gRPC;

[0020] The client initiates a call request for the corresponding chain code to the endorsement node through gRPC, the endorsement node forwards the request to the chain code, and the chain code executes the smart contract logic;

[0021] The endorsement node calls the corresponding business party chain code program to execute the transaction and generate a read-write set;

[0022] The chaincode program queries the read set generated by the corresponding Key value in the information storage object, then executes a series of business logic written in the chaincode, and calculates the update of the Key-Value in the information storage object;

[0023] The endorsement node initiates a chain code call request to the endorsement node and executes the intelligent

[0024] The process of the smart contract can be recorded, and the final smart contract execution result and related logs generate a read-write set object.

[0025] Furthermore, step S4 specifically includes:

[0026] The endorsing node assigns a sequentially increasing number SN to the transactions packaged by the client to ensure that the replica nodes in multiple nodes execute the transactions in the same order;

[0027] The ordering node accepts parallel transactions from different clients, sorts and numbers the transactions internally, and then assembles them into blocks;

[0028] After receiving the transaction request, the endorsing node creates a pre-prepared message, including the view number, sequence number, and transaction information, and then broadcasts it to all replica nodes;

[0029] After the replica node receives the pre-prepare message, if it is confirmed that the pre-prepare message is valid, it enters the preparation phase, and the replica node sends a prepare message to all other nodes, and the prepare message includes its commitment to the transaction;

[0030] The replica node collects 2f+1 prepare messages with the same sequence number and view number, where f is the maximum number of Byzantine nodes that can be tolerated in the system;

[0031] When a replica node collects f prepare messages, it enters the commit phase and sends a commit message to all nodes;

[0032] When a replica node receives 2f+1 commit messages with the same sequence number and view number, the replica node considers that the transaction has reached consensus, executes the transaction and updates the status.

[0033] Furthermore, step S5 specifically includes:

[0034] The accounting node pulls the block from the sorting node, verifies the legitimacy of the block, and verifies whether the transaction meets the endorsement rules. If the transaction verification passes, the block is written into the local blockchain account book;

[0035] When the user publishes data, each node verifies the sharing policy according to the policy format and compliance, and confirms it after reaching a consensus;

[0036] For the user's request to read data, each node verifies the reading conditions according to the shared strategy and authorizes it after reaching a consensus;

[0037] The users evaluate the quality of the shared data, and the evaluation is entered into the system to form an unalterable blockchain account record.

[0038] An energy data distributed sharing system based on blockchain technology, comprising: a client, an endorsement node, a sorting node, a replica node and a bookkeeping node;

[0039] The client is used to send energy data transaction proposals to endorsing nodes and accounting nodes through broadcasting;

[0040] The endorsement node is used to verify whether the signature matches the transaction data using the public key sent by the client after receiving the broadcast message from each client. After the signature verification is successful, a container running the corresponding chain code is created;

[0041] The client is also used to initiate a chain code call request to the endorsement node through gRPC after the chain code is started. The endorsement node forwards the call request to the chain code. The chain code in the container starts to execute the smart contract logic of each business party, generates a read-write set object, and feeds back the endorsement result to the client. The client collects the endorsement feedback result from the endorsement node, packages the transaction proposal and endorsement, and submits it to the sorting node;

[0042] The sorting node is used to globally sort the legal transactions in the blockchain network and package a batch of sorted transactions into blocks;

[0043] The replica node is used to verify the transactions in the block on all nodes through the FastBFT consensus algorithm. The verified transactions are stored in the ledger by the accounting node, and the information storage object status is updated;

[0044] The accounting node is used to regularly obtain the sorted batch transaction block structure from the sorting node for pre-disk inspection, and finally write the transaction into the account book for users to publish data.

[0045] Furthermore, the smart contract logic includes a transaction processing mechanism, a data storage mechanism and a complete state machine, which are used to accept and process various conditions of users during data sharing operations, and the triggering, processing and data preservation of transactions must be performed on the chain, and finally the calculation results are permanently stored in the chain structure.

[0046] The present invention aims at business scenarios in which power grid master data, power dispatching data, and power system production equipment data are efficiently shared, and solves the problems of insufficient data security and operational transparency in the data sharing process, as well as achieving the purpose of data source traceability and non-tamperability of data operations through anti-counterfeiting evidence storage. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 It is a flow chart of the energy data distributed sharing method based on blockchain technology of the present invention;

[0048] Figure 2 It is a schematic diagram of the FastBFT consensus algorithm in the present invention;

[0049] Figure 3 It is the logic diagram of the operation of the smart contract in the present invention;

[0050] Figure 4 It is a schematic diagram of the CA certificate verification process in the present invention;

[0051] Figure 5 It is a schematic diagram of the operation of the data sharing module in the present invention;

[0052] Figure 6 It is a structural schematic diagram of the energy data distributed sharing system based on blockchain technology of the present invention. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0054] See also Figure 1 , an embodiment of the present invention provides a distributed sharing method of energy data based on blockchain technology, comprising the following steps:

[0055] Step S1: The client SDK sends a broadcast message of the energy data transaction proposal to the blockchain network. Step S1 specifically includes:

[0056] The client SDK initiates an energy data transaction proposal to the chain code of the endorsement node. The transaction proposal contains the chain code function to be executed and related parameters, such as Init: initialize the variables and status required for the chain code; Invoke: execute the function call of the chain code; Query: query the status of the data on the chain, etc. Taking the Invoke function as an example, the parameters are pre: the function or task list run before the task is executed; post: the function or task list run after the task is executed; dynamic: if set to True, the task can accept additional parameters, etc. The chain code is a piece of code deployed on each endorsement node that can be used to interact with the distributed ledger. The chain code is executed in an isolated sandbox (Docker container) on the endorsement node and is called and queried by the corresponding endorsement node or client through the gRPC protocol.

[0057] The client needs to select a group of endorsement nodes to execute the transaction proposal. These endorsement nodes are composed of the business party member nodes within the organization, or are selected according to the requirements of business logic.

[0058] like Figure 4 As shown, when the client sends a transaction proposal, it uses asymmetric encryption technology and the national secret SM2 digital signature algorithm to generate a public key and a private key, uses the private key to encrypt the transaction content, and generates a digital signature.

[0059] Step S2: After receiving the broadcast message from each client, the endorsing node uses the public key sent by the client to verify whether the signature matches the transaction data. After the signature verification is successful, a container running the corresponding chain code is created. Step S2 specifically includes:

[0060] After receiving the broadcast message at the same time, the endorsing node and the accounting node will use the public key sent by the client to verify the digital signature attached to the transaction.

[0061] The endorsement node will run the chain code and sign the transaction result. The transaction proposal contains the caller's digital signature and the transaction number generated by the program. The endorsement node and the accounting node can check whether there are duplicate transactions through the transaction number.

[0062] The endorsement node and the accounting node verify the digital signature, proving that the integrity of the transaction has not been destroyed during the transmission process, and that the transaction is indeed issued by the private key signature corresponding to the public key, thereby confirming that the transaction is a valid transaction.

[0063] The endorsement node obtains the chain code files corresponding to different business parties from the local chain code package, and compiles the chain code files using the corresponding compiler to generate executable files, and packages them into a Docker image, and then uses the image to create a container that runs the corresponding chain code.

[0064] Step S3: Figure 2 As shown in the figure, after the chain code is started, the corresponding client initiates a call request to the endorsement node through gRPC. The endorsement node forwards the call request to the chain code, and the chain code starts to execute the smart contract logic of each business party, generates a read-write set object, and feeds back the endorsement result to the client. Step S3 specifically includes:

[0065] After the chain code is started, the client and the endorsing node communicate via gRPC.

[0066] The client initiates a call request for the corresponding chain code to the endorsement node through gRPC. The endorsement node forwards the request to the chain code, and the chain code executes the smart contract logic. During this process, it will interact with the information storage object data multiple times, including reading specific values ​​from the endorsement node status database and writing specific values ​​to the endorsement node status database.

[0067] The endorsement node calls the corresponding business party chain code program to execute the transaction and generate a read-write set.

[0068] The chaincode program queries the read set generated by the corresponding Key value in the information storage object, then executes the business logic written in a series of chaincodes, and calculates the update of the Key-Value in the information storage object.

[0069] The endorsing node records this process, and the final result generates a read-write set object.

[0070] Step S4: The client collects endorsement feedback results from the endorsement node, packages the transaction proposal and endorsement, and submits it to the sorting node. The sorting node sorts the transactions and packages them into blocks. The consensus mechanism verifies the transactions in the blocks on all nodes. The verified transactions will be stored in the ledger by the accounting node, and the information storage object status will be updated. Step S4 specifically includes:

[0071] The endorsing node will assign a sequentially increasing number SN to the packaged transaction to ensure that the replica nodes in multiple nodes execute the transactions in the same order.

[0072] The ordering node accepts parallel transactions from different clients, sorts and numbers the transactions internally, and then assembles them into blocks.

[0073] After receiving the transaction request, the endorsing node creates a pre-prepared message including the view number, sequence number and transaction information, and then broadcasts it to all replica nodes.

[0074] After receiving the pre-prepare message, the replica nodes will enter the prepare phase if they think it is valid. They will send a prepare message to all other nodes, including their own commitment to the transaction.

[0075] like Figure 3 As shown, the replica node needs to collect 2f+1 preparation messages with the same sequence number and view number, where f is the maximum number of Byzantine nodes that can be tolerated in the system.

[0076] When a replica node collects enough prepare messages, it enters the commit phase and sends commit messages to all nodes.

[0077] When a replica node receives 2f+1 commit messages with the same sequence number and view number, it considers that the transaction has reached consensus and can safely execute the transaction and update the status.

[0078] Step S5: The accounting node periodically obtains the sorted batch transaction block structure from the sorting node for pre-storage inspection, and finally stores the transaction (writes it to the ledger), and then allows users to publish data. Step S5 specifically includes:

[0079] The accounting node pulls blocks from the sorting node, verifies the legitimacy of the blocks, and verifies whether the transactions meet the endorsement rules. If the transaction verification passes, the blocks are written into the local blockchain ledger.

[0080] When the user publishes data, for the sharing strategy, such as Figure 5 As shown, each node verifies according to the policy format, compliance, etc., and confirms after reaching a consensus.

[0081] When the user requests to read data, each node verifies the reading conditions according to the shared strategy and authorizes the request after reaching a consensus.

[0082] The users can evaluate the quality of the shared data, and after the evaluation is entered into the system, a blockchain account record that cannot be tampered with is formed.

[0083] See also Figure 6 An embodiment of the present invention provides an energy data distributed sharing system based on blockchain technology, including: a client, an endorsement node, a sorting node, a replica node and a bookkeeping node.

[0084] The client is a related system that manages the main data of the power grid, the power grid dispatching data and the power grid production equipment data in the power system, or an information terminal that can access and obtain such system data. The client is used to send energy data transaction proposals to the endorsement node and the accounting node through broadcasting.

[0085] The endorsement node is designated by a client and is the node that needs to complete the endorsement processing of the corresponding transaction proposal. The endorsement node needs to simulate the operation of the chain code called by the exchange locally, endorse the state changes caused by the exchange and return the results to the corresponding client. After receiving the broadcast message from each client, the endorsement node uses the public key sent by the client to verify whether the signature matches the transaction data. After the signature verification is successful, a container running the corresponding chain code is created.

[0086] After the chain code is started, the client initiates a chain code call request to the endorsement node through gRPC. The endorsement node forwards the call request to the chain code. The chain code in the container starts to execute the smart contract logic of each business party, generates a read-write set object, and feeds back the endorsement result to the client. The client collects the endorsement feedback results from the endorsement node, packages the transaction proposal and endorsement, and submits them to the sorting node.

[0087] The sorting node is responsible for globally sorting legal transactions in the blockchain network, packaging a batch of sorted transactions into blocks, and transmitting them to the accounting node for block storage.

[0088] The replica node is responsible for the FastBFT consensus algorithm (such as Figure 2 As shown in the figure, the legality of the transaction message content generated by each client is checked. If the check passes, the message content will be broadcast to other consensus nodes for cross-verification. If the check fails, the message will not be sent. The transaction message content is checked for consistency. If the cluster nodes can reach a consensus on the ledger data, the Commit message can be broadcast and the transaction can be executed. If no consensus is reached, there is a possibility that the master node is malicious, and an application is made to switch the master node.

[0089] The accounting node is responsible for maintaining the blockchain ledger structure of this system. The ledger is a series of ordered, tamper-proof state transfer record logs. The state transfer is the result of chain code execution (transaction). When a series of ordered transactions are packaged into blocks, such ledgers are connected in series to form a blockchain, and the accounting node is responsible for maintaining the current state of the ledger.

[0090] The smart contract logic (such as Figure 3 The blockchain (as shown) includes a transaction processing mechanism, a data storage mechanism, and a complete state machine, which are used to accept and process various conditions of users during data sharing operations. The triggering, processing, and data storage of transactions must be performed on the chain, and the calculation results must be permanently stored in the chain structure.

[0091] The present invention introduces blockchain technology to record the information resource directory of shared data of various professions and departments in the energy industry on the blockchain shared account book. Each department, as an alliance party of the blockchain, is responsible for sorting out its own data resource directory, and other departments as alliance parties can see the shared information resource directory in real time. If a department wants to change the published information resource directory, it needs to pass the blockchain's alliance party multi-party endorsement strategy before the change is allowed to take effect. The blockchain's shared account book and multi-party endorsement strategy can effectively avoid the data provider from arbitrarily changing the data. At the same time, all data recorded on the blockchain node saves the historical full record of the release and change of the information resource directory, and the historical record can be traced back according to the timestamp. According to the audit characteristics of the energy industry, this can meet the management requirements of the management department for the traceability of any historical change records of data and information resources of various professions and departments.

[0092] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A distributed sharing method of energy data based on blockchain technology, characterized in that: The steps include: Step S1: The client SDK sends an energy data transaction proposal to the endorsing node through broadcasting. The transaction proposal includes a digital signature generated by encrypting the transaction content. Step S2: After receiving the broadcast message from each client, the endorsing node uses the public key sent by the client to verify whether the digital signature matches the transaction data. After the signature verification is successful, a container running the corresponding chain code is created; Step S3: After the chain code is started, the corresponding client initiates a chain code call request to the endorsement node through gRPC. The endorsement node forwards the call request to the chain code. The chain code in the container starts to execute the smart contract logic of each business party, generates a read-write set object, and feeds back the endorsement result to the client; Step S4: The client collects endorsement feedback results from the endorsement node, packages the transaction proposal and endorsement, and submits them to the sorting node. The sorting node sorts the transactions and packages them into blocks. The replica node verifies the transactions in the block on all nodes through the FastBFT consensus algorithm. The verified transactions are stored in the ledger by the accounting node, and the information storage object status is updated; Step S5: The accounting node periodically obtains the sorted batch transaction block structure from the sorting node for pre-storage inspection, and finally writes the transaction into the ledger for users to publish data.

2. The energy data distributed sharing method based on blockchain technology as claimed in claim 1, characterized in that: Step S1 specifically includes: The client SDK initiates an energy data transaction proposal to the chain code of the endorsing node, wherein the transaction proposal includes the chain code function to be executed and related parameters; When the client sends a transaction proposal, it uses asymmetric encryption technology and the national secret SM2 digital signature algorithm to generate a public key and a private key, uses the private key to encrypt the transaction content, and generates a digital signature.

3. The distributed sharing method of energy data based on blockchain technology as claimed in claim 2, characterized in that: Step S2 specifically includes: After receiving the broadcast message, the endorsement node uses the public key sent by the client to verify the digital signature attached to the transaction. If the endorsement node verifies the digital signature successfully, it proves that the integrity of the transaction has not been destroyed during the transmission process, and the transaction is indeed issued by the private key signature corresponding to the public key, thereby confirming that the transaction is a valid transaction; The endorsement node obtains the chain code files corresponding to different business parties from the local chain code package, and compiles the chain code files using the corresponding compiler to generate executable files, and packages them to generate a Docker image, and then uses the Docker image to create a container that runs the corresponding chain code.

4. The distributed sharing method of energy data based on blockchain technology as claimed in claim 1, characterized in that: Step S3 specifically includes: After the chain code is started, the client and the endorsing node communicate via gRPC; The client initiates a call request for the corresponding chain code to the endorsement node through gRPC, the endorsement node forwards the request to the chain code, and the chain code executes the smart contract logic; The endorsement node calls the corresponding business party chain code program to execute the transaction and generate a read-write set; The chaincode program queries the read set generated by the corresponding Key value in the information storage object, then executes a series of business logic written in the chaincode, and calculates the update of the Key-Value in the information storage object; The endorsement node records the process of the client initiating a chain code call request to the endorsement node and executing the smart contract, and the final smart contract execution result and related logs generate a read-write set object.

5. The distributed sharing method of energy data based on blockchain technology as claimed in claim 1, characterized in that: Step S4 specifically includes: The endorsing node assigns a sequentially increasing number SN to the transactions packaged by the client to ensure that the replica nodes in multiple nodes execute the transactions in the same order; The ordering node accepts parallel transactions from different clients, sorts and numbers the transactions internally, and then assembles them into blocks; After receiving the transaction request, the endorsing node creates a pre-prepared message, including the view number, sequence number, and transaction information, and then broadcasts it to all replica nodes; After the replica node receives the pre-prepare message, if it is confirmed that the pre-prepare message is valid, it enters the preparation phase, and the replica node sends a prepare message to all other nodes, and the prepare message includes its commitment to the transaction; The replica node collects 2f+1 prepare messages with the same sequence number and view number, where f is the maximum number of Byzantine nodes that can be tolerated in the system; When a replica node collects f prepare messages, it enters the commit phase and sends a commit message to all nodes; When a replica node receives 2f+1 commit messages with the same sequence number and view number, the replica node considers that the transaction has reached consensus, executes the transaction and updates the status.

6. The energy data distributed sharing method based on blockchain technology as claimed in claim 1, characterized in that: Step S5 specifically includes: The accounting node pulls the block from the sorting node, verifies the legitimacy of the block, and verifies whether the transaction meets the endorsement rules. If the transaction verification passes, the block is written into the local blockchain account book; When the user publishes data, each node verifies the sharing policy according to the policy format and compliance, and confirms it after reaching a consensus; For the user's request to read data, each node verifies the reading conditions according to the shared strategy and authorizes it after reaching a consensus; The users evaluate the quality of the shared data, and the evaluation is entered into the system to form an unalterable blockchain account record.

7. An energy data distributed sharing system based on blockchain technology, characterized in that: include: Clients, endorsing nodes, sorting nodes, replica nodes, and accounting nodes; The client is used to send energy data transaction proposals to endorsing nodes and accounting nodes through broadcasting; The endorsement node is used to verify whether the signature matches the transaction data using the public key sent by the client after receiving the broadcast message from each client. After the signature verification is successful, a container running the corresponding chain code is created; The client is also used to initiate a chain code call request to the endorsement node through gRPC after the chain code is started. The endorsement node forwards the call request to the chain code. The chain code in the container starts to execute the smart contract logic of each business party, generates a read-write set object, and feeds back the endorsement result to the client. The client collects the endorsement feedback result from the endorsement node, packages the transaction proposal and endorsement, and submits it to the sorting node; The sorting node is used to globally sort the legal transactions in the blockchain network and package a batch of sorted transactions into blocks; The replica node is used to verify the transactions in the block on all nodes through the FastBFT consensus algorithm. The verified transactions are stored in the ledger by the accounting node, and the information storage object status is updated; The accounting node is used to regularly obtain the sorted batch transaction block structure from the sorting node for pre-disk inspection, and finally write the transaction into the account book for users to publish data.

8. The energy data distributed sharing system based on blockchain technology as claimed in claim 7 is characterized in that: The smart contract logic includes a transaction processing mechanism, a data storage mechanism and a complete state machine, which are used to accept and process various conditions of users during data sharing operations. The triggering, processing and data storage of transactions must be performed on the chain, and finally the calculation results are permanently stored in the chain structure.

Images