KR102523069B1 - Method of use blockchain smart contract using API providing system - Google Patents

Abstract

The present invention relates to a method for using a blockchain smart contract using an API providing system. The method for using a blockchain smart contract using an API providing system comprises the steps of: receiving a call for an application programming interface (API) for using a first smart contract of a first blockchain network supporting a smart contract service in a second blockchain network that does not support the smart contract service; mapping the first smart contact to the second blockchain network; storing mapping data about the mapping in an API providing system; obtaining a private key between the first blockchain network and the second blockchain network; storing the private key in the API providing system; generating a first transaction based on the mapping data and first information on the first smart contract; transmitting the generated first transaction to the first blockchain network and storing the first transaction in the first blockchain network; and responding a result to the called API. Therefore, provided is a method for using a blockchain smart contract using an API providing system, wherein a user is enabled to perform a smart contract and to refer for a transaction more easily and more conveniently.

Description

Method of use blockchain smart contract using API providing system}

The present invention relates to a method of using a blockchain smart contract using an API providing system. Specifically, the present invention provides a method for utilizing decentralized blockchain smart contract functions through a REST API in a centralized server so that blockchain smart contracts can be conveniently used without prior knowledge, and a mainnet that does not support smart contracts (for example, , Bitcoin Mainnet, etc.), it is about how to use a blockchain smart contract using an API providing system that enables smart contracts to be used.

Recently, various technologies using blockchain smart contracts are emerging. The field to be serviced using blockchain smart contracts is also increasing rapidly, but the technical hurdles for blockchain are high and complex, making it difficult to actually use them.

In addition, there are cases where it is difficult to deal with errors due to unclear error handling for transaction errors that may occur when using blockchain. In addition, blockchains that do not support smart contracts, such as Bitcoin, cannot be expected to operate other than asset transactions, so their utilization is very limited, which acts as a factor hindering the use of various blockchains.

There is a need for a method and system for overcoming the above problems.

Registered Patent Publication No. 10-2461213

The purpose of the present invention is to provide a method of using a blockchain smart contract using an API providing system that can more easily and conveniently query the execution and transaction of a smart contract for users who have difficulty using blockchain smart contracts due to technical difficulties. is to do

In addition, an object of the present invention is to provide a method of using a blockchain smart contract using an API providing system that can more conveniently respond to transaction errors by providing a detailed and clear error message when a transaction error occurs.

In addition, the purpose of the present invention is to use a blockchain smart contract using an API providing system that enables smart contracts to be utilized for a blockchain that does not support smart contracts in order to improve scalability for the use of blockchains that do not support smart contracts. is to provide a way

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention not mentioned above can be understood by the following description and will be more clearly understood by the examples of the present invention. It will also be readily apparent that the objects and advantages of the present invention may be realized by means of the instrumentalities and combinations indicated in the claims.

A method of using a blockchain smart contract using an API providing system according to some embodiments of the present invention to solve the above problem is to provide a first smart contract of a first blockchain network supporting a smart contract service to the smart contract service. Receiving an application programming interface (API) for use in a second blockchain network that is not supported, mapping the first smart contract and the second blockchain network, and sending mapping data for the mapping to the API Storing in a providing system, obtaining a private key between the first blockchain network and the second blockchain network, storing the private key in the API providing system, the mapping data and the first smart contract Generating a first transaction based on first information about, transmitting the generated first transaction to the first blockchain network to store the first transaction in the first blockchain network, and receiving a call and responding the result to the API.

In addition, generating a second transaction based on the called API, and transmitting the second transaction to the first blockchain network to store the second transaction in the first blockchain network. can do.

In addition, the API providing system may perform communication with an external device based on Representational State Transfer (REST).

In addition, the API providing system includes a blockchain network connection unit that receives the generated first transaction, transmits the first transaction to the first blockchain network, and transmits the first transaction to the second blockchain network. The storing may include transmitting the first transaction to a node of the first blockchain network through the blockchain network connection unit.

In addition, the step of transmitting the first transaction to the first blockchain network and storing the first transaction in the first blockchain network is the step of receiving update data of the mapping data based on the first transaction. can include

An API providing system according to some embodiments of the present invention for solving the above problems receives an API (Application Programming Interface; API) call from a user device, and sends a request corresponding to the call to the user device through a blockchain network. 1 includes an API providing module that responds to a result and a blockchain network mapping module that controls mapping data between the blockchain network and a smart contract, wherein the API providing module provides a REST API (Representational State Transfer Application Programming Interface) to the user device. REST API), a storage unit for storing intermediate data used when generating the first result, and a communication unit configured to communicate with at least one of the user device, the storage unit, and the blockchain network. The control unit includes a transaction processing unit generating a transaction for executing the smart contract according to the call, a blockchain network connection unit transmitting the transaction to the blockchain network according to the call, and from the user device A service processing unit receiving the call and transmitting the call to the transaction processing unit, the blockchain network connection unit, and the storage unit is further included.

In addition, the blockchain network mapping module retrieves the mapping data from at least one blockchain network, and generates a blockchain data control unit that generates a private key by communicating with a node of the blockchain network, and generates the mapping data. The mapping data processing unit may further include storing the data in the storage unit and providing the mapping data to the transaction processing unit.

In addition, the blockchain network includes a first blockchain network that supports the service for the smart contract and a second blockchain network that does not support the service for the smart contract, and the blockchain data control unit, It may further include a network mapping module for mapping the first smart contract distributed in the first blockchain network and the second blockchain network, and storing data for the mapping in the storage unit.

In addition, the blockchain data control unit searches for first information about the first blockchain network and the first smart contract, generates a first transaction according to the first information, and transmits it to the first blockchain network. It may further include a data mapping module that does.

In addition, the intermediate data is at least one of information about the blockchain network, information about a wallet included in the blockchain network, information about the smart contract, information about the transaction, and information about the mapping data. It may further include information, wherein the information on the wallet included in the blockchain network includes an address for the wallet or a key for the wallet, and the information on the transaction may include hash information on the transaction. .

The method of using a blockchain smart contract using the API providing system of the present invention provides an accessible and familiar REST API and executes a smart contract through the API, thereby enabling easy and convenient use of the smart contract, thereby improving the utilization of the blockchain. can do.

In addition, when a transaction error occurs, it is possible to accurately and quickly respond to transaction errors by providing detailed and clear error messages to users through the REST API.

In addition, by connecting a blockchain that supports smart contracts to a blockchain that does not support smart contracts, the scalability of the blockchain can be improved by enabling the blockchain that does not support smart contracts to utilize the smart contracts.

In addition to the above description, specific effects of the present invention will be described together while explaining specific details for carrying out the present invention.

1 is a diagram for showing interactions between a user device, an API providing module, a blockchain network mapping module, and a blockchain network.
2 is a diagram for showing components of an API providing system.
3 is a diagram illustrating a process in which a user device executes a smart contract of a blockchain network supporting smart contracts through a REST API.
4 is a diagram for illustrating a process in which a user device uses a smart contract in a blockchain network that does not support smart contracts through a REST API.
5 is a diagram illustrating a process in which a user device retrieves a result of a transaction executed through a REST API.
6 is a diagram for explaining a process performed to utilize a smart contract in a network that does not support smart contracts.
7 is a diagram for illustrating an API sequence for executing a transaction.
8 is a diagram for illustrating an API sequence for querying a transaction result.
9 is a diagram illustrating a mapping process and a transaction execution process of a blockchain network that does not support smart contracts.
10 is a flowchart for briefly illustrating the process up to transaction transmission depending on whether smart contracts are supported.
11 is a flowchart for specifically showing the process up to transaction transmission depending on whether smart contracts are supported.
12 is a diagram for showing how a blockchain network mapping management unit is included in the control unit of the API providing system.

Terms or words used in this specification and claims should not be construed as being limited to a general or dictionary meaning. According to the principle that an inventor may define a term or a concept of a word in order to best describe his/her invention, it should be interpreted as meaning and concept consistent with the technical spirit of the present invention. In addition, the embodiments described in this specification and the configurations shown in the drawings are only one embodiment in which the present invention is realized, and do not represent all of the technical spirit of the present invention, so they can be replaced at the time of the present application. It should be understood that there may be many equivalents and variations and applicable examples.

Terms such as first, second, A, and B used in this specification and claims may be used to describe various components, but the components should not be limited by the terms. These terms are only used for the purpose of distinguishing one component from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the present invention. The term 'and/or' includes a combination of a plurality of related recited items or any one of a plurality of related recited items.

Terms used in this specification and claims are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. It should be understood that terms such as "include" or "have" in this application do not preliminarily exclude the presence or addition of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification. .

The meaning of a sentence containing “at least one of a, b, and c” means that the part includes only a, includes only b, includes only c, includes a and b, includes a and b, A case including c, a case including b and c, and a case including a, b, and c may be included.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs.

Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and unless explicitly defined in this application, it should not be interpreted in an ideal or excessively formal meaning. don't

In the present invention, blockchain or blockchain data is data maintained by each blockchain node constituting a blockchain network, in which at least one block is composed of a chain-type data structure. points to In a blockchain system, all blockchain nodes maintain the same blockchain data.

In the present invention, a blockchain network refers to a peer-to-peer (P2P) network composed of a plurality of blockchain nodes that operate according to a blockchain algorithm (or protocol).

In the present invention, a blockchain node refers to a computing node that constitutes a blockchain network and operates according to a blockchain algorithm (or protocol). The computing node may be implemented as a physical device, but may also be implemented as a logical device such as a virtual machine. When the computing node is implemented as a virtual machine, a plurality of blockchain nodes may be included in one physical device.

In the present invention, an application programming interface (API) refers to a language or message format used for communication between an operating system and an application program. Specifically, an API has a language or message format used by an application program to communicate with a system program, such as an operating system or database management system. is implemented as An API therefore has several program modules or routines that either already exist or must be linked to perform the work requested by the call to the function.

In the present invention, REST (Representational State Transfer; REST) refers to the web as a service API. Specifically, REST refers to a web interface environment that enables immediate use of various web services from a user's point of view. REST can implement a standardized technology environment that combines resources distributed on the web as a web service.

In the present invention, a smart contract refers to a script or software code used for transaction processing in a blockchain system. More specifically, the smart contract is code written programmatically for various conditions, states, and actions according to the conditions used in transaction processing, and may include, for example, an Ethereum smart contract. In a blockchain system, blockchain nodes can share smart contracts through the blockchain.

In the present invention, a transaction or blockchain transaction refers to any action that causes a change in state (eg, increase or decrease in balance, transfer of assets) in a blockchain environment, a state recorded in a blockchain ) may refer to all actions of retrieving data, or data indicating those actions. For example, the transaction may cover both an act of writing specific data to the blockchain and an act of reading specific data recorded in the blockchain. The transaction may be classified into a write-type transaction (eg, a transaction that adds, modifies, or deletes state data) and a read-type transaction (eg, a transaction that retrieves state data). Of course, depending on the blockchain platform, there may be various types of transactions (eg, execution) in addition to the read and write types, and in that case, the transaction may include all of the various types of transactions. Also, in the related art, terms such as a query of the read type transaction may be used interchangeably. The transaction can be executed through a smart contract (for example, accessing the blockchain through functions and variables defined in the smart contract), but this can vary depending on the blockchain platform.

Hereinafter, with reference to FIGS. 1 to 6, a method and system for using a smart contract in a blockchain network according to some embodiments of the present invention will be described.

FIG. 1 is a diagram illustrating interactions between a user device, an API providing module, a blockchain network mapping module, and a blockchain network, and FIG. 2 is a diagram illustrating components of an API providing system.

Referring to FIGS. 1 and 2 , the API providing system 10000 may include an API providing module 1000 and a blockchain network mapping management module 2000. The API providing module 1000 may receive an application programming interface (API) call from the user device UD, and respond a result corresponding to the call to the user device UD through a blockchain network.

When the call is a call to utilize a smart contract in a blockchain network that does not support smart contracts, the API providing module 1000 maps the blockchain network with the smart contract from the blockchain network mapping module 2000 The first mapping data may be queried to confirm whether or not there is a mapping. The searched first mapping data may be stored in the API providing module 1000 .

The blockchain network mapping module 2000 may control mapping data between the blockchain network and the smart contract.

In one embodiment, when the first mapping data exists in the blockchain network mapping module 2000, the blockchain network mapping module 2000 may transmit the first mapping data to the API providing module 1000, The API providing module 1000 may store the first mapping data.

In another embodiment, when the first mapping data does not exist in the blockchain network mapping module 2000, the blockchain network mapping module 2000 maps the blockchain network and the smart contract to generate second mapping data. can create The blockchain network mapping module 2000 may transmit the generated second mapping data to the API providing module 1000, and the API providing module 1000 may store the second mapping data.

The API providing module 1000 may compare the mapping data received from the blockchain network mapping module 2000 with the mapping data of the blockchain network (net).

When the mapping data stored in the API providing module 1000 and the mapping data of the blockchain network (net) match, the API providing module 1000 may generate a transaction that executes the smart contract. The API providing module 1000 may transmit the generated transaction to a blockchain network (net).

The API providing module 1000 may receive a query request for the transaction from the user device UD. The API providing module 1000 may request the transaction inquiry from the blockchain network net according to the inquiry request of the user device UD. The blockchain network (net) may respond to the result of the transaction to the API providing module 1000 according to the request of the API providing module 1000. The API providing module 1000 may receive the result and transmit it to the user device UD.

The blockchain network mapping module 2000 may modify or newly add mapping data based on the transaction or the result. The blockchain network (net) may provide data necessary for updating mapping data to the blockchain network mapping module 2000 .

The API providing system 10000 may include an API providing module 1000 and a blockchain network mapping management module 2000.

The API providing module 1000 may receive an API call from the user device UD and respond a result corresponding to the call to the user device UD through the blockchain network net. The API providing module 1000 may include a communication unit 1100, a storage unit 1200, and a control unit 1300.

The communication unit 1100 may be configured to communicate with at least one of the user device UD, the storage unit 1200, and a blockchain network net. The communication unit 1100 may transmit and receive data by communicating with at least one of the user device UD, the storage unit 1200, and the blockchain network net.

The storage unit 1200 may store intermediate data used in a process of generating a result corresponding to the call received from the user device UD.

The intermediate data includes information about a blockchain network (net), information about a wallet included in the blockchain network (net), information about a smart contract mapped with a blockchain network (net) that does not support smart contracts, It may include at least one of information about a transaction for executing a smart contract and information about mapping data between a blockchain network (net) and a smart contract.

In this case, the information about the wallet may include an address of the wallet or a key of the wallet. The information on the transaction may include hash information on the transaction.

The controller 1300 may provide a REST API 1311 to the user device UD. The control unit 1300 may include a service processing unit 1310, a transaction processing unit 1320, and a blockchain network connection unit 1330.

The service processing unit 1310 may transmit the API call received from the user device UD to the transaction processing unit 1320, the blockchain network connection unit 1330, and the storage unit 1200.

The transaction processing unit 1320 may create a transaction that executes a smart contract according to the API call. The transaction processing unit 1320 may transmit the generated transaction to the blockchain network connection unit 1330.

The blockchain network connection unit 1330 may transmit the transaction received from the transaction processing unit 1320 to the blockchain network (net) according to the API call.

The blockchain network mapping management module 2000 may control mapping data between a blockchain network (net) and a smart contract. The blockchain network mapping management module 2000 may include a blockchain data control unit 2100 and a mapping data processing unit 2200.

The blockchain data control unit 2100 may retrieve mapping data from at least one or more blockchain networks (net) and generate a private key by communicating with a node of the blockchain network (net). The blockchain data controller 2100 may include a network mapping module 2110 and a data mapping module 2120.

The network mapping module 2110 maps the first smart contract of the first blockchain network supporting the smart contract service and the second blockchain network that does not support the smart contract service, and stores data for the mapping in the storage unit 1200. ) can be stored.

The data mapping module 2120 may query first information about the first blockchain network and the first smart contract, generate a first transaction according to the first information, and transmit it to the first blockchain network there is. The data mapping module 2120 may include a contract mapping part 2121, a data mapping part 2122, and a key mapping part 2123.

The mapping data processing unit 2200 may generate and store mapping data in the storage unit 1200 and provide the mapping data to the transaction processing unit 1320 . The mapping data processing unit 2200 may include a key generation module 2210.

The key generation module 2210 generates the private key when a new private key is needed between the second blockchain network and the first blockchain network, and stores information on the private key in the API providing system 10000. It can be stored in unit 1200.

3 is a diagram illustrating a process in which a user device executes a smart contract of a blockchain network supporting smart contracts through a REST API.

Referring to FIG. 3 , the user device (UD) may call the REST API 1311 provided by the API providing system 10000 to execute the contract A (con_a) deployed in the blockchain network A (net_a). At this time, blockchain network A (net_a) means a blockchain network that supports contract A (con_a), and contract A (con_a) may mean an embodiment of a smart contract.

When the user device (UD) calls the REST API 1311 that executes the contract A (con_a) of the blockchain network A (net_a), the API providing system 10000 uses the information stored in the storage unit 1200 to make a transaction A transaction that executes contract A (con_a) corresponding to the REST API 1311 called by the processing unit 1320 may be created. The generated transaction may be transmitted to the node A (nd_a) of the blockchain network A (net_a) through the blockchain network connection unit 1330.

In one embodiment, the API providing system 10000 may transmit an API response to the user device UD after transmitting the transaction to the blockchain network A (net_a).

In another embodiment, the API providing system 10000 transmits the transaction to the blockchain network A (net_a), receives a response from the blockchain network A (net_a), and then sends the API to the user device (UD). response can be sent.

4 is a diagram for illustrating a process in which a user device uses a smart contract in a blockchain network that does not support smart contracts through a REST API.

Referring to FIG. 4 , the user device (UD) may utilize the second contract B (con_b2) distributed from the blockchain network C (net_c) to the blockchain network B (net_b) through the API providing system 10000. At this time, the blockchain network B (net_b) refers to a blockchain network supporting the first contract B (con_b1) and the second contract B (con_b2), and the blockchain network C (net_c) is a block that does not support smart contracts. It means a chain network, and the first contract B (con_b1) and the second contract B (con_b2) may mean some embodiments of smart contracts.

Hereinafter, the configuration of the blockchain network necessary for the process performed in FIG. 4 will be described.

A blockchain network (net) may refer to a P2P structured network composed of at least one blockchain node. In FIG. 4, the blockchain network (net) may include a blockchain network A (net_a), a blockchain network B (net_b), and a blockchain network C (net_c). At this time, blockchain network A (net_a) and blockchain network B (net_b) refer to blockchain networks that support smart contract services, and blockchain network C (net_c) refers to blockchain networks that do not support smart contract services. can mean

A blockchain network A (net_a) can be formed by participating at least one node A (nd_a). Each node A (nd_a) can manage blocks in a chain-type data structure. Each node A (nd_a) can ensure the integrity and security of the transaction and the integrity of the contract A (con_a) through a consensus process that records and verifies the transaction for contract A (con_a).

A blockchain network B (net_b) can be formed by participating at least one Node B (nd_b). Each Node B (nd_b) can manage blocks in a chain-type data structure. Each node B (nd_b) guarantees the integrity and security of the transaction through a consensus process of recording and verifying the transaction for the first contract B (con_b1) or the second contract B (con_b2), and the first contract B (con_b1) or the integrity of the second contract B (con_b2) can be guaranteed.

Blockchain network C (net_c) may include a wallet (wal_c). The wallet (wal_c) may mean a wallet that interacts with the blockchain network C (net_c). Specifically, the wallet (wal_c) may include information about a public key or a private key required for a transaction.

The network mapping module 2110 may map the second contract B (con_b2) and the blockchain network C (net_c), and store information about the mapping in the storage unit 1200 of the API providing system 10000. Accordingly, blockchain network C (net_c) can utilize the second contract B (con_b2) distributed in blockchain network B (net_b).

The key generation module 2210 generates the private key when a new private key is needed between the blockchain network C (net_c) and the blockchain network B (net_b), and transmits information about the private key to the API providing system 10000. Can be stored in the storage unit 1200 of.

The data mapping module 2120 includes information on the blockchain network (net), information on the smart contract (eg, smart contract address, etc.), and information on the wallet (wal_c) (eg, wallet address, etc.) At least one piece of information may be mapped with other information, and information on the mapping may be stored in the data mapping module 2120 or the storage unit 1200 .

Hereinafter, the process performed in FIG. 4 will be described in order.

When the user device (UD) calls the REST API (1311) of the API providing system (10000) to utilize the smart contract in the blockchain network C (net_c), the API providing system (10000) uses the data mapping module (2120) After retrieving the first mapping data between the blockchain network B (net_b) and the blockchain network C (net_c) and the second mapping data between the second contract B (con_b2) and the blockchain network C (net_c) through In step 1320, a transaction corresponding to the called REST API 1311 may be created.

The API providing system 10000 may generate a transaction in the transaction processing unit 1320 based on the first and second mapping data and transmit it to the blockchain network B (net_b). Blockchain network C (net_c) can view transactions transmitted to blockchain network B (net_b) through the wallet (wal_c).

The data mapping module 2120 may modify the first and second mapping data or add new third mapping data based on the generated transaction and the result of the transaction.

5 is a diagram illustrating a process in which a user device retrieves a result of a transaction executed through a REST API.

Referring to FIG. 5 , the API providing system 10000 may serve to process API requests received from the user device UD. The API providing system 10000 may play a role of generating a transaction according to the API request and transmitting it to a blockchain network (net). When an error occurs in the process of connecting to a blockchain network (net), the API providing system 10000 can leave a log of the error and respond to the user with details about the error.

In order to perform the role of the above-mentioned API providing system 10000, the block chain network (net) needs a process of retrieving transactions from the API providing system 10000, and to explain the above process, refer to FIG. 5 again. If so, the user device UD may request an API for executing transaction inquiry. The transaction may refer to a transaction generated from the API providing system 10000 and transmitted to the blockchain network A (net_a).

The API providing system 10000 may request a result of the transaction from the node A (nd_a) of the blockchain network A (net_a) through the blockchain network connection unit 1330.

The API providing system 10000 may receive the result from node A (nd_a) through the blockchain network connection unit 1330. The API providing system 10000 may store the received result in the storage unit 1200 and respond to the result to the user device UD.

6 is a diagram for explaining a process performed to utilize a smart contract in a network that does not support smart contracts.

Hereinafter, the configuration of a system used to perform the process and the role of the configuration will be described.

Referring to FIGS. 2 and 6, the system used to perform the process is a user device (UD), an API providing module 1000, a blockchain network mapping management module 2000, a blockchain network B (net_b), It may include blockchain network C (net_c) and blockchain network D (net_d). At this time, blockchain network B (net_b) may mean a blockchain network supporting smart contract service, and blockchain network C (net_c) and blockchain network D (net_d) are blockchains that do not support smart contract service. can mean a network.

The 1st, 2nd and 3rd contracts B (con_b1, con_b2, con_b3) deployed on the blockchain network B (net_b) transfer transactions for smart contract execution from the API providing module 1000 to the blockchain network B (net_b). It can be executed by sending

Below, we will explain the process performed when trying to utilize a smart contract deployed in blockchain network B (net_b) in blockchain network C (net_c), which does not support smart contracts.

A first contract B (con_b1), a second contract B (con_b2), or a third contract B (con_b3) may be deployed on a blockchain network B (net_b) supporting smart contracts.

In one embodiment, the second and third contract B (con_b3) may mean a smart contract having the same configuration as the first contract B (con_b1).

In another embodiment, the second and third contracts B (con_b3) add a configuration for storing necessary information when executing the second contract B (con_b2) or the third contract B (con_b3) in the blockchain network B (net_b). It can mean a smart contract.

The network mapping module 2110 may map information in the blockchain network B (net_b) and information in the blockchain network C (net_c), and transmit first data for the mapping to the API providing module 1000. The API providing module 1000 may store the received first data.

For example, the network mapping module 2110 maps at least one of the first, second, and third contracts B (con_b3) in the blockchain network B (net_b) and information in the blockchain network C (net_c), Second data for mapping may be transmitted to the API providing module 1000 . The API providing module 1000 may store the received second data.

At this time, the information in the blockchain network C (net_c) may mean information such as an address for a wallet in the blockchain network C (net_c).

When the user device (UD) calls an API for utilizing the second contract B (con_b2) in the blockchain network C (net_c), the API providing module 1000 maps information in the blockchain network C (net_c) A transaction for executing the second contract B (con_b2) may be created. In this case, the transaction may be generated using the first and second data. However, this embodiment is not limited thereto. That is, when a smart contract is used in a network that does not support smart contract services, the network may mean blockchain network C (net_c) or blockchain network D (net_d), and the smart contract is the first and second smart contracts. 2 and 3 contract B (con_b1, con_b2, con_b3).

Hereinafter, processes of transaction execution, result inquiry, and execution will be described with reference to FIGS. 7 to 9 .

7 is a diagram for illustrating an API sequence for executing a transaction.

Referring to FIGS. 2 and 7 , the API sequence for executing a transaction proceeds in the following order.

The user device UD requests an API for executing a transaction from the API providing system 10000 (SA1). The API providing system 10000 requests a wallet key from the storage unit 1200 (SA2). The storage unit 1200 responds to the wallet key request to the API providing system 10000 (SA3). The API providing system 10000 transmits the transaction to the blockchain network (net) (SA4). The blockchain network (net) responds to the transaction received from the API providing system (10000) (SA5). The API providing system 10000 stores a record of the transaction in the storage unit 1200 (SA6). The API providing system 10000 responds with the API to the user device UD (SA7).

8 is a diagram for illustrating an API sequence for querying a transaction result.

Referring to FIGS. 2 and 8 , the API sequence for querying the transaction result proceeds in the following order.

The user device (UD) requests an API for querying the transaction result (SB1). The API providing system 10000 requests the hash of the transaction from the storage unit 1200 (SB2). The storage unit 1200 responds to the request to the API providing system 10000 (SB3). The API providing system 10000 requests a result of the transaction from the blockchain network (net) (SB4). The blockchain network (net) responds the result of the transaction to the API providing system (10000) (SB5). The API providing system 10000 stores the result of the transaction in the storage unit 1200 (SB6). The API providing system 10000 responds the result of the transaction to the user device UD (SB7).

9 is a diagram illustrating a mapping process and a transaction execution process of a blockchain network that does not support smart contracts.

Referring to FIGS. 2 and 9, the mapping process (SC) of a blockchain network that does not support smart contracts proceeds in the following order.

The blockchain network mapping management module 2000 queries the data structure of the blockchain network C (net_c) that does not support the smart contract service (SC1). The blockchain network mapping management module 2000 maps contract B deployed in blockchain network B (net_b) supporting smart contracts and information in blockchain network C (net_c) (SC2). The blockchain network mapping management module 2000 stores the mapping data in the API providing module (SC3).

Referring back to FIGS. 2 and 9 , the transaction execution process (SD) of a blockchain network that does not support smart contracts proceeds in the following order.

The user device UD requests an API for executing a transaction from the API providing module 1000 (SD1). The API providing module 1000 requests mapping data between the contract B deployed in the blockchain network B (net_b) and the blockchain network C (net_c) from the blockchain network mapping management module 2000 (SD2). The blockchain network mapping management module 2000 generates a key in the blockchain network B (net_b) (SD3). The blockchain network B (net_b) maps the key through the blockchain network mapping management module 2000 (SD4). The blockchain network mapping management module 2000 responds with the mapping data to the API providing module 1000 (SD5). The API providing module 1000 transmits the transaction to blockchain network B (net_b) (SD6). The API providing module 1000 updates the mapping data to the blockchain network mapping management module 2000 (SD7). The blockchain network mapping management module 2000 stores the mapping data in the API providing module 1000 (SD8). The API providing module 1000 responds with the requested API result to the user device (SD9).

Hereinafter, with reference to FIGS. 10 and 11, the process of transmitting a transaction according to whether a smart contract is supported by a blockchain network will be described.

10 is a flowchart for briefly illustrating the process up to transaction transmission depending on whether smart contracts are supported.

Referring to FIGS. 2 and 10 , an API service is registered and managed in a user device (UD) (S100). It is checked whether an API request is received from the user device (UD) in the API providing system (10000) (S200). When receiving the API request, the API providing system 10000 checks whether the blockchain network used for the request supports the smart contract service (S300). In the case of a blockchain network that does not support smart contracts, the API providing system 10000 searches the smart contract mapped with the blockchain network in the storage unit 1200 (S400). The API providing system 10000 generates a transaction corresponding to the API request (S500). The API providing system 10000 connects to at least one node constituting the blockchain network (S600). The API providing system 10000 transmits the generated transaction to the blockchain network through the connected node (S700).

11 is a flowchart for specifically showing the process up to transaction transmission depending on whether smart contracts are supported.

Referring to FIGS. 2 and 11 , an API service is registered and managed in the user device (UD) (S100). Specifically, registering and managing the API service may mean that the user device UD and the API providing system 10000 maintain communication with each other. At this time, the API providing system may perform communication with an external device based on REST. However, this embodiment is not limited thereto.

It is checked whether an API request is received from the user device (UD) in the API providing system (10000) (S200). Specifically, the API providing system 10000 is for using a first smart contract of a first blockchain network supporting a smart contract service from a user device (UD) in a second blockchain network that does not support the smart contract service. API can be called.

When receiving the API request, the API providing system 10000 checks whether the blockchain network used for the request supports the smart contract service (S300).

In the case of a blockchain network that does not support smart contract services, the API providing system 10000 searches the smart contract mapped with the blockchain network in the storage unit 1200 (S400). Conversely, in the case of a blockchain network supporting smart contract services, the API providing system 10000 may generate a transaction based on the API request. The API providing system 10000 may transmit and store the generated transaction in a blockchain network supporting a smart contract service.

If there is no smart contract mapped in the storage unit 1200, the smart contract of the blockchain network supporting the smart contract and the blockchain network not supporting the smart contract are mapped (S420). Specifically, the first smart contract and the second blockchain network may be mapped using the blockchain network mapping management module 2000.

Data for the mapping is stored in the storage unit 1200 (S430). Specifically, mapping data for the mapping may be stored in the API providing system 10000.

A private key between the first blockchain network and the second blockchain network is obtained (S440). Specifically, when the private key used for the request does not exist in the storage unit 1200, the API providing system 10000 may generate the private key using the blockchain network mapping management module 2000.

The private key is stored in the storage unit 1200 of the API providing system 10000 (S450).

A transaction corresponding to the API request is generated (S500). Specifically, the API providing system 10000 may generate a first transaction based on the mapping data and information on the first smart contract. The API providing system 10000 may transmit the generated first transaction to the first blockchain network and store the first transaction in the first blockchain network. At this time, the API providing system 10000 may receive update data of the mapping data from the first blockchain network or the second blockchain network based on the first transaction.

The API providing system 10000 connects to at least one node constituting the blockchain network (S600).

The API providing system 10000 transmits the generated transaction to the blockchain network through the connected node (S700). Specifically, the API providing system 10000 may include a blockchain network connection unit 1330 receiving the generated first transaction. The API providing system 10000 may transmit the first transaction to the node of the first blockchain network through the blockchain network connection unit 1330. After step S700, the API providing system 10000 may respond with a result of the API request.

Hereinafter, referring to FIG. 12, a case in which the blockchain network mapping management unit is included in the control unit of the API providing system will be described.

12 is a diagram for showing how a blockchain network mapping management unit is included in the control unit of the API providing system.

Referring to FIGS. 2 and 12 , the blockchain network mapping management module 2000 and the blockchain network mapping management unit 1340 may include the same or similar components. While the blockchain network mapping management module 2000 of FIG. 2 is a concept separate from the API providing module 1000, the blockchain network mapping management unit 1340 of FIG. 12 is in the control unit 1300 of the API providing system 10000. It can perform the same or similar role as the included blockchain network mapping management module 2000.

The above description is merely an example of the technical idea of the present embodiment, and various modifications and variations can be made to those skilled in the art without departing from the essential characteristics of the present embodiment. Therefore, the present embodiments are not intended to limit the technical idea of the present embodiment, but to explain, and the scope of the technical idea of the present embodiment is not limited by these embodiments. The scope of protection of this embodiment should be interpreted according to the claims below, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of rights of this embodiment.

Claims (10)

Receiving a call to an API (Application Programming Interface; API) for using a first smart contract of a first blockchain network supporting a smart contract service in a second blockchain network that does not support the smart contract service;
Mapping the first smart contract and the second blockchain network;
Storing mapping data for the mapping in an API providing system;
obtaining a private key between the first blockchain network and the second blockchain network;
storing the private key in the API providing system;
generating a first transaction based on the mapping data and first information on the first smart contract;
transmitting the generated first transaction to the first blockchain network and storing the first transaction in the first blockchain network; and
Including the step of responding to the result of the called API,
How to use blockchain smart contract using API provision system.
According to claim 1,
generating a second transaction based on the called API;
Further comprising transmitting the second transaction to the first blockchain network and storing the second transaction in the first blockchain network.
How to use blockchain smart contract using API provision system.
According to claim 1,
The API providing system,
Communication with an external device based on REST (Representational State Transfer; REST),
How to use blockchain smart contract using API provision system.
According to claim 1,
The API providing system,
A blockchain network connection unit receiving the generated first transaction,
The step of transmitting the first transaction to the first blockchain network and storing the first transaction in the first blockchain network,
Transmitting the first transaction to a node of the first blockchain network through the blockchain network connection unit,
How to use blockchain smart contract using API provision system.
According to claim 1,
The step of transmitting the first transaction to the first blockchain network and storing the first transaction in the first blockchain network,
Receiving update data of the mapping data based on the first transaction,
How to use blockchain smart contract using API provision system.
An API providing module that receives an API (Application Programming Interface) call from a user device and responds to a first result corresponding to the call to the user device through a blockchain network; and
Including a blockchain network mapping module that controls mapping data between the blockchain network and smart contract,
The API providing module,
A control unit providing a REST API (Representational State Transfer Application Programming Interface; REST API) to the user device;
a storage unit for storing intermediate data used when generating the first result;
A communication unit configured to communicate with at least one of the user device, the storage unit, and the blockchain network;
The control unit,
A transaction processor generating a transaction for executing the smart contract according to the call;
A blockchain network connection unit for transmitting the transaction to the blockchain network according to the call;
Further comprising a service processing unit that receives the call from the user device and transmits it to the transaction processing unit, the blockchain network connection unit, and the storage unit.
API delivery system.
According to claim 6,
The blockchain network mapping module,
A blockchain data control unit that retrieves the mapping data from at least one blockchain network and generates a private key by communicating with a node of the blockchain network;
Further comprising a mapping data processing unit generating and storing the mapping data in the storage unit and providing the mapping data to the transaction processing unit.
API delivery system.
According to claim 7,
The blockchain network,
A first blockchain network that supports services for the smart contract;
Including a second blockchain network that does not support the service for the smart contract,
The blockchain data control unit,
Further comprising a network mapping module for mapping the first smart contract distributed in the first blockchain network and the second blockchain network and storing data for the mapping in the storage unit,
API delivery system.
According to claim 8,
The blockchain data control unit,
Further comprising a data mapping module for querying first information about the first blockchain network and the first smart contract, generating a first transaction according to the first information, and transmitting it to the first blockchain network,
API delivery system.
According to claim 6,
The intermediate data is
Further including at least one of information about the blockchain network, information about a wallet included in the blockchain network, information about the smart contract, information about the transaction, and information about the mapping data,
The information on the wallet included in the blockchain network includes an address for the wallet or a key for the wallet,
The information about the transaction includes hash information about the transaction,
API delivery system.

Images