Lottery method, lottery program, and lottery device

Abstract

To provide a lottery method, a lottery program and a lottery device consuming crypto assets.SOLUTION: In a lottery method, a computer receives a lottery request including a user ID, updates the number of held tickets associated with the received user ID, and purchasable with on-chain token of crypto assets, performs a lottery and transmits a lottery result.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] The present invention relates to a lottery method, a lottery program, and a lottery device for consuming cryptocurrency.

Background Art

[0002] In online games, a random item providing method is employed. The random item providing method is what is called a so-called "gacha" (registered trademark). Gacha is a method of providing characters, items, etc. that can be used on an online game in which characters, pictures, symbols, etc. are displayed electromagnetically, by using chance to determine the types of items, etc.

[0003] On an online game, a virtual world is constructed where a user exists as an avatar. Commercial activities similar to those in the real world are carried out in the virtual world, and currency is used as what undertakes them. Since the currency is the currency in the virtual world, it is called virtual currency. Patent Document 1 discloses a game program for promoting the consumption of virtual currency.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In recent years, crypto assets have been attracting attention. Crypto assets are monetary assets that can be exchanged over the internet. Because the internet is considered a virtual world, they were formerly called virtual currencies. However, while the aforementioned virtual currencies include some that can only be used in online games, crypto assets can be used in places that are not limited to online games. Furthermore, because crypto assets utilize blockchain technology and cryptography, they are now called crypto assets to distinguish them from virtual currencies that are only valid in the virtual world.

[0006] Generally, crypto assets can be obtained and exchanged for cash from businesses called "exchanges" or "trading platforms" (crypto asset exchange operators). While crypto assets are also used as a means of payment in commercial transactions, trading is primarily for investment purposes. This invention was made in view of these circumstances. Its purpose is to provide a lottery method, a lottery program, and a lottery device for consuming crypto assets. [Means for solving the problem]

[0007] The lottery method disclosed herein involves a computer receiving a lottery request including a user ID, updating the number of tickets held that can be purchased with on-chain cryptocurrency tokens and associated with the received user ID, conducting a lottery, and transmitting the lottery results. A lottery method for executing a process, wherein the prize granted when the lottery result is a winner includes the right to use an application program for managing the crypto asset. . [Effects of the Invention]

[0008] In one aspect of this application, a lottery method, a lottery program, and a lottery device for consuming crypto assets can be provided. [Brief explanation of the drawing]

[0009] [Figure 1] This is an explanatory diagram showing an example configuration of a tokenback system. [Figure 2] Block diagram showing an example of a server hardware configuration. [Figure 3] This is a block diagram showing an example of a terminal's hardware configuration. [Figure 4] This is an explanatory diagram showing an example of a user database. [Figure 5] This is an explanatory diagram showing an example of a merchant database. [Figure 6] This is an explanatory diagram showing an example of a purchase history database. [Figure 7] This is an explanatory diagram showing an example of a grant history database. [Figure 8] This is an explanatory diagram illustrating an example of a restricted database. [Figure 9] This is an explanatory diagram showing an example of a rewards database. [Figure 10] This is an explanatory diagram showing an example of a database of winning results. [Figure 11] This flowchart shows an example of the procedure for executing the lottery. [Figure 12] This flowchart shows an example of the procedure for receiving rewards. [Modes for carrying out the invention]

[0010] The following embodiments will be described with reference to the drawings. (Embodiment 1) Figure 1 is an explanatory diagram showing an example configuration of a token back system. In this embodiment, the token back system 100 grants tokens to users who purchase goods or services (hereinafter referred to as "goods, etc.") with legal tender at a designated merchant. These tokens can also be obtained by exchanging legal tender. The token back system 100 provides users with a lottery game in which they can spend their tokens.

[0011] The token back system 100 includes a lottery device 1, terminals 2, 2, 2..., an exchange server 3, an EC (Electronic Commerce) server 4, and an issuance server 5. Each device is connected to the others via a network N such as the Internet, enabling them to communicate with each other.

[0012] The lottery device 1 can perform various information processes and information transmission and reception, and is composed of, for example, a server computer, a personal computer, etc. In the present embodiment, the lottery device 1 is composed of a server computer, and hereinafter, for simplicity, it is read as server 1. Server 1 is a server computer of an administrator who manages the token-back system 100. Server 1 provides a lottery game to users and performs processing related to token-back, which is a basic function of the token-back system 100. Server 1 performs cash-back (token-back) in tokens for users who purchase goods, etc. at affiliated stores of the token-back system 100. The token here is a token unique to this system (hereinafter referred to as "unique token").

[0013] In the token-back system 100, there are two types of tokens. The two types of tokens are off-chain tokens and on-chain tokens. Off-chain tokens are only valid within the token-back system 100. The quantity of off-chain tokens held by users is stored in the database managed by this system. Off-chain tokens are not in a state where transaction histories are recorded in the blockchain system (hereinafter referred to as "blockchain"). When a user transfers an off-chain token to another person, etc., it is necessary to move the token to the wallet once. At this time, server 1 receives the issuance of tokens from the exchange and sends them to the user's wallet. The said token is an on-chain token in which transaction histories are recorded in the blockchain. On-chain tokens are cryptocurrency assets (cryptocurrencies or virtual currencies) in which transaction histories are recorded in the blockchain. Cryptocurrency assets can be obtained and redeemed from business operators (cryptocurrency exchange operators) called "exchanges" or "trading houses". Also, cryptocurrency assets are property values that can be exchanged on the Internet.

[0014] It is said that a user "withdrawing" means storing an off-chain token as an on-chain token in a wallet. An off-chain token exists based on an agreement between the operator of the token back system 100 and the user, and when the user withdraws it to the wallet, it becomes an on-chain token, that is, a normal cryptocurrency. The on-chain token given by server 1 does not have to be a unique token. For example, the on-chain token may be an existing cryptocurrency such as Bitcoin (registered trademark), Ethereum (registered trademark), Ripple, NEM, etc. In this specification, withdrawal and exchange are collectively referred to as "transfer".

[0015] An off-chain token is a token for which it is promised that it can be exchanged at an equivalent value, for example, with an on-chain token. That is, one unit amount of an off-chain token is exchangeable with one unit amount of an on-chain token. However, it is not limited to this, and instead of an off-chain token, it may be a point of a point service. The exchange between points and on-chain tokens does not necessarily have to be one-to-one, and an exchange ratio may be determined and points may be exchanged for on-chain tokens at that exchange ratio. For example, if the exchange ratio is 10 to 1, 10 points can be exchanged for one unit amount of an on-chain token. Exchanging an off-chain token or points for an on-chain token is also called "converting" an off-chain token or points into an on-chain token.

[0016] The cryptocurrency required for the lottery game described later is assumed to be an on-chain unique token newly purchased by the user using legal tender, a credit card, etc. However, it is not limited to this, and it may be possible to participate in the lottery game using an off-chain unique token or points approved by the operator.

[0017] In this specification, supply and demand information is interpreted broadly and is not limited to information regarding the supply and demand of crypto assets. Market prices that fluctuate due to the supply and demand balance of crypto assets, the amount of crypto assets issued that is related to the market circulation volume, and the amount held by users and operators are also included in supply and demand information. Information that affects the asset value of crypto assets will be referred to as supply and demand information here.

[0018] Terminal 2 is a terminal device (user terminal) used by each user utilizing the tokenback system 100. Terminal 2 can consist of, for example, a smartphone, a tablet, or a personal computer. In this embodiment, we will explain assuming that Terminal 2 is a smartphone equipped with a touch panel. Terminal 2 has an application program (hereinafter referred to as "app") pre-installed to implement the functions related to the tokenback system 100.

[0019] The exchange server 3 is a server computer of a cryptocurrency exchange operator that provides a cryptocurrency exchange. The on-chain token according to this embodiment is listed on one or more exchanges, and users can buy and sell the on-chain token on the exchange.

[0020] EC Server 4 is the server computer of an e-commerce site (virtual store) operator that provides electronic commerce services. The tokenback system 100 includes not only businesses that sell goods in physical stores, but also e-commerce site operators. Each user can receive off-chain tokens when they purchase goods from a participating physical store or e-commerce site.

[0021] The issuance server 5 is a server computer that issues on-chain tokens related to the tokenback system 100 and controls the upper limit of on-chain token issuance. In this system, the issuance server 5 issues on-chain tokens and supplies them to the trading market (exchanges, etc.). The upper limit of on-chain token issuance is determined by the issuance server 5, and the issuance server 5 adjusts the issuance amount while referring to the supply and demand situation of on-chain tokens in the market.

[0022] Figure 2 is a block diagram showing an example of a server hardware configuration. Server 1 includes a control unit 11, a main memory unit 12, a communication unit 13, and an auxiliary storage unit 14. The control unit 11, the main memory unit 12, the communication unit 13, and the auxiliary storage unit 14 are connected by bus B.

[0023] The control unit 11 includes one or more arithmetic processing units such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit). The control unit 11 reads and executes the program P1 (program product) stored in the auxiliary storage unit 14, thereby performing various information processing, control processing, etc. related to the server 1. Furthermore, by executing the program P1, the control unit 11 realizes functional units such as a receiving unit, an updating unit, a lottery unit, and a transmission unit.

[0024] The main memory unit 12 is an SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), flash memory, etc. The main memory unit 12 temporarily stores the data necessary for the control unit 11 to perform calculation processing.

[0025] The communication unit 13 includes processing circuits and the like for performing communication-related processing. It transmits and receives information with terminal 2 and the like.

[0026] The auxiliary storage unit 14 is a large-capacity memory, SSD (Solid State Drive), hard disk, etc. The auxiliary storage unit 14 stores the program P1 and other data necessary for the control unit 11 to execute processing. The auxiliary storage unit 14 also stores the user DB 141, merchant DB 142, purchase history DB 143, grant history DB 144, restriction DB 145, benefits DB 146, and winning status DB 147. The auxiliary storage unit 14 may also be an external storage device connected to the server 1. The databases stored in the auxiliary storage unit 14 may also be stored in cloud storage.

[0027] Server 1 may be configured as a multicomputer consisting of multiple computers, a virtual machine virtually constructed by software, or a quantum computer. Furthermore, the functions of Server 1 may be implemented as a cloud service.

[0028] Furthermore, Server 1 may include a reading unit (not shown) for reading a portable storage medium 1m such as a CD (Compact Disk)-ROM or DVD (Digital Versatile Disc)-ROM, and may read and execute Program P1 from the portable storage medium 1m. Alternatively, Server 1 may read Program P1 from a semiconductor memory 1n. In addition to the above configuration, Server 1 may also include, for example, an input unit for receiving operation inputs, a display unit for displaying images, etc.

[0029] Figure 3 is a block diagram showing an example of the terminal's hardware configuration. Terminal 2 includes a control unit 21, a main memory unit 22, a communication unit 23, a display unit 24, an input unit 25, an imaging unit 26, and an auxiliary memory unit 27.

[0030] The control unit 21 includes one or more arithmetic processing units such as CPUs and MPUs. The control unit 21 reads and executes the program P2 (program product) stored in the auxiliary storage unit 27, thereby performing various information processing, control processing, etc. related to the terminal 2. The program P2 corresponds to the application described above.

[0031] The main memory unit 22 is an SRAM, DRAM, flash memory, etc. The main memory unit 22 temporarily stores the data necessary for the control unit 21 to perform calculation processing.

[0032] The communication unit 23 includes an antenna, processing circuitry, etc., for communication. The communication unit 23 transmits and receives information with the server 1, etc.

[0033] The display unit 24 includes a display panel such as a liquid crystal display or an organic EL (Electro-Luminescence) display. The display unit 24 displays an image provided by the control unit 21.

[0034] The input unit 25 is an input interface such as a touch panel or mechanical keys. The input unit 25 receives operation input from the user.

[0035] The imaging unit 26 is a camera equipped with an image sensor such as a CMOS (Complementary Metal Oxide Semiconductor) sensor. The imaging unit 26 performs imaging according to user input.

[0036] The auxiliary storage unit 27 is a large-capacity memory, SSD, hard disk, etc., and stores the program P2 and other data necessary for the control unit 21 to execute processing.

[0037] Terminal 2 may also be equipped with a reading unit (not shown) for reading the portable storage medium 2n, and may read and execute the program P2 from the portable storage medium 2n. Alternatively, terminal 2 may read the program P2 from the semiconductor memory 2m.

[0038] Figure 4 is an explanatory diagram showing an example of a user database. User DB 141 stores information about users. User DB 141 includes columns for User ID, Username, Holdings, Wallet, Rank, Ticket, Auxiliary Voucher, and Personal Information. The User ID column stores the user ID to identify each user. The Username column stores the user's name. The Holdings column stores the quantity of off-chain tokens held by the user. The Wallet column stores wallet information (e.g., public key of a hot wallet) where the on-chain tokens held by the user are stored. The Rank column stores the user's rank. The rank is determined by purchase history at participating merchants, token holdings, holding period, grant history, withdrawal history, etc. For example, the ranks from highest to lowest are Diamond, Platinum, Gold, Silver, and Bronze. The Ticket column stores the number of tickets required to participate in the lottery that the user holds. The Auxiliary Voucher column stores the number of pass auxiliary vouchers obtained as benefits that the user holds. Pass auxiliary vouchers will be discussed later. The personal information column stores the user's personal information (gender, age, nationality, etc.).

[0039] Figure 5 is an explanatory diagram showing an example of a merchant database. Merchant database 142 stores information about merchants. Merchant database 142 includes a merchant ID column, a merchant name column, a merchant information column, and a commission rate column. The merchant ID column stores the merchant ID to identify each merchant. The merchant name column stores the name of the merchant. The merchant information column stores information about the merchant other than the name. The commission rate column stores the percentage of commission collected from merchants.

[0040] Figure 6 is an explanatory diagram showing an example of a purchase history database. The purchase history database 143 stores the history of a user's purchases of goods and services from a merchant. The purchase history database 143 includes columns for purchase ID, purchaser, merchant, date, purchased item, and purchase amount. The purchase ID column stores the purchase ID assigned to each purchase history when a user purchases goods from a merchant. The purchaser column stores the user ID of the user who made the purchase. The merchant column stores the merchant ID of the merchant from which the user purchased the goods. The date column stores the date on which the user purchased the goods. The purchased item column stores the name of the goods purchased by the user. The purchase amount column stores the purchase price of the goods.

[0041] Figure 7 is an explanatory diagram showing an example of a grant history database. Grant history DB 144 stores the history of granting off-chain tokens to users (grant history). Grant history DB 144 includes a date and time column and a token return column. The date and time column stores the date and time when the token was granted to the user. The token return column stores information about the token return to the user. The token return column further includes a user column, a grant amount column, and a purchase ID column. The user column stores the user ID of the user who was the recipient of the token. The grant amount column stores the quantity of tokens granted to the user. The purchase ID column stores the purchase ID that identifies the purchase history of the product, etc., that triggered the token grant. As mentioned above, points may be granted to users instead of off-chain tokens.

[0042] Figure 8 is an explanatory diagram showing an example of a restriction database. Restriction DB 145 stores the application restriction status for each user. Restriction DB 145 includes a user column, a function 1 column, a function 2 column, and a function 3 column. The user column stores the user ID. The function 1 column stores whether or not function 1 is restricted. The function 2 column stores whether or not function 2 is restricted. The function 3 column stores whether or not function 3 is restricted. The function n column specifies the number of functions in the application.

[0043] Figure 9 is an explanatory diagram showing an example of a reward database. Reward database 146 stores information about rewards awarded when a winner is selected in a lottery game. Reward database 146 includes a reward ID column and a reward column. The reward ID column stores a reward ID that uniquely identifies the reward. The reward column stores the content of the reward. Rewards include, for example, cash rewards such as a 1 million yen prize, cryptocurrency rewards such as 0.1 Bitcoin or 10,000 Tether, and highly scarce NFTs (non-fungible tokens). Cryptocurrency rewards may include assets other than Bitcoin and Tether. Furthermore, there is the right to remove the functional restrictions of the application for using the tokenback system 100 (usage rights). In addition, one pass voucher is included as a reward. Ten pass vouchers can be used as a fast pass ticket. The fast pass ticket allows for a relaxation of the limit on exchanging off-chain tokens for on-chain tokens. The predetermined amount is, for example, twice the number of tokens the user pays to play the lottery game. Regarding cash payments, since immediate payment after the lottery is difficult, users will be granted the right to receive the payment (a monetary claim). The settings in Rewards DB146 allow the lottery game to be configured such that the probability of winning increases with each subsequent attempt, eventually resulting in a gacha-like system, or it can be configured as a probability-based game where the probability of winning does not change even after multiple attempts. It is also acceptable for some participants to receive no rewards as a result of the lottery game.

[0044] Let me add some details about the app's functions. The functions of the Tokenback System 100 include shopping, withdrawal, and cryptocurrency purchase. The shopping function allows users to be redirected to a shopping site and receive tokenback when they make a purchase there. The withdrawal function allows users to withdraw cryptocurrency (off-chain tokens) within the app to a wallet on the blockchain or convert them to on-chain tokens. The cryptocurrency purchase function allows users to purchase cryptocurrency with fiat currency and store it within the app. If the shopping function is restricted, users can still make purchases on the shopping site, but they will not receive tokenback. If the withdrawal function is restricted, it will be impossible to convert off-chain tokens to on-chain tokens, or the amount that can be converted will be limited. In the cryptocurrency purchase function, a minimum purchase quantity will be set, and users will not be able to purchase more than the minimum quantity. The above-mentioned right to remove the restriction is a privilege that allows these restrictions to be removed for a specified period.

[0045] Figure 10 is an explanatory diagram showing an example of a winning status database. The winning status database 147 stores the winning status for each prize. The winning status database 147 includes a prize ID column, a maximum number of winners column, a cumulative number of winners column, and a winning number column. The prize ID column stores the prize ID. The maximum number of winners column stores the maximum number of users who will be awarded the prize by winning. The cumulative number of winners column stores the number of users who have won. The winning number column stores the winning number for the prize. In the example shown in Figure 10, for prizes with prize IDs 40001 and 40002, the maximum number of users who can win is 1, and there have been no winners yet. The winning number is a 128-bit number. In Figure 10, the 128-bit value is represented as a 32-digit hexadecimal number. For prize with prize ID 40003, the maximum number of users who can win is 100, and there have already been 10 winners. The lower 16 bits of the winning number are 4579. The Winning Status DB147 may store the user ID, winning ID, and expiration date of the winning user for each prize.

[0046] Figure 11 is a flowchart illustrating an example of the lottery execution process. The lottery execution process is a process that performs a lottery game once, according to the user's request. When the user instructs to execute the lottery game from the app's menu, the lottery execution process begins. Before the lottery, the user purchases the necessary tickets using on-chain tokens. The control unit 21 of terminal 2 sends a request to execute the lottery game to server 1 (step S1). This request includes the user ID. The control unit 11 of server 1 receives the request (step S2). The control unit 11 refers to the value of the ticket column in user DB 141 and determines whether the user possesses the tickets necessary to participate in the lottery game (step S3). The number of tickets required to participate in the lottery game is predetermined and is assumed to have been notified to the user. If the control unit 11 determines that the user has the tickets necessary to participate in the lottery game (YES in step S3), it updates the number of tickets the user possesses (step S4). The control unit 11 updates the value of the ticket column in user DB 141 to a value that is less than the number of tickets required to participate in the lottery game. The control unit 11 generates a random number (step S5). The control unit 11 generates, for example, a 128-bit random number. The control unit 11 determines whether or not the user has won (step S6). The control unit 11 determines whether the generated random number matches the value in the last column of the winning number in the winning status DB 147, or whether some of the digits match, etc. If the control unit 11 determines that there is a match, it compares the values ​​in the maximum number of winners column and the cumulative number of winners column in the winning status DB 147, and determines that the user has won if the cumulative number of winners has not reached the maximum number of winners. If the control unit 11 determines that the user has not won (NO in step S6), it moves the process to step S8. If the control unit 11 determines that the user has won (YES in step S6), it updates the value in the cumulative number of winners column in the winning status DB 147 (step S7). The control unit 11 generates a notification of winning or losing (step S8). The control unit 11 sends a notification (lottery result) to the terminal 2 (step S9). The control unit 21 of the terminal 2 receives the notification and displays it on the display unit 24 (step S10). The control unit 21 terminates processing.If the control unit 11 determines that the user does not have a ticket necessary to participate in the lottery game (NO in step S3), it sends a notification to terminal 2 indicating that the lottery game cannot be played (step S11). The control unit 21 of terminal 2 receives the notification (step S12). The control unit 21 displays the notification (step S13) and terminates the process. After receiving the notification, the control unit 21 may display a message prompting the user to purchase a ticket and redirect them to a website where they can purchase a ticket using on-chain tokens. After the user purchases a ticket, the control unit 21 executes again from step S1. Other crypto assets such as Bitcoin and Ethereum may be exchanged for on-chain tokens in the tokenback system 100 before the user can purchase a ticket. The above explanation assumes that a ticket is purchased before participating in the lottery game, but this is not the only option. On-chain tokens may be collected from users who do not have a ticket to allow them to participate in the lottery game. In this case, the amount of on-chain tokens required may be greater than when a ticket is purchased. The aforementioned tickets may, for example, allow one entry into a lottery game, and sets of 10 tickets may be sold in exchange for on-chain tokens equivalent to 9 entries, thus selling what are known as multi-use tickets. The aforementioned tickets may also have an expiration date.

[0047] Figure 12 is a flowchart illustrating an example of the procedure for receiving a prize. Receiving a prize is a necessary process when a prize other than a pass voucher is won. The control unit 21 of terminal 2 sends a receipt request to server 1 (step S31). The receipt request includes the user ID. The control unit 11 of server 1 receives the receipt request (step S32). The control unit 11 sends an input screen to terminal 2 (step S33). The control unit 21 of terminal 2 receives and displays the input screen (step S34). The user enters the necessary information. The necessary information includes the winning ID and contact email address. After entering the information, the user instructs to send. The control unit 21 sends the entered information to server 1 (step S35). The control unit 11 of server 1 receives the information (step S36). The control unit 11 determines whether the request is valid or not (step S37). For example, the winner's user ID is stored in the winning status DB 147. The control unit 11 determines that the request is valid if the user ID of the user making the request is stored in the winning status DB 147 and has not expired, and that it is invalid if it is not stored. If the control unit 11 determines that the request is valid (YES in step S37), it stores the received information in the auxiliary storage unit 14 (step S38). The control unit 11 sends a notification to terminal 2 that the request has been received (step S39). The control unit 21 of terminal 2 receives the notification (step S40). The control unit 21 displays the notification (step S41) and terminates the process. Based on the stored information, the control unit 11 separately performs the process of granting the benefit to the user. If the control unit 11 determines that the request is invalid (NO in step S37), it sends a rejection notification to terminal 2 that the benefit cannot be received (step S42). The control unit 21 of terminal 2 receives the rejection notification (step S43). The control unit 21 displays the rejection notification (step S41) and terminates the process.

[0048] In this embodiment, it becomes possible to provide a lottery game using cryptocurrency. Furthermore, by devising the prizes for winning the lottery, it becomes possible to provide an interesting lottery game.

[0049] In the above description, the lottery game is premised on providing one type of game, but it is not limited to this. Various lottery games may be provided. For example, a game that requires two tickets to participate but has a higher winning probability than a game that requires only one ticket may be provided. Also, a game that has the same winning probability as the above-described lottery game but requires five tickets and offers a more valuable prize may be provided.

[0050] The technical features (constituent elements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed. The embodiments disclosed this time should be considered as illustrative in all respects and not restrictive. The scope of the present invention is shown not by the above description but by the claims, and all modifications within the meaning and scope equivalent to the claims are intended to be included. Furthermore, the claims use a format (multi-claim format) that describes claims that cite two or more other claims, but it is not limited to this. A format that describes a multi-claim (multi-multi-claim) that cites at least one multi-claim may also be used.

Explanation of Signs

[0051] 100: Token Back System 1: Server, Lottery Device 11: Control Unit 12: Main Memory Unit 13: Communication Unit 14: Auxiliary Storage Unit 141: User DB 142: Franchisee DB 142: User DB 143: Purchase History DB 144: Grant History DB 145: Restriction DB 146: Privilege DB 147: Winning Status DB P1: Program 1m: Portable Storage Medium 1n: Semiconductor memory 2: Terminal 21: Control Unit 22: Main memory 23: Communications Department 24: Display section 25: Input section 26: Imaging Department 27: Auxiliary storage section P2: Program 2m: Semiconductor memory 2n: Portable storage medium 3: Exchange Server 4: EC Server 5: Issuing Server B: Bus N: Network

Claims

1. Computers Upon receiving a lottery request that includes a user ID, The number of tickets held, which can be purchased with on-chain cryptocurrency tokens, is updated and associated with the received user ID. A lottery will be held. Sending the lottery results A lottery method for executing a process, The benefits granted if the lottery result is successful include the right to use the application program for managing the aforementioned crypto assets. The method of drawing lots.

2. The benefits granted if the lottery result is a win include monetary claims. The lottery method according to claim 1.

3. The prize awarded if the lottery result is a winner includes a predetermined quantity of Bitcoin, Ethereum, or Tether, or the provision of NFTs. The lottery method according to claim 1.

4. The aforementioned usage rights include relaxing the quantitative restrictions on converting off-chain tokens of the aforementioned crypto asset into on-chain tokens. The lottery method according to claim 1.

5. to the computer Upon receiving a lottery request that includes a user ID, The number of tickets held, which can be purchased with on-chain cryptocurrency tokens, is updated and associated with the received user ID. A lottery will be held. Sending the lottery results A lottery program that executes a process, The prize awarded if the lottery result is a win includes the right to use the application program for managing the aforementioned crypto assets. Lottery program.

6. A receiving unit that receives a lottery request including a user ID, An update unit that associates the received user ID with the number of tickets held that can be purchased with on-chain cryptocurrency tokens, The lottery department that conducts the drawing, A transmission unit that sends the lottery results and A lottery device equipped with, The prize awarded if the lottery result is a win includes the right to use the application program for managing the aforementioned crypto assets. A lottery device.

Images