Game user node, probability verification system including the same, and verification method

Abstract

The present invention relates to a probability verification method for verifying probability events of a game item, comprising: a step in which at least one user node captures a communication packet with a server providing the game item; a step in which the user node extracts probability event data of the game item from the captured communication packet; a step in which the user node signs the extracted probability event data within a pre-established independent security area, called a Trusted Execution Environment (TEE), and transmits it to a blockchain network; and a step in which the blockchain network verifies the probability event based on the statistical consistency of the probability event data according to a pre-established smart contract. Through this, data regarding the probability item is verified, and the actual probability of the verified probability item is calculated, thereby enabling checks on the probability itself and creating a trustworthy environment throughout the game industry.

Description

Technology Field

[0001] The present invention relates to a user node, a probability verification system including the same, and a probability verification method. More specifically, it relates to a user node capable of verifying the actual probability of a game item, a probability verification system including the same, and a probability verification method. Background Technology

[0002] With the recent development of the digital content industry, probability-type items (random reward systems commonly referred to as 'gacha' or 'looting boxes') are being widely utilized across various platforms, including online games, mobile games, and the metaverse. These probability-type items are designed so that users receive items randomly based on probability after paying a certain amount of money.

[0003] While probabilistic items have the advantage of providing users with high immersion and profitability, if the probability of obtaining them is not transparently disclosed or if the actual probability differs from the stated value, it may lead to social controversy regarding consumer harm and unfair trade practices.

[0004] In fact, there have been reports of cases undermining user trust, such as when the acquisition probability of specific items was set significantly lower than the stated value or when probabilities were dynamically adjusted during event periods. Consequently, there is a growing institutional demand both domestically and internationally for the disclosure and verification of information regarding probability-based items, and the need for technical measures to ensure fairness and transparency is being emphasized.

[0005] However, to date, there is a lack of technical systems capable of independently verifying the actual application probabilities of probability-type items from the outside or explaining probability results to users in a reliable manner. In particular, due to the structural nature where probability results are processed by closed algorithms within the server, users have no means to directly verify whether the probabilities have been properly applied. Consequently, this is increasing distrust toward game operators and negatively impacting the creation of a healthy ecosystem for the industry as a whole.

[0006] Therefore, there is a need for technology that reliably verifies whether the actual probability of obtaining a probability-type item matches the probability notified in advance, and provides the results so that third parties or users can verify them. Prior art literature

[0007] Korean Patent Publication No. 10-2006-0011899 The problem to be solved

[0008] The present invention has been devised to solve the above-mentioned problems, and the objective of the present invention is to provide a user node capable of creating a trustworthy environment throughout the game industry by verifying data regarding probability items and calculating the actual probability of the verified probability item, thereby enabling checks on the probability itself, a probability verification system including the same, and a probability verification method. means of solving the problem

[0009] A probability verification method according to an embodiment of the present invention for achieving the above objective is a probability verification method for verifying a probability event of a game item, comprising: a step in which at least one user node captures a communication packet with a server providing the game item; a step in which the user node extracts probability event data of the game item from the captured communication packet; a step in which the user node signs the extracted probability event data within a pre-established independent security area, such as a Trusted Execution Environment (TEE), and transmits it to a blockchain network; and a step in which the blockchain network verifies the probability event based on the statistical consistency of the probability event data according to a pre-established smart contract.

[0010] And the step of capturing the communication packet may include the step of capturing dynamic OS metadata, which is metadata that changes dynamically during the execution of the game.

[0011] Additionally, the step of extracting the probability event data may include: a step of extracting the probability event data by filtering packets containing data related to the game item from among the communication packets; and a step of performing verification on the extracted probability event data based on the dynamic OS metadata.

[0012] And the probability verification method further includes, as a step performed prior to the step of capturing the communication packet, a step of storing reference data including a binary hash at the time the user node installs the game in the TEE, and the step of transmitting to the blockchain network may include: a step of generating combined data by combining the verified probability event data, the dynamic OS metadata, and the reference data within the TEE; a step of signing the combined data within the TEE with a pre-prepared secret key; and a step of converting the signed combined data into a guarantee token and transmitting it to the blockchain network.

[0013] In addition, the smart contract may be configured to check the integrity of the received guarantee token, store probability event data included in the guarantee token whose integrity has been verified in a pre-prepared data store, and count the number of probability event data stored in the data store.

[0014] And the smart contract may be configured such that when the number of probability event data stored in a pre-prepared data store reaches a pre-prepared threshold, it calculates an actual probability value using the probability event data stored in the data store, stores the calculated actual probability value in the data store, and returns the actual probability value when a request for verification of the actual probability value is received.

[0015] In addition, the smart contract may be configured to update the actual probability value at predetermined intervals after the actual probability value has been calculated.

[0016] And the step of verifying the probability event may be a step of verifying the probability event by confirming the statistical consistency using at least one statistical technique among the Kolmogorov-Smirnov test or the chi-square goodness-of-fit test.

[0017] Meanwhile, a probability verification system according to one embodiment of the present invention for achieving the above objective comprises: at least one user node that captures a communication packet with a server providing the game item, extracts probability event data of the game item from the captured communication packet, signs the extracted probability event data within a pre-established independent security area called a Trusted Execution Environment (TEE), and transmits it to a blockchain network; and the blockchain network that verifies the probability event based on the statistical consistency of the probability event data according to a pre-established smart contract.

[0018] And the above user node can capture dynamic OS metadata, which is metadata that changes dynamically during the execution of the game.

[0019] In addition, the user node can filter packets containing data related to the game item from the communication packets to extract the probability event data, and perform verification of the extracted probability event data based on the dynamic OS metadata.

[0020] And the user node can store reference data including the binary hash at the time the game is installed in the TEE, generate combined data by combining the verified probability event data, the dynamic OS metadata, and the reference data within the TEE, sign the combined data with a pre-prepared secret key within the TEE, convert the signed combined data into a guarantee token, and transmit it to the blockchain network.

[0021] In addition, the smart contract may be configured to check the integrity of the received guarantee token, store probability event data included in the guarantee token whose integrity has been verified in a pre-prepared data store, and count the number of probability event data stored in the data store.

[0022] The smart contract may be configured such that when the number of probability event data stored in a pre-prepared data store reaches a pre-prepared threshold, it calculates an actual probability value using the probability event data stored in the data store, stores the calculated actual probability value in the data store, and returns the actual probability value when a request for verification of the actual probability value is received.

[0023] In addition, the smart contract may be configured to update the actual probability value at predetermined intervals after the actual probability value has been calculated.

[0024] And the blockchain network can verify the probability event by confirming the statistical consistency using at least one statistical technique among the Kolmogorov-Smirnov test or the chi-square goodness-of-fit test.

[0025] Meanwhile, at least one user node receiving a game item according to an embodiment of the present invention for achieving the above objective comprises: a communication unit communicating with a server providing the game item and a blockchain network; a packet capture unit capturing a communication packet with the server and extracting probability event data of the game item from the captured communication packet; and a Trusted Execution Environment (TEE) which is a pre-prepared independent security area that performs a signature on the extracted probability event data and transmits it to the blockchain network. Effects of the invention

[0026] According to one aspect of the present invention described above, by providing a user node, a probability verification system including the same, and a probability verification method, data regarding probability items is verified, and the actual probability of the verified probability item is calculated, thereby enabling checks on the probability itself and creating a trustworthy environment throughout the game industry. Brief explanation of the drawing

[0027] FIG. 1 is a diagram illustrating the configuration of a probability verification system according to an embodiment of the present invention, FIG. 2 is a block diagram for explaining a user node according to an embodiment of the present invention, FIG. 3 is a diagram illustrating a smart contract in a probability verification system according to an embodiment of the present invention, FIG. 4 is a flowchart for explaining a probability verification method performed in a probability verification system according to an embodiment of the present invention, FIG. 5 is a flowchart illustrating a probability verification method performed at a user node according to an embodiment of the present invention, and FIG. 6 is a flowchart illustrating a probability verification method based on a smart contract according to an embodiment of the present invention. Specific details for implementing the invention

[0028] The following detailed description of the invention refers to the accompanying drawings, which illustrate specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that various embodiments of the invention are different but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in relation to one embodiment. It should also be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the following detailed description is not intended to be limiting, and the scope of the invention is limited only by the appended claims, including all equivalents to those claimed therein, provided appropriately described. Similar reference numerals in the drawings refer to the same or similar functions across various aspects.

[0029] The components according to the present invention are defined by functional distinction rather than physical distinction, and can be defined by the functions each performs. Each component may be implemented as hardware or as program code and processing units that perform each function, and the functions of two or more components may be included and implemented in a single component. Therefore, it should be noted that the names assigned to the components in the following embodiments are not intended to physically distinguish each component but are assigned to imply the representative function performed by each component, and that the technical concept of the present invention is not limited by the names of the components.

[0030] Preferred embodiments of the present invention will be described in more detail below with reference to the drawings.

[0031] FIG. 1 is a diagram illustrating the configuration of a probability verification system (10) according to one embodiment of the present invention.

[0032] The probability verification system (10, hereinafter the system) according to the present embodiment is provided to create a trustworthy environment throughout the game industry by verifying the probability events of game items and analyzing whether the actual probability of a game item matches the probability announced by the game company.

[0033] To this end, the system (10) according to the present embodiment may be composed of at least one user node (100) and a blockchain network (BN).

[0034] The system (10) according to this embodiment may be based on a blockchain technique that generates transactions from a plurality of blockchain nodes connected to a blockchain network (BN) into blocks according to a pre-set period or condition and connects them to a chain stored in each node.

[0035] And blockchain nodes participating in the blockchain network (BN) may refer to terminal devices such as smartphones and tablets, computing devices and server devices, etc., that are connected to the blockchain network (BN) wirelessly or via wired connection, and such a blockchain network (BN) may refer to a distributed ledger.

[0036] Accordingly, a blockchain network (BN) can collect transactions (T) generated from multiple nodes and add them to a block or create a block, and in this regard, the blockchain network (BN) may be configured so that a random representative node elected according to pre-set conditions among multiple servers collects transactions (T) generated from a random server and creates a block.

[0037] At this time, the blockchain network (BN) creating a block may be a node elected as a representative node among multiple nodes connected to the blockchain network (BN) creating a block according to a transaction (T) received from multiple nodes.

[0038] Meanwhile, a block generated in a blockchain network (BN) can be generated to include information from a previously generated block and transactions (T) received from multiple nodes, and the node that generated the block can transmit the generated block to multiple nodes connected to the blockchain network (BN).

[0039] Here, the block can include information from a previously created block in an encrypted state using a hash function.

[0040] In addition, multiple nodes can verify the received block using a public consensus algorithm, and the verified block can be linked to a previously created block.

[0041] Accordingly, at least one user node (100) according to the present embodiment may be one of a plurality of nodes participating in such a blockchain network (BN).

[0042] In addition, at least one user node (100) according to the present embodiment is a device in which game software is installed and a game is executed, and such user node (100) can perform the purchase of probability-type game items. To this end, the user node (100) can download game software through a game server (200) and can perform the purchase of probability-type game items through the game server (200).

[0043] FIG. 2 is a block diagram for explaining a user node (100) according to an embodiment of the present invention. As shown in FIG. 2, the user node (100) according to the present embodiment may include a communication unit (110), a storage unit (120), and a control unit (130). In addition, software (application) for performing a probability verification method may be installed and executed on the user node (100), and the communication unit (110), the storage unit (120), and the control unit (130) may be controlled by the software (application) for performing the probability verification method.

[0044] At this time, the user node (100) is a device possessed by the game user and may be a separate terminal or a part module of the terminal. Additionally, the configuration of the communication unit (110), storage unit (120), and control unit (130) may be formed as an integrated module or may consist of one or more modules. However, conversely, each configuration may consist of a separate module.

[0045] Additionally, the user node (100) may be mobile or fixed. This user node (100) may be in the form of a device, server, or engine, and may be referred to by other terms such as device, apparatus, terminal, UE (user equipment), MS (mobile station), wireless device, or handheld device. Furthermore, the user node (100) may execute or create various software based on an operating system (OS), that is, a system. Here, the operating system is a system program that enables software to use the hardware of the device, and may include all mobile computer operating systems such as Android OS, iOS, Windows Mobile OS, Bada OS, Symbian OS, BlackBerry OS, etc., as well as computer operating systems such as Windows family, Linux family, Unix family, MAC, AIX, HP-UX, etc.

[0046] First, the communication unit (110) can be provided to communicate with the game server (200) and the blockchain network (BN).

[0047] Meanwhile, a program for performing a probability verification method is recorded in the storage unit (120). Additionally, the storage unit (120) temporarily or permanently stores data processed by the control unit (130) and may include a volatile storage medium or a non-volatile storage medium, but the scope of the present invention is not limited thereto.

[0048] And the storage unit (120) can store data accumulated while performing the probability verification method. For example, the storage unit (120) can store various types of packets and metadata received from the game server (200).

[0049] Meanwhile, a control unit (130) is provided to control the entire process of providing a probability verification method. This control unit (130) may include a game client (131), a packet capture unit (133), and a Trusted Execution Environment (TEE) (135).

[0050] The game client (131) can store reference data containing a binary hash in the TEE (135) when the game program is first installed.

[0051] Here, reference data may refer to information that can prove the integrity of the client. And when the game client (131) is updated for a version up after the game is initially installed, it can update the reference data to match the binary of the upgraded client and ensure that the updated reference data is stored in the TEE (135).

[0052] And the game client (131) according to the present embodiment can transmit and receive information with the game server (200) or transmit all data generated during the process of running the game to the packet capture unit (133).

[0053] Meanwhile, the packet capture unit (133) according to the present embodiment can capture communication packets with the game server (200) and extract probability event data of game items from the captured communication packets.

[0054] These communication packets may contain different data depending on the type of game. For example, the raw data in the communication packet may include images, data lists, and image CIDs. Specifically, the data list may include game type, draw type and user ID, draw result including item name, and time of issuance in string form.

[0055] Accordingly, the packet capture unit (133) can extract a communication packet corresponding to data containing at least one of a drawing type and a drawing result among various types of communication packets as probability event data.

[0056] In addition, the packet capture unit (133) according to the present embodiment can capture dynamic OS metadata, which is metadata that is dynamically changed during the execution of the game.

[0057] Specifically, the packet capture unit (133) can collect reliable metadata at the OS and kernel levels by utilizing eBPF, etc., and can present unforgeable evidence regarding the game client (131) that generated the packet.

[0058] The dynamic OS metadata captured by the packet capture unit (133) according to this embodiment may be reliable metadata extracted from the OS, such as a process ID, process creation time, and packet creation time per process.

[0059] And the packet capture unit (133) can extract probability event data by filtering packets containing data related to probability items among communication packets. To filter packets containing data related to probability items, the packet capture unit (133) can utilize techniques such as the libpcap library or kernel-level packet filtering.

[0060] Additionally, the packet capture unit (133) can perform verification on the probability event data extracted based on dynamic OS metadata. That is, the packet capture unit (133) can verify the source of the packet by utilizing the captured packet and reliable dynamic OS metadata, such as the packet generation time per process from the OS.

[0061] And data from the game server (200) can be verified through the public key generated by the server.

[0062] Meanwhile, the TEE (135) according to the present embodiment is a pre-prepared independent security area, which can perform a signature on the extracted probability event data and transmit the signed data to the blockchain network (BN).

[0063] In such a TEE (135), an internal secret key may be generated in advance to be ready to sign packets.

[0064] And in the TEE (135) according to the present embodiment, combined data can be generated by combining the probability event data verified by the packet capture unit (133), dynamic OS metadata, and reference data received from the game client (131).

[0065] And within the TEE (135), the combined data can be signed with a pre-prepared secret key, and the signed combined data can be converted into a guarantee token and then transmitted to the blockchain network (BN).

[0066] More specifically, in TEE (135), after the reference data I is stored, the verified probability event data D and dynamic OS metadata M are combined as in Equation 1 below to generate combined data X, and a signature is performed on the generated combined data and converted into an endorsement token.

[0067] [Mathematical Formula 1]

[0068]

[0069]

[0070] And TEE (135) can transfer the guarantee token to the blockchain network (BN).

[0071] Through this TEE (135), the user node (100) according to the present embodiment can prevent malicious users from accessing the internal private key, thereby preventing the creation of a forged endorsement token using a contaminated packet.

[0072] And the TEE (135) according to the present embodiment may be provided as ARM Trust Zone, Intel SGX, Apple Secure Enclave, Samsung Knox TEE, OP-TEE, but is not limited thereto.

[0073] In addition, through this TEE (135), the user can protect the data needed to create a forged packet, and the blockchain network (BN) that collects the transmitted data can guarantee that the token is data processed in a place free from the risk of tampering.

[0074] Meanwhile, the blockchain network (BN) can receive guarantee tokens from at least one user node (100).

[0075] And the blockchain network (BN) can verify probability events based on the statistical consistency of probability event data received from at least one user node (100) based on a pre-arranged smart contract.

[0076] FIG. 3 is a diagram illustrating a smart contract in a probability verification system (10) according to one embodiment of the present invention.

[0077] As illustrated in FIG. 3, the smart contract according to the present embodiment may include a data reception / processing function, a probability information calculation function, and a probability information request processing function to verify probability events based on the statistical consistency of probability event data.

[0078] And to process operations using these functions, nodes participating in the blockchain network (BN) can perform roles such as integrity checkers, data processors, data storage, and probability calculators as shown in Fig. 3.

[0079] The smart contract according to the present embodiment may be configured to receive a guarantee token from at least one user node, verify the integrity of the received data including the guarantee token through an integrity validator, and transmit it to a data processor if there is no problem.

[0080] Additionally, the smart contract may be configured to store probability event data included in a guarantee token whose integrity has been verified by a data processor in a pre-prepared data store, and to check whether a preset threshold has been reached by counting the number of probability event data stored in the data store. Here, the threshold refers to a number of data sufficient to calculate a meaningful probability of drawing the item, and may be a value that can be changed by the user.

[0081] And, when it is confirmed that the number of probability event data stored in the data store has reached a pre-established threshold, the smart contract may be configured to request and receive the corresponding probability event data stored in the data store from the data processor for probability calculation.

[0082] Additionally, the smart contract may be configured to request the probability calculator to calculate the actual probability value while transmitting all probability event data received by the data processor, and to return the calculated actual probability value to the data processor after the probability calculator calculates the actual probability value.

[0083] Furthermore, the smart contract can be configured not only to store the actual probability value received through the data processor in the data repository, but also to update the actual probability value at pre-set intervals after the actual probability value is calculated.

[0084] In addition, the smart contract according to the present embodiment may be configured such that when a request for verification of actual probability values ​​is subsequently received by the probability information request processing function, the data processor within the probability information request processing function checks whether there are actual probability values ​​corresponding to the game in the data storage.

[0085] And if the smart contract confirms that there is an actual probability value corresponding to the game, it can enable the data processor to return that actual probability value to the requesting node.

[0086] In addition, the blockchain network (BN) according to the present embodiment may use at least one statistical technique among the Kolmogorov-Smirnov test or the chi-square goodness-of-fit test to verify probability events by checking the deviation between the actual probability value and the probability value notified by the game company.

[0087] The system (10) according to the present embodiment, including the above configuration, can safely protect sensitive data and operations from external attacks or vulnerabilities in the system by performing data extraction and signature processing through a hardware-based isolated execution environment (TEE) (135).

[0088] And the system (10) according to the present embodiment can be configured to periodically execute a remote attestation protocol to check the TEE operating status, and the remote attestation protocol can be configured to comply with Intel EPID (Enhanced Privacy ID) or TPM 2.0 standards.

[0089] In addition, the system (10) according to the present embodiment can ensure data integrity with a tamper-proof hash chain based on distributed ledger technology, namely a blockchain network (BN).

[0090] FIG. 4 is a flowchart for explaining a probability verification method performed in a probability verification system (10) according to an embodiment of the present invention. Since the probability verification method according to an embodiment of the present invention is performed on a configuration substantially identical to that of the system (10) shown in FIG. 1, the same reference numerals are assigned to components identical to those of the system (10) in FIG. 1, and repetitive descriptions are omitted.

[0091] The probability verification method according to the present embodiment is for verifying the probability event of a game item, and first, at least one user node (100) captures a communication packet with a game server (200) that provides the game item (S110).

[0092] Afterwards, the user node (100) extracts probability event data of the game item from the captured communication packet (S130).

[0093] Then, the user node (100) signs (S150) the probability event data extracted within the TEE (Trusted Execution Environment), which is a pre-established independent security area, and transmits the signed data to the blockchain network (BN) (S160).

[0094] Subsequently, the blockchain network (BN) integrates data signed based on a pre-prepared smart contract (S170) and verifies the probability event according to the statistical consistency of the probability event data (S180).

[0095] FIG. 5 is a flowchart illustrating a probability verification method performed at a user node (100) according to an embodiment of the present invention.

[0096] Below, with reference to FIG. 5, the process from the step (S110) in which the user node (100) captures a communication packet to the step (S160) in which the signed data is transmitted to the blockchain network (BN) will be explained in more detail.

[0097] First, the game client (131) transmits reference data containing the client binary hash when the game is first installed to the TEE (135) (S305).

[0098] Afterwards, reference data is stored in TEE (135) (S310).

[0099] Then, the game client (131) can transmit all data generated during the game execution process to the packet capture unit (133) (S315).

[0100] And the packet capture unit (133) can capture communication packets (S320) and capture dynamic OS metadata (S325). The step of capturing dynamic OS metadata (S325) may be a step of capturing dynamic OS metadata, which is metadata that changes dynamically during the execution of the game. Also, although FIG. 5 is illustrated as capturing dynamic OS metadata after capturing communication packets, this is merely an exemplary case for convenience of explanation and is not limited thereto.

[0101] Afterwards, the packet capture unit (133) can extract probability event data by filtering out packets containing data related to game items from among the captured communication packets (S330).

[0102] And the packet capture unit (133) can perform verification on the probability event data extracted based on dynamic OS metadata (S335). The step of performing verification on the extracted probability event data (S335) may be a step of verifying whether the data is generated from a game client.

[0103] Subsequently, the packet capture unit (133) transmits the entire data, including verified probability event data, to the TEE (135) (S340). The entire data in the step (S340) of transmitting the entire data to the TEE (135) may include verified probability event data and dynamic OS metadata.

[0104] When the TEE (135) receives the entire data from the packet capture unit (133), it combines the received data with reference data to generate combined data (S345). Here, the combined data refers to data that combines verified probability event data, dynamic OS metadata, and reference data.

[0105] Afterwards, TEE (135) performs a signature on the combined data (S350).

[0106] Then, TEE (135) converts the signed combined data into a guarantee token and sends it to the blockchain network (BN) (S355).

[0107] Subsequently, the blockchain network (BN) can verify probabilistic events based on smart contracts (S360).

[0108] FIG. 6 is a flowchart illustrating a probability verification method based on a smart contract according to an embodiment of the present invention.

[0109] Below, we will explain in detail the process of verifying probabilistic events in a blockchain network (BN).

[0110] First, an integrity checker within the data reception / processing function receives a guarantee token from the user node (100) (S405).

[0111] Then, the integrity checker within the data reception / processing function performs an integrity check on the guarantee token (S410).

[0112] Then, if the integrity checker in the receiving / processing function confirms the integrity, it passes the guarantee token to the data processor in the data receiving / processing function (S415).

[0113] Subsequently, the data handler within the data reception / processing function requests a threshold check while transmitting the probability event data included in the received guarantee token to the data store (S420).

[0114] Accordingly, the data store returns the result of the threshold check to the integrity checker within the data receiving / processing function (S425).

[0115] And when probability event data for a specific game is collected above a threshold value, the data processor within the data receiving / processing function requests the data processor within the probability information calculation function to calculate probability information for calculating actual probability values ​​(S430).

[0116] Afterwards, the data processor within the probability information calculation function can request (S435) the probability event data stored in the data storage and receive it from the data storage (S440).

[0117] And the data processor within the probability information calculation function requests a probability information calculation to calculate the actual probability value using the probability calculator within the probability information calculation function (S445), and can receive the actual probability value calculated from the probability calculator within the probability information calculation function (S450).

[0118] Afterwards, the data processor within the probability information calculation function ensures that the calculated actual probability value is stored in the data storage (S455).

[0119] Then, the data processor within the data reception / processing function requests the data processor within the probability information calculation function to update the actual probability value at a preset period using probability event data collected above a threshold (S460).

[0120] Through the above process, the probability verification method according to the present embodiment not only allows the use of only verified probability event data, but also enables checks on the probability itself by calculating the actual probability value for the probability event of the corresponding probability item and comparing it with the disclosed probability value when a certain number of probability event data are collected, thereby creating a trustworthy environment throughout the game industry.

[0121] The probability verification method of the present invention as described above can be implemented in the form of program instructions that can be executed through various computer components and recorded on a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc., either individually or in combination.

[0122] The program instructions recorded on the above-mentioned computer-readable recording medium may be those specifically designed and configured for the present invention, or they may be those known and available to those skilled in the art of computer software.

[0123] Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical recording media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, and flash memory.

[0124] Examples of program instructions include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The hardware device may be configured to operate as one or more software modules to perform processing according to the present invention, and vice versa.

[0125] Although various embodiments of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments described above. It is understood that various modifications can be made by those skilled in the art without departing from the essence of the invention as claimed in the claims, and such modifications should not be understood individually from the technical spirit or perspective of the present invention. Explanation of the symbols

[0126] 10: Probability Verification System 100 : User Node 110 : Communications Department 120 : Storage unit 130 : Control unit 131 : Game Client 133 : Packet capture section 135 : TEE 200 : Game Server BN: Blockchain Network

Claims

Claim 1 A probability verification method for verifying a probability event of a game item, comprising: a step in which at least one user node captures a communication packet with a server providing said game item; a step in which the user node extracts probability event data of said game item from said captured communication packet; a step in which the user node signs said extracted probability event data within a pre-established independent security area, such as a Trusted Execution Environment (TEE), and transmits it to a blockchain network; and a step in which the blockchain network verifies said probability event according to the statistical consistency of said probability event data based on a pre-established smart contract. Claim 2 A probability verification method according to claim 1, wherein the step of capturing the communication packet includes the step of capturing dynamic OS metadata, which is metadata that is dynamically changed during the execution of the game. Claim 3 In paragraph 2, the step of extracting probability event data comprises: a step of extracting probability event data by filtering packets containing data related to the game item from among the communication packets; and a step of performing verification on the extracted probability event data based on the dynamic OS metadata. Claim 4 In paragraph 3, the probability verification method further comprises, as a step performed prior to the step of capturing the communication packet, the step of storing reference data including a binary hash when the user node installs the game in the TEE, and the step of transmitting to the blockchain network comprises: the step of generating combined data by combining the verified probability event data, the dynamic OS metadata, and the reference data within the TEE; the step of signing the combined data within the TEE with a secret key prepared in advance; and the step of converting the signed combined data into a guarantee token and transmitting it to the blockchain network. Claim 5 A probability verification method according to claim 4, wherein the smart contract is configured to verify the integrity of the received guarantee token, store probability event data included in the guarantee token whose integrity has been verified in a pre-prepared data store, and count the number of probability event data stored in the data store. Claim 6 A method for verifying probability according to claim 4, wherein the smart contract is configured such that when the number of probability event data stored in a pre-prepared data storage reaches a pre-prepared threshold, it calculates an actual probability value using the probability event data stored in the data storage, stores the calculated actual probability value in the data storage, and returns the actual probability value when a request for verification of the actual probability value is received. Claim 7 A probability verification method according to claim 6, wherein the smart contract is configured to update the actual probability value at predetermined intervals after the actual probability value is calculated. Claim 8 A probability verification method according to claim 1, wherein the step of verifying the probability event is a step of verifying the probability event by confirming the statistical consistency using at least one statistical technique among the Kolmogorov-Smirnov test or the chi-square goodness-of-fit test. Claim 9 A probability verification system for verifying probability events of a game item, comprising: at least one user node that captures a communication packet with a server providing the game item, extracts probability event data of the game item from the captured communication packet, signs the extracted probability event data within a pre-established independent security area called a Trusted Execution Environment (TEE), and transmits it to a blockchain network; and the blockchain network that verifies the probability event according to the statistical consistency of the probability event data based on a pre-established smart contract. Claim 10 In claim 9, the above user node is a probability verification system that captures dynamic OS metadata, which is metadata that changes dynamically during the execution of the game. Claim 11 In claim 10, the user node is a probability verification system that filters packets containing data related to the game item from the communication packets to extract the probability event data, and performs verification of the extracted probability event data based on the dynamic OS metadata. Claim 12 A probability verification system according to claim 11, wherein the user node stores reference data including a binary hash at the time the game is installed in the TEE, generates combined data by combining the verified probability event data, the dynamic OS metadata, and the reference data within the TEE, signs the combined data with a secret key prepared in advance within the TEE, converts the signed combined data into a guarantee token, and transmits it to the blockchain network. Claim 13 A probability verification system according to claim 12, wherein the smart contract is configured to verify the integrity of the received guarantee token, store probability event data included in the guarantee token whose integrity has been verified in a pre-prepared data store, and count the number of probability event data stored in the data store. Claim 14 A probability verification system according to claim 12, wherein the smart contract is configured to calculate an actual probability value using the probability event data stored in the data store when the number of probability event data stored in the data store reaches a pre-prepared threshold, to store the calculated actual probability value in the data store, and to return the actual probability value when a request for verification of the actual probability value is received. Claim 15 In claim 14, the probability verification system is configured such that the smart contract updates the actual probability value at predetermined intervals after the actual probability value is calculated. Claim 16 In claim 9, the blockchain network is a probability verification system that verifies the probability event by confirming the statistical consistency using at least one statistical technique among the Kolmogorov-Smirnov test or the chi-square goodness-of-fit test. Claim 17 A user node comprising: at least one user node receiving a game item, a communication unit communicating with a server providing the game item and a blockchain network; a packet capture unit capturing a communication packet with the server and extracting probability event data of the game item from the captured communication packet; and a Trusted Execution Environment (TEE) which is a pre-arranged independent security area that performs a signature on the extracted probability event data and transmits it to the blockchain network.

Images