WO2023163415A1

WO2023163415A1 - Application data blockchain storage method, and system using same

Info

Publication number: WO2023163415A1
Application number: PCT/KR2023/001638
Authority: WO
Inventors: 임태현
Original assignee: 주식회사 원유니버스
Priority date: 2022-02-22
Filing date: 2023-02-06
Publication date: 2023-08-31
Also published as: KR20230125951A; KR102634318B1

Abstract

The present invention comprises: a data determination step in which an application determines object data to be stored in a blockchain; and a blockchain storage step of storing the object data in the blockchain, wherein the blockchain storage step comprises: a smart contract generation step in which a transaction management unit generates, on the basis of the object data, a smart contract including an initiation function, a rollback function and a commit function; an initiation function execution step in which the transaction management unit executes the initiation function for the object data so as to initiate transaction; an initiation function signature step in which a blockchain signature management unit signs for initiation function execution of the generated smart contract; a final command transmission step in which the application transmits a commit request or a rollback request; a final command execution step in which the transaction management unit executes the commit function or the rollback function according to a final command; and a final command signature step in which the blockchain signature management unit signs for final command execution in the transaction management unit.

Description

Block chain storage method of application data and system using the same

The present invention relates to a blockchain storage method of application data and a system using the same.

When storing data such as data tokens in applications such as games, the data can be stored in the blockchain to prevent forgery. However, this creates a difference in functionality from using an existing database. A typical example is the applicability of transactions.

Existing database systems can manage a series of processes of reading and writing data as transactions. In order to maintain the integrity of the database, a transaction either completes the entire process when several processes are executed in succession, or prevents it from proceeding.

As a typical example, when withdrawing money from one account and depositing money into another account, if the money is not withdrawn from the account in the preceding process, all procedures together with the process of depositing money into another account fail. , the process of transferring deposits is managed as a transaction.

In the existing blockchain system, it is not easy to cancel the process in which data is stored when a part of a series of processes fails in the recording of data. In particular, in applications that require rapid data input and output, such as games, when blockchain is applied, defects may occur in data processing that requires such transactions.

The present invention has been devised to solve the above conventional problems, and an object of the present invention is to provide a method of storing application data in a blockchain that can be easily used in applications such as games.

In addition, an object of the present invention is to provide a system using a method of storing application data on a blockchain.

The blockchain storage method for application data provided by the present invention includes a data determination step of determining target data to be stored in a block chain in an application, and a block chain storage step of storing the target data on the block chain,

In the blockchain storage step, a smart contract creation step in which a transaction management unit creates a smart contract including an initiation function, a rollback function, and a commit function based on target data, and a transaction management unit performs an initiation function for the target data to complete the transaction. The initiation function execution step, the initiation function signature step in which the blockchain signature management unit signs the initiation function execution of the created smart contract, the final command sending step in which the application sends a commit request or rollback request, and the transaction management unit executes the final command It is characterized in that it includes a final command execution step of performing a commit function or a rollback function according to the function, and a final command signing step of proceeding to sign the final command execution in the transaction management unit in the block chain signature management unit.

In one embodiment, the data determination step may include a mission condition completion determination step in which the success of the mission is determined when the player satisfies the completion condition of the specified mission in the game, and a reward provided online to the player is paid according to the completion of the mission. Including a reward data payment step in which doing is initiated, and a state storage step of saving the state of the player,

The target data determined in the data determination step may be data regarding compensation according to task completion.

In one embodiment, after the data determining step, a database storage step of storing the target data in the database, may be characterized in that it further comprises.

In one embodiment, the application block chain data storage method, characterized in that the database storage step and the block chain storage step are bound and processed as one transaction.

In one embodiment, the activation condition of the rollback function of the smart contract may be a condition in which database transaction rollback occurs during the storage step in the database.

In one embodiment, the target data is data about tokens provided to players in the application, and the target data may include an owner and an amount of tokens provided.

In one embodiment, the step of performing the initiation function and the step of signing the initiation function may be characterized in that the application pre-allocates the amount of tokens provided to the player.

In one embodiment, the target data is data about a token used by a player as an application, and the target data may include an owner and an amount of tokens provided.

In one embodiment, the step of performing the initiation function and the step of signing the initiation function may be characterized by moving a token provided from the player to the application to the application.

In one embodiment, the target data is data about a non-fungible token (NFT), and the target data may be characterized as owner data and CDN data of used data.

Therefore, according to the present invention, when an application stores data on a blockchain, it is possible to implement rollback of data storage using a separate transaction manager. Because of this, in the case of incorrect storage, it remains unprocessed, so it is possible to reprocess by rechecking the process later. A more stable supply is possible when rewards such as blockchain tokens are paid.

In addition, by processing the database and the block chain in parallel, all transactions can be treated as failures when the database side determines failure.

In addition, in the process of storing data on the blockchain at the initiation stage of the smart contract, processes to be processed in advance, such as restriction processing or transfer processing of tokens, are first processed, effectively performing the subsequent storage stage of the blockchain. can make it

1 is a conceptual diagram of a system using a blockchain storage method of application data according to an embodiment of the present invention.

FIG. 2 is a flowchart illustrating a method of storing application data in a block chain according to the embodiment of FIG. 1 .

FIG. 3 is a conceptual diagram illustrating the operation of a system using the blockchain storage method of application data according to the embodiment of FIG. 1 .

4 is a flowchart illustrating a method of storing application data in a block chain according to another embodiment of the present invention.

5 is a conceptual diagram of a system using a blockchain storage method of application data according to another embodiment of the present invention.

6 is a flowchart illustrating a method of storing application data in a block chain according to the embodiment of FIG. 5 .

7 is a conceptual diagram showing an object of a blockchain storage system according to another embodiment of the present invention.

Hereinafter, with reference to the accompanying drawings, a preferred embodiment will be described with reference to the accompanying drawings. In this process, the thickness of lines or the size of components shown in the drawings may be exaggerated for clarity and convenience of description. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of a user or operator. Therefore, definitions of these terms will have to be made based on the content throughout this specification.

In this specification, a module may mean a functional and structural combination of hardware for implementing the technical idea of the present invention and software for driving the hardware. For example, the module may refer to a predetermined code and a logical unit of hardware resources for executing the predetermined code, and does not necessarily mean a physically connected code or one type of hardware according to the present invention. can be easily deduced to the average expert in the art.

In addition, the following examples do not limit the scope of the present invention, but are presented as examples only, and there may be various embodiments implemented through the technical idea.

어플리케이션 데이터의 블록체인 저장 시스템Blockchain storage system for application data

Referring to FIG. 1 , the blockchain storage system of this embodiment includes an application 100, a transaction management unit 200, a blockchain 300, and a blockchain signature management unit 400.

The application 100 can be applied to any system that needs to store games or other data in the blockchain 300. The blockchain storage system of this embodiment utilizes the transaction management unit 200 to use a smart contract of the blockchain in an application 100 such as a game.

In general, in order to utilize a blockchain smart contract, separate data must be created, the data must be signed by a user, and transmitted to the blockchain. This process is complicated and inconvenient to use compared to general databases. In particular, applications such as games need to be fast and easy to use.

In this embodiment, when there is a request from the application 100 to store data that needs to be stored in the block chain 300, the transaction management unit 200 forms a smart contract in a form suitable for the block chain 300 with the request related to the data. let it

After that, when a necessary request is generated, the blockchain signature management unit 400 can manage the signature for the corresponding function. The blockchain signature management unit 400 may use a wallet service such as Metamask. A detailed description of the process will be given with reference to FIG. 2 .

어플리케이션 데이터의 블록체인 저장 방법Blockchain storage method of application data

Referring to FIG. 2, the block chain storage method of application data according to the embodiment according to the present embodiment includes a data determination step (S100) of determining target data to be stored in the block chain in the application and storing the target data on the block chain. It includes a blockchain storage step (S200).

In the data determination step ( S100 ), data to be stored may be determined under various circumstances and conditions according to the process and logic of the application. In the present invention, storing data in a game has been described as an example, but it can be applied to various other implementation applications as well as silk. As a result, in the data determination step (S100), various types of information about the data to be stored in the block chain are determined. When these constraints are satisfied, it is possible to modify and apply various parts such as additional conditions, data storage format, and stored data capacity.

In the block chain storage step (S200), the data determined in the data determination step (S100) is stored in the block chain. The characteristic of this embodiment is that the data stored in the blockchain storage step (S200) can be rolled back. Specifically, the blockchain storage step (S200) is described as follows.

In the blockchain storage step (S200), first, a smart contract including an initiation function, a rollback function, and a commit function is created based on the target data in the transaction management unit 200 (S210). The smart contract created at this time includes an initiation function to initiate data storage, a rollback function to rollback data storage, and a commit function to confirm data storage.

Thereafter, the application 100 may communicate with the transaction management unit 200 with a command requesting a start function, a rollback function, and a commit function, i.e., start, cancel, and completion of a query. Since the smart contract created by the transaction management unit 200 was created including an initiation function, a rollback function, and a commit function at the time of creation, when each request of the application 100 occurs, the transaction management unit 200 corresponds to each proceed to perform the function.

First, the transaction management unit 200 may perform an initiation function for target data to initiate a transaction (S220). Initiation function execution step (S220) proceeds with the initiation of the task of storing the corresponding data in the block chain 300, and may be a criterion for transaction management.

When the transaction management unit 200 performs the initiation function, the electronic signature required in this step is signed in the block chain signature management unit 400 to perform the initiation function (S230).

After the initiation function execution step (S220) and the initiation function execution signature step (S230) are performed, the application 100 may proceed with another process. As a result of the progress of other processes, it may be decided whether to cancel or complete the blockchain storage transaction of the data currently in progress. This is determined by subsequent processes.

Afterwards, the application 100 may send a commit request or rollback request command to the transaction management unit 200 . This proceeds in the final command sending step (S240). The data to be finally stored can be communicated by selecting one of a completion or cancellation command, and the transaction management unit 200 receiving such a command from the application 100 executes the command.

The transaction management unit 200 performs a commit function or a rollback function according to the final command, which proceeds in the final command execution steps S251 and S252. The execution of the final command may be a commit execution (S251) or a rollback execution (S252).

As before, in the final command signing step (S261, S262), immediately before performing each function in the transaction management unit 200, the blockchain signature management unit 400 proceeds to sign the final command execution. The signature for the execution of the final command may be a signature for commit execution (S261) or a signature for rollback execution (S262).

Referring to FIG. 3 , the transaction management unit 200 may perform an initiation function, a commit function, and a rollback function according to the generated smart contract. Each of these functions is performed by a command transmitted from the application 100 .

On the other hand, in order to reflect the performance of each step to the blockchain 300, a separate signature must be performed, and the blockchain signature management unit 400 proceeds to sign the smart contract immediately before performing each step.

When the transaction management unit 200 performs the function of the smart contract, the blockchain signature management unit 400 can proceed with signing immediately before execution of each step so that each signature can be performed more efficiently.

게임 내에서 진행 프로세스Progression process within the game

Referring to FIG. 4 , a flowchart showing an embodiment applied to a specific game application can be grasped.

When applied to a game application, the target data determination step (S100) is a mission condition completion determination step (S110) in which the success of the mission is determined when the player satisfies the completion conditions of the specified mission in the game (S110), and the player is provided online according to the completion of the mission. It can be embodied by including a compensation data payment step (S120) in which the payment of the reward provided is initiated and a state storage step (S130) for storing the state of the player.

When the quest completion conditions are identified (S110), reward data such as items or coins is paid (S120), and these reward data are stored as state data for each individual player (S130). In the prior art, when saving as individual player's state data (S130), it can be stored in a general database, and in this case, transaction management is possible due to its own database.

On the other hand, in the case of this embodiment, which includes the process of storing in the blockchain (S200) in case of saving as individual player state data (S130), due to the characteristics of the blockchain, the operation is not synchronized with the data storage in real time. , additional management for transactions is required.

데이터베이스와 블록체인의 병렬 구성Parallel configuration of database and blockchain

5 is a conceptual diagram of a system using a blockchain storage method of application data according to another embodiment of the present invention. 6 is a flowchart illustrating a method of storing application data in a block chain according to the embodiment of FIG. 5 .

Referring to FIG. 5, the blockchain storage system according to this embodiment further includes a database 500 in addition to the application 100, the transaction management unit 200, the blockchain 300, and the blockchain signature management unit 400. do. The database 500 can store data to be stored in parallel with the block chain 300 and complement the process of storing the block chain 300 alone.

Referring to FIG. 6 , the block chain storage method of this embodiment further includes a general database storage step (S300) of storing target data in a database after the data determination step (S100). The step of storing in the database and the step of storing in the blockchain are bound and processed as one transaction.

Expressing this in capital code is as follows.

dbTx = Database. BeginTransaction();

contractTx = Contract.BeginTransaction();

try {

dbTx. Commit();

contractTx. Commit();

} catch {

dbTx. Rollback();

contractTx. Rollback();

}

When binding the blockchain and the database as a single transaction, the processing condition of the database can be used as the activation condition of the blockchain. The condition for activating the smart contract's rollback function can be a condition in which database transaction rollback occurs during the saving step to the database.

For example, the following situation can be assumed. After receiving an item and a token that the player can wear as a reward, the system tried to save the item, but at that time, the inventory space was full and the database process was unable to save any more.

In this case, in the first case, the item reward is not received and only the token reward is received, and the task is completed, or in the second case, the item reward is not received and the token reward is received, but the task is not completed. The first is a problem because the player did not receive the reward that he was clearly supposed to receive, and the second is a problem because there may be a situation where the token reward continues to be received continuously.

Therefore, in this embodiment, it is necessary to convert this process to the one in which the task is not completed without item compensation and token compensation. To do this, the database process and the blockchain process must be tied together as a transaction.

Expressing this in capital code is as follows.

UpdateData(player, rewards) {

itemReward = reward[0];

tokenReward = reward[1];

dbTx = Database. BeginTransaction();

contractTx = Contract.BeginTransaction();

try {

task1 = dbtx.AsyncExecuteProc("AddItem", itemReward.ItemId);

task2 = contractTx.AsyncSend("EarnToken", player, tokenReward.Amount);

WaitAll(task1, task2);

dbTx. Commit();

contractTx. Commit();

} catch {

dbTx. Rollback();

contractTx. Commit();

}

트랜잭션 관리자의 각 모듈별 구현Implementation of each module of transaction manager

Referring to FIG. 7 , an example of storing data in a blockchain through a transaction management unit within an application may include three types of player token acquisition, player token use, and player NFT acquisition.

The first is a case of providing tokens to players due to rewards within the application. In principle, it is assumed that the application holds an infinite number of tokens, or if there is already a limited number of issued tokens, the number of newly provided tokens can be limited or pre-allocated within the system in consideration of the limited number of issued tokens.

The code for the number of modules called when a player acquires a token in the game is as follows.

EarnToken {

Begin(user, amount) {

this. amount = amount;

this. user = user;

}

Commit() {

contract = SmartContract.Get(TOKEN_CONTRACT_ADDRESS);

userAddress = GetAddress(this.user);

tx = contract.TransferTo(userAddress, this.amount);

signedTx = InternalWallet. Sign(tx);

signedTx. Call();

Reply(SUCCESS);

}

Rollback() {

Reply(FAIL);

}

When applied to the blockchain storage method of the present invention, target data can be limited to data related to a token provided to a player in an application. Also, the target data is designed to include the owner and the amount of tokens offered.

Within the process of the blockchain storage method of the present invention, the operation of the initiation step can be performed in the initiation function execution step and initiation function signature step. The initiation function performed at this time may be a task of pre-allocating the amount of tokens provided to the player in the application.

The second is the case of using the player's token within the application. In the case of using a token owned by a player, fast processing can be performed by moving the token owned by the player into the system in advance.

The number of modules that are called when a user uses a token is also code.

ConsumeToken {

Begin(user, amount)} {

this. amount = amount;

this. user = user;

contract = SmartContract.Get(TOKEN_CONTRACT_ADDRESS);

tx = tokenContract.TransferTo(GetGameAddress(), this.amount);

userAddress = GetAddress(this.user);

signedTx = ExternalWalletService. sign(userAddress , tx);

signedTx. Call();

}

Commit(user) {

Reply(SUCCESS);

}

Rollback(user) {

contract = SmartContract.Get(TOKEN_CONTRACT_ADDRESS);

userAddress = GetAddress(this.user);

tx = tokenContract.TransferTo(userAddress, this.amount);

signedTx = InternalWallet. Sign(tx)

signedTx. Call();

Reply(FAIL);

}

When applied to the blockchain storage method of the present invention, target data can be limited to data related to a token used as an application in a player. Subject data may include the owner and amount of tokens provided.

Within the process of the blockchain storage method of the present invention, the operation of the initiation step can be performed in the initiation function execution step and initiation function signature step. In the starting function execution step and the starting function signing step, the token provided to the application from the player may be transferred to the application.

The third is when a user acquires a Non-Fungible Token (NFT). NFT consists of two parts: data and contract. When the NFT is created successfully, the data is uploaded to the CDN. At this time, in order to have an address related to the NFT, the contract address of the NFT is provided as a hint to the CDN.

The following is the code for the number of modules called when a player acquires an NFT.

CreateNFT {

Begin(user, data) {

this. data = data;

this. user = user;

}

Commit(user) {

contract = SmartContract.Get(NFT_FACTORY_CONTRACT);

// NFTs

userAddress = GetAddress(this.user);

tx = contract.MintTo(this.url, userAddress);

signedTx = InternalWallet. Sign(tx)

nftAddress = signedTx. Call();

// CDN

this.url = CDN.Upload(nftAddress, this.data);

Reply(SUCCESS, nftAddress);

}

Rollback(user) {

Reply(FAIL);

}

When applied to the block chain storage method of the present invention, the target data is data on a non-fungible token (NFT), and the target data can be limited to owner data and CDN data of used data.

블록체인 상의 롤백이 필요한 다양한 예시Various examples requiring rollback on the blockchain

Although not shown in the drawing, the following situations may occur in cases where rollback processing is required when data is stored on the blockchain.

As a typical example, a situation in which an item cannot be logically stored, such as when an inventory is full in storing data such as an item, may occur. There may be cases where other players' users are in an inactive state such as when they die in the game. In this case, rollback can be performed on the storage of data for which compensation payment has been confirmed.

In other cases, the network connection between the game server and the database momentarily fails, and the command is forcibly rolled back. This may be in an uncertain situation such as a network temporarily not being maintained due to network equipment problems or other power outages. If the network fails momentarily, the work that could not be performed can be re-executed by reconnecting to the network.

In addition, there may be programmatic bugs found during game operation. In an environment where it is frequently updated and the structure of the program can be changed, errors in the system can occur at any time, and the problem of compensation processing due to this is a problem that must be brought within a manageable range.

Finally, there is the possibility of using cheating programs such as hacking programs by malicious users. Even in this case, when a hacking program is detected, there is a need to recover rewards such as tokens provided through rollback processing.

Meanwhile, embodiments within the scope of the present invention include computer-readable media having or conveying computer-executable instructions or data structures stored on the computer-readable media. Such computer readable media can be any available media that can be accessed by a general purpose or special purpose computer system. For example, such computer readable media may be in the form of RAM, ROM, EPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage, or computer executable instructions, computer readable instructions or data structures. It can include a physical storage medium, such as any other medium that can be used to store or convey certain program code means in , and that can be accessed by a general purpose or special purpose computer system.

One embodiment of the present invention described above is only exemplary, and those skilled in the art will appreciate that various modifications and equivalent other embodiments are possible therefrom. . Therefore, it will be well understood that the present invention is not limited to the forms mentioned in the detailed description above. Therefore, the true technical protection scope of the present invention should be determined by the technical spirit of the appended claims. It is also to be understood that the present invention includes all modifications, equivalents and alternatives within the spirit and scope of the present invention as defined by the appended claims.

Claims

A data determination step in which target data to be stored in the blockchain is determined in the application; And a blockchain storage step of storing the target data on a blockchain,

The block chain storage step,

In a transaction management unit, a smart contract creation step of creating a smart contract including an initiation function, a rollback function, and a commit function based on the target data;

performing an initiating function of initiating a transaction by performing the initiating function for the target data in the transaction management unit;

An initiation function signing step of signing the initiation function of the generated smart contract in a blockchain signature management unit;

Sending a final command to send a commit request or rollback request from the application; and

a final command execution step of performing the commit function or the rollback function according to the final command by the transaction management unit;

In the block chain signature management unit, a final command signing step of proceeding with a signature for the execution of the final command in the transaction management unit;

Application data block chain storage method comprising a.
According to claim 1,

The data determination step,

a task condition completion determination step in which the player satisfies a completion condition of a specified task in the game and the success of the task is determined;

a reward data payment step in which a reward provided to the player on-line is started to be paid upon completion of the mission; and

A state storage step of storing the state of the player,

The method of storing application blockchain data, characterized in that the target data determined in the data determining step is data related to compensation according to the completion of the mission.
According to claim 1,

After the data determination step,

A database storage step of storing the target data in a database; application block chain data storage method characterized in that it further comprises.
According to claim 3,

The method of storing application block chain data, characterized in that the step of storing in the database and the step of storing blockchain are bound and processed as one transaction.
According to claim 4,

The activation condition of the rollback function of the smart contract is

Blockchain data storage method, characterized in that the database transaction rollback occurs during the storing in the database step.
According to claim 2,

The target data is data related to a token provided to the player in the application,

The method of storing application blockchain data, characterized in that the target data includes the owner and the amount of tokens provided.
According to claim 6,

In the step of performing the initiation function and the step of signing the initiation function, the amount of the token provided to the player in the application is pre-allocated.
According to claim 2,

The target data is data related to a token used by the application in the player,

The method of storing application blockchain data, characterized in that the target data includes the owner and the amount of tokens provided.
According to claim 8,

In the step of performing the initiation function and the step of signing the initiation function, the token provided to the application from the player is moved to the application.
According to claim 2,

The target data is data about a non-fungible token (NFT),

The method of storing application blockchain data, characterized in that the target data is owner data and CDN data of used data.