Program, method and system

The system addresses the challenge of managing gaming records by using NFTs on a distributed ledger to securely accumulate and authenticate competition results, enhancing user engagement through achievement-based rewards.

JP2024156363APending Publication Date: 2024-11-06PLAYGROUND CO LTD

Patent Information

Application Number
JP2023070763
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-24
Publication Date
2024-11-06

AI Technical Summary

Technical Problem

Conventional systems fail to manage users' winning and losing records across the entire gaming industry, making it difficult to accumulate tournament records in a secure and authentic manner.

Method used

A system that issues non-fungible tokens (NFTs) linked to competition performance, using a distributed ledger to ensure authenticity and manage competition results, including match proof, custom match proof, task proof, and winning proof NFTs, and issues medal NFTs based on accumulated achievements.

Benefits of technology

Enables the secure accumulation of competition results while ensuring authenticity, encourages participation through rewards, and motivates users by providing NFTs that serve as proof of achievement and incentives.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024156363000001_ABST
    Figure 2024156363000001_ABST
Patent Text Reader

Abstract

To provide a system which can store the competition achievements of participants while ensuring credibility.MEANS FOR SOLVING THE PROBLEM: A program of the present invention is the one to be executed by a system having a computer provided with a processor. The program causes the processor to execute steps of: acquiring competition achievements including the results of a competition conducted by plural participants; and issuing a competition certificate NFT (Non-Fungible-Token) with linked information regarding the competition achievements based on the acquired competition achievements to at least one of the participants.SELECTED DRAWING: Figure 19
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a program, a method, and a system. [Background technology]

[0002] In recent years, e-sports, which treat competitive games as sports, have been attracting attention. For example, the following Patent Document 1 discloses a gaming infrastructure system used for holding various game tournaments. By using this system, the content of the matches in each tournament can be distributed and tournament records can be accumulated. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2021-516087 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional systems, tournament records were managed on a tournament-by-tournament or infrastructure-by-infrastructure basis, making it impossible to manage users' winning and losing records across the entire gaming industry, and making it difficult to accumulate participants' competitive records in a way that guaranteed their authenticity.

[0005] An object of the present disclosure is to provide a system that can accumulate participants' competition results in a manner that ensures their authenticity. [Means for solving the problem]

[0006] A program according to one embodiment of the present disclosure is a program to be executed by a system having a computer equipped with a processor, and the program causes the processor to execute the steps of acquiring competition results including the results of a competition held by a plurality of participants, and issuing a competition proof NFT, which is a non-fungible token linked to information related to the competition results, to at least one of the participants based on the acquired competition results. Effect of the Invention

[0007] According to the present disclosure, the competition results of participants can be accumulated with credibility guaranteed. [Brief description of the drawings]

[0008] [Figure 1] A diagram explaining the types of competitive NFTs handled by the NFT management system of the present invention. [Diagram 2] FIG. 2 is a diagram explaining the function of the competitive NFT shown in FIG. 1. [Diagram 3] A diagram showing the overall configuration of the NFT management system of the present invention. [Figure 4] 2 is a diagram illustrating a hardware configuration of the user terminal illustrated in FIG. 1. [Diagram 5] 2 is a diagram showing the hardware configuration of the competition management server shown in FIG. 1. [Figure 6] A diagram showing the hardware configuration of the NFT management server 30 shown in Figure 1. [Figure 7] FIG. 2 is a diagram illustrating the configuration of the distributed ledger system shown in FIG. [Figure 8] This is a diagram explaining the holding status of various databases used by the NFT management system. [Figure 9] FIG. 9A is a diagram showing an example of the data structure of a user database, FIG. 9B is a diagram showing an example of the data structure of a team database, and FIG. 9C is a diagram showing an example of the data structure of an event database. [Figure 10] FIG. 10A is a diagram showing an example of the data structure of a match database, and FIG. 10B is a diagram showing an example of the data structure of a match history database. [Figure 11] FIG. 11A is a diagram showing an example of the data structure of a custom match database, and FIG. 11B is a diagram showing an example of the data structure of a custom match history database. [Figure 12] FIG. 15 is a diagram showing an example of the data structure of an assignment database, and FIG. 15B is a diagram showing an example of the data structure of an assignment history database. [Figure 13] FIG. 13A is a diagram showing an example of the data structure of the prize winning database, and FIG. 13B is a diagram showing an example of the data structure of the prize winning history database. [Figure 14] FIG. 4 is a diagram illustrating an example of a data structure of a grant condition database. [Figure 15] FIG. 13 is a diagram showing an example of the data structure of a competition NFT type database. [Figure 16] FIG. 2 is a diagram illustrating an example of a data structure of an ownership history database. [Figure 17] FIG. 17A is a diagram showing an example of the data structure of a Dapps account database, and FIG. 17B is a diagram showing an example of the data structure of a wallet database. [Figure 18] FIG. 1 is a conceptual diagram showing the structure of a distributed ledger realized by a distributed ledger system. [Figure 19] FIG. 1 is a diagram showing an overview of the present embodiment. [Figure 20] A diagram showing the flow of the competition proof NFT issuance process. [Figure 21] A diagram showing the flow of the medal NFT issuance process. [Figure 22] FIG. 13 is a conceptual diagram showing the structure of a distributed ledger according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and the repeated description will be omitted.

[0010] (1) Overview of the present invention and definitions of terms used in the description First, an overview of the present invention and definitions of terms used in the description will be given. System 1 is a system that manages the results of competitive games known as e-sports, for example, and promotes an increase in the number of participants in the games.

[0011] (1-1) Overview of Competitive NFTs System 1 issues and grants NFTs (Non-Fungible Tokens) to users (hereinafter referred to as participants) who participate in the competition based on their performance in the competition, thereby proving the participants' performance in the competition and promoting competitive activities. Here, an NFT is a token that is linked to digital content and whose owner information is recorded on a distributed ledger (blockchain) 50, which will be described later. In other words, an NFT is a token that is linked to digital content that has asset value, for example, and refers to digital data that is given to participants as proof of their participation in the competition.

[0012] Digital content that can be linked to NFTs includes, for example, image data, video data, audio data, as well as text data commented on SNS (Social Networking Service). Generally, digital content data can be copied at will. On the other hand, even if the original data of the digital content is copied and reused, if the owner's information is recorded in the distributed ledger as mentioned above, it is possible to confirm who the true owner of the original data is.

[0013] In other words, since NFTs can clarify the owner's information, they are treated as objects of trade and have asset value according to the content of the digital content. Some NFTs can be freely transferred based on the agreement between users. As with general transactions, NFTs can be transferred together with the provision of money or other value, or free of charge. In the following explanation, NFTs may be simply referred to as tokens.

[0014] Next, using Figure 1, we will define the types of NFTs managed by the system 1 in this embodiment.

[0015] Competitive NFT: A general term for NFTs that are related to participation in a competition (competitive activities) and that are specifically handled by the system 1 of the present invention. Competitive NFTs are classified into Proof of Competition NFTs and Medal NFTs depending on the amount of competitive achievements that triggers acquisition. Here, the acquisition trigger refers to the conditions related to competitive activities that a user must meet in order to acquire the competitive NFT (in other words, to receive issuance from the issuing entity). In other words, the acquisition trigger of a competitive NFT is synonymous with the issuance conditions of the competitive NFT.

[0016] Next, we will explain Proof of Competition NFTs and Medal NFTs, which are sub-concepts of Competition NFTs. Proof-of-Competition NFT: A competition NFT that is issued or transferred primarily based on a single competition performance. Medal NFT: A competitive NFT issued or transferred primarily based on the accumulation of multiple competitive achievements. In other words, medal NFTs may be issued as an award for a user's past competitive achievements, based on the user's holdings of competition certificate NFTs that they have acquired in the past.

[0017] Since Proof-of-Competition NFTs primarily function as proof of competition achievements, in principle they cannot be transferred from the user who first acquired them to another user. In other words, the fundamental value of Proof-of-Competition NFTs is that they record and prove "who achieved what kind of competition achievements, when, and what kind of competition achievements." In contrast, medal NFTs have value as a reward for accumulated athletic achievements in the past, and can be transferred freely between users in transactions. Note that these configurations are merely examples, and competition proof NFTs may be transferable between users, while medal NFTs may not be transferable between users.

[0018] Next, the types of competing NFTs will be described with reference to Fig. 2. Fig. 2 is a diagram for explaining the functions of the competing NFTs shown in Fig. 1. First, among the competing NFTs, the proof-of-competition NFT will be described.

[0019] (1-2) Contents of the Proof of Competition NFT As shown in Figure 2, the Proof-of-Competition NFT includes the following four NFTs: Proof-of-match NFT Custom Proof-of-Match NFT ·Proof-of-challenge NFTs · Winning Certificate NFT

[0020] A match proof NFT is a non-fungible token issued based on the outcome of a single competition (match). A match proof NFT has the function of proving the winner or loser of the match of its holder. A match proof NFT may include a victory proof NFT issued to the winner of the match and a defeat proof NFT issued to the loser of the match. In other words, a match proof NFT is issued to at least one of the winner and loser among the participants who competed. A match proof NFT is basically issued or transferred based on the outcome of a single match. A match proof NFT may be newly issued, or may be transferred to a new owner by newly recording the owner information of a match proof NFT held by the tournament organizer.

[0021] Digital content (e.g., image data) linked to a competition proof NFT displays information indicating that the NFT related to the image data is a competition proof NFT (the fact that it is a competition proof NFT). In other words, digital content linked to a competition proof NFT displays the competition results related to the corresponding competition. The competition results include, for example, the following items: - Name of the tournament to which the sport (match) belongs -Name of the competition (information that can identify the match during the competition, such as first round, semi-final, or number xx) - Date of the event Competitor's name Names of the winners and losers Competitive performance (competitive scores, etc.)

[0022] A custom match NFT is a non-fungible token issued to participants who have achieved results in a competition (custom match) conducted based on arbitrary match rules agreed upon by the participants in advance. A custom match NFT has the function of proving the holder's victory or defeat in a custom match.

[0023] Here, a battle format called a custom battle will be described in detail. Battles (competitions) in tournaments such as e-sports are generally set in advance by the tournament organizer. However, unlike tournaments managed by such tournament organizers, users may compete against each other individually to determine superiority in the competition. In such cases, for example, handicaps may be set according to the respective competitive abilities or competitive achievements. For this reason, in the system 1, a battle in which such battle rules are set based on an agreement between users is defined as a custom battle. In a custom battle, the battle rules agreed upon between users who will be participants in the battle may include, for example, the following items:

[0024] (Custom battle rules agreed upon in advance between users) Competition Date and Time Competitors ·Competition environment Competition details ·Winning and losing conditions ·Handicap availability Prizes for the winners · Whether or not someone is present A custom match proof NFT is basically issued or transferred based on the outcome of a match played under arbitrary rules. In addition to being newly issued, a custom match result NFT may be transferred to a new owner by newly recording owner information for a custom match result NFT held by the tournament organizer.

[0025] In addition, in the system 1, the prize for the winner of the custom match can be set to an NFT provided by each of the competitors (for example, a medal NFT owned by the competitor). In this case, the winner of the custom match can receive the NFT provided by the opponent as a prize, along with a custom proof NFT that proves the fact.

[0026] Digital content (e.g., image data) linked to a custom match proof NFT displays information indicating that the NFT related to the image data is a custom match proof NFT (the fact that it certifies it as a custom match proof NFT). In other words, digital content linked to a custom match proof NFT displays the competitive record for the corresponding custom match. The competitive record for the custom match includes, for example, the following items: Battle rules Competitive performance (competitive scores, etc.)

[0027] A Proof-of-Challenge NFT is a non-fungible token that is issued when a player's actions in the competition achieve a preset challenge action. A Proof-of-Challenge NFT has the function of proving the holder's achievement of the challenge action. A Proof-of-Competition NFT is issued or transferred based on the success or failure of the challenge completion.

[0028] Digital content (e.g., image data) linked to a task proof NFT displays information indicating that the NFT related to the image data is a task proof NFT (the fact that it certifies it as a task proof NFT). In other words, digital content linked to a task proof NFT displays the achievements of the corresponding task. The achievements of the task proof NFT include, for example, the following items: -Name of the project -Content of the assignment -Period during which the challenge can be taken -Name of the challenger - Achievements (details of the actions taken by the challenger, etc.)

[0029] A prize-winning NFT is a non-fungible token issued in response to winning a competition. A prize-winning NFT serves as proof that its holder won a competition. A prize-winning NFT is issued or transferred based on the award results in the competition.

[0030] The digital content (e.g., image data) linked to the winning certificate NFT displays information indicating that the NFT related to the image data is a winning certificate NFT (the fact that it certifies that it is a winning certificate NFT). In other words, the digital content linked to the winning certificate NFT displays the awards the user has received. The awards include, for example, the following items: - Name of the event for which the award is to be given - Content of the competition for which the award is given - Date of the competition to which the award relates Competitor's name Awards (details of awards)

[0031] (1-3) Contents of the medal NFT Next, we will explain about medal NFTs, one of the competitive NFTs. As shown in Figure 2, the Medal NFTs include the following five NFTs: -Second prize NFT Ranking NFTs ·Hall of Fame NFT Nicknamed NFT Campaign NFT

[0032] The secondary prize NFT is a non-fungible token that is a secondary prize for the competition achievement that led to the acquisition of the competition proof NFT. For example, the secondary prize NFT is linked to digital content related to the competition, which is highly rare and has customer appeal to the competitors of the competition, as bonus content. Athletes are encouraged to participate in the competition in which the secondary prize NFT is set in order to obtain the bonus content. The secondary prize NFT may also have value attached, such as a voucher or a complimentary ticket for various services. The secondary prize NFT is issued or transferred based on the result (win or loss) of any single match in the competition. Specific examples of secondary prize NFTs include the following. Championship Flag NFT Trophy NFT Champion Belt NFT

[0033] The secondary prize NFT may further be linked to digital content (e.g., image data) that displays information indicating that the NFT related to the image data is a secondary prize NFT (a fact that proves it as a secondary prize NFT). In other words, the digital content linked to the secondary prize NFT displays information related to the corresponding secondary prize. The information related to the secondary prize may include, for example, the following items: Name of the prize - Name of the competition (tournament) in which the prize was awarded The date on which the prize was awarded Competitor's name - Details of the prize (name of the bonus content or name of the bonus voucher, etc.)

[0034] Ranking NFTs are non-fungible tokens that indicate the ranking of the members of the competition based on their performance. Ranking NFTs are issued or transferred based on the holding status of the competition proof NFT. For example, ranking NFTs are issued or transferred to the winner based on the holding ranking of each contestant before the competition. If the competition results overturn the holding ranking, a ranking NFT equivalent to the loser's ranking is issued or transferred. Also, if the competition results are in accordance with the holding ranking, a new issuance or transfer is not necessary.

[0035] Digital content (e.g., image data) linked to a ranking NFT displays information indicating that the NFT related to the image data is a ranking NFT (a fact that certifies it as a ranking NFT). In other words, digital content linked to a ranking NFT displays information about the corresponding ranking. The information about the ranking includes, for example, the following items: - Name of the group that is the subject of the ranking - Name of the sport that is the subject of the ranking -The ranking evaluation date -Target of the ranking - Ranking results (ranking details)

[0036] Hall of Fame NFTs are issued when a holder exceeds a pre-set performance threshold, and are non-fungible tokens that indicate that the holder's competitive achievements have led to achievements. Hall of Fame NFTs are issued or transferred based on the accumulation of Proof of Competition NFTs held. The conditions for issuing Hall of Fame NFTs can be set at will.

[0037] Digital content (e.g., image data) linked to a Hall of Fame NFT displays information indicating that the NFT related to the image data is a Hall of Fame NFT (a fact that certifies it as a Hall of Fame NFT). In other words, digital content linked to a Hall of Fame NFT displays information regarding the achievements achieved by the user to whom it is granted. The information regarding achievements includes, for example, the following items: - Name of the sport in question - Name of the Hall of Fame -The date of issue of the Hall of Fame - Name of the person to whom the Hall of Fame NFT will be granted Hall of Fame Achievements (details of achievements)

[0038] A pseudonymous NFT is a non-fungible token that is issued when the holder's ownership meets a preset grant condition as a tendency of the holder's behavioral pattern in the competition. The pseudonymous NFT is issued or transferred based on the holder's ownership of the competition proof NFT. The pseudonymous NFT may be an NFT that is granted indefinitely, for example.

[0039] Digital content (e.g., image data) linked to a pseudonymous NFT displays information indicating that the NFT related to the image data is a pseudonymous NFT (a fact that certifies it as a pseudonymous NFT). In other words, digital content linked to a pseudonymous NFT displays information regarding the behavioral patterns of the user to whom it is assigned. The information regarding the behavioral patterns includes, for example, the following items: Name of the alias - Details of the actions corresponding to the nickname -Issuance date of the alias NFT - The name of the athlete who was given the alias NFT · Achievement (achievement corresponding to the nickname)

[0040] A campaign NFT is a non-fungible token issued in response to satisfying the granting conditions set in any campaign held in connection with the holding of a competition. A campaign NFT is issued or transferred based on the ownership status of the competition proof NFT. For example, a campaign NFT may be an NFT that is granted with a deadline. In this case, when a certain period of time has passed, another entity such as the operator is recorded as the owner information of the campaign NFT, and the campaign NFT is transferred (converted) to the operator.

[0041] Digital content (e.g., image data) linked to a campaign NFT displays information indicating that the NFT related to the image data is a campaign NFT (a fact that certifies it as a campaign NFT). In other words, digital content linked to a campaign NFT displays a record of participation in the corresponding campaign. The record of participation in the campaign includes, for example, the following items: - Name of the campaign - Campaign information (date, location, tournament, etc.) -Content of the campaign Name of the participant of the campaign Participation history (such as actions recognized as participating in a campaign)

[0042] Next, taking into account the definition of NFT mentioned above, we will provide an overview of System 1. In system 1, for any competition, a competition NFT that serves as proof of the competition achievements is awarded to users who are participants in that competition, and the status of holdings of the competition NFTs is made public on a blockchain, which is difficult to tamper with. In this state, the operator of any competition can refer to the publicly disclosed holdings of each user's competition NFTs.

[0043] In other words, because the competitive results in various competitions are published on the blockchain, where data is difficult to tamper with, it is possible to understand a user's ability in a given competition by checking the number of competition NFTs held by each user. For this reason, unlike conventional game tournaments, there is no need to manage information regarding the results of matches or information regarding the ranking of each user as an athlete based on wins and losses for each game server individually, and the competitive results of users who are participants in the competition can be easily and securely accumulated.

[0044] Furthermore, in System 1, in addition to the competition proof NFT that proves the competition achievements, users can be given medal NFTs based on their accumulated competition achievements, thereby providing users with an incentive to participate in competitions to which System 1 is applied. This is expected to promote an increase in the number of participants in competitions to which System 1 is applied, leading to more active competition activities. The configuration of such a system 1 will be described below.

[0045] (2) Overall configuration of NFT management system 1 The overall configuration of an NFT management system 1 (hereinafter simply referred to as system 1) according to this embodiment will be described. FIG. 3 is a block diagram showing the overall configuration of the system 1 according to this embodiment. As shown in FIG. 2, the system 1 includes a participant terminal 10A, a competition management server 20, an NFT management server 30, and a P2P distributed system 40. The participant terminal 10A, the competition management server 20, the NFT management server 30, and the P2P distribution system 40 are connected via a network (e.g., the Internet or an intranet) NW.

[0046] The participant terminal 10A is an information processing device used by a user of the system 1. The users of the system 1 include the following people. Participants in the competition (game tournament players) ·Competition operators (game tournament organizers) That is, the participant terminals 10A include a participant terminal 10A used by a participant and an operator terminal 10B used by the operator.

[0047] Of the participant terminals 10A, the participant terminal 10A is configured to be able to request participation in a game competition provided by an external game server (see FIG. 8). Of the participant terminals 10A, the operator terminal 10B is configured to be able to manage the results of a game competition provided from an external game server (see FIG. 8).

[0048] In the following description, the information processing device may include various computers such as a smartphone, a tablet terminal, a personal computer, a server computer (e.g., a web server, an application server, a database server, or a combination thereof), a wearable device (e.g., a smart watch or smart glasses), etc. In this embodiment, the participant terminal 10A will be described taking as an example a personal computer (see FIG. 22) connectable to the network NW.

[0049] The competition management server 20 is an information processing device that manages competition results. The competition management server 20 is configured to accumulate information related to competition results in response to input from the participant terminal 10A.

[0050] The NFT management server 30 is an information processing device that manages the issuance of various competition NFTs related to competition results. The competition NFTs managed by the NFT management server 30 include, for example, the following. - Competition NFTs issued by competition organizers - Competition NFTs issued by businesses commissioned by the competition organizers -Participants will use the competition NFTs as a trading target based on the competition results, based on the agreement between the two parties. In addition, an NFT management server 30 may be provided for each business operator that issues competitive NFTs, and the system 1 may be equipped with multiple NFT management servers 30.

[0051] The P2P distributed system 40 is a system in which a P2P network is constructed by a plurality of information processing devices. The P2P distributed system 40 realizes functions as a distributed ledger, a distributed application, and a distributed data storage.

[0052] The distributed ledger is a database that processes and records transaction history related to NFTs in a distributed manner using cryptographic technology through collaborative processing by information processing devices that make up the P2P distributed system 40. When an NFT is transferred between users, new transaction data is recorded in a block of the blockchain, and information about the owner of the NFT is updated. In the following explanation, when transaction data related to user information about a new NFT is recorded in a block of the blockchain, the NFT is issued (granted) to the user.

[0053] A decentralized application is a digital application that runs in the P2P distributed system 40. For example, a smart contract that autonomously executes processing according to a script linked to a distributed ledger can be used as a decentralized application. In other words, a decentralized application can be realized by a bundle of interoperable smart contracts that run in the background of the same user interface.

[0054] The distributed data storage is a storage area in which data is shared and stored among information processing devices constituting the P2P distributed system 40. A file uploaded to the storage of each information processing device of the P2P distributed system 40 is encrypted and fragmented, and is distributed and stored among each information processing device as a cache file. The original file is restored by linking the distributed and stored cache files by specifying a specific hash value. Examples of distributed data storage include IPFS and Swarm.

[0055] (2-1) Configuration of participant terminal 10A The configuration of the participant terminal 10A will be described below with reference to Fig. 4, which is a block diagram showing the configuration of the ticket purchase terminal of this embodiment.

[0056] 4, the participant terminal 10A includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14. The participant terminal 10A is connectable to at least one of an input device 15 and an output device 16.

[0057] The storage device 11 is configured to store programs and data. The storage device 11 is, for example, a combination of a Read Only Memory (ROM), a Random Access Memory (RAM), and a storage (for example, a flash memory or a hard disk).

[0058] The programs include, for example, the following programs: ·OS (Operating System) programs · Programs for applications that process information (e.g. web browsers)

[0059] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0060] The processor 12 is configured to realize the functions of the participant terminal 10A by starting a program stored in the storage device 11. The processor 12 is an example of a computer.

[0061] The input / output interface 13 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 15 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 16.

[0062] The input device 15 is, for example, a keyboard, a pointing device, a touch panel, a physical button, a sensor (for example, a camera, a vital sensor, or a combination thereof), or a combination thereof.

[0063] The output device 16 is, for example, a display, a speaker, a printing device, or a combination thereof.

[0064] The communication interface 14 is configured to control communication between the participant terminal 10A and external devices.

[0065] (2-2) Configuration of the competition management server 20 The following describes the configuration of the competition management server 20. Fig. 5 is a block diagram showing the configuration of the competition management server 20 of this embodiment.

[0066] 5, the competition management server 20 includes a storage device 21, a processor 22, an input / output interface 23, and a communication interface 24. The competition management server 20 is connectable to at least one of an input device 25 and an output device 26.

[0067] The storage device 21 is configured to store programs and data, and is, for example, a combination of a ROM, a RAM, and a storage (for example, a flash memory or a hard disk).

[0068] The programs include, for example, the following programs: -OS programs Application programs that perform information processing

[0069] The data includes, for example, the following data: Databases referenced in information processing Results of information processing

[0070] The processor 22 is configured to realize the functions of the competition management server 20 by running the programs stored in the storage device 21. The processor 22 is an example of a computer.

[0071] The input / output interface 23 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 25 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 26.

[0072] The input device 25 is, for example, a keyboard, a pointing device, a touch panel, a sensor, or a combination thereof.

[0073] The output device 26 is, for example, a display, a speaker, or a combination thereof.

[0074] The communication interface 24 is configured to control communications between the competition management server 20 and external devices.

[0075] (2-3) Configuration of NFT management server 30 An explanation will be given of the configuration of the NFT management server 30. Fig. 6 is a block diagram showing the configuration of the NFT management server 30 of this embodiment.

[0076] 6, the NFT management server 30 includes a storage device 31, a processor 32, an input / output interface 33, and a communication interface 34. The NFT management server 30 is connectable to at least one of an input device 35 and an output device 36.

[0077] The storage device 31 is configured to store programs and data, and is, for example, a combination of a ROM, a RAM, and a storage device.

[0078] The programs include, for example, the following programs: -OS programs Application programs that perform information processing

[0079] The data includes, for example, the following data: Databases referenced in information processing Data obtained through information processing

[0080] The processor 32 is configured to realize the functions of the NFT management server 30 by starting a program stored in the storage device 31. The processor 32 is an example of a computer.

[0081] The input / output interface 33 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 35 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 36.

[0082] The input device 35 is, for example, a keyboard, a pointing device, a touch panel, a sensor (for example, a camera, a vital sensor, or a combination thereof), or a combination thereof.

[0083] The output device 36 is, for example, a display, a speaker, or a combination thereof. The communication interface 34 is configured to control communication between the NFT management server 30 and external devices.

[0084] (2-6) Configuration of P2P distributed system 40 7 is a diagram showing the configuration of a P2P distributed system 40. The P2P distributed system 40 is a distributed system including signal processing devices 40A to 40E that function as nodes.

[0085] As shown in Fig. 7, the signal processing devices 40A to 40E are, for example, personal computers connected to a network. In this embodiment, the network may be a LAN, or may be a public network such as the Internet or a communication network provided by a communication carrier. The signal processing devices 40A to 40E are connected to the network, for example, by wire or wirelessly. The signal processing devices 40A to 40E communicate with each other using a peer-to-peer system.

[0086] The signal processing devices 40A to 40E constituting the P2P distributed system 40 realize a distributed ledger using blockchain technology. The signal processing device 40A, one of the signal processing devices 40A to 40E, acquires data related to NFT transactions to be recorded. The signal processing device 40A creates a block including the acquired data and adds it to the blockchain.

[0087] The signal processing device 40A transmits information on the added block to the other signal processing devices 40A. The other signal processing devices 40B to 40E verify the correctness of the received block, and if the correctness is verified, add it to the blockchain. The signal processing devices 40A to 40E finalize the blockchain according to, for example, the number of linked blocks (number of approvals). As a result, the same distributed ledger is stored by the signal processing devices 40A to 40E. Note that the stored data may be encrypted as appropriate.

[0088] The signal processing devices 40A to 40E constituting the P2P distributed system 40 realize distributed applications using block chain technology. One of the signal processing devices 40A to 40E, the signal processing device 40A, autonomously executes processing according to a script linked to a distributed ledger.

[0089] The signal processing device 40A transmits information on the added block to the other signal processing devices 40A. The other signal processing devices 40B to 40E verify the correctness of the executed process, and when the correctness is verified, the process is approved. As a result, one process is executed by the signal processing devices 40A to 40E. Note that the stored data may be encrypted using a hash function as appropriate.

[0090] The configuration of the P2P distributed system 40 is not limited to that shown in Fig. 7. For example, the number of signal processing devices 40A included in the P2P distributed system 40 may be any number equal to or greater than two.

[0091] The signal processing device 40A includes a storage device 41, a processor 42, an input / output interface 43, and a communication interface 44. The signal processing device 40A is connectable to at least one of an input device 45 and an output device 46.

[0092] The storage device 41 is configured to store programs and data. The storage device 41 is, for example, a combination of a Read Only Memory (ROM), a Random Access Memory (RAM), and a storage (for example, a flash memory or a hard disk).

[0093] The programs include, for example, the following programs: ·OS (Operating System) programs · Programs for applications that process information (e.g. web browsers)

[0094] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0095] The processor 42 is configured to realize the functions of the signal processing device 40A by running a program stored in the storage device 41. The processor 42 is an example of a computer.

[0096] The input / output interface 43 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 45 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 46.

[0097] The input device 45 is, for example, a keyboard, a pointing device, a touch panel, a physical button, a sensor (for example, a camera, a vital sensor, or a combination thereof), or a combination thereof.

[0098] The output device 46 is, for example, a display, a speaker, a printing device, or a combination thereof.

[0099] The communication interface 44 is configured to control communications between the signal processing device 40A and external devices.

[0100] (3) Data Structure The structure of data used in this embodiment will be described below. Fig. 8 is a diagram for explaining the state of ownership of various databases used by the system 1. As shown in FIG. 8, each device manages the following databases: 1) Database managed by the competition management server 20 User database (hereinafter referred to as User DB) Team Database (hereinafter referred to as Team DB) Event Database (hereinafter referred to as Event DB) · Match Database (hereinafter, Match DB) - Match History Database (hereinafter, Match History DB) Custom Match Database (hereinafter referred to as "Custom Match DB") Custom match history database (hereinafter, Custom Match History DB) · Issue Database (hereinafter, Issue Database) · Task History Database (hereinafter, Task History DB) · Prize-winning database (hereinafter, Prize-winning DB) · Prize history database (hereinafter, Prize History DB)

[0101] 2) Database managed by the NFT management server 30 - Grant condition database (hereinafter, Grant condition DB) Competitive NFT type DB (hereinafter referred to as Competitive NFT type DB) - Ownership history database (hereinafter, Ownership History DB)

[0102] 3) Database managed by the P2P distributed system 40 Dapps account database (hereinafter referred to as Dapps account DB) Wallet Account Database (hereinafter referred to as "Wallet Account DB") Next, an example of the data structure of each of these databases will be described in turn.

[0103] First, the database managed by the competition management server 20 will be described.

[0104] <Database managed by the competition management server 20> (3-1) User DB The user DB is a database that stores information about users who will be participants in the competition. FIG. 9A is a diagram illustrating an example of a data structure of the user DB.

[0105] As shown in FIG. 9A, the user DB includes a "User ID" field, an "Account Name" field, a "Login PASS" field, a "User Name" field, a "User Attributes" field, a "Contact Information" field, a "Team" field, and a "Wallet ID" field.

[0106] The "user ID" field stores user identification information that can identify a user. The user identification information is information that identifies a user as a participant in a competition managed by the competition management server 20.

[0107] The "account name" field stores the name of the account used by the user corresponding to the user ID to participate in the game.

[0108] The “Login PASS” field stores information regarding the login password that a user corresponding to the user ID is required to enter when logging in to an external game server to participate in a competition managed by the competition management server 20.

[0109] The "user name" field stores the name of the user corresponding to the user ID.

[0110] The "user attribute" field stores information indicating the attributes of the user corresponding to the user ID. The user attributes include age, date of birth, sex, occupation, nationality, residential area, family structure, place of residence, and other attribute information based on the user's personal information.

[0111] The "Contact" field stores information indicating the contact information of the user corresponding to the user ID. The contact information may be, for example, an email address, a phone number, account information for a social networking service (SNS) or other messaging-enabled application, or a combination thereof. The contact information is not limited to the examples given here, and may include any type of information that can be used to send notifications to attendees in real time via the participant terminal 10A.

[0112] The "Team" field stores the identification information of a team to which the user corresponding to the user ID belongs, if any. The roles of the teams in the competition will be described later.

[0113] The “Wallet ID” field stores the identification information of the wallet in the distributed ledger for the user corresponding to the user ID. 9 is merely an example, and other information may be stored in the user DB. Also, the user DB may not include any of the above-mentioned fields.

[0114] (3-2) Team DB The team DB will now be described. Fig. 9B is a diagram showing an example of the data structure of the team DB. The team DB stores information about teams to which participants in a competition can belong.

[0115] As shown in FIG. 9B, the team DB includes a "team ID" field, a "team name" field, a "representative" field, and a "date of establishment" field.

[0116] The "Team ID" field stores identification information for identifying a team. The team ID is a unique value for each team in which volunteer participants become members.

[0117] The "Team Name" field stores the name of the team that corresponds to the team ID. The team name is determined by the members of the team.

[0118] The "Representative" field stores the user ID of the user who will be the representative (leader) of the team that corresponds to the team ID. A team representative is a person who has certain authority in managing the team. Examples of authority in managing a team include the following: - Decision-making authority regarding the addition of new members to the team - Decision-making authority regarding the expulsion of existing members of the team - Decision-making authority regarding the setting of custom matches in which members of the team will participate

[0119] The "date of establishment" field stores the date of establishment of the team corresponding to the team ID. Note that the structure of the team DB shown in FIG. 9B is merely an example, and other information may be stored. For example, the team DB may store conditions regarding the possession of competitive NFTs that are required to be possessed when joining the team as a joining condition. In addition, the team DB may not include any of the fields described above, such as the "date of establishment" field.

[0120] (3-3) Event DB The event DB will now be described. Fig. 9C is a diagram showing an example of the data structure of the event DB. The event DB stores information related to the holding of various competitive events related to competitions. In the system 1, the various competitive events related to competitions include any of the following: - Competitions held for the sport -Various campaigns held in relation to the event - A specific challenge plan for participants in relation to the competition Details of the campaign and challenge projects will be described later.

[0121] As shown in FIG. 9C, the event DB includes an "event ID" field, an "event name" field, an "event event type" field, an "event schedule" field, an "event environment" field, an "event location" field, and an "organizer" field.

[0122] The "event ID" field stores identification information for identifying the event.

[0123] The "event name" field stores the name of the event corresponding to the event ID.

[0124] The "Sport Event" field stores the content of the sport that is the subject of the event corresponding to the event ID. For example, if the event is a game tournament, the content of the sport corresponds to the name of the game.

[0125] The "Event Date" field stores information regarding the period during which the event corresponding to the event ID will be held.

[0126] The "Environment" field stores information about the environment in which the event corresponding to the event ID is held. For example, in the case of a game tournament in which participants participate online from their homes, the environment would be the "Internet environment," and in the case of a game tournament in which participants gather at an event venue, the environment would be the "event venue."

[0127] The "venue" field stores information about the location where the event corresponding to the event ID will be held.

[0128] The "organizer" field stores information about the organizer who is running the event corresponding to the event ID. It should be noted that the structure of the event DB shown in FIG. 9C is merely an example, and other information may be stored therein.

[0129] (3-4) Match DB Next, the match DB will be described. Fig. 10A is a diagram showing an example of the data structure of the match DB. The match DB stores information about match schedules for competitions.

[0130] As shown in FIG. 10A, the match DB includes a "match ID" field, a "event ID" field, a "match name" field, and a "granting condition ID" field.

[0131] The "Match ID" field stores identification information for identifying a match (game) between participants in the corresponding competition.

[0132] The "event ID" field stores identification information for an event in which a match corresponding to the match ID is to be held.

[0133] The "Match Name" field stores the name of the match that corresponds to the match ID.

[0134] The “granting condition ID” field stores an identification number of the granting condition for the battle proof NFT issued based on the results of the battle corresponding to the battle ID. It should be noted that the structure of the match DB shown in FIG. 10A is merely an example, and other information may be stored.

[0135] (3-5) Match History DB Next, the match history DB will be described. Fig. 10B is a diagram showing an example of the data structure of the match history DB. The match history DB stores information about the match results of a competition.

[0136] As shown in FIG. 10B, the match history DB includes a "match history ID" field, a "match ID" field, a "user ID" field, a "match result" field, and a "match date and time" field.

[0137] The "battle history ID" field stores identification information for identifying the battle history.

[0138] The "battle ID" field stores identification information of a match whose match history ID indicates the track record of the match.

[0139] The "user ID" field stores the name of the winner in the match corresponding to the match history ID.

[0140] The "Match Result" field stores information about the match result of the match that corresponds to the match history ID. Information about the match result includes, for example, the score of the match.

[0141] The "match date and time" field stores information about the date and time when the match corresponding to the match history ID took place. It should be noted that the structure of the battle history DB shown in FIG. 10B is merely an example, and other information may be stored.

[0142] (3-6) Custom Match DB Next, the custom match DB will be described. FIG. 12A is a diagram showing an example of the data structure of the custom match DB. The custom match DB stores information about custom matches that are the subject of awards in a competition. Here, a custom match refers to a match set by agreement between participants. In a custom match, participants can each deposit some of the competitive NFTs they hold to the operator as a reward for the winner, and the winner can obtain the deposited competitive NFT. In a custom match, the conditions for winning or losing can be set arbitrarily.

[0143] As shown in FIG. 12A, the custom match DB includes a "custom match ID" field, a "event ID" field, a "custom match name" field, and a "granting condition ID" field.

[0144] The "Custom Battle ID" field stores identification information for identifying the custom battle set by the participant.

[0145] The "event ID" field stores the event ID of the event for which the custom battle corresponding to the custom battle ID is set.

[0146] The "custom match name" field stores the name of the custom match that corresponds to the custom match ID.

[0147] The “granting condition ID” field stores an identification number of the granting condition for the custom match certificate NFT issued based on the results of the custom match corresponding to the custom match ID. Note that the structure of the custom battle DB shown in FIG. 12A is merely an example, and other information may be stored.

[0148] (3-7) Custom match history DB Next, the custom battle history DB will be described. Fig. 12B is a diagram showing an example of the data structure of the custom battle history DB. The custom battle history DB stores information about the results of custom battles in competitions.

[0149] As shown in FIG. 12B, the custom battle history DB includes a "custom battle history ID" field, a "custom battle ID" field, a "user ID" field, a "custom battle result" field, and a "date and time" field.

[0150] The "custom match history ID" field stores identification information that identifies the results of custom matches.

[0151] The "custom match ID" field stores identification information of the award (custom match) indicated by the custom match history ID.

[0152] The "user ID" field stores the name of the award recipient corresponding to the custom match history ID.

[0153] The "Custom Battle Result" field stores information about the award corresponding to the custom battle history ID. Information about the custom battle result includes, for example, first place, second place, third place custom battle, fighting spirit award, sponsor award, etc.

[0154] The "Date and Time" field stores information about the date and time when the award corresponding to the custom match history ID was given. Note that the structure of the custom battle history DB shown in FIG. 12B is merely an example, and other information may be stored.

[0155] (3-8) Assignment DB Next, the task DB will be described. Fig. 12A is a diagram showing an example of the data structure of the task DB. The task DB stores information on the content of plays to be achieved during a game that are set as tasks by the organizer of a competition.

[0156] As shown in FIG. 12A, the assignment DB includes an "assignment ID" field, an "event ID" field, an "assignment name" field, and an "assignment condition ID" field.

[0157] The "task ID" field stores identification information for identifying a task set by the organizer in the relevant competition.

[0158] The "Event ID" field stores the event ID of the competition in which the task corresponding to the task ID is set.

[0159] The "Assignment Name" field stores the name of the assignment that corresponds to the assignment ID.

[0160] The “Granting Condition ID” field stores the identification number of the granting condition for the assignment proof NFT issued based on the performance of the assignment corresponding to the assignment ID. Note that the structure of the assignment DB shown in FIG. 12A is merely an example, and other information may be stored therein.

[0161] (3-9) Task History DB Next, the task history DB will be described. Fig. 12B is a diagram showing an example of the data structure of the task history DB. The task history DB stores information about the history of challenges by the competition participants to challenges set by the organizer.

[0162] As shown in FIG. 12B, the assignment history DB includes an "assignment history ID" field, an "assignment ID" field, a "user ID" field, an "assignment result ID" field, and a "date and time" field.

[0163] The "assignment history ID" field stores identification information for identifying the assignment history.

[0164] The "task ID" field stores identification information of a challenged task in the task history corresponding to the task history ID.

[0165] The "user ID" field stores the identification information of the user who is the subject of the challenge in the challenge history corresponding to the challenge history ID.

[0166] The "Assignment Result ID" field stores information regarding the result of whether or not the corresponding assignment was accomplished in the assignment history corresponding to the assignment history ID.

[0167] The "date and time ID" field stores information about the date and time when the corresponding task was attempted in the task history corresponding to the task history ID. Note that the structure of the assignment history DB shown in FIG. 12B is merely an example, and other information may be stored therein.

[0168] (3-10) Winning DB Next, the prize DB will be described. Fig. 13A is a diagram showing an example of the data structure of the prize DB. The prize DB stores information about prizes that are awarded in the competition.

[0169] As shown in FIG. 13A, the prize DB includes a "prize ID" field, an "event ID" field, a "prize name" field, and a "award condition ID" field.

[0170] The "prize winner ID" field stores identification information for identifying the prize winner that is eligible for an award in the relevant competition.

[0171] The "Event ID" field stores the event ID of the competition in which the prize corresponding to the prize ID is set.

[0172] The "prize name" field stores the name of the prize that corresponds to the prize ID.

[0173] The “Granting Condition ID” field stores an identification number of the granting condition for the winning certificate NFT issued in accordance with the winning achievement corresponding to the winning ID. It should be noted that the structure of the winning DB shown in FIG. 13A is merely an example, and other information may be stored therein.

[0174] (3-11) Award History DB Next, the winning history DB will be described. FIG. 13B is a diagram showing an example of the data structure of the winning history DB. Information regarding the achievements of winning awards in a competition is stored in the winning history DB.

[0175] As shown in FIG. 13B, the winning history DB includes a "winning history ID" field, a "winning ID" field, a "user ID" field, a "winning result" field, and a "date and time" field.

[0176] In the "winning history ID" field, identification information for specifying the achievement of winning an award is stored.

[0177] In the "winning ID" field, identification information for the commendation (winning an award) indicated by the winning history ID is stored.

[0178] In the "user ID" field, the name of the person who is the subject of the commendation corresponding to the winning history ID is stored.

[0179] In the "winning result" field, information regarding the content of the commendation corresponding to the winning history ID is stored. Information regarding the winning result includes, for example, winning the championship, runner-up, third place, fighting spirit award, sponsor award, etc.

[0180] In the "date and time" field, information regarding the date and time when the commendation corresponding to the winning history ID was given is stored. Note that the structure of the winning history DB shown in FIG. 13B is merely an example, and other information may be stored.

[0181] Next, the database managed by the NFT management server 30 will be described.

[0182] <The database managed by the NFT management server 30> (3-12) Grant condition DB FIG. 14 is a diagram showing an example of the data structure of the grant condition DB. The grant condition DB is a database in which grant conditions, which are the conditions for awarding various competition NFTs, are stored.

[0183] As shown in FIG. 14, the granting condition DB has an “granting condition ID” field, an “granting condition name” field, an “NFT type ID to be granted” field, and an “NFT ledger ID to be granted” field.

[0184] The “granting condition ID” field stores identification information of the granting condition of the competitive NFT.

[0185] The "Name of Grant Condition" field stores the name of the grant condition corresponding to the grant condition ID.

[0186] The "condition content" field stores the content of the granting condition corresponding to the granting condition ID. For example, the type ID of the competition proof NFT that needs to be held in order to grant the medal NFT is stored as the content of the granting condition.

[0187] The "Granted NFT type ID" field stores the type ID of the competition NFT that is granted under the grant condition corresponding to the grant condition ID.

[0188] The “NFT ledger ID to be granted” field stores the ledger ID of the distributed ledger of the competitive NFT to be granted under the granting conditions corresponding to the granting condition ID. It should be noted that the structure of the grant condition DB shown in FIG. 14 is merely an example, and other information may be stored.

[0189] (3-13) Competitive NFT type DB 15 is a diagram showing an example of the data structure of the competition NFT type DB. The competition NFT type ID is a database that stores information about the type of the competition NFT that serves as the master of the competition NFT.

[0190] As shown in FIG. 15, the competitive NFT type DB includes a "competitive NFT type ID" field, a "competitive NFT type name" field, a "digital content address" field, a "granting conditions" field, a "competitive achievements to be certified" field, and a "transferable" field.

[0191] The "Competition NFT type ID" field stores identification information regarding the type of competition NFT, which is a unique value for each type of competition NFT.

[0192] The "Competition NFT type name" field stores the name of the competition NFT type corresponding to the competition NFT type ID.

[0193] The "digital content address" field stores address information (resource information) of the digital content associated with the racing NFT corresponding to the racing NFT type corresponding to the racing NFT type ID.

[0194] The "Granting Conditions" field stores conditions for a user to receive a grant for a competitive NFT corresponding to the competitive NFT type corresponding to the competitive NFT type ID. For example, in the case of a match proof NFT, information about the match that must be played and won in order to receive the grant is recorded. On the other hand, in the case of a challenge proof NFT, information about the challenge that must be completed in order to receive the grant is stored. These acquisition conditions are defined for each competitive NFT type.

[0195] In the "certified competition achievements" field, when a competition NFT corresponding to the competition NFT type corresponding to the competition NFT type ID is held, information regarding the competition achievements to be certified for the holder is stored. For example, the following information is recorded as the certified competition achievements. - Winning records in specific matches - Achievements in specific tasks -Winning in specific competitions

[0196] The "transferability" field stores an attribute regarding whether the user who first acquired the competitive NFT corresponding to the competitive NFT type corresponding to the competitive NFT type ID can transfer it to another user. In other words, whether the competitive NFT issued to the user by the issuer of the competitive NFT can be transferred to another user by transfer or the like is defined for each competitive NFT type. Basically, the Proof of Competition NFT is not transferable, and the Medal NFT is transferable. However, the Proof of Competition NFT may be made transferable, and the Support Item NFT may be made non-transferable. Note that the structure of the competition NFT type DB shown in FIG. 15 is merely an example, and other information may be stored.

[0197] (3-14) Ownership history DB 16 is a diagram showing an example of the data structure of a holding history DB. The holding history DB is a database that stores the holding history of competitive NFTs. The holding history of competitive NFTs is periodically updated by recording new records, for example, through a process of periodically aggregating holding status.

[0198] As shown in FIG. 16, the holding history DB includes an "holding history ID" field, an "holder" field, an "NFT ledger ID" field, an "NFT type ID" field, an "acquisition date" field, and an "aggregation date" field.

[0199] The "holding history ID" field stores identification information regarding the type of the competition NFT, which is a valuable value that can identify the holding history of the competition NFT.

[0200] The "Owner" field stores identification information of the user who is the owner of the competitive NFT in the ownership history corresponding to the ownership history ID.

[0201] The "NFT Ledger ID" field stores the identification information of the distributed ledger that records information about the competitive NFT that is the object of holding in the holding history corresponding to the holding history ID.

[0202] In the "NFT type" field, identification information of the NFT type of the competitive NFT that is the object of possession is stored in the possession history corresponding to the possession history ID.

[0203] In the "acquisition date" field, information regarding the time when the competitive NFT that is the object of possession was acquired (granted) by the user who is the subject of possession is stored in the possession history corresponding to the possession history ID.

[0204] In the "aggregation date" field, information regarding the time when the possession history corresponding to the possession history ID was aggregated is stored. Note that the structure of the possession history DB shown in FIG. 16 is merely an example, and other information may be stored.

[0205] Next, the following databases managed in the distributed data storage of the P2P distributed system 40 will be described. · Dapps account DB · Wallet account DB

[0206] Based on the configuration of the distributed data storage described above, actually, each of the signal processing devices 40A to 40E constituting the P2P distributed system 40 stores fragmented cache data. In the following description of FIG. 17, for the sake of assisting understanding, each database is illustrated in the state of the original file restored by a specific hash value, and its content is described.

[0207] <Database Managed by NFT Management Server 30> (3-15) Dapps account DB FIG. 17A is a diagram showing an example of the data structure of the Dapps account DB. The Dapps account DB is a database that manages the account information of users in the NFT management platform provided by the distributed application (Dapps) 60.

[0208] As shown in FIG. 17A, the Dapps account DB includes a “Dapps account ID” field, a “Dapp login PASS” field, a “user name” field, and a “contact” field.

[0209] The “Dapps Account ID” field stores a user ID in the NFT management platform provided by the decentralized application (Dapps) 60.

[0210] The “Dapp Login PASS” field stores the login password that a user corresponding to the Dapps account ID is required to enter when logging in to the NFT management platform.

[0211] The "User Name" field stores information indicating the name of the user corresponding to the Dapps account ID. Information indicating the user's name includes not only the user's name but also the handle name registered by the user himself / herself.

[0212] The "Contact" field stores information indicating the contact of the user corresponding to the Dapps account ID. The contact information may be, for example, an email address, a phone number, account information of a social networking service (SNS) or other messaging-enabled application, or a combination thereof. The contact information is not limited to the examples given here, and may include information regarding any contact means available for sending notifications to the user in real time via the participant terminal 10A. Note that the structure of the Dapps account DB shown in FIG. 17A is merely an example, and other information may be stored therein.

[0213] (3-16) Wallet DB 17B is a diagram showing an example of the data structure of the wallet DB. The wallet DB is a database that stores the holding status of NFTs managed by owners in a distributed ledger.

[0214] As shown in FIG. 17B, the wallet DB has a “wallet ID” field, a “wallet PASS” field, and a “Dapps account ID” field.

[0215] The “Wallet ID” field stores the wallet identification information that will serve as the public key in the distributed ledger.

[0216] The "Wallet PASS" field stores the password information, which serves as the private key in the distributed ledger, for the wallet corresponding to the wallet ID. By using the wallet password information, NFTs associated with the wallet can be transferred.

[0217] The “Dapps account ID” field stores the Dapps account ID of the user who owns the wallet corresponding to the wallet ID. Note that the structure of the wallet DB shown in FIG. 17B is merely an example, and other information may be stored therein.

[0218] (3-17) Distributed Ledgers Next, we will explain the data structure of the distributed ledger. Figure 18 is a diagram showing an example of the data structure of a distributed ledger that manages competitive NFTs. As shown in Figure 18, the distributed ledger is associated with digital content stored on an external server.

[0219] Competitive NFTs are managed on a distributed ledger. Competitive NFTs allow you to refer to the transaction history associated with the transfer of ownership, which will be described later. By referencing all transaction history related to a certain NFT, it is possible to identify the past owners of the token.

[0220] A distributed ledger consists of a ledger (blockchain) that contains the following blocks: - Blocks that record contract data, including scripts for executing smart contracts as distributed applications - A block containing information about the competitive NFT A block that contains at least a hash value and transaction data When NFTs are transferred between users, new transaction data is generated in the distributed ledger, and a new block is added after verification by the signal processing devices 40A to 40E shown in FIG. 8.

[0221] The distributed ledger stores various information about the competitive NFTs. The various information about the competitive NFTs includes the following items: Ledger ID: Identification information of the distributed ledger that records information about the relevant competition NFT Competitive NFT Type ID: Identification information for the relevant competitive NFT type Digital content address: the corresponding value in the competitive NFT type DB - Granting conditions: Values ​​corresponding to the competitive NFT type DB - Proof of competition record: The corresponding value in the competition NFT type DB Actual competition results: The competition results entered Transferability: The corresponding value in the competitive NFT type DB Issuer information: Information about the person who issued the competitive NFT - Acquirer information: Information about the user who was granted the competitive NFT (the user who first acquired it) -Issue date and time: The date and time when the issuing entity issued the relevant competitive NFT.

[0222] A ledger ID is information that identifies the transaction history of one token in a distributed ledger. A ledger ID is set for each token, and a token ID that is a unique value for each token can be used. In other words, the ledger ID may be used as the token ID, or the token ID may be used as the ledger ID. Also, a token ID that is a unique value for the ledger ID may be set separately.

[0223] The competitive NFT type is information indicating the type of competitive NFT managed by the blockchain corresponding to the ledger ID, and is identification information regarding the type of competitive NFT defined in the competitive NFT type DB.

[0224] The issuer information may include, for example, any of the following companies: · Competition organizers who hold competitions such as game tournaments · System 1 vendor

[0225] The acquirer information includes the following information: Information that identifies the acquirer (user ID, name, nickname, handle name, etc.) Information about the organization or team to which the recipient belongs Information about the acquirer's attributes (various attribute information stored in the user database)

[0226] The transaction data contains the wallet ID of the owner of the NFT managed by the blockchain. By identifying the wallet ID included in the transaction data of the latest block, it is possible to identify the current owner of the NFT.

[0227] The distributed ledger may use a public blockchain and a private blockchain. In this case, a multi-layered structure may be used, in which ordinary transactions are recorded on the private blockchain and the latest information is periodically updated on the public blockchain.

[0228] (4) Overview of the embodiment An overview of this embodiment will be described below. Fig. 19 is an explanatory diagram of the overview of this embodiment.

[0229] (4-1) Issuance (granting) of a competition proof NFT by inputting the competition results As shown in Fig. 19, in the system 1, the competition management server 20 accepts input of the results of matches in a game tournament using an external game server or the like shown in Fig. 8. At this time, the input of the results of the matches is performed by any of the following methods. At least one of the contestants (winners and losers) Competition organizer (automatic entry) -Automatic entry followed by confirmation by the contestant After the contestant enters the information, it is confirmed by the contest organizer.

[0230] In the system 1, the NFT management server 30 issues a competition proof NFT that is set as a granting condition based on the competition results input to the competition management server 20. In principle, the competition proof NFT is issued to the winner, but a competition proof NFT that proves defeat may also be issued to the loser.

[0231] In addition, for custom battles in which users (competitors) individually set the rules for winning and losing, in response to input of the battle results to the competition management server 20, the NFT management server 30 issues a custom battle certificate NFT based on the set rules for the custom battle.

[0232] In addition, for example, with regard to a task set by the organizer of a game tournament, in response to the judgment result on the game server side being input to the competition management server 20, the NFT management server 30 issues a task proof NFT based on the granting conditions for the set task.

[0233] In addition, in response to the information on the winning results of the game tournament compiled by the game server being input to the competition management server 20, the NFT management server 30 issues a winning certificate NFT based on the set awarding conditions for winning.

[0234] (4-2) Issuance (granting) of medal NFTs based on the compilation of competition results Next, we will explain the process of issuing (granting) medal NFTs based on the compilation of competition results. The NFT management server 30 tally up the status of each user's holding of competition proof NFTs at a preset frequency. In addition, the NFT management server 30 may tally up the status of each user's holding of competition proof NFTs in response to an operation instruction from an administrator who manages the system 1.

[0235] In the system 1, the NFT management server 30 issues (grant) medal NFTs to the corresponding users based on the collected information on the ownership of the competition certificate NFTs of each user. The conditions for granting medal NFTs are registered in advance in the granting conditions DB. This allows each user to be granted a medal NFT based on their competition performance. Such processing by the system 1 will be specifically described below.

[0236] (5) System 1 control processing The control process of the system 1 in this embodiment will be described.

[0237] (5-1) Proof of Competition NFT issuance process The competition proof NFT issuing process in this embodiment will be described. Fig. 20 is a flowchart of the competition proof NFT issuing process. In this description, issuing an NFT to a user may be expressed as "granting the NFT" to the user.

[0238] As shown in FIG. 20, in the process of issuing a competition proof NFT, first, the operator terminal 10B inputs competition results to the competition management server 20 (step S101). Specifically, the processor 12 of the operator terminal 10B transmits the following information to the competition management server 20 as the competition results.

[0239] 1) If the Proof-of-Competition NFT is a Proof-of-Battle NFT -Competitor's user ID Corresponding match ID - Results (actual competition results) 2) If the Proof of Competition NFT is a custom match NFT -Competitor's user ID -Corresponding custom match ID - Results (actual competition results)

[0240] 3) If the Proof-of-Competition NFT is a Proof-of-Challenge NFT - User ID of the contestant who challenged the challenge Corresponding issue ID - Results of challenges (actual competition results) 4) If the Proof of Competition NFT is a Proof of Winning NFT Winner's User ID Corresponding prize winning ID · Winning history (actual competition results) The competition results may be input by the competition participants themselves, or may be automatically input from an external game server.

[0241] After step S101, the competition management server 20 accepts competition results (step S01). Specifically, the processor 32 of the NFT management server 30 accepts information regarding the competition results transmitted from the operator terminal 10B.

[0242] After step S202, the competition management server 20 records the competition results accepted in step S202 (step S203). Specifically, the processor 22 of the competition management server 20 records the competition results as follows. If the competition results are a match history: the competition results are stored in the match history DB. If the competition record is a history of a custom match: the competition record is stored in the custom match history DB. If the competition record is a history of task challenges: the competition record is stored in the task history DB. If the competition results are a winning history: the competition results are stored in the winning history DB. This causes a new record to be recorded in each corresponding database.

[0243] After step S202, the competition management server 20 transmits the competition results to the NFT management server 30 (step S203). Specifically, the processor 22 of the competition management server 20 transmits, from among the competition results, the competition results to which a competition proof NFT is to be granted to the NFT management server 30. The competition results transmitted by the competition management server 20 include at least the following information. - When granting a match proof NFT: Match history ID and corresponding grant condition ID - When granting a custom match proof NFT: Custom match history ID and corresponding grant condition ID - When granting a proof NFT: the project history ID and the corresponding grant condition ID - When granting a winning proof NFT: winning history ID and corresponding grant condition ID

[0244] After step S203, the NFT management server 30 acquires the competition results (step S301). Specifically, the NFT management server 30 acquires the competition results transmitted from the competition management server 20 in step S203.

[0245] After step S301, the NFT management server 30 determines the granting conditions for the competition proof NFT (step S302). Specifically, the processor 32 of the NFT management server 30 refers to the granting condition DB for the granting condition included in the acquired competition results, and determines whether the granting condition ID included in the competition results is recorded in the granting condition DB. If the granting condition corresponding to the granting condition ID is not recorded in the granting condition DB, the NFT issuance process is terminated.

[0246] On the other hand, in step S302, if the granting condition corresponding to the granting condition ID is recorded in the granting condition DB, the NFT management server 30 issues an instruction to issue a competition proof NFT (step S303). Specifically, the processor 32 of the NFT management server 30 refers to the granting condition DB for the granting conditions included in the acquired competition results, identifies the NFT type ID and grant target ledger ID of the competition certificate NFT to be granted, and then transmits them to the P2P distributed system 40.

[0247] After step S303, the P2P distributed system 40 records the transaction data of the competition proof NFT to be granted in the distributed ledger (step S401). Specifically, the distributed application of the P2P distributed system 40 records information about the acquirer and the issuance date and time as information about the NFT in the newly created distributed ledger. The distributed application then refers to the user DB to identify the wallet ID of the user who will be newly issued with a competition proof NFT. The distributed application records the wallet ID of the user to be granted as owner information in the latest block as new transaction data (TX) in the newly issued ledger.

[0248] This records the information of the owner of the competition proof NFT to be granted. In other words, this process grants the competition proof NFT to the contestant who achieved the corresponding competition results.

[0249] After step S303, the NFT management server 30 sends a notification of issuance of the corresponding competition certificate NFT to the participant terminal 10A (step S304).

[0250] After step S304, the participant terminal 10A receives a grant notification regarding the competition certificate NFT sent from the NFT management server 30 (step S102). This completes the process of granting the competition proof NFT.

[0251] (5-2) Proof-of-challenge NFT issuance process

[0252] Next, the medal NFT issuing process in this embodiment will be described. Figure 21 is a flowchart of the medal NFT issuing process.

[0253] As shown in FIG. 21, in the medal NFT issuance process, first, the NFT management server 30 counts up the holding status of the competition proof NFT of each user (step S311). Specifically, the processor 32 of the NFT management server 30 accesses the distributed ledger managed by the P2P distributed system 40 and tally up the competition proof NFTs held by each user. The processor 32 of the NFT management server 30 records the totaled holding status as a new record in the holding history DB.

[0254] After step S311, the NFT management server 30 determines the granting conditions (step S312). Specifically, the processor 32 of the NFT management server 30 refers to the holding history DB and the granting conditions DB and determines whether the holding status of the competition proof NFT for each user satisfies the conditions for granting the medal NFT. If the holding status of the competition proof NFT of the user does not satisfy the conditions for granting the medal NFT, the NFT management server 30 ends the medal NFT issuance process.

[0255] On the other hand, in step S312, if the user's holdings of the competition proof NFT satisfy the conditions for granting a medal NFT, the NFT management server 30 issues an instruction to issue a medal NFT (step S313). Specifically, the processor 32 of the NFT management server 30 refers to the granting conditions DB for the medal NFT granting conditions set based on the user's ownership of the competition proof NFT, identifies the NFT type ID and grant target ledger ID of the medal NFT to be granted, and then transmits them to the P2P distributed system 40.

[0256] After step S313, the P2P distributed system 40 records the transaction data of the medal NFT to be awarded in the distributed ledger (step S411). Specifically, the distributed application of the P2P distributed system 40 records information about the acquirer and the issuance date and time as information about the NFT in the newly created distributed ledger. The distributed application then refers to the user DB to identify the wallet ID of the user who will be newly issued the medal NFT. The distributed application records the wallet ID of the user to be granted as owner information in the latest block as new transaction data (TX) in the newly issued ledger.

[0257] This records the information of the owner of the medal NFT to be awarded. In other words, this process grants the medal NFT to the contestant who achieved the corresponding competition results.

[0258] After step S313, the NFT management server 30 sends a notification of issuance of the corresponding medal NFT to the participant terminal 10A (step S314).

[0259] After step S314, the participant terminal 10A receives a grant notification regarding the medal NFT sent from the NFT management server 30 (step S121). This completes the process of granting the medal NFT.

[0260] (6) Variations A modification of this embodiment will now be described. In this modification, the partition in which the content data associated with the NFT is managed is different from that in the above embodiment. Figure 22 is a diagram showing another example of the structure of the distributed ledger. As shown in FIG. 22, in a distributed ledger according to a modified example, digital content data (e.g., image data) is incorporated as part of the blockchain.

[0261] (7) Summary As described above, in the system 1, the NFT management server 30 acquires the competition results including the results of the competitions performed by multiple participants, and issues a competition proof NFT linked to information related to the competition results to the relevant participant based on the acquired competition results. Therefore, the participants' competition results can be accumulated with their authenticity guaranteed.

[0262] Furthermore, in System 1, the Proof of Competition NFT includes a Proof of Battle NFT that serves as proof of the holder's victory or defeat in a match. Therefore, depending on the possession of the Proof of Battle NFT, the results of the match can be stored with guaranteed authenticity.

[0263] Furthermore, in the system 1, the competition proof NFT includes a custom match NFT that serves as proof of victory or defeat under the competition rules of the holder. Therefore, depending on the possession of the custom match proof NFT, the results of custom matches held between users under rules set by the users can be stored with guaranteed authenticity.

[0264] In addition, in the system 1, the competition proof NFT includes a challenge proof NFT that serves as proof of the holder's achievement of the challenge action. This allows the achievement of the user's achievement of the challenge action to be accumulated with guaranteed credibility.

[0265] In addition, in the system 1, the competition proof NFT includes a winning proof NFT that serves as proof of the holder's winning in the competition. This allows the user's winning record in the competition to be accumulated with its authenticity guaranteed.

[0266] In addition, the system 1 tally up the users' ownership of the competition proof NFTs, and based on the tally up, issue the users with medal NFTs as a reward for their past competition achievements. Therefore, the accumulated competition achievements of participants can be rewarded with medal NFTs.

[0267] In addition, in the system 1, the medal NFT includes a secondary prize NFT that is a secondary prize for the competition achievement that led to the acquisition of the competition certificate NFT. Therefore, it is possible to reward a user for the competition achievement that the user has achieved by granting the user an NFT.

[0268] In addition, in the system 1, the medal NFT includes a ranking NFT that indicates a ranking based on the competition performance of the members composed of the participants in the competition. Therefore, a user can be rewarded by being given a ranking NFT for the ranking the user achieved among a group of participants.

[0269] Furthermore, in the system 1, medal NFTs are issued when the holding status exceeds a preset achievement threshold, and include a Hall of Fame NFT that indicates that the holder's competitive achievements have reached an achievement. For this reason, a user can be rewarded for a certain achievement in a competition by being granted a Hall of Fame NFT.

[0270] Furthermore, in the system 1, medal NFTs are issued in response to the holding status satisfying a predetermined granting condition as a tendency of a behavioral pattern in a competition, and include a pseudonymous NFT that indicates the behavioral pattern of the holder. Therefore, a user can be rewarded by being given a pseudonymous NFT for the tendency of the behavioral pattern in the competition that the user has realized.

[0271] Furthermore, in the system 1, the medal NFT includes a campaign NFT that is issued in response to satisfying the conditions for granting set in any campaign held in connection with the holding of the competition. Therefore, a user can be rewarded for participating in the campaign by being granted a campaign NFT.

[0272] (8) Other modifications Other variations of the system 1 will now be described. The storage device 11 may be connected to the participant terminal 10A via the network NW. The storage device 21 may be connected to the competition management server 20 via the network NW. The storage device 31 may be connected to the NFT management server 30 via the network NW.

[0273] In the above embodiment, the configuration was described in which the process of issuing the competition proof NFT and the medal NFT was automatically executed using the wallet ID of the user recorded in the user DB, but this is not limited to this. For example, the process of issuing the competition proof NFT and the medal NFT may be executed via an acquisition request from the user to be issued.

[0274] Specifically, the NFT management server 30 sends a URL (mintURL) which is an acquisition application resource for executing the process of newly issuing a competition certificate NFT and a medal NFT to the contact information of the participant terminal 10A. The participant terminal 10A then receives the acquisition application resource attached to, for example, an email. The participant terminal 10A then applies to acquire the attendance certificate NFT. Specifically, the processor 12 of the participant terminal 10A accepts an operation from the user to click on the mintURL as the acquisition application resource attached to the email, thereby accessing the resource information indicated by the mintURL. As a result, an acquisition application is sent to the NFT management server 30.

[0275] Also, at this time, the user may operate the participant terminal 10A to perform a login operation to the NFT management platform provided by the NFT management server 30. Specifically, the processor 12 of the participant terminal 10A accepts the information of the "Dapps account ID" and "Dapps account PASS" input by the user. This allows the user to log in to the NFT management platform and input an application to acquire a competition proof NFT.

[0276] The medal NFTs will also include a team flag NFT that symbolizes the team made up of competitors, and a team member badge NFT that certifies the competitor's membership in that team. A team flag NFT is a non-fungible token that serves to prove that its holder (group) is an official or unofficial team related to the sport. A team flag NFT is newly issued upon application from the team leader (representative), and the leader's wallet ID or the team's wallet ID is recorded on the blockchain as the owner information. Here, an official team is one that has been approved by the governing body of the sport, and an unofficial team is one that is made up of volunteer competitors. The team flag NFT is linked to digital content prepared for each team (for example, an illustration of the team flag with the team symbol on it).

[0277] The Team Member Badge NFT is a non-fungible token that serves to prove that the holder is a member of a specific team. Team Member Badge NFTs are issued by specific users (team executive members) designated within a team, such as the team leader.

[0278] Here are some examples of how you can use the Faction Flag NFT: 1) Issue a member badge NFT based on the group flag NFT. A member badge NFT, which is a non-fungible token that has the function of proving team membership, can be issued to new team members as a medal NFT displaying an illustration of the team symbol or other image displayed on the team flag.

[0279] 2) Use of the team symbol included in the team flag NFT on original merchandise The team symbol contained in the team flag NFT can be used on original goods, either physical or virtual, created for each team.

[0280] 3) Offering them as prizes in custom team battles For example, in a custom match between teams, such as a team competition, the team's flag NFT can be set as a secondary prize NFT to be issued to the winning team. In this case, the executive members of the team are authorized to offer the flag NFT as a prize for the custom match. In this case, the winning team can acquire the flag NFT of the losing team. With the transfer of ownership of the flag NFT, various authorities regarding the management of the team that were given to the executives of the losing team may be transferable to new members of the team to which the transfer is made.

[0281] In addition, among the secondary prize NFTs, the championship flag NFT and the trophy NFT may be returned by the current owner (the winner of the most recent tournament) to the organizer of the tournament at a specified time, such as immediately before the next tournament. The secondary prize NFT may be returned by the current owner's operation, or the secondary prize NFT may be automatically transferred in response to the arrival of the return time. This point will be described in detail.

[0282] First, a championship flag NFT is a type of prize NFT issued to the winning athlete or team, and is a non-fungible token that is primarily loaned to its owner. In addition, a trophy NFT is a type of prize NFT issued to a winning athlete or team, and is a non-fungible token that is loaned exclusively to its owner.

[0283] Here, the following distinction can be made between the award certificate NFT as the proof of competition NFT and the championship flag NFT as the secondary prize NFT. - Award Certificate NFT: A competition certificate NFT that proves that the winner won a prize (in principle, the winner will own it permanently) - Winner's flag NFT: A medal NFT loaned to the previous winner as a prize for winning for a certain period of time (for example, until the next tournament (in principle, the winner will own it temporarily) In addition, restrictions can be placed on the holding period of trophy NFTs, just like with championship pennant NFTs, which are also secondary prize NFTs.

[0284] Then, for medal NFTs that are primarily owned by a user, such as championship flag NFTs (and trophy NFTs), when the preset return time arrives, information about the tournament organizer is overwritten in a new block of the distributed ledger as the owner information of the corresponding medal NFT, allowing the medal NFT to be transferred (returned) to the tournament organizer. The process of returning such a specific medal NFT can be performed automatically by setting the time of the transfer process (return) to the tournament organizer in advance in contract data that includes a script for executing the processing of a smart contract as a decentralized application.

[0285] Furthermore, the medal NFT may be provided with a display equivalent to the pennant ribbon on which the names of past winners are written on an actual championship flag. For example, for a wallet ID recorded as holder information on the blockchain, the wallet DB and Dapps account DB may be referenced, and the user name (such as an in-game handle name) associated with the wallet ID may be displayed on the digital content associated with the medal NFT.

[0286] In addition, depending on the holdings of any of the aforementioned competition NFTs, participation in the competition may be evaluated and reward tickets that provide various services related to the competition may be issued.

[0287] In the above embodiment, an example of handling the results of a game competition was shown, but the system 1 is not limited to this. That is, the system 1 may be applied to accumulate competition results not only for competitions conducted in a virtual space such as a game, but also for the results of various sports competitions conducted in a real space.

[0288] Although the embodiment of the present invention has been described in detail above, the scope of the present invention is not limited to the above embodiment. Furthermore, the above embodiment can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above embodiment and modified examples can be combined, or a part of them can be omitted.

[0289] (9) Additional Notes The matters described in the embodiment and the modified examples are supplemented below.

[0290] (Appendix 1) A program to be executed by a system having a computer equipped with a processor, The program causes the processor to A step of acquiring a competition record including the results of a competition performed by a plurality of participants (step S301); A program that executes a step (step S303) of issuing a competition proof NFT, which is a non-fungible token linked to information regarding the competition results, to at least one of the participants based on the acquired competition results.

[0291] (Appendix 2) Proof of Competition NFTs are The program described in Appendix 1, including a Proof-of-Game NFT, which is a non-fungible token that is issued in response to the outcome of a single competitive match and serves as proof of the holder's victory or defeat in the match.

[0292] (Appendix 3) Proof of Competition NFTs are The program described in Appendix 1, including a custom battle NFT, which is a non-fungible token that is issued to participants in the competition who have achieved a competitive record in a competition conducted based on any battle rules agreed upon in advance by the participants, and which serves as proof of victory or defeat under the holder's any battle rules.

[0293] (Appendix 4) Proof of Competition NFTs are A program as described in Appendix 1, including a proof-of-challenge NFT, which is a non-fungible token that is issued in response to the achievement of a pre-set challenge action by an action in the competition and serves as proof of the holder's achievement of the challenge action. (Appendix 5) Proof of Competition NFTs are The program described in Appendix 1, including a prize-winning NFT, which is a non-fungible token issued in response to a prize-winning performance in a competitive tournament and which serves as proof of a holder's winning in the tournament.

[0294] (Appendix 6) The processor further comprises: A step of aggregating the users' ownership status of competition proof NFTs (step S311); The program described in Appendix 1 executes a step (step S313) of issuing a medal NFT, which is a non-fungible token that serves as an award for the holder's past competitive achievements, to the user based on the compiled holdings.

[0295] (Appendix 7) Medal NFTs are The program described in Appendix 6, including a prize NFT, which is a non-fungible token that serves as a prize for the competition achievement that led to the acquisition of the Proof of Competition NFT.

[0296] (Appendix 8) Medal NFTs are The program described in Appendix 6, including a ranking NFT, which is a non-fungible token that indicates a ranking based on the competition performance of a member consisting of participants in the competition.

[0297] (Appendix 9) Medal NFTs are The program described in Appendix 6, including a Hall of Fame NFT, a non-fungible token that is issued in response to a holder crossing a pre-established achievement threshold and indicates that the holder's athletic achievements have amounted to achievement.

[0298] (Appendix 10) Medal NFTs are The program described in Appendix 6, including a pseudonymous NFT, which is a non-fungible token that is issued in response to the holding status satisfying a predetermined grant condition as a tendency of a behavioral pattern in a competition and indicates the behavioral pattern of the holder.

[0299] (Appendix 11) Medal NFTs are The program described in Appendix 6, including a campaign NFT, which is a non-fungible token issued in response to fulfilling the grant conditions set in any campaign held in connection with the holding of the competition.

[0300] (Appendix 12) 1. A method executed by a system having a computer with a processor, comprising: The method includes a processor: A step of acquiring a competition record including the results of a competition performed by a plurality of participants (step S301); A program that executes a step (step S303) of issuing a competition proof NFT, which is a non-fungible token linked to information regarding the competition results, to at least one of the participants based on the acquired competition results.

[0301] (Appendix 13) A system having a computer with a processor, The system may include a processor. A means for acquiring competition results including results of competitions conducted by a plurality of participants; A program that executes a means for issuing a competition proof NFT, which is a non-fungible token linked to information regarding the competition results, to at least one of the participants based on the acquired competition results. [Explanation of symbols]

[0302] 1: NFT Management System 10: User terminal 20: Competition results management server 30: NFT Management Server 40: P2P distributed systems

Claims

1. A program to be executed by a system having a computer equipped with a processor, The program causes the processor to: acquiring competition results including results of competitions conducted by a plurality of participants; A program that executes a step of issuing a competition proof NFT, which is a non-fungible token linked to information regarding the competition results, to at least one of the participants based on the acquired competition results.

2. The competition proof NFT is: The program of claim 1, further comprising a match proof NFT, which is a non-fungible token issued in response to the outcome of a match related to the competition and serves as proof of the holder's victory or defeat in the match.

3. The competition proof NFT is: The program of claim 1, further comprising a custom battle NFT, which is a non-fungible token issued to participants in the competition who have achieved a competitive record in a competition conducted based on any battle rules previously agreed upon by the participants, and which serves as proof of the holder's victory or defeat under the any battle rules.

4. The competition proof NFT is: The program of claim 1, wherein the action in the competition includes a challenge proof NFT, which is a non-fungible token that is issued in response to the achievement of a predetermined challenge action and serves as proof of the holder's achievement of the challenge action.

5. The competition proof NFT is: The program of claim 1, further comprising a prize proof NFT, which is a non-fungible token issued in response to a winning achievement in a tournament related to the competition and serves as proof of the holder's winning in the tournament.

6. The processor further comprises: A step of collecting information on the users' holdings of the competition proof NFTs; The program of claim 1, further comprising: a step of issuing to the user a medal NFT, which is a non-fungible token that serves as an award for the holder's past athletic achievements, based on the compiled holding status.

7. The said medal NFT is: The program of claim 6, further comprising a secondary prize NFT that is a non-fungible token that serves as a secondary prize for the competition achievement that led to the acquisition of the competition proof NFT.

8. The said medal NFT is: The program of claim 6, further comprising a ranking NFT, which is a non-fungible token indicating a ranking based on the competition performance of members consisting of participants in the competition.

9. The said medal NFT is: The program of claim 6, further comprising a Hall of Fame NFT, which is a non-fungible token issued in response to the holding status exceeding a preset performance threshold and indicating that the holder's athletic achievements have led to said achievement.

10. The said medal NFT is: The program of claim 6, wherein the holding status includes a pseudonymous NFT, which is a non-fungible token that is issued in response to satisfying a predetermined grant condition as a tendency of a behavioral pattern in the competition and indicates the behavioral pattern of the holder.

11. The said medal NFT is: The program of claim 6, further comprising a campaign NFT, which is a non-fungible token issued in response to satisfaction of grant conditions set in any campaign held in connection with the holding of the competition.

12. 1. A method executed by a system having a computer with a processor, comprising: The method further comprises the processor: acquiring competition results including results of competitions conducted by a plurality of participants; and issuing a competition proof NFT, which is a non-fungible token linked to information regarding the competition results, to at least one of the participants based on the acquired competition results.

13. A system having a computer with a processor, The system further comprises: A means for acquiring competition results including results of competitions conducted by a plurality of participants; A system that executes a means for issuing a competition proof NFT, which is a non-fungible token linked to information regarding the competition results, to at least one of the participants based on the acquired competition results.

Citation Information

Patent Citations

  • Scaled VR engagement and views at eSports events

    JP2021516087A

Cited By

  • Method for creating non-fungible tokens (NFTS)

    WO2026196258A1