TWI824625B - Device and method for securing and verifying business data via a blockchain system - Google Patents

Abstract

In a blockchain system, a user device obtains an address of a smart contract according to a transaction hash, and generates a private data hash according to business data. The user device then generates a transaction based on the private data hash and the address of the smart contract, and submits the transaction to the blockchain system to store the private data hash into the smart contract, such that confidential information of a business deal in the real world is secured. On the other hand, an authentication device generates a private data hash according to business data, obtains an address of a smart contract in the blockchain system according to a transaction hash, and accesses the smart contract via the address to determine whether the private data hash is stored in the smart contract. The authentication device approves the business data when the smart contract includes the private data hash.

Description

Devices and methods for protecting and verifying business data through blockchain systems

The present disclosure relates to a device and method for protecting and verifying business information through a blockchain system. More specifically, the present disclosure relates to a device and method for protecting and verifying business information through a blockchain system, which device and method ensures that business evidence is preserved and the confidentiality of business evidence is protected.

Blockchain is commonly used to maintain business records between two parties due to its decentralized and immutable structure, which makes it almost impossible to tamper with the records held within it. In order to utilize a blockchain to retain business evidence, relevant information (e.g., payment amount, destination address, and/or other information to be retained) needs to be provided to all nodes of the blockchain system so as to treat it as a record (i.e., a blocks) are stored on the blockchain, that is, the information must be public to all nodes.

However, in some cases, business-related information provided to nodes will be considered confidential, that is, its content should only be accessible to certain nodes, rather than to all nodes on the blockchain. All words are available. Therefore, there is an urgent need in the technical field to which the present invention belongs, for a solution that can retain business evidence on the blockchain while still ensuring its confidentiality.

In order to at least solve the above problems, the present disclosure provides a device for protecting business data through a blockchain system. The device may include a storage, a transceiver electrically connected to the storage, and a processor electrically connected to the storage and the transceiver. The storage can be used to store the business data and transaction hashes. The processor can be used to obtain an address of a smart contract in the blockchain system based on the transaction hash; generate a dedicated data hash based on the business data; and based on the dedicated data hash and the bit of the smart contract address to generate a transaction. The transceiver can be used to submit the transaction to the blockchain system to hash and store the dedicated data in the smart contract, so that confidential information of a commercial transaction in the real world is protected by the blockchain system.

In order to at least solve the above problems, the present disclosure also provides a device for verifying business data through a blockchain system. The device may include a storage, a transceiver electrically connected to the storage, and a processor electrically connected to the storage and the transceiver. The storage can be used to store the business data and transaction hashes. The processor can be used to generate a dedicated data hash based on the business data, and obtain an address of a smart contract in the blockchain system based on the transaction hash. The transceiver can be used to access the smart contract via the address of the smart contract. In addition, the processor may also be used to determine whether the dedicated data hash is included in the smart contract, and approve the business data when it is determined that the dedicated data hash is stored in the smart contract, so that one of the real-world Business transaction activities are verified by the blockchain system.

In order to at least solve the above problems, the present disclosure also provides a method of protecting business data through a blockchain system. The method may include the following steps executed by an electronic device in the blockchain system: obtaining an address of a smart contract in the blockchain system based on a transaction hash; generating a dedicated data based on the business information Hash; Generate a transaction based on the dedicated data hash and the address of the smart contract; and submit the transaction to the blockchain system to store the dedicated data hash in the smart contract, enabling a commercial transaction in the real world Confidential information is protected by the blockchain system.

In order to at least solve the above problems, the present disclosure also provides a method of verifying business information through a blockchain system. The method may include the following steps performed by an electronic device in the blockchain system: generating a dedicated data hash based on the business data; obtaining a smart contract in the blockchain system based on a transaction hash. address; access the smart contract via the address of the smart contract; determine whether the private data hash is stored in the smart contract; and when it is determined that the private data hash is stored in the smart contract, approve the business data, So that a commercial transaction activity in the real world can be verified by the blockchain system.

The present disclosure provides devices and methods for protecting and verifying business information through a blockchain system to ensure the retention of business evidence and the confidentiality of business evidence by generating a hash of confidential business information and deploying it to a smart contract. protect. The smart contract and the corresponding block on the blockchain do not display business information, but display a piece of information that cannot be interpreted based on its content, and the immutable mechanism of the blockchain retains an index to verify the business information. Therefore, as long as a person or organization is provided with business information, it can still verify the business information when necessary (that is, determine whether a business behavior/a transaction actually occurred in the manner shown in the business information). In view of this, the device and method provided by the present disclosure for protecting and verifying business data through a blockchain system have indeed solved the above technical problems in the technical field to which the present invention belongs.

The summary of the present invention generally explains the core concepts of the present invention, and covers the problems to be solved, the means to solve the problems and the effects of the present invention, so that those with ordinary knowledge in the art can have a basic understanding of the present invention. It should be understood, however, that this summary is not intended to cover all embodiments of the invention, but is merely provided to present core concepts of the invention in a simplified form and as an introduction to the detailed description that follows. In order to enable those skilled in the art to better understand the features of the claimed invention, detailed techniques and preferred embodiments of the invention are described in the following paragraphs in conjunction with the drawings.

1: Blockchain system

2: Process for protecting business information

3: Process of verifying business information

4: Methods to protect business data through a blockchain system

5: Method of verifying business information through a blockchain system

10:Blockchain

11, 12: Electronic devices

111, 121: Processor

112, 122: Storage

113, 123: transceiver

201, 202, 203, 204, 205, 206, 207, 208, 209, 301, 302, 303, 304: Action

401, 402, 403, 404, 501, 502, 503, 504, 505: steps

AD1, AD2: address

B0, B1, B2: block

C1: Smart Contract

DH1, DH2: Special data hashing

IN1: input

K1: private key

K2: public key

OP1: Output message

PD1, PD2: business information

R0, R1, R2: transaction request

T0: Contract deployment transaction

T1, T2: Transaction

TH0, TH1: transaction hash

Drawings can assist in describing the present disclosure, wherein: Figure 1 illustrates a schematic diagram of a blockchain system according to one or more embodiments of the present disclosure.

Figure 2 is a schematic diagram of a process for protecting business data according to one or more embodiments of the present disclosure.

Figure 3 is a schematic diagram of a process for verifying business information according to one or more embodiments of the present disclosure.

Figure 4 illustrates a method of protecting business data through a blockchain system according to one or more embodiments of the present disclosure.

Figure 5 illustrates a method of verifying business information through a blockchain system according to one or more embodiments of the present disclosure.

In the following description, reference will be made to the embodiments of the present disclosure to explain the devices and methods provided by the present disclosure for protecting business data and the devices and methods for verifying business data through a blockchain system. However, these examples are not intended to limit the invention to any environment, application or implementation set forth in these examples. Therefore, the description of these embodiments is for illustrative purposes only and does not limit the present invention. invention. It should be understood that in the following embodiments and drawings, elements irrelevant to the present invention are not shown. In addition, the sizes and dimensional proportions of various elements in the drawings are provided for illustration only and do not limit the scope of the present invention.

Figure 1 illustrates a schematic diagram of a blockchain system according to one or more embodiments of the present disclosure. The content shown in Figure 1 is only for illustrative embodiments and does not limit the scope of the present disclosure.

Please refer to picture 1. A blockchain system 1 can include a plurality of nodes, and these nodes can together form a decentralized peer-to-peer (P2P) network structure. The blockchain system 1 may be a network based on, for example, but not limited to, Ethereum or other blockchain platforms that support Solidity, which is an object-oriented programming language widely used to implement smart contracts. .

For example, Figure 1 shows two of the nodes, namely the electronic device 11 and the electronic device 12 . Each of the electronic device 11 and the electronic device 12 may have general blockchain functions (for example, storing and changing the state of a blockchain virtual machine, creating a transaction and publishing the transaction to the blockchain, deploying A smart contract, a device that executes a specific program or function contained in a smart contract, activates an account in the blockchain system and interacts with it, etc.). Based on the present disclosure, those with ordinary skill in the art can directly understand the basic materials, components and/or behaviors used to implement the described functions, and therefore they will not be described again below.

The electronic device 11 as a whole can be used to retain business information using a blockchain 10 , and the electronic device 12 as a whole can be used to verify the business information via the blockchain 10 . The electronic device 11 may include a processor 111 , a memory 112 electrically connected to the processor 111 , and a transceiver 113 electrically connected to the processor 111 and the memory 112 . Similarly, the electronic device 12 may include a processor 121 , a memory 122 electrically connected to the processor 121 , and a transceiver 123 electrically connected to the processor 121 and the memory 122 . Should Note that the electrical connection between the aforementioned elements may be direct (ie, connected to each other without any functional elements therebetween) or indirect (ie, connected to each other via other functional elements).

Each of processor 111 and processor 121 may be a microprocessor or microcontroller. A microprocessor or microcontroller is a programmable special integrated circuit with functions such as computing, storage, output/input, etc., and can accept and process various coded instructions to perform various logical operations and arithmetic operations. And output the corresponding operation results. The processor 111 and the processor 121 can be programmed to execute various instructions, thereby processing data in the electronic device 11 and the electronic device 12 respectively, and executing various calculation programs or programs.

The memory 112 and the memory 122 can be used to store data generated by the electronic device 11 and the electronic device 12 respectively, data transmitted to the electronic device from an external device, or data input into the electronic device by a user. Each of the storage 112 and the storage 122 may include a primary memory (also referred to as main memory or internal memory), and the corresponding processor 111 or 121 may directly read the storage in the primary memory. instruction set and execute the instruction set as needed. Each of storage 112 and storage 122 may include secondary memory (also known as external memory or auxiliary memory), and the secondary memory may transfer stored data via a data buffer to the primary memory. For example, the auxiliary memory may be a hard disk, an optical disk or a similar device, but is not limited thereto. Storage 112 and storage 122 may each include Level 3 memory (ie, a storage device (eg, a mobile hard drive) that can be plugged directly into or removed from a computer).

As shown in Figure 1, the storage 112 can store commercial data PD1, and the storage 122 can store commercial data PD2. Each of the business data PD1 and PD2 may be data related to a business behavior (eg, payment) of a user. The business activity may be a cryptocurrency transaction between two accounts in the blockchain system 1, and in some embodiments, the business activity may also be, for example, US dollars, RMB, Trading of real world currencies such as Euros. More specifically, the business data PD1 and PD2 may include, for example, information related to the identity of the participants in a business transaction (for example, a personal ID number, a tax number or a company's registration number, etc.), invoices, delivery orders, etc. , shipment, certificate of origin and/or any other items involved in different stages of a commercial transaction. Therefore, the commercial data PD1 and PD2 may include a text, an image, an audio, a video and/or any other format corresponding to commercial activities. Business data PD1 and PD2 can be used as proof of trading activities and are therefore useful in checking whether a business activity actually occurred as claimed.

Each of the transceiver 113 and the transceiver 123 may be used for wired or wireless communication with other external devices. Taking wireless communication as an example, the transceiver 113 and the transceiver 123 may include but are not limited to an antenna, an amplifier, a modulator, a demodulator, a detector, an analog-to-digital converter, and a digital-to-analog converter. or other communication components. Taking wired communication as an example, the transceiver 113 and the transceiver 123 can be, for example but not limited to, a gigabit Ethernet transceiver, a gigabit Ethernet interface converter (GBIC), a small package A pluggable (small form-factor pluggable; SFP) transceiver, a ten-gigabit small form-factor pluggable (XFP) transceiver, or other similar transceivers.

Figure 2 is a schematic diagram of a process for protecting business data according to one or more embodiments of the present disclosure. The content shown in Figure 2 is only used to illustrate the embodiment and does not limit the scope of the present disclosure.

Please refer to both Picture 1 and Picture 2. Whenever the user wants to retain the business data PD1 as evidence on the blockchain system 1, he or she can execute a process 2 for protecting the business data. Before starting the process 2, the storage 112 may store a private key K1 corresponding to a user account representing the electronic device 11 in the blockchain system 1, and may generate a user account corresponding to the private key K1 based on the private key K1. Public key K2. In some embodiments, the public key K2 may be generated by the processor 111. Then, based on the public key K2, the corresponding The address AD1 of the user account in the blockchain system 1. In some embodiments, the address AD1 can also be generated by the processor 111.

Process 2 can start with an action 201. In action 201, the processor 111 can generate a contract deployment transaction T0 based on the private key K1, public key K2 and address AD1 of the user account in order to deploy one corresponding to the user account. Smart contract C1. In an action 202, the processor 111 can use the private key K1 to sign the contract deployment transaction T0, and in an action 203, the transceiver 113 can deploy the smart contract C1 by submitting a transaction request R0 to the blockchain system 1 . A block B0 containing the contract deployment transaction T0 can be generated in the blockchain 10, and the transaction request R0 and the corresponding contract deployment transaction T0 have been verified and executed by one of the miners (ie, one of the nodes) After submitting it to the blockchain system 1, the transaction hash TH0 representing the contract deployment transaction T0 can be obtained. Storage 112 may store transaction hash TH0.

It should be noted that the smart contract C1 shown in Figure 1 is only a schematic diagram, and there is no limit on its number or location. Those with ordinary knowledge in this technology should realize that after action 203, the smart contract C1 is actually stored in every valid node of the blockchain system 1.

When the user of the electronic device 11 wants to submit evidence of the aforementioned business behavior to the blockchain 10, in an action 204, the transceiver 113 can access the block B0 to reach the contract deployment transaction T0. Then the processor 111 can obtain one of the addresses AD2 of the smart contract C1 according to the contract deployment transaction T0, which is action 205.

On the other hand, in action 206, the processor 111 may generate a dedicated data hash DH1 based on the business data PD1. Commercial data PD1 may represent information that not only needs to be retained by the blockchain 10 but is also unavailable to unrelated users of the blockchain system 1 because its content usually contains the information of one or more parties involved in commercial activities. Private or confidential information. In some embodiments, the processor 111 may use a third-generation secure hash algorithm (secure hash algorithm-3; SHA-3) such as Keccak256. 3) Algorithm generates special data hash DH1. In some embodiments, act 206 may occur before any of acts 201-205.

After obtaining the address AD2 and the private data hash DH1, the processor 111 may generate a transaction T1 for interacting with the smart contract C1 based on the address AD2 and the private data hash DH1 in an act 207, and in an act 208 Use private key K1 to sign transaction T1. Specifically, for example, address AD2 may be included in a recipient field of transaction T1, and private data hash DH1 may be included in a data field of transaction T1.

Transceiver 113 may then submit (ie, by broadcasting) a transaction request R1 corresponding to signed transaction T1 to blockchain system 1 (ie, act 209). Once the transaction request R1 is verified, executed and submitted to the blockchain system 1 by a miner, the dedicated data hash DH1 can be sent as an input to the smart contract C1 to set the variables defined therein at execution time, because in the transaction T1 The recipient has been designated as smart contract C1, and the data contained is dedicated data hash DH1. A block B1 containing transaction T1 may be generated in blockchain 10, and a transaction hash TH1 representing transaction T1 may then be obtained.

More specifically, smart contract C1 may initially be programmed by processor 111 to include a function that captures an input value and assigns it to a variable so that a dedicated data hash DH1 may be stored therein upon execution by transaction T1.

Through process 2 for protecting business data, the private data hash DH1 can be successfully stored in the smart contract C1 as a link to the business data PD1. Any valid node in the blockchain system 1 can observe the record of the dedicated data hash DH1, but cannot obtain the content of the business data PD1 just by viewing the dedicated data hash DH1.

In some embodiments, processor 111 may alternatively program and deploy smart contract C1 as an upgradable smart contract (e.g., by deploying a proxy smart contract, or directly Directly use tools such as "deployProxy" provided by "OpenZeppelin"). Smart contract C1 can therefore be upgraded via transaction T1 based on the dedicated data hash DH1.

Figure 3 is a schematic diagram of a process for verifying business information according to one or more embodiments of the present disclosure. The content shown in Figure 3 is only used to illustrate the embodiment and does not limit the scope of the present disclosure.

Please refer to Picture 1, Picture 2 and Picture 3 at the same time. When any individual wants to prove that the business action corresponding to the business data PD2 is the exact business action corresponding to the business data PD1, the person can provide the transaction hash TH1 and the business data to the electronic device 12 through, for example, the transceiver 123 or other input methods. PD2. After the process 2, the electronic device 12 can execute a process 3 for verifying commercial data to verify whether the commercial data PD2 and the commercial data PD1 are consistent. It should be noted that the electronic device 12 may be different from the electronic device 11 and therefore may not know anything about the commercial data PD1 since the commercial data PD1 is kept proprietary to the electronic device 11 . However, the verification mechanism provided in process 3 of the present invention does not require the electronic device 12 to know the content of the commercial data PD1.

Process 3 may begin with an action 301, in which the processor 121 may arrive/visit transaction T1 based on transaction hash TH1. In an action 302, the processor 121 may then obtain the address AD2 of the smart contract C1 from the transaction T1. On the other hand, in an action 303, the processor 121 may generate a dedicated data hash DH2 based on the business data PD2 in the same manner as the processor 111 generates the dedicated data hash DH1. In some embodiments, act 303 may be performed before act 301 or act 302.

After obtaining the address AD2 and the private data hash DH2, in an action 304, the processor 121 can determine whether the private data hash DH2 is included in the smart contract C1 (the presence of the private data hash DH2 indicates that the business data PD2 is used to generate The exact business information of transaction T1 and construction block B1). When it is determined that the private data hash DH2 is included in the smart contract C1, the processor 121 can approve the business data PD2, because if the two data are not the same, it is almost impossible for the business data PD1 and PD2 to be processed by the same hashing mechanism. produces the same hash value. On the other hand, when determining that the private data hash DH2 is not included in the smart contract C1, the processor 121 may not approve the business data PD2. Therefore, it can be concluded that the approval/disapproval of commercial data PD2 can indicate the fact that the two commercial data PD1 and PD2 are the same/different.

In some embodiments, regarding action 304, the processor 121 may first generate a transaction T2 for interacting with the smart contract C1 based on the address AD2 and the private data hash DH2, and use the corresponding user account of the electronic device 12 private key to sign transaction T2. The transceiver 123 may then submit a transaction request R2 corresponding to the signed transaction T2 to the blockchain system 1 .

Once the transaction request R2 has been verified, executed and submitted to the blockchain system 1 by a miner, the dedicated data hash DH2 can be sent to the smart contract C1 as an input IN1. Smart contract C1 may then be executed by processor 121 and certain functions (e.g., query/search functions) in smart contract C1 may be called to check for the presence of private data hash DH2 and provide an indication of the result (i.e., private data hash DH2 Whether it is included in smart contract C1) one of the output messages OP1. Thus, a block B2 containing transaction T2 may be generated in blockchain 10, and a transaction hash representing transaction T2 may then be obtained.

To achieve the operations described above, smart contract C1 may, for example, include capturing an input value (e.g., a dedicated data hash DH2) and matching it with a variable defined in the same or a different function (which as explained previously is designed to store Special data hash DH1) is a function that performs comparisons. However, the way in which smart contract C1 checks the existence of the private data hash DH2 is not limited to this implementation.

In some embodiments, each of the business data PD1 and PD2 may be processed into a JSON (JavaScript Object Notation) file before being further processed into a dedicated data hash DH1 or DH2.

In some embodiments, the processor 121 may determine whether the transaction hash TH1 is generated based on a private key corresponding to a user account in the blockchain system. Specifically, for example, the storage 122 also A public key (eg, public key K2) corresponding to a certain user account (eg, the user of the electronic device 11) may be stored, and the processor 121 may use the public key to authenticate the transaction hash TH1 to determine the transaction hash. Whether TH1 is generated based on the user's private key (for example, private key K1). The processor 121 may only approve the business data PD2 when it is determined that "the transaction hash TH1 is generated based on a specific private key" and "the private data hash DH2 is included in the smart contract C1".

Figure 4 illustrates a method of protecting business data through a blockchain system according to one or more embodiments of the present disclosure. The content shown in Figure 4 is only used to illustrate the embodiments of the present disclosure, but does not limit the scope of the present disclosure.

Please refer to Figure 4. A method 4 of protecting business data through a blockchain system may include the following steps performed by an electronic device in the blockchain system: Obtaining an address of a smart contract in the blockchain system based on a transaction hash (labeled as step 401); generate a private data hash based on the business data (labeled as step 402); generate a transaction based on the private data hash and the address of the smart contract (labeled as step 403); and The blockchain system submits the transaction to hash and store the private data in the smart contract, so that confidential information of a commercial transaction in the real world is protected by the blockchain system (marked as step 404).

In some embodiments, the smart contract may correspond to a user account of the blockchain system, and method 4 may further include the following steps: using one of the user accounts before submitting the transaction to the blockchain system private key to sign the transaction.

In some embodiments, regarding method 4, the smart contract may correspond to a user account in the blockchain system, and method 4 may further include the following steps: generating by the electronic device based on a private key of the user account The public key of the user account; the electronic device generates the address of the user account in the blockchain system based on the public key; the electronic device generates the address of the user account in the blockchain system based on the private key, the public key and the user The address of the account generates a contract deployment transaction; and the smart contract is deployed by the electronic device by submitting the contract deployment transaction to the blockchain system to obtain the transaction hash. In addition, in some embodiments, method 4 may further include the following steps: using the private key to sign the contract deployment transaction before submitting the contract deployment transaction to the blockchain system.

In some embodiments, regarding method 4, the electronic device may generate a dedicated data hash of the business data based on the SHA-3 algorithm. Likewise, in some embodiments, the commercial information may include at least one of text, an image, an audio, and a video corresponding to the commercial transaction activity.

Figure 5 illustrates a method of verifying business information through a blockchain system according to one or more embodiments of the present disclosure. The content shown in Figure 5 is only used to illustrate the embodiments of the present disclosure, but does not limit the scope of the present disclosure.

Please refer to Figure 5. Method 5 of verifying business data through a blockchain system may include the following steps performed by an electronic device in the blockchain system: generating a dedicated data hash based on the business data (labeled step 501); Hash to obtain the address of a smart contract in the blockchain system (marked as step 502); access the smart contract through the address of the smart contract (marked as step 503); determine whether the dedicated data hashing Stored in the smart contract (labeled step 504); and When it is determined that the special data is hashed and stored in the smart contract, the business data is approved, so that a commercial transaction activity in the real world is verified by the blockchain system (marked as step 505).

In some embodiments, method 5 may further include the following step: determining whether the transaction hash is generated based on a private key corresponding to a user account of the blockchain system. When it is determined that the transaction hash is generated based on the private key and the private data hash is included in the smart contract, the electronic device can approve the business data. In addition, in some embodiments, the electronic device can authenticate the transaction hash by using a public key corresponding to the user account, and thereby determine whether the transaction hash is generated based on the private key.

In some embodiments, regarding method 5, the electronic device may generate the private data hash based on the SHA-3 algorithm. In addition, in some embodiments, the commercial information may include at least one of text, an image, an audio, and a video corresponding to the commercial transaction activity.

Each embodiment of method 4 and method 5 basically corresponds to a certain embodiment of the electronic device 11 or the electronic device 12 of the blockchain system 1 . Therefore, even though all the embodiments of method 4 and method 5 are not described in detail above, those with ordinary knowledge in the technical field to which the present invention belongs can refer to the above description of the electronic device 11 or the electronic device 12 of the blockchain system 1 All corresponding embodiments of Method 4 and Method 5 can be fully understood and implemented.

The above disclosure relates to its detailed technical content and inventive features. Those with ordinary skill in the technical field to which the present invention belongs may make various modifications and substitutions based on the disclosure and suggestions of the present invention without departing from the characteristics of the present invention. However, although such modifications and substitutions are not fully disclosed in the above description, such modifications and substitutions are basically covered by the appended patent scope below.

4: Methods to protect business data through a blockchain system

401, 402, 403, 404: steps

Claims (22)

A device for protecting business data through a blockchain system, including: a storage device for storing the business data and a transaction hash, the business data corresponding to confidential information of a business transaction in the real world; a transceiver a processor, electrically connected to the storage; and a processor, electrically connected to the storage and the transceiver, for: obtaining an address of a smart contract in the blockchain system based on the transaction hash. ; Generate a dedicated data hash based on the business data; and generate a transaction based on the dedicated data hash and the address of the smart contract; wherein the transceiver is used to submit the transaction to the blockchain system, thereby converting the transaction Special data hashes are stored in the smart contract to allow a verification device to verify whether the business transaction actually occurred in the manner indicated by the business data by accessing the smart contract. The device of claim 1, wherein the smart contract corresponds to a user account of the blockchain system, the storage is also used to store a private key of the user account, and the processor is also used to This private key is used to sign the transaction before it is submitted to the blockchain system. The device as described in claim 1, wherein: the smart contract corresponds to a user account of the blockchain system; the storage is also used to store a private key of the user account; the processor is also used to: Generate the public key of the user account based on the private key; generate the address of the user account in the blockchain system based on the public key; and generate the address of the user account in the blockchain system based on the private key, the public key and the user The address of the account is used to generate a contract deployment transaction; and the transceiver is also used to deploy the smart contract by submitting the contract deployment transaction to the blockchain system, thereby obtaining the transaction hash. The device as described in claim 3, wherein the processor is also used to use the private key to sign the contract deployment transaction before submitting the contract deployment transaction to the blockchain system. The device of claim 1, wherein the processor generates the specialized data hash of the business data based on a third-generation secure hash algorithm. The device according to claim 1, wherein the commercial information includes at least one of text, an image, an audio and a video corresponding to the commercial transaction activity. A device for verifying business data through a blockchain system, including: a storage to store the business data and a transaction hash; a transceiver, electrically connected to the storage; and a processor, to the storage The storage and the transceiver are electrically connected to: generate a dedicated data hash based on the business data; and obtain an address of a smart contract in the blockchain system based on the transaction hash; wherein, the transceiver The processor is used to access the smart contract through the address of the smart contract, and the processor is also used to: determine whether the dedicated data hash is included in the smart contract; and when it is determined that the dedicated data hash is stored in the smart contract When in contract, confirm A business transaction in the real world has actually occurred in the manner shown in the business information, and then the business information is approved. The device as described in claim 7, wherein: the processor is also used to determine whether the transaction hash is generated based on a private key corresponding to a user account of the blockchain system; when determining that the transaction hash is The processor approves the business data when it is generated based on the private key and the private data hash is included in the smart contract. The device of claim 8, wherein the storage is also used to store a public key corresponding to the user account, and the processor is also used to use the public key to authenticate the transaction hash to determine the transaction hash. Whether it is generated based on the private key. The device of claim 7, wherein the processor generates the dedicated data hash based on a third generation secure hash algorithm. The device of claim 7, wherein the commercial information includes at least one of text, an image, an audio and a video corresponding to the commercial transaction activity. A method of protecting business data through a blockchain system, the business data corresponding to confidential information of a commercial transaction in the real world, and the method includes the following steps executed by an electronic device in the blockchain system : Obtain the address of a smart contract in the blockchain system based on a transaction hash; generate a dedicated data hash based on the business data; generate a transaction based on the dedicated data hash and the address of the smart contract; and submitting the transaction to the blockchain system to hash and store the dedicated data in the smart contract, so that a verification device can verify the commercial transaction by accessing the smart contract. Whether the trading activities have actually occurred in the manner shown in the business information. The method of claim 12, wherein the smart contract corresponds to a user account of the blockchain system, and the method further includes the following steps: before submitting the transaction to the blockchain system, use the user account Sign the transaction with one of the account's private keys. The method of claim 12, wherein the smart contract corresponds to a user account of the blockchain system, and the method further includes the following steps: generating the user account based on a private key of the user account a public key; generate the address of the user account in the blockchain system based on the public key; generate a contract deployment transaction based on the private key, the public key and the address of the user account ; and deploy the smart contract by submitting the contract deployment transaction to the blockchain system, thereby obtaining the transaction hash. The method described in request 14 also includes the following steps: using the private key to sign the contract deployment transaction before submitting the contract deployment transaction to the blockchain system. The method of claim 12, wherein the electronic device generates the dedicated data hash of the business data based on a third-generation secure hash algorithm. The method of claim 12, wherein the commercial information includes at least one of text, an image, an audio and a video corresponding to the commercial transaction activity. A method of verifying business data through a blockchain system, including the following steps performed by an electronic device in the blockchain system: generating a dedicated data hash based on the business data; obtaining an intelligence based on a transaction hash One of the addresses of the contract in the blockchain system; Access the smart contract via the address of the smart contract; determine whether the dedicated data hash is stored in the smart contract; and when it is determined that the dedicated data hash is stored in the smart contract, confirm one of the real-world Business transactions have actually occurred in the manner shown in the business information, and the business information is approved. The method described in claim 18 also includes the following steps: determining whether the transaction hash is generated based on a private key corresponding to a user account of the blockchain system; wherein, when it is determined that the transaction hash is The electronic device approves the business information generated based on the private key and the private information hash is included in the smart contract. The method of claim 19, wherein the electronic device authenticates the transaction hash by using a public key corresponding to the user account, and then determines whether the transaction hash is generated based on the private key. The method of claim 18, wherein the electronic device generates the dedicated data hash based on a third-generation secure hash algorithm. The method of claim 18, wherein the commercial information includes at least one of text, an image, an audio and a video corresponding to the commercial transaction activity.

Images