Patent Description:
Currently, fluorocarbon management is performed as follows. An air conditioner manager requests a fluorocarbon filling and collecting operator to handle fluorocarbon and receive a report on collected volume or filled volume of fluorocarbon from the requested fluorocarbon filling and collecting operator. The air conditioner manager reports leakage volume of fluorocarbon to the authorities, which is calculated based on the collected volume or filled volume of fluorocarbon.

As an existing system for fluorocarbon management, there is a refrigerant management system of Japan Refrigerants and Environment Conservation Organization (JRECO). In JRECO's refrigerant management system, an air conditioner manager registers an air conditioner on the refrigerant management system, and a fluorocarbon filling and collecting operator registers an inspection and maintenance record of the air conditioner. Also, <CIT> relates to a blockchain-based traceability monitoring system for hazardous product containers, wherein identity verification and quality inspection is performed to allow an interaction with the hazardous products.

[NPL <NUM>]
https://www. jp/freon_system.

The present disclosure proposes a technology for improving data authenticity in a fluorocarbon management system.

The subject-matter of the independent claims solves the above technical problem/s. The dependent claims describe further preferred embodiments, and the following description exemplifies best modes for carrying out the present invention.

Claims <NUM>, <NUM> disclose the present invention. Preferred embodiments are disclosed in claims <NUM>-<NUM>. According to an embodiment of the present invention, data authenticity regarding each fluorocarbon-related event can be improved.

Also, according to an embodiment of the present invention, distribution volume of fluorocarbon is managed in the distribution ledger and the fluorocarbon manager is managed in a separate database. Therefore, the fluorocarbon manager can be changed without affecting the recording of the distribution volume of fluorocarbon.

Also, according to an embodiment of the present invention, proper implementation of fluorocarbon disposal can be ensured.

Also, according to an embodiment of the present invention, a specific node is designated as a management node and a fluorocarbon management system can be implemented as a private blockchain network.

Also, according to an embodiment of the present invention, nodes other than the management node can be motivated to perform mining.

Also, according to an embodiment of the present invention, the management node having a relatively high computing resource can perform mining.

Also, according to an embodiment of the present invention, it is possible to know the fluorocarbon distribution status, such as distribution volume of fluorocarbon, based on authentic data in the fluorocarbon management system.

Hereinafter, embodiments will be described.

In the following embodiment, a fluorocarbon management system for managing data regarding fluorocarbon-related events is disclosed.

In the fluorocarbon management system according to the present disclosure, fluorocarbon-related data is managed by a blockchain. The fluorocarbon-related data includes fluorocarbon volume, an apparatus using fluorocarbon, a manager of the apparatus, and the like, recorded at each fluorocarbon-related event from production, filling, collection, and recovery, to destruction of fluorocarbon.

The flow of the fluorocarbon-related events regarding an air conditioner is, for example, illustrated in <FIG>. When a manufacturer first fills the air conditioner with fluorocarbon, the filled volume of fluorocarbon and the air conditioner are recorded in the fluorocarbon management system. Next, when a contractor installs the air conditioner in a building and the like, it is recorded in the fluorocarbon management system that the air conditioner has been transferred to a building manager. Thereafter, when the air conditioner is filled with fluorocarbon or when fluorocarbon is collected from the air conditioner, the filled or collected volume of fluorocarbon and the filling and collecting operator are recorded in the fluorocarbon management system. When disposing and the like of the air conditioner, the recovered or destroyed volume of fluorocarbon, together with the recovery operator or destruction operator, is recorded in the fluorocarbon management system. These fluorocarbon-related data recorded in the fluorocarbon management system are managed on a distributed ledger of each node of a blockchain network.

Data stored in a blockchain format is difficult to falsify. For example, the manager of the fluorocarbon management system can know current total volume of fluorocarbon, volume of fluorocarbon managed by each building manager, occurrence of fraud transaction, and the like, from reliable data managed on a distributed ledger via an application server.

First, a configuration of the fluorocarbon management system according to an embodiment of the present disclosure will be described with reference to <FIG>. The fluorocarbon management system according to the present embodiment is implemented as a private blockchain network, although not limited thereto. In the fluorocarbon management system, a block composed of transactions validated and approved by some trusted nodes such as a management node is distributed and managed among the nodes as a blockchain. <FIG> is a block diagram illustrating a configuration of the fluorocarbon management system according to an embodiment of the present disclosure.

As illustrated in <FIG>, a fluorocarbon management system <NUM> includes a management node <NUM> and nodes <NUM>. The management node <NUM> and nodes <NUM> are communicatively connected via a network such as the Internet, for example. The management node <NUM> may be, for example, a computing device, such as a server operated by an operator of the fluorocarbon management system <NUM>. Each node <NUM> may be, for example, a user terminal such as a personal computer (PC) of each operator that performs fluorocarbon-related processing. The examples of the operator that performs fluorocarbon-related processing include a manufacturer and a contractor of an apparatus using fluorocarbon such as an air conditioner, a filling and collecting operator that fills and/or collects fluorocarbon, a recovery operator that recovers collected fluorocarbon, a destruction operator that destroys collected fluorocarbon, and the like.

The management node <NUM> is a node of the fluorocarbon management system <NUM> and functions as an agent server. The management node <NUM> operates the fluorocarbon management system <NUM> which is implemented as a private blockchain network. In the illustrated embodiment, only one management node <NUM> is illustrated, but the present disclosure is not limited thereto, and multiple management nodes <NUM> may be disposed.

Next, referring to <FIG>, the management node <NUM> according to an embodiment of the present disclosure will be described. <FIG> is a block diagram illustrating a functional configuration of the management node <NUM> according to an embodiment of the present disclosure.

As illustrated in <FIG>, the management node <NUM> includes a node management unit <NUM> and a transaction processing unit <NUM>.

The node management unit <NUM> adds and removes the node <NUM> to/from the blockchain network and manages node information of the group of nodes <NUM>. Specifically, the node management unit <NUM> determines whether or not the node <NUM> belongs to the fluorocarbon management system <NUM>. That is, the node management unit <NUM> may permit the node <NUM> to join the blockchain network and may remove the joined node <NUM> from the blockchain network. The node management unit <NUM> holds node information, such as identification information of each node <NUM> that has joined, and a public key.

For example, when an operator desires to join the fluorocarbon management system <NUM>, as illustrated in <FIG>, the operator first accesses the management node <NUM> via its user terminal and the like and transmits an adding request to the management node <NUM> along with necessary information, in step S101.

Upon receipt of the adding request from the operator's user terminal, the management node <NUM> determines whether to add the operator based on the received information. When adding is permitted, the node management unit <NUM> distributes to the operator's user terminal a node tool or an application for functioning as the node <NUM> of the fluorocarbon management system <NUM>, in step S102. For example, whether to add the operator may be determined automatically based on the information received from the operator, or may be determined based on result of examination by the manager based on the information received from the operator.

When adding is permitted and the node tool or the application is received, the operator installs the received node tool or application on the user terminal, in step S103. For example, in the installation process, the operator sets the identification information and password for accessing the blockchain network and creates a private key and a public key for use in the blockchain network.

After the installation process of the node tool or the application is completed, the operator participates in the fluorocarbon management system <NUM> by holding the created private key in the user terminal and sending the created public key to the management node <NUM>, in step S104. The node management unit <NUM> holds the public key thus received from the operator with the identification information of the operator.

When there is an operator which violates the fluorocarbon management or violates rules of the fluorocarbon management system <NUM>, the node management unit <NUM> may prohibit the node <NUM> of the operator from accessing the fluorocarbon management system <NUM> and may remove the operator from the blockchain network.

The transaction processing unit <NUM> monitors the fluorocarbon-related event in the fluorocarbon management system <NUM> based on transactions related to the fluorocarbon-related event. For example, the fluorocarbon-related event may include one or more of the following: fluorocarbon production, fluorocarbon destruction, fluorocarbon recovery, fluorocarbon filling, fluorocarbon collection, a change of a fluorocarbon handler, and a transfer of the apparatus using fluorocarbon (for example, an air conditioner, a refrigerator, a cylinder, and the like). For example, the transactions may include one or more of the following: date, name of the fluorocarbon handler, identification information of the apparatus using fluorocarbon, transfer volume of fluorocarbon, type of fluorocarbon, fluorocarbon handling status, type of handler, name of a fluorocarbon producer, and identification information of fluorocarbon manager. Specifically, when the node <NUM> that has joined the fluorocarbon management system <NUM> performs the fluorocarbon-related event, the node <NUM> generates a transaction related to the fluorocarbon-related event and transmits the generated transaction to the management node <NUM> of the blockchain network. The transaction may include a hash value of transaction information about the fluorocarbon-related event performed and data in which the hash value is encoded by the private key of the node <NUM>.

When the transaction generated in this manner is received from node <NUM>, the transaction processing unit <NUM> validates the received transaction and composes a block from the approved transaction. For example, to verify the transaction, the transaction processing unit <NUM> decodes the data encoded by the public key of the node <NUM> held in the node management unit <NUM> and compares the decoded data with the hash value contained in the transaction. When the decoded data matches the hash value, the transaction processing unit <NUM> approves and holds the transaction.

When the transaction received from the group of nodes <NUM> is validated, and a predetermined block generation condition is satisfied, the transaction processing unit <NUM> composes a block from the approved transaction held and distributes the composed block to each node <NUM> of the blockchain network, as illustrated in <FIG>. For example, block i is composed of a transaction approved after generation of immediately preceding block i-<NUM> and a hash value generated by mining block i-<NUM>, and is added to the blockchain connecting from block <NUM> to block i-<NUM>.

In one example, the transaction processing unit <NUM> may perform mining of a previously composed block, compose a block from a hash value generated by the mining and from the approved transaction, and add the block to the blockchain that is distributed and managed among the nodes <NUM>.

In another example, the transaction processing unit <NUM> may compose a block from a hash value generated by mining by the other node <NUM> and from the approved transaction and add the block to the blockchain that is distributed and managed among the nodes <NUM>. In this case, the transaction processing unit <NUM> may reward the node <NUM> that performed the mining to compose the block. This allows an incentive for load balancing of the nodes <NUM> without having only the management node <NUM> perform the large computational load mining.

In an embodiment, the transaction processing unit <NUM> may monitor distribution volume of fluorocarbon based on the data of the fluorocarbon-related event recorded in the blockchain. Specifically, fluorocarbon volume to be produced, destroyed, recovered, filled, collected, and the like is recorded in the blockchain. Accordingly, it is possible to know fluorocarbon distribution status such as the total volume of fluorocarbon currently in circulation and which volume of fluorocarbon is under the control of which operator. For example, the transaction processing unit <NUM> monitors a transaction related to a node <NUM>, and when there is a significant inconsistency between the volumes of fluorocarbon inflow and outflow to/from the node <NUM>, it can be determined that the operator may have disposed of fluorocarbon by fraud.

For example, such monitoring may be activated when the manager prepares a report on calculated leakage volume of fluorocarbon, when the manager checks the state of fluorocarbon in a specific air conditioner, when the manager checks the state of fluorocarbon related to the manager, and the like. When the manager prepares a report on the calculated leakage volume of fluorocarbon, the transaction processing unit <NUM> may calculate the calculated leakage volume of fluorocarbon from the produced volume, collected volume, filled volume, and destroyed volume of fluorocarbon of the transaction recorded in the distributed ledger. When the manager checks the state of fluorocarbon in a specific air conditioner, the transaction processing unit <NUM> may output the fluorocarbon handling status related to the air conditioner, the fluorocarbon volume for each handling status, the name of the handler, and the like, of the transaction recorded in the distributed ledger. When the manager checks the state of fluorocarbon related to the manager, the transaction processing unit <NUM> may output all of the following: the fluorocarbon handling status, the fluorocarbon volume for each handling status, the name of the handler, and the like, related to the manager of the transaction recorded in the distributed ledger.

Referring to <FIG> and <FIG>, a node <NUM> according to an embodiment of the present disclosure will be described. The node <NUM> may be implemented as, for example, a computing device, such as a personal computer of each operator. In the computing device, a tool or an application provided by the management node <NUM> for accessing the fluorocarbon management system <NUM> is installed. <FIG> is a block diagram illustrating a functional configuration of the node <NUM> according to an embodiment of the present disclosure.

As illustrated in <FIG>, the node <NUM> includes a transaction processing unit <NUM> and a distributed ledger management unit <NUM>.

In response to occurrence of a fluorocarbon-related event, the transaction processing unit <NUM> generates a transaction related to the fluorocarbon-related event and transmits the generated transaction to the blockchain network. For example, the fluorocarbon-related event may include one or more of the following: fluorocarbon production, fluorocarbon destruction, fluorocarbon recovery, fluorocarbon filling, fluorocarbon collection, a change of a fluorocarbon handler, and a transfer of the apparatus using fluorocarbon (for example, an air conditioner, a refrigerator, a cylinder, and the like). For example, the transactions may include one or more of the following: date, name of the fluorocarbon handler, identification information of the apparatus using fluorocarbon, transfer volume of fluorocarbon, type of fluorocarbon, fluorocarbon handling status, type of handler, name of a fluorocarbon producer, and identification information of fluorocarbon manager.

For example, in response to the occurrence of the fluorocarbon-related event, the transaction processing unit <NUM> may generate a transaction including data items as illustrated in <FIG>.

The data item "transaction date" indicates the date on which the transaction occurred.

The data item "from (previous handler)" indicates the fluorocarbon handler before transferring fluorocarbon, and the data item "to (next handler)" indicates the fluorocarbon handler after transferring fluorocarbon. For example, when the fluorocarbon-related event is a transfer of an apparatus using fluorocarbon, the handler of the apparatus using fluorocarbon before the transfer is indicated in "from (previous handler)" and the handler of the apparatus using fluorocarbon after the transfer is indicated in "to (next handler)".

The data item "air conditioner ID" indicates ID of the air conditioner filled with fluorocarbon. The "air conditioner ID" can be used to search for fluorocarbon associated with the air conditioner.

The data item "transfer volume of fluorocarbon" indicates fluorocarbon volume transferred in a transaction. For example, when the fluorocarbon-related event is fluorocarbon filling, the "transfer volume of fluorocarbon" indicates the fluorocarbon volume that is filled.

The data item "fluorocarbon type" indicates the type of fluorocarbon exchanged in the transaction.

The data item "fluorocarbon handling status" indicates the state of fluorocarbon handled in the transaction (for example, waiting for recovery, waiting for destruction, collected, and the like). For example, when the fluorocarbon-related event is fluorocarbon destruction, the "fluorocarbon handling status" indicates "waiting for destruction".

The data item "handler type" indicates the type of fluorocarbon handler (for example, producer/manufacturer, filling and collecting operator, recovery operator, destruction operator, and the like).

The data item "fluorocarbon handler name" indicates the name of the fluorocarbon handler.

The data item "fluorocarbon manager ID" indicates identification information (ID) of the fluorocarbon manager. The "fluorocarbon manager ID" may be associated with the name of the fluorocarbon manager in a database different from the distributed ledger for the blockchain. In other words, data related to transfer of fluorocarbon is managed in a distributed ledger, and information related to the manager is managed in a separate database. Accordingly, organizational changes on the manager side do not affect the fluorocarbon distributed ledger, making it possible to flexibly respond to changes in the organizational structure.

It should be noted that the data item described above is merely an example, and other data items may be included, or a portion of the data item described above may be omitted.

Different data items may be used depending on the type of fluorocarbon-related events.

For example, in the case of fluorocarbon production, data may be input by the fluorocarbon producer into data items such as "transaction date", "produced volume of fluorocarbon", "type of fluorocarbon", "name of fluorocarbon producer", and "fluorocarbon handling status (for example, production)", and a transaction may be generated.

In the case of fluorocarbon destruction, data may be input by the fluorocarbon destruction operator into data items such as "transaction date", "destruction volume of fluorocarbon", "type of fluorocarbon", "name of fluorocarbon destruction operator", and "state of handling of fluorocarbon (for example, destroyed)", and a transaction may be generated.

In the case of fluorocarbon recovery, data may be input by the fluorocarbon recovery operator into data items such as "transaction date", "recovery volume of fluorocarbon", "type of fluorocarbon", "name of fluorocarbon recovery operator", and "fluorocarbon handling status (for example, recovered)", and a transaction may be generated.

In the case of fluorocarbon filling and collection, data may be input by the fluorocarbon filling and collecting operator into data items such as "transaction date", "filled or collected volume of fluorocarbon", "type of fluorocarbon", "air conditioner ID", "name of filling and collecting operator", and "fluorocarbon handling status (for example, filled/collected, waiting for recovery, recovered, waiting for destruction, and destroyed)", and a transaction may be generated.

In the case of a change of fluorocarbon handler, data may be input by the fluorocarbon handler into data items such as "transaction date", "name of fluorocarbon handler (for example, names of fluorocarbon handlers before and after change)", "fluorocarbon volume", "type of fluorocarbon" and "fluorocarbon handling status (for example, waiting for collection, collected, waiting for recovery, recovered, waiting for destruction, and destroyed)", and a transaction may be generated.

In the case of a transfer of an apparatus using fluorocarbon, data may be input, by a transfer operator for the apparatus, into data items such as "transaction date", "air conditioner ID", and "location before and after air conditioner transfer", and a transaction may be generated.

The distributed ledger management unit <NUM> stores the block distributed from the management node <NUM> in the distributed ledger. When a block is generated from an approved transaction, the generated block is distributed to a group of nodes <NUM> of the blockchain network. The distributed ledger management unit <NUM> of each node <NUM> stores the received block in addition to the blockchain that is held. In this manner, a block storing the approved transaction is recorded in each node <NUM> in a blockchain format, making it substantially impossible to falsify the data.

Next, a fluorocarbon management process according to an embodiment of the present disclosure will be described with reference to <FIG>. The fluorocarbon management process is implemented by the management node <NUM> and nodes <NUM> in the fluorocarbon management system <NUM> described above. The fluorocarbon management process may be implemented, for example, by processors of the management node <NUM> and nodes <NUM> executing a program or instruction. <FIG> is a flowchart illustrating a fluorocarbon management process according to an embodiment of the present disclosure.

As illustrated in <FIG>, in step S201, the management node <NUM> receives a transaction from the node <NUM>. Specifically, when a fluorocarbon-related event such as fluorocarbon production, fluorocarbon destruction, fluorocarbon recovery, fluorocarbon filling, fluorocarbon collection, a change of fluorocarbon handler, or a transfer of an apparatus using fluorocarbon is performed, the node <NUM> related to the fluorocarbon-related event generates a transaction related to the fluorocarbon-related event and transmits the generated transaction to the management node <NUM> of the blockchain network.

For example, in order to generate a transaction from data such as date, name of a fluorocarbon handler, identification information of an apparatus using fluorocarbon, transfer volume of fluorocarbon, type of fluorocarbon, fluorocarbon handling status, type of handler, name of a fluorocarbon producer, and identification information of a fluorocarbon manager, the node <NUM> may calculate a hash value of the data and may include in the transaction the calculated hash value and a signature in which the calculated hash value is encoded by a private key of the node <NUM>.

In the present embodiment, the fluorocarbon management system <NUM> is implemented as a private blockchain network in which the management node <NUM> validates a transaction and generates a block from an approved transaction. The blockchain network according to the present disclosure is not limited thereto. For example, the management node <NUM> may be primarily responsible for adding and removing of a node and distribution of a tool or an application for accessing the fluorocarbon management system <NUM>. In the blockchain network, not only the management node <NUM> but also the nodes <NUM> may validates a transaction and generates a block. In this case, the transaction generated by the node <NUM> may be distributed to, for example, the management node <NUM> and/or other node <NUM> and may be validated by the management node <NUM> and/or the other node <NUM>. The validated transaction may be held by the management node <NUM> as an approved transaction.

In step S202, the management node <NUM> validates the received transaction. Specifically, the management node <NUM> decodes the signature of the transaction by the public key of the source node <NUM> and compares the decoding result with the hash value of the transaction. When the decoding result matches the hash value of the transaction, the management node <NUM> approves the received transaction and holds it as an approved transaction. On the other hand, when the decoding result does not match the hash value of the transaction, the management node <NUM> does not approve the received transaction.

In step S203, the management node <NUM> determines whether the block generation condition is satisfied. The block generation condition may be, for example, a predetermined block generation interval such as <NUM> minutes elapsed.

When the block generation condition is not satisfied (S204: NO), the management node <NUM> returns to step S201 and receives a next transaction. When the block generation condition is satisfied (S204: YES), the management node <NUM> composes a block from the approved transaction in step S204. Specifically, the management node <NUM> generates a block from a hash value acquired by performing mining or by having the other node <NUM> perform mining and the approved transaction.

In step S205, the management node <NUM> adds the newly composed block to the blockchain held in its distributed ledger and distributes the newly composed block to the group of nodes <NUM> of the blockchain network. Upon receipt of a block from the management node <NUM>, each node <NUM> adds the received block to a blockchain that is held in its distributed ledger. Then, the management node <NUM> returns to step S201 and receives a transaction for a next block.

In an embodiment, a fluorocarbon disposal cost may be delivered via a multi-signature address set among the nodes <NUM> related to fluorocarbon disposal.

For example, as illustrated in <FIG>, in step S301, an air conditioner manager (for example, a building owner) requests a collecting operator to dispose of the air conditioner via the management node <NUM>. For example, the manager may designate the collecting operator from the collecting operator list provided by the management node <NUM> and request the disposal of the air conditioner.

In step S302, the collecting operator requests the management node <NUM> to register the destruction operator (or the recovery operator).

In step S303, the management node <NUM> generates a <NUM>-of-<NUM> multi-signature address among the management node <NUM>, the node <NUM> of the collecting operator, and the node <NUM> of the destruction operator.

In step S304, when the management node <NUM> receives the fluorocarbon disposal cost from the air conditioner manager, the management node <NUM> sends a transaction indicating the fluorocarbon disposal cost to the multi-signature address. The fluorocarbon disposal cost may be automatically deducted from a wallet and the like of the manager.

In step S305, the collecting operator collects fluorocarbon from the requested air conditioner.

In step S306, the node <NUM> of the collecting operator sends a transaction with a signature requesting the cost of the fluorocarbon collection to the multi-signature address.

In step S307, the collecting operator delivers the collected fluorocarbon to the destruction operator.

In step S308, the node <NUM> of the destruction operator sends a transaction with a signature requesting the cost of the fluorocarbon destruction to the multi-signature address.

In step S309, because the signatures have been received from the node <NUM> of the collecting operator and the node <NUM> of the destruction operator, the collection cost and the destruction cost are transferred from the multi-signature address to each of the node <NUM> of the collecting operator and the node <NUM> of the destruction operator.

According to the present embodiment, by using the <NUM>-of-<NUM> multi-signature address, it is possible to reliably dispose of fluorocarbon and transfer costs, and fraud related to the disposal of fluorocarbon can be prevented.

The management node <NUM> and the node <NUM> may have, for example, a hardware configuration as illustrated in <FIG>. That is, the management node <NUM> and the node <NUM> include a drive device <NUM>, an auxiliary storage device <NUM>, a memory device <NUM>, a central processing unit (CPU) <NUM>, an interface device <NUM>, and a communication device <NUM>, that are interconnected via a bus B.

Various computer programs including programs for implementing the various functions and processes described above in the management node <NUM> and the node <NUM>, may be provided by a recording medium <NUM>, such as a compact disk-read only memory (CD-ROM). When the recording medium <NUM> on which the program is stored is set to the drive device <NUM>, the program is installed in the auxiliary storage device <NUM> from the recording medium <NUM> via the drive device <NUM>. The program need not necessarily be installed from the recording medium <NUM>, and may be downloaded from any external device via a network and the like. The auxiliary storage device <NUM> stores the installed program and stores necessary files, data, and the like. The memory device <NUM> reads out and stores a program or data from the auxiliary storage device <NUM> when an instruction to start the program is given. The CPU <NUM>, which functions as a processor, performs various functions and processes of the management node <NUM> and the node <NUM> described above according to various data such as a program stored in the memory device <NUM> and parameters necessary to execute the program. The interface device <NUM> is used as a communication interface for connecting to a network or an external device. The communication device <NUM> performs various communication processing for communicating with an external device.

The management node <NUM> and the node <NUM> are not limited to the hardware configurations described above, and may be implemented in any other suitable hardware configuration.

Claim 1:
A fluorocarbon management system (<NUM>) comprising:
a group of nodes (<NUM>), wherein each node is a computer device; and
a blockchain network connecting the group of nodes (<NUM>), wherein
in response to occurrence of a predetermined fluorocarbon-related event, an origin node (<NUM>) related to the fluorocarbon-related event
generates a transaction related to the fluorocarbon-related event, the transaction including
a hash value of transaction information about the fluorocarbon-related event performed and
data, in the data the hash value is encoded by a private key of the origin node (<NUM>), and
sends the generated transaction to the blockchain network,
a node (<NUM>, <NUM>) that received the transaction validates the received transaction by
decoding the data by a public key of the origin node (<NUM>) held in the node (<NUM>, <NUM>),
comparing the decoded data with the hash value contained in the transaction and approving the transaction when the decoded data matches the hash value, and
the group of nodes (<NUM>) add a block composed from the approved transaction to a blockchain.