Non-storage type wallet management system, non-storage type wallet management method and program

Abstract

To provide a better non-storage type wallet management system, a method and a program which manage a non-storage type wallet.SOLUTION: A system: executes login processing to a user account of an information processing device by a user terminal; performs management processing for managing a transaction by a wallet account through the user account, on the basis of transaction information about the transaction performed by the wallet account; executes transaction processing based on transaction operation of a user associated with predetermined verification operation, when the transaction operation is performed; during the processing, after performing processing which confirms a predetermined user himself / herself, suppresses that a share more than a threshold value is held in a management account, by transmitting a third share in a mode in which at least the management account cannot be read, with respect to the user; allows only the user to perform authentication by electronic signature with respect to the transaction; and maintains non-storage property of an electronic wallet.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a non-custodial wallet management system, a non-custodial wallet management method, and a program. [Background technology]

[0002] Patent document 1 discloses a system and method for improved electronic transfer of resources via a blockchain.

[0003] The method described in Patent Document 1 is a computer-implemented method for performing a transfer of at least one resource from a user's non-custodial wallet to a recipient over a network, comprising the steps of receiving a first share of a private key from a first network entity by a second network entity having access to a second share of the private key, generating a private key using the first share and the second share, creating a blockchain transaction signed with the private key at the second network entity for performing the transfer from the user's wallet to the recipient based on transfer-related data, and submitting the transaction to a blockchain network. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Special Publication No. 2022-551915 Summary of the Invention [Problem to be solved by the invention]

[0005] However, there is still room for improvement in the technology for managing non-custodial wallets described in Patent Document 1 above. [Means for solving the problem]

[0006] According to one aspect of the present invention, a non-custodial wallet management system is provided. The non-custodial wallet management system includes at least one processor and at least one storage unit. At least one of the storage units stores account information related to a user account. The user account is configured to be linked to a wallet account held by the user. The wallet account generates transactions based on a plurality of shares including a first share generated based on at least a part of the account information and a second share managed by a user of the user account and inaccessible to a management account different from the user account of the user account. The wallet account is configured to hold tokens using distributed ledger technology and execute token transactions based on transactions. In a first receiving step, information on a first transaction operation, which is an operation related to a token transaction that can be executed by the user account, is received. The first transaction operation is associated with a predetermined verification operation. The verification operation can verify a risk corresponding to the first transaction operation and includes an operation executed by a party other than the user account. In a specifying step, a second transaction operation, which is a transaction operation permitted for the user account, is specified from among the first transaction operations based on a result of execution of the verification operation.

[0007] Such a configuration can provide a better technique for managing non-custodial wallets. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a configuration diagram showing a non-custodial wallet management system 1. [Diagram 2] FIG. 1 is an activity diagram showing an overview of this information processing. [Diagram 3] FIG. 11 is an activity diagram showing an example of a login process. [Figure 4] FIG. 13 is an activity diagram illustrating an example of a wallet generation process. [Diagram 5] FIG. 11 is an activity diagram showing an example of a management process. [Figure 6] FIG. 2 is an activity diagram showing an example of a transaction process. [Figure 7] FIG. 11 is an activity diagram showing an example of a restoration process. [Figure 8] FIG. 4 is a diagram showing an example of a login screen 5. [Figure 9] FIG. 2 is a diagram showing an example of a registration screen 6. [Figure 10] FIG. 13 is a diagram showing an example of a backup screen 6a. [Figure 11] FIG. 2 is a diagram showing an example of a management screen 7. [Figure 12] FIG. 11 is an activity diagram showing an example of a game process including the information process. [Figure 13] FIG. 13 is a diagram showing an example of a game start screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described with reference to the drawings. Various characteristic features shown in the following embodiments can be combined with each other.

[0010] Incidentally, the program for realizing the software appearing in this embodiment may be provided as a non-transitory computer-readable recording medium, or may be provided so as to be downloadable from an external server, or may be provided so that the program is started on an external computer and its functions are realized on a client terminal (so-called cloud computing).

[0011] In addition, in this embodiment, the term "unit" may include, for example, a combination of hardware resources implemented by a circuit in the broad sense and software information processing that can be specifically realized by these hardware resources. In addition, in this embodiment, various information is handled, and this information is represented, for example, by physical values ​​of signal values ​​representing voltage and current, high and low signal values ​​as a binary bit collection consisting of 0 or 1, or quantum superposition (so-called quantum bits), and communication and calculation can be performed on the circuit in the broad sense.

[0012] In addition, a circuit in the broad sense is a circuit realized by at least appropriately combining a circuit, circuitry, a processor, a memory, etc. In other words, it includes an application specific integrated circuit (ASIC), a programmable logic device (e.g., a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), etc.

[0013] 1. Hardware Configuration This section describes the hardware configuration.

[0014] <Non-custodial wallet management system 1> FIG. 1 is a configuration diagram showing a non-custodial wallet management system 1. The non-custodial wallet management system 1 includes an information processing device 2 and a user terminal 3. The information processing device 2, the user terminal 3, and the distributed ledger system 4 are configured to be able to communicate with each other via an electric communication line. In one embodiment, the non-custodial wallet management system 1 is composed of one or more devices or components. For example, if the non-custodial wallet management system 1 is composed of only the information processing device 2, the non-custodial wallet management system 1 can be the information processing device 2. In this case, the information processing device 2 can be a non-custodial wallet management device for managing a non-custodial wallet. These components will be described below.

[0015] <Information processing device 2> The information processing device 2 includes a communication unit 21, a storage unit 22, and a processor 23, and these components are electrically connected to each other via a communication bus 20 inside the information processing device 2.

[0016] The communication unit 21 is preferably a wired communication means such as USB, IEEE1394, Thunderbolt (registered trademark), wired LAN network communication, etc., but may also include wireless LAN network communication, mobile communication such as 3G / LTE / 5G, BLUETOOTH (registered trademark) communication, etc. as necessary. In other words, it is more preferable to implement it as a collection of multiple communication means. In other words, the information processing device 2 may communicate various information from the outside via the communication unit 21 and the network.

[0017] The storage unit 22 stores various information defined by the above description. This can be implemented, for example, as a storage device such as a solid state drive (SSD) that stores various programs and the like related to the information processing device 2 executed by the processor 23, or as a memory such as a random access memory (RAM) that stores temporarily required information (arguments, arrays, etc.) related to the program calculations. The storage unit 22 stores various programs, variables, etc. related to the information processing device 2 executed by the processor 23.

[0018] For example, the storage unit 22 stores account information. The account information includes information about a user account. A user account is an account associated with a user who can access the information processing device 2. In this embodiment, the account information may further include information about a management account. A management account is an account that can be accessed in a state in which the user has administrator authority in the information processing device 2. The management account is associated with, for example, an administrator of the information processing device 2, and can view and manage information about user accounts. Note that the account information does not need to be stored as one database in the storage unit 22, and may be stored in the storage unit 22 such that, for example, the account information of a user account and the account information of a management account are stored in separate databases.

[0019] The processor 23 processes and controls the overall operations related to the information processing device 2. The processor 23 is, for example, a central processing unit (CPU) not shown. The processor 23 realizes various functions related to the information processing device 2 by reading out a predetermined program stored in the storage unit 22. That is, information processing by software stored in the storage unit 22 can be specifically realized by the processor 23, which is an example of hardware, and executed as each functional unit included in the processor 23. These will be described in more detail in the next section. The processor 23 is not limited to being single, and may be implemented to have multiple processors 23 for each function, or a combination thereof.

[0020] The processor 23 is configured to be able to acquire information from the user terminal 3 or other devices as an acquisition unit, for example. The processor 23 is configured to be able to acquire various pieces of information by reading out various pieces of information stored in a storage area that is at least a part of the memory unit 22, and writing the read out information in a working area that is at least a part of the memory unit 22. The storage area is, for example, an area of ​​the memory unit 22 that is implemented as a storage device such as an SSD. The working area is, for example, an area that is implemented as a memory such as a RAM. Note that acquisition by the processor 23 includes acquiring output results of each functional unit included in the processor 23.

[0021] The processor 23 is configured to be able to display various information as, for example, a display processing unit. The information can be presented to the user via the display unit 34 of the user terminal 3 or another device. In such a case, for example, the processor 23 controls the display unit 34 of the user terminal 3 to display visual information such as a screen, an image including a still image or a video, an icon, a message, etc. The processor 23 may generate only rendering information for displaying the visual information on the user terminal 3. The processor 23 may present the output information to the user without going through the user terminal 3 or another device user.

[0022] <User terminal 3> The user terminal 3 includes a communication unit 31, a storage unit 32, a processor 33, a display unit 34, and an input unit 35, and these components are electrically connected via a communication bus 30 inside the user terminal 3. Descriptions of the communication unit 31, the storage unit 32, and the processor 33 are omitted because they are similar to the descriptions of each unit in the information processing device 2. In other words, the non-custodial wallet management system 1 includes at least one processor 23, 33 and at least one storage unit 22, 32. At least a part of the account information may be stored in the storage unit 32.

[0023] The display unit 34 may be included in the housing of the user terminal 3 or may be externally attached. The display unit 34 displays a screen of a graphical user interface (GUI) that can be operated by the user. This may be implemented by using, for example, a display device such as a CRT display, a liquid crystal display, an organic EL display, a plasma display, or the like, depending on the type of the user terminal 3.

[0024] The input unit 35 is configured to be able to accept input from a user. The input unit 35 may be included in the housing of the user terminal 3, or may be externally attached. For example, the input unit 35 may be implemented as a touch panel integrated with the display unit 34. If it is a touch panel, the user can input a tap operation, a swipe operation, or the like. Of course, instead of a touch panel, a switch button, a mouse, a QWERTY keyboard, a voice recognition device, a gesture detection device, a gaze detection device, a biosignal detection device, an imaging device, or the like may be adopted. That is, the input unit 35 accepts an operation input made by a user. In response, the input unit 35 transfers a signal corresponding to the operation input to the processor 33 via the communication bus 30. The processor 33 can execute a predetermined control or calculation as necessary.

[0025] <Distributed Ledger System 4> The distributed ledger system 4 is configured to manage a distributed ledger. As an example, the distributed ledger system 4 manages transaction history regarding transfer of crypto assets or tokens (which may include NFTs (Non-Fungible Tokens)). The distributed ledger is, for example, a blockchain. A smart contract for realizing each function of the payment system is deployed in the distributed ledger system 4. The smart contract is executed in response to a request from the information processing device 2 or the user terminal 3.

[0026] The distributed ledger system 4 includes a plurality of node computers 41. The plurality of node computers 41 are connected to each other via a network (which may include the network of FIG. 1). In this embodiment, the network may include a public network, a private network, a dedicated line, a Virtual Private Network (VPN), or a combination thereof. The node computers 41 are connected to the network, for example, by wire or wirelessly. The node computers 41 are configured to communicate with each other in a peer-to-peer manner. The distributed ledger system 4 is configured to allow the same database to be managed by a plurality of node computers on a distributed network without a central administrator by using distributed ledger technology.

[0027] 2. Information processing In this section, the information processing executed in the non-custodial wallet management system 1 described above will be described with reference to Figs. 2 to 7. The information processing may include any exception processing not shown. Exception processing includes interruption of the information processing and omission of each process. Selection or input performed in the information processing may be based on a user operation or may be performed automatically without relying on a user operation.

[0028] 2.1. Overview of information processing FIG. 2 is an activity diagram showing an overview of this information processing.

[0029] [Activity A100] First, in activity A100, the non-custodial wallet management system 1 executes a login process, which is a process related to logging in to a user account of the information processing device 2 by the user terminal 3. This allows the user to log in to his or her own user account.

[0030] <user account> The user account is an account managed by the information processing device 2, and is configured to be linked to a wallet account held by the user. The wallet account is configured to be capable of managing tokens granted to the user's non-custodial wallet by the blockchain. Note that managing tokens is not limited to managing the token value itself, and may include data linked to the token. In this embodiment, a non-fungible token (NFT) is used as the token. Data linked to an NFT may include any data, particularly data requiring proof of uniqueness, such as crypto assets, NFT art, and data indicating real rights held by a user (e.g., intangible assets such as intellectual property rights).

[0031] <Wallet account> The wallet account is configured to hold tokens using distributed ledger technology and to execute token transactions based on transactions, and is specified by an address on a platform (e.g., a blockchain that is the basis of transactions, specifically Ethereum, etc.) on which NFTs and the like can be traded. The wallet account may function as an externally owned account (EOA) that can generate transactions. A transaction may include information necessary to identify the transaction content related to data, such as the sender's address ("From"), the receiver's address ("To"), the data to be sent ("Date"), and the gas fee ("Fee"). In other words, information related to the transaction operation may include information related to the token's trading partner. An authenticated transaction is stored as one of the records of the transaction by propagating the distributed ledger system 4, and a block and a hash value corresponding to the block are generated by collecting multiple transactions. Hereinafter, for the convenience of explanation, the data to be sent is mainly crypto assets.

[0032] The wallet account is associated with, for example, a private key. A transaction generated from the wallet account may be authenticated by a digital signature using the private key and a public key that constitutes a pair of the private key. Such an authentication process may be executed, for example, by a smart contract on the Web 3 implemented in the distributed ledger system 4. The private key is configured to be distributable into, for example, multiple shares. A transaction generated from the wallet account may be digitally signed using a part of the multiple shares, for example, a number of shares equal to or greater than a predetermined threshold value. More specifically, such shares may be generated using any technique related to secret sharing, such as multisig, Shamir's secret sharing, or multi-party computation (MPC). For example, the multiple shares may include a first share and a second share. The first share is configured to be generated based on at least a part of the account information of the user account (for example, a character string included in the user account name). For example, the first share is generated by linking the user account and the wallet account. Note that the management account is configured to be able to access the account information but not to access the first share itself. The second share is managed by the user, and the management account is configured to be inaccessible. Note that being configured to be inaccessible is not limited to being configured to be inaccessible by physically or electrically blocking the information communication path, but may include being configured to be inaccessible without using illegal means such as hacking, or being configured to be inaccessible after the fact by deleting the private key. When a third share is further generated, the wallet account may allow the generation of a transaction using at least two of the multiple shares including the first share, the second share, and the third share. An electronic wallet implemented using a wallet account managed by a private key held by a user is called a non-custodial wallet, and is a wallet in which the user himself can authenticate a transaction using the private key, and a third party other than the user, including the management account, cannot authenticate a transaction using the private key.Such electronic wallets may include, for example, those that are not limited to those configured to prevent a third party from accessing all private key shares, but may also include those that are configured to prevent a third party from accessing a threshold number of private key shares.

[0033] [Activity A200] If login to the user account is permitted by the login process, the process proceeds to activity A200, and the non-custodial wallet management system 1 performs management processing. The management processing is processing for managing transactions by the wallet account via the user account based on transaction information related to transactions being performed by the wallet account. Through the management processing, the non-custodial wallet management system 1 presents the user with information about the tokens linked to the wallet account (e.g., cryptocurrency balance) and information about potential token trading partners, and can perform transaction operations for trading the tokens, such as sending the tokens (e.g., remittance of cryptocurrency).

[0034] [Activity A300] When a transaction operation is performed in activity A300, the process proceeds to activity A300, and the non-custodial wallet management system 1 executes a transaction process based on the user's transaction operation. At this time, at least a part of the transaction operation (corresponding to the first transaction operation) is associated with a predetermined verification operation.

[0035] The verification operation is a process capable of verifying the risk of a certain transaction operation to a certain degree, and may include a process executed by a party other than the user (for example, an administration account or a contract account on Web3). For example, the verification operation includes verifying the reliability of a transaction partner based on information about the transaction partner designated by the administration account. The information about the transaction partner is a blacklist or a whitelist, and is represented, for example, by a list of remittance destination addresses (for example, a 66-digit character string represented by "0x..."). With this configuration, for example, when trading tokens using a non-custodial wallet, it is possible to prevent transactions from being generated for unreliable transaction partners that are the subject of suspicious transactions. In addition, the transaction operation associated with the verification operation (hereinafter, for convenience of explanation, it may be referred to as a first transaction operation) may include a transaction operation in which the token transaction amount is higher than a predetermined reference value. The reference value may be set based on at least the user's past transaction history. The reference value may be set based on, for example, the difference from the average value of the cryptocurrency that the user has previously remitted, or the maximum value of the cryptocurrency that the user has previously remitted. According to this configuration, when a user remits an excessively large transaction amount compared to the past transaction history in a non-custodial wallet, it is possible to suppress the generation of an inadvertent transaction. The reference value may be set based on the value of a token currently associated with the wallet account. According to this configuration, it is possible to reduce the possibility that an excessively large transaction not commensurate with the user's current assets occurs. The reference value may be set by the user, such as an available amount set by the user himself. The reference value may be set based on an accumulated value of transaction amounts in a predetermined period, such as one week, one month, or one year. In short, the verification operation may further include a user verification operation including a user condition that can be set by the user of the user account. According to this configuration, despite being a non-custodial wallet, the user's transaction operation can be pseudo-restricted by anyone other than the user, specifically, by anyone other than the user and the administrator, and therefore the transaction security of the non-custodial wallet can be further improved.Therefore, for example, even a user who is unfamiliar with Web3 technology can reduce anxiety about transactions using Web3 technology.

[0036] The information processing device 2 executes a verification operation according to the verification operation associated with the transaction operation desired by the user, and determines whether or not to permit the generation of a transaction based on the transaction operation based on the result. After that, the process returns to activity A200 again, where token management continues, and when a predetermined end operation is performed, the non-custodial wallet management system 1 ends this information processing.

[0037] [Activity A400, Activity A401] In addition, when the non-custodial wallet management system 1 receives a restoration operation by a user (activity A400) while this information processing is being performed, for example, while processing of activity A200 or activity A300 is being performed, it performs restoration processing of activity A401. As a result, the non-custodial wallet management system 1 performs a process of verifying the identity of a predetermined user, and then transmits the third share to the user in a manner that at least the management account cannot view it. This prevents the management account from holding a share equal to or greater than a threshold, and maintains the non-custodial nature (non-custodial nature) of the electronic wallet, in which only the user can authenticate a transaction by electronic signature. In this embodiment, the management account is configured to hold the user's account information but not the share held by the user itself. This ensures the non-custodial nature of the user's wallet account with respect to the management account.

[0038] 2.2. Details of data processing In this section, an example of each process included in the above-mentioned information processing will be described in detail.

[0039] 2.2.1. Login process FIG. 3 is an activity diagram illustrating an example of a login process.

[0040] [Activity A1] 3, first, in activity A1, the processor 23 of the information processing device 2 (hereinafter simply referred to as the processor 23) requests input of login information from the user terminal 3. The login information is information necessary for a user to log in to a user account, and includes, for example, a user ID and a password.

[0041] [Activity A2] Next, in activity A2, the processor 33 of the user terminal 3 (hereinafter simply referred to as the processor 33) responds to the request by displaying the login screen 5 (see FIG. 8) on the display unit 34. The login screen 5 is configured to be capable of accepting an input operation indicating the input of login information by the user and a registration operation for generating a new user account.

[0042] [Activity A3] When an input operation is performed, the process proceeds to activity A3, and the processor 33 transmits the login information input by the user to the information processing device 2.

[0043] [Activity A4] Next, in activity A4, the processor 23 checks the transmitted login information against information related to the user account stored in the storage unit 22. In response to this, the processor 23 determines whether or not to permit login to the user account.

[0044] [Activity A5] If the result of the comparison in activity A4 is that the login by the user terminal 3 is successful, the process proceeds to activity A5, where the processor 23 permits login to the user account from the user terminal 3, and proceeds to the process of activity A6, which will be described later. On the other hand, if the login is unsuccessful, the process returns to activity A1, where the processor 23 requests the input of login information again.

[0045] [Activity A6] On the other hand, when a registration operation is performed in activity A2, the process proceeds to activity A6, and processor 33 causes registration screen 6 (see FIG. 9) to be displayed on display unit 34. Registration screen 6 is configured to allow input of information required to generate a new user account, such as a user ID, a password, contact information for identifying the user (e.g., a phone number, an email address, etc.), a password required when restoring a private key, etc. Information related to the new user account is stored in storage unit 22, etc. Information related to the user account includes the login information described above.

[0046] In this embodiment, the processor 23 further displays a backup screen 6a (see FIG. 10) on the display unit 34. The backup screen 6a is a UI for generating restoration data. The restoration data is generated based on a user's command to create a backup. The processor 23 requests linkage with an account (e.g., an account provided by a business other than the business that manages the managed account) that is different from the user account managed in the non-custodial wallet management system 1 among accounts accessible by the user. Thereafter, the processor 23 transmits the restoration data on a cloud storage associated with the linked account. As a result, the restoration data is configured to be inaccessible by the managed account of the non-custodial wallet management system 1. Such an operation for creating the restoration data is an example of the above-mentioned restoration operation. Note that the creation and storage of the restoration data based on the restoration operation is not limited to being performed by the processor 23, and may be performed by a smart contract deployed on the Web3 platform.

[0047] [Activity A7] Next, in activity A7, the processor 33 transmits the user's input result to the information processing device 2.

[0048] [Activity A8] Next, in activity A8, the processor 23 accepts the submitted input results and creates a new user account based on the results.

[0049] [Activity A9] Next, in activity A9, the processor 23 executes a wallet generation process. As a result, the processor 23 generates a new wallet account based on the new user account. The details of the wallet generation process will be described later.

[0050] [Activity A10] Next, in activity A10, processor 23 associates the wallet account generated by the wallet generation process with a new user account. After that, the process returns to activity A1, and processor 23 requests input of login information. The user can log in to the new user account via user terminal 3 by inputting the login information of the new user account on login screen 5. Note that processor 23 may automatically perform the login process of the newly generated user account.

[0051] 2.2.2. Wallet Creation Process Here, an example of the wallet generation process (activity A9) described in the previous section will be described. Fig. 4 is an activity diagram showing an example of the wallet generation process.

[0052] [Activity A91] First, in activity A91, the processor 23 generates a pair of a private key and a public key based on at least a part of the login information. For example, the processor 23 generates the pair of a private key and a public key by using at least a part of a character string included in a user ID of the login information as a secret recovery phrase.

[0053] [Activity A92] Next, in activity A92, the distributed ledger system 4 generates a wallet account corresponding to the private key using a smart contract on Web3.

[0054] On the other hand, after activity A91, in activity A93, processor 23 generates multiple shares from the private key generated in activity A91 using any of the above-mentioned secret division related algorithms. The multiple shares include at least the above-mentioned first share and second share. Note that a third share may be generated together with the first share and the second share by the processing of activity A93.

[0055] [Activity A94] Next, in activity A94, the distributed ledger system 4 obtains the first share and stores the first share such that it can be accessed by obtaining a predetermined authorization based on the distributed ledger system 4. The first share can be managed by the user himself.

[0056] [Activity A95] Next, in activity A95, the processor 23 transmits the second share generated in activity A93 to the user terminal 3. As a result, the second share is generated for the user terminal 3 used when linking the user account with the wallet account.

[0057] [Activity A96] After that, in activity A96, the processor 23 stores the second share transmitted from the information processing device 2 in the user terminal 3, for example, in the storage unit 32.

[0058] [Activity A97] On the other hand, after activity A95, in activity A97, processor 23 deletes information about the generated second share. This configures the second share to be unviewable by the management account. Note that the method of making the share unviewable by the management account is not limited to this and can be any method, and can be realized, for example, by a method similar to that of issuing a secret key that is performed after inputting an access key in API integration.

[0059] 2.2.3. Management process Next, an example of the management process (activity A200) will be described. Fig. 5 is an activity diagram showing an example of the management process.

[0060] [Activity A11] After the login process is completed, in activity A11, the processor 23 sends a request for transaction information by the wallet account linked to the user account to the distributed ledger system 4. The transaction information may include any information related to cryptocurrency transactions, such as the balance of cryptocurrency currently associated with the wallet account, a transaction history based on transactions sent in the past, etc. The transaction history may include, for example, the amount of cryptocurrency sent and received in the past, the transaction destination (remittance destination, etc.), the time of transaction, etc.

[0061] [Activity A12] Next, in activity A12, the distributed ledger system 4 transmits the transaction information of the user account to the information processing device 2 based on a request for transaction information from the information processing device 2.

[0062] [Activity A13] Next, proceeding to activity A13, the processor 23 identifies candidates for transaction operations to be presented to the user based on the transaction information transmitted from the distributed ledger system 4. The candidates for transaction operations can be specified by information for identifying the contents of the transaction, such as the sender's address ("From"), the receiver's address ("To"), the data to be transmitted ("Date"), and the gas fee ("Fee") described above. For example, the processor 23 identifies candidates for transaction operations to be presented to the user based on information about business partners such as past remittance destinations and payment destinations.

[0063] [Activity A14] Next, proceeding to activity A14, processor 23 executes a first verification operation on the candidate transaction operation in activity A13. The first verification operation is one of the verification operations. The first verification operation is an operation capable of verifying the risk corresponding to the candidate transaction operation (in other words, the first transaction operation) presented to the user. The first verification operation also includes an operation performed by a third party (e.g., an administrative account) other than the user account. Specific aspects of the verification operation are as described above. For example, the first verification operation may include checking whether the remittance destination of the candidate transaction operation in activity A13 is included in a predetermined whitelist.

[0064] [Activity A15] Next, the process proceeds to activity A15, where the processor 23 identifies a transaction operation to be presented to the user based on the verification result of the verification operation of activity A14, and generates visual information based on the identification result. The transaction operation identified here to be presented to the user is a transaction operation permitted for the user account, and is an example of a second transaction operation. Therefore, the processing of activity A15 can be said to be an example of an identification step of identifying the second transaction operation, which is a transaction operation permitted for the user account, from among the first transaction operations based on the execution result of the verification operation.

[0065] The visual information is information for generating the management screen 7 (see FIG. 11). The management screen 7 is configured to be able to display at a glance information relating to at least a part of the transaction operation (in other words, the first transaction operation) presented to the user.

[0066] The management screen 7 is a user interface through which a user can send a command to execute a trading operation, and is an example of visual information. The management screen 7 is configured so that the display mode of information on the trading operation (second trading operation) specified in the activity A15 is different from the display mode of information on other candidates for trading operations (first trading operation) presented to the user. For example, the management screen 7 is configured so that the information on the trading operation presented to the user and the information on the other trading operations are displayed in a visually distinguishable manner by different colors, font sizes, fonts, etc. According to this configuration, it is possible to reduce the possibility that the user will mistakenly execute the first trading operation that is not permitted by the verification operation. In addition, the management screen 7 may be configured so that the display mode of these trading operations is different by being configured so that the trading operation specified in the activity A15 is presented preferentially over other trading operations. In this embodiment, the visual information is configured so that information on the first trading operation not included in the second trading operation, for example, trading operations other than the trading operation specified in the activity A15, is not visible to the user. According to this configuration, it is possible to reduce the possibility that the user will mistakenly execute the first trading operation that is not permitted by the verification operation. The visual information generated in activity A15 is transmitted to the user terminal 3.

[0067] [Activity A16] Next, in activity A16, the processor 33 displays the management screen 7 on the display unit 34 based on the visual information transmitted from the information processing device 2. The user can generate a command to execute a transaction operation by performing a predetermined operation on the management screen 7. This allows the user to specify the content of a transaction related to crypto assets via the management screen 7 and instruct the execution of the transaction. The user can also execute an end operation (e.g., a logout operation from a user account) to end this information processing on the management screen 7. A transaction operation related to a token transaction that can be executed by a user account via the management screen 7 is an example of a first transaction operation in the transaction processing described later. The transaction command includes information on the transaction operation such as the trading partner and the transaction amount. When a command to execute a transaction operation is generated in activity A16, the processing shifts from the management processing to activity A21 of the transaction processing (activity A300).

[0068] 2.2.4. Transaction Processing Next, the transaction process (activity A300) will be described. Fig. 6 is an activity diagram showing an example of the transaction process. The transaction process is a process of generating a transaction operation for the distributed ledger system 4 based on a user's instruction to generate the transaction operation.

[0069] [Activity A21] First, in activity A21, the processor 33 transmits an execution command for a transaction operation from a user account to the information processing device 2. The execution command may include one or more transaction operations.

[0070] [Activity A22] Next, in activity A22, the processor 23 receives an execution command for one of the transaction operations in activity A21 from the user account, and accordingly receives information related to the transaction operation.

[0071] [Activity A23] Next, in activity A23, processor 23 performs a verification operation on the transaction operation included in the received execution command. Specific examples of the verification operation are as described above. For example, when the execution command includes a cryptocurrency remittance operation as a transaction operation, processor 23 performs a verification operation to check whether the amount of the cryptocurrency to be remitted is equal to or greater than the above-mentioned reference value.

[0072] [Activity A24] Next, in activity A24, processor 23 determines whether or not to permit the transaction operation included in the execution command based on the execution result of the verification operation in activity A23. For example, processor 23 restricts the transaction operation when the amount of cryptocurrency to be remitted is equal to or greater than a reference value, and permits the transaction operation when the amount is less than the reference value. Note that restricting a transaction operation is not limited to prohibiting the transaction operation, and may include having user terminal 3 present information encouraging the user to stop the transaction operation.

[0073] [Activity A25] Next, in activity A25, the processor 23 allows the wallet account linked to the user account to generate a transaction based on a trading operation, whereby a signal to execute transaction generation is sent from the processor 33 to the wallet account, and a transaction corresponding to the trading operation is generated from the wallet account.

[0074] [Activity A26] Next, in activity A26, the processor 23 transmits to the user terminal 3 the first share corresponding to the user account.

[0075] [Activity A27] Next, in activity A27, the processor 33 obtains the first share transmitted from the information processing device 2.

[0076] [Activity A28] Next, in activity A28, the processor 33 transmits the acquired first share and the second share stored in the memory unit 32 to a wallet account in the distributed ledger system 4.

[0077] [Activity A29] Next, in activity A29, the distributed ledger system 4 uses the transmitted share to digitally sign the transaction generated from the wallet account and authenticates the transaction. As a result, the cryptocurrency is transferred from the wallet account linked to the user account to the wallet account of the transaction partner based on the transaction operation.

[0078] [Activity A30] Next, in activity A30, the processor 23 obtains the latest transaction information after the transaction of activity A29 is performed from the distributed ledger system 4. After that, the transaction processing is terminated, activity A16 of the management processing is performed, and the management screen 7 reflecting the latest transaction information is displayed on the display unit 34.

[0079] 2.2.5. About the restoration process Next, the restoration process will be described with reference to Fig. 7, which is an activity diagram showing an example of the restoration process.

[0080] [Activity A41] After the restoration operation is performed, in activity A41, the processor 23 accepts a predetermined restoration operation from the user and generates a request to input restoration data.

[0081] [Activity A42] Next, in activity A42, the processor 33 requests the user to input restoration data. For example, the processor 33 requests the user to input restoration data via a user interface displayed on the display unit .

[0082] [Activity A43] Next, in activity A43, the processor 33 transmits the restoration data input by the user to the information processing device 2.

[0083] [Activity A44] Next, in activity A44, the processor 23 compares the transmitted restoration data with the restoration data set, for example, when a new user account was created. If the two do not match and the restoration data is determined to be inappropriate, the process returns to activity A42, and the processor 23 again requests the user to input restoration data.

[0084] [Activity A45] On the other hand, if the comparison in activity A44 shows that the two match and that the restoration data is determined to be appropriate, in activity A44, the processor 23 generates a third share different from the first share and the second share and transmits it to the user terminal 3. At this time, the processor 23 generates the third share in a manner that cannot be viewed by the management account. The method for making the third share inaccessible is the same as the method related to the API cooperation described above.

[0085] [Activity A46] Next, in activity A46, the distributed ledger system 4 generates a third share based on the generation command of activity A45 and transmits it to the user account. As a result, even if the user forgets how to log in to the user account and has difficulty logging in, the user can authenticate a transaction through the wallet account using the second share stored in the user terminal 3 and the third share newly transmitted to the user terminal 3. In other words, when the third share is generated, the non-custodial wallet management system 1 may allow the generation of a transaction related to a token transaction through the wallet account using at least two of the multiple shares including the first share, the second share, and the third share. With this configuration, it is possible to maintain the freedom of a non-custodial wallet that allows a user to freely trade, while retaining the possibility of accessing the user account even if the user forgets part of the key information such as the first share or the second share.

[0086] 3.4. Example of a screen displayed on the display unit 34 Next, an example of a screen displayed on the display unit 34 by the above information processing will be described.

[0087] <Login screen 5> FIG. 8 is a diagram showing an example of the login screen 5. The login screen 5 includes an ID input field 51, a password input field 52, a login execution button 53, and a new registration button 54. The ID input field 51 is a field for inputting a user ID, which is one of the login information. The password input field 52 is a field for inputting a password, which is one of the login information. The ID input field 51 and the password input field 52 display the input result to the input unit 35 when each is specified. The login execution button 53 is a UI for transmitting the input login information. The new registration button 54 is a UI for performing a registration operation. When the new registration button 54 is operated, the display content of the display unit 34 transitions to the registration screen 6.

[0088] <Registration screen 6> FIG. 9 is a diagram showing an example of the registration screen 6. The registration screen 6 includes an ID setting field 61, a password setting field 62, a contact information setting field 63, a password setting field 64, a wallet designation field 65, and a switch button 66. The ID setting field 61 is an area for inputting a user ID of a new user account. The password setting field 62 is an area for inputting a password of the new user account. The contact information setting field 63 is an area for inputting contact information indicating a destination of a notification for confirming whether the user is the user himself / herself. For example, an email address or a telephone number is inputted into the contact information setting field 63. The password setting field 64 is a field for inputting a password for emergency login set for the new user account. The wallet designation field 65 is a field for inputting designation related to the wallet, for example, designation of a platform to be used. The switch button 66 is a UI for transmitting the contents inputted into the above fields 61 to 65 to the information processing device 2. After these inputs are sent, a check is made to see if there are any duplicate login information, and an identity verification operation is performed for the contact information entered in the contact information setting field 63, whereby a new user account is generated and the information is stored in the storage unit 22. When the switch button 66 is pressed, the screen displayed on the display unit 34 transitions from the registration screen 6 to the backup screen 6a.

[0089] <Backup screen 6a> FIG. 10 is a diagram showing an example of the backup screen 6a. The backup screen 6a is a screen for generating and storing restoration data. The backup screen 6a includes a cloud backup button 67, a local backup button 68, and a decision button 69. When the cloud backup button 67 is selected, the processor 33 requests the setting of an account for linkage through the display unit 34. After the setting is completed, the processor 33 generates the restoration data and a third share associated therewith using a predetermined smart contract. Then, the processor 33 stores the generated restoration data in the cloud storage associated with the account. Note that the entity that executes this process is not limited to the processor 33, and may be the processor 23 or another device other than these.

[0090] The local backup button 68 stores the generated restoration data in the storage unit 32 of the user terminal 3 being used by the user.

[0091] The decision button 69 is a button for ending the login process. When the decision button 69 is pressed, the login screen 5 shown in Fig. 8 is displayed again, and the management screen 7 is displayed on the display unit 34 as a result of the login being performed.

[0092] <Management screen 7> 11 is a diagram showing an example of the management screen 7. The management screen 7 includes a remittance source designation field 71, a business partner designation field 72, a remittance content designation field 73, a gas fee designation field 74, and a confirmation button 75.

[0093] The remittance source specification field 71 is a field where the digital wallet to be the remittance source can be specified. Digital wallets linked to the user account are displayed by default in the remittance source specification field 71, and the user can specify the desired wallet by operating the remittance source specification field 71 while viewing candidates for the digital wallet to be the remittance source.

[0094] The transaction partner designation field 72 is a field where a transaction partner to which crypto assets are to be transferred from the digital wallet can be designated. By operating the transaction partner designation field 72, a user can designate a desired transaction partner while viewing a list of transaction partner addresses. Note that transaction partners that are not identified as transaction partners to be presented as a result of the verification operation in the management process are hidden from the list. This can reduce the possibility that a user will transfer funds to a risky transaction partner.

[0095] The remittance content specification field 73 allows the user to specify data as remittance content, such as the amount of cryptocurrency. Note that the remittance content specification field 73 may be configured to allow the user to specify any data as long as it can be specified by a token linked to a wallet account.

[0096] The gas fee specification field 74 is configured to allow the user to specify the gas fee to be charged when sending a transaction.

[0097] The decision button 75 is a UI for generating an execution command for a transaction operation specified based on the contents of the above-mentioned fields 71 ​​to 74. After the decision button 75 is pressed, a verification operation is performed on the transaction operation. As a result, the generation of the transaction is permitted.

[0098] On the other hand, when the generation of a transaction is restricted as a result of the verification operation, the restriction information 751 is displayed on the management screen 7. The restriction information 751 indicates that the generation of a transaction has been restricted by the management account as a result of the verification operation. The restriction information may further include information regarding the verification operation used in the judgment to restrict the transaction operation. When the verification operation used in the judgment to restrict the transaction operation includes "a process of confirming whether the remittance amount is greater than the past remittance amount by a predetermined value or more," the information may be implemented as text information indicating, for example, "the remittance amount is significantly greater than the past remittance amount" as "reason 1." Furthermore, when the generation of a transaction is restricted as a result of the verification operation, the processor 23 may generate visual information that displays, in a different manner from other information, the information included in the transaction operation that is the basis for the restriction by the verification operation. This makes it easier to visually understand the reason why the generation of the transaction was not approved by the management account.

[0099] In this way, the verification operation prevents suspicious transactions from being carried out by the user, and even users who are unfamiliar with digital wallets can exchange tokens through the distributed ledger system 4 relatively safely.

[0100] 4. Examples of application of the above information processing when providing games The information processing related to the above-mentioned non-custodial wallet can be used in NFT games. Fig. 12 is an activity diagram showing an example of game processing including the above-mentioned information processing. In the following description, an example in which the processor 23 is the main entity that executes the processing will be described, but the present invention is not limited to this.

[0101] As shown in FIG. 12, the processor 23 first executes a game login process in activity A501 and accepts a user's login to the NFT game. As a result, the processor 23 acquires information about a game account for the user to access a specific game. Note that the account for the game (hereinafter referred to as a game account) may be different from the above-mentioned user account and wallet account. The NFT game is configured to be able to grant data with tradeable NFTs through the wallet account by linking with the user account.

[0102] Next, in activity A502, the processor 23 displays a game start screen 8 on the display unit 34. The game start screen 8 may include a UI capable of transmitting various requests, such as a wallet link request, a data transaction request, and a game start request, to the processor 23 in response to a user operation.

[0103] When the processor 23 acquires the wallet link request, the login process of the activity A100 is executed. As a result, the login screen 5 and the like are displayed on the display unit 34. When the login to the user account is completed, the process returns to the activity A502.

[0104] When the processor 23 acquires a data transaction request, transaction processing of activity A200 is performed. As a result, the management screen 7 and the like are displayed on the display unit 34. The user can execute transactions of the NFT game appearing in the game via the management screen 7 and the like. When the management processing of the processing of activity A200 is completed, the process returns to activity A502.

[0105] When the processor 23 acquires a game start request, the processor 23 starts the progress of the game in activity A503. Thereafter, when a game end condition is satisfied, the process proceeds to activity A504, where the processor 23 tallies the game results and displays the tallied results on the display unit 34. At this time, when the processor 23 is linked to a game account through the login process of activity A100, the processor 23 may link the game to which the NFT in the game is granted according to the tallied results to the wallet account and make it available for trading. Then, the game process ends.

[0106] In this embodiment, the NFT game is configured to be able to proceed regardless of whether or not there is a link with a user account (in other words, a link with a wallet account). In other words, the processor 23 progresses the game in response to the operation of the user of the game account, regardless of whether or not the game account is linked with a user account. This makes it possible to prevent the game from becoming less interesting for users who are unfamiliar with technology such as NFT.

[0107] FIG. 13 is a diagram showing an example of a game start screen. As shown in FIG. 13, the game start screen 8 includes a game display area 81, a game start button 82, a wallet setting button 83, and a data management button 84. The game display area is an area showing an outline of a game (game) that can be provided to a user. The game start button 82 is a UI for generating a game start request. When the game start button 82 is pressed, the processor 23 starts the progress of the game. The wallet setting button 83 is a UI for generating a wallet link request. When the wallet setting button 83 is pressed, the processor 23 causes the display unit 34 to display the login screen 5. The data management button 84 is a UI for generating a data transaction request. When the data management button 84 is pressed, the processor 23 causes the display unit 34 to display the management screen 7.

[0108] The game may include any content that can be implemented in a digital space such as the metaverse. The NFT data may be, for example, a user's avatar that can be used in a digital space such as the metaverse. The process of creating an avatar by a user is arbitrary, but for example, the processor 23 displays a preset question on the display unit 34 and accepts an input from the user regarding an answer to the question. Next, the processor 23 generates an AI avatar using an information processing device including a generated image AI based on the input. At this time, it is preferable that the AI ​​avatar is configured to embody the user's hobbies, tastes, etc. Thereafter, the AI ​​avatar NFT is stored in the non-custodial wallet in parallel with the generation of the avatar. As a result, an avatar reflecting one's unique identity is generated as an NFT in conjunction with the creation of a user account.

[0109] 5.Other The non-custodial wallet management system 1 and the like can be modified, for example, as follows, within the scope of technical compatibility. Note that in the modifications described below, components common to the above-described embodiment are given the same reference numbers and descriptions thereof may be omitted.

[0110] The first share does not need to be configured to be accessible only to the management account, and may be configured to be shared with users of user accounts. In this case, the user can generate transactions and perform electronic signatures by directly operating a wallet account without going through the information processing device 2 by operating the user terminal 3, rather than a user account of the information processing device 2. In this case, the user can trade tokens regardless of the verification operation by the information processing device 2.

[0111] The login process (activity A100), management process (activity A200), transaction process (activity A300), and restoration process (activity A401) do not have to be performed as a series of information processes, and may be performed as separate information processes.

[0112] The information processing device 2 may be an on-premise type or a cloud type. As the information processing device 2 in the cloud type, the above-mentioned functions and processes may be provided in the form of, for example, SaaS (Software as a Service) or cloud computing.

[0113] In the above embodiment, the information processing device 2 performs various storage and control, but multiple external devices may be used instead of the information processing device 2. That is, various information and programs may be distributed and stored in multiple external devices using block chain technology or the like.

[0114] The above embodiment is not limited to the non-custodial wallet management system 1, and may be an information processing method or an information processing program. The information processing method includes each step of the non-custodial wallet management system 1. The information processing program causes at least one computer to execute each step of the non-custodial wallet management system 1.

[0115] It may be provided in any of the following ways:

[0116] (1) A non-custodial wallet management system comprising: at least one processor and at least one memory unit, at least one of which stores account information related to a user account, the user account being configured to be linked to a wallet account held by a user, the wallet account being configured to generate transactions based on a plurality of shares including a first share generated based on at least a part of the account information and a second share managed by a user of the user account and inaccessible to a management account different from the user account of the user account, hold tokens using a distributed ledger technology, and execute transactions of the tokens based on the transactions, wherein a first receiving step receives information related to a first transaction operation which is an operation related to a transaction of the token which can be executed by the user account, the first transaction operation being associated with a predetermined verification operation, the verification operation being capable of verifying a risk corresponding to the first transaction operation and including an operation executed by an account other than the user account, and wherein an identifying step identifies a second transaction operation which is a transaction operation permitted for the user account from among the first transaction operations based on a result of execution of the verification operation.

[0117] According to this configuration, even in the case of a non-custodial wallet in which each user manages their own private key, the transaction generation mode can be determined based on a verification operation predetermined for a non-custodial wallet management system for cryptocurrency, etc., thereby preventing inexperienced users from performing processing that does not correspond to a verification operation.

[0118] (2) A non-custodial wallet management system as described in (1) above, wherein the first receiving step further receives an execution command for one of the first transaction operations from a user of the user account, and the first allowing step further allows the wallet account to generate a transaction based on the second transaction operation if the first transaction operation corresponding to the execution command is included in the identified second transaction operations.

[0119] With this configuration, in a non-custodial wallet management system, it is possible to prevent users who are unfamiliar with token transactions from performing careless transaction operations.

[0120] (3) A non-custodial wallet management system according to (1) or (2) above, wherein the first transaction operation includes at least an instruction regarding the transfer of the token associated with the user account.

[0121] With this configuration, in a non-custodial wallet, when a user transfers a user account to a third party, it is possible to prevent suspicious transactions, such as the transfer of a token account or the token itself, from being inadvertently carried out.

[0122] (4) A non-custodial wallet management system according to any one of (1) to (3) above, wherein the information relating to the first transaction operation includes information relating to a trading partner of the token, and the verification operation includes verifying the reliability of the trading partner based on information relating to the trading partner specified by the management account.

[0123] With this configuration, for example, when trading tokens using a non-custodial wallet, it is possible to prevent transactions from being generated toward unreliable trading partners who are the target of suspicious transactions.

[0124] (5) In the non-custodial wallet management system described in any one of (1) to (4) above, a first transaction operation associated with the verification operation includes a transaction operation in which the transaction amount of the token is higher than a predetermined reference value, and the reference value is set based at least on a past transaction history of a user of the user account.

[0125] With this configuration, it is possible to prevent a transaction from being inadvertently generated in a non-custodial wallet when a user transfers an amount that is excessively large compared to past transaction history.

[0126] (6) A non-custodial wallet management system according to any one of (1) to (5) above, further comprising: in the display processing step, generating visual information capable of displaying at a glance information relating to at least a portion of the first transaction operation by a user of the user account; and configuring the visual information so that a display manner of the information relating to the second transaction operation is different from a display manner of the information relating to the first transaction operation that is not included in the second transaction operation.

[0127] According to this configuration, it is possible to reduce the possibility that the user will mistakenly execute the first transaction operation that is not permitted by the verification operation.

[0128] (7) A non-custodial wallet management system as described in (6) above, wherein the visual information is configured such that information regarding the first transaction operation that is not included in the second transaction operation is not visible to a user of the user account.

[0129] According to this configuration, it is possible to reduce the possibility that the user will mistakenly execute the first transaction operation that is not permitted by the verification operation.

[0130] (8) A non-custodial wallet management system according to any one of (1) to (7) above, wherein the second share is generated for a user terminal used when linking the user account with the wallet account, a second receiving step receives a predetermined restoration operation from a user of the user account, and a restoration step generates a third share different from the first share and the second share in response to the restoration operation, in a manner in which the third share cannot be viewed by the management account, and a second allowing step allows the wallet account to generate a transaction related to a trade of the token using at least two of a plurality of shares including the first share, the second share, and the third share, when the third share is generated.

[0131] With this configuration, the freedom of a non-custodial wallet that allows users to trade freely is maintained, while the user account remains accessible even if the user forgets part of the key information, such as the first share or the second share.

[0132] (9) A non-custodial wallet management system according to any one of (1) to (8) above, wherein the verification operation further includes a user verification operation including a user condition that can be set by a user of the user account.

[0133] According to such a configuration, despite being a non-custodial wallet, a user's transaction operations can be pseudo-restricted by persons other than the user, more specifically, by persons other than the user and the administrator, thereby further improving the transaction security of the non-custodial wallet.

[0134] (10) A non-custodial wallet management system according to any one of (1) to (9) above, further comprising: in the acquisition step, acquiring information about a game account for a user of the user account to access a predetermined game, wherein the game is configured to be able to grant data having an NFT that is tradable through the wallet account by linking with the user account; and in the game progress step, progressing the game in accordance with an operation of the user of the game account, regardless of whether the game account is linked with the user account.

[0135] This configuration makes it possible to prevent the game from losing its appeal for users who are unfamiliar with technologies such as NFTs.

[0136] (11) A non-custodial wallet management method, comprising each step of the non-custodial wallet management system according to any one of (1) to (10) above.

[0137] (12) A program causing at least one computer to execute each step of the non-custodial wallet management system described in any one of (1) to (10) above. Of course, this is not the case.

[0138] Finally, although various embodiments according to the present disclosure have been described, these are presented as examples and are not intended to limit the scope of the invention. The novel embodiment can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. The embodiments and their modifications are included within the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0139] 1: Non-custodial wallet management system 2: Information processing equipment 3: User terminal 4: Distributed ledger system 5: Login screen 6: Registration screen 6a: Backup screen 7: Management screen 20: Communication bus 21: Communications Department 22: Storage section 23: Processor 30: Communication bus 31: Communications Department 32: Storage section 33: Processor 34: Display section 35: Input section 41: Node computer 51: ID input field 52: Password entry field 53: Login execution button 54: New registration button 61: ID setting field 62: Password setting field 63: Contact information setting field 64: Recovery data setting field 65: Wallet specification field 66: Switch button 67: Cloud backup button 68: Local backup button 69: Decision button 71: Remittance source specification field 72: Supplier designation field 73: Remittance details field 74: Gas fee specification column 75: Decision button 751: Regulatory Information 81: Game display area 82: Game start button 83: Wallet setting button 84: Data management button

Claims

1. 1. A non-custodial wallet management system, comprising: At least one processor and at least one memory unit; At least one of the storage units stores account information relating to a user account; The user account is configured to be linked to a wallet account held by the user, The wallet account is generating a transaction based on a plurality of shares, the plurality of shares including a first share generated based at least in part on the account information and a second share managed by a user of the user account and inaccessible to a management account distinct from the user account of the user account; The system is configured to hold tokens using distributed ledger technology and execute transactions of the tokens based on the transactions; In the first receiving step, information regarding a first transaction operation, which is an operation regarding a transaction of the token that can be executed by the user account, is received; The first transaction operation is associated with a predetermined verification operation; the verification operation is capable of verifying a risk corresponding to the first transaction operation and includes an operation performed by a means other than the user account; In the identification step, the non-custodial wallet management system identifies a second transaction operation, which is an allowable transaction operation for the user account, from among the first transaction operations based on the execution result of the verification operation.

2. 2. The non-custodial wallet management system of claim 1, The first receiving step further includes receiving an execution command for one of the first transaction operations from a user of the user account; Further, in the first permission step, the non-custodial wallet management system allows the wallet account to generate a transaction based on the second transaction operation when the first transaction operation corresponding to the execution command is included in the identified second transaction operation.

3. 2. The non-custodial wallet management system of claim 1, The first transaction operation includes instructions regarding a transfer of at least the tokens associated with the user account.

4. 2. The non-custodial wallet management system of claim 1, The information relating to the first trading operation includes information regarding a counterparty of the tokens; A non-custodial wallet management system, wherein the verification operation includes verifying the authenticity of the trading partner based on information about the trading partner specified by the management account.

5. 2. The non-custodial wallet management system of claim 1, The first transaction operation associated with the verification operation includes a transaction operation in which the transaction amount of the token is higher than a predetermined reference value; The reference value is set based at least on a past transaction history of a user of the user account.

6. 2. The non-custodial wallet management system of claim 1, Further, in the display processing step, visual information is generated that allows information regarding at least a part of the first transaction operation by the user of the user account to be viewed at a glance; A non-custodial wallet management system, wherein the visual information is configured so that the display manner of information relating to the second transaction operation is different from the display manner of information relating to the first transaction operation that is not included in the second transaction operation.

7. 7. The non-custodial wallet management system according to claim 6, The visual information is configured such that information regarding the first transaction operation that is not included in the second transaction operation is not visible to a user of the user account.

8. 2. The non-custodial wallet management system of claim 1, The second share is generated for a user terminal used when linking the user account with the wallet account, In a second receiving step, a predetermined restoration operation is received from a user of the user account; In the restoration step, a third share different from the first share and the second share is generated in response to the restoration operation, the third share being inaccessible to the management account; and in a second allowing step, when the third share is generated, allowing generation of a transaction for trading the token by the wallet account using at least two of a plurality of shares including the first share, the second share, and the third share.

9. 2. The non-custodial wallet management system of claim 1, The verification operation further includes a user verification operation including user conditions configurable by a user of the user account.

10. 2. The non-custodial wallet management system of claim 1, Further, in the acquisition step, information regarding a game account for a user of the user account to access a predetermined game is acquired, and the game is configured to be capable of being granted data to which NFTs that can be traded through the wallet account are granted by linking with the user account; Furthermore, in the game progress step, the non-custodial wallet management system progresses the game in accordance with the operation of the user of the game account, regardless of whether the game account is linked to the user account.

11. 1. A method for managing a non-custodial wallet, comprising: A non-custodial wallet management method comprising the steps of the non-custodial wallet management system according to any one of claims 1 to 10.

12. A program, A program causing at least one computer to execute each step of the non-custodial wallet management system according to any one of claims 1 to 10.

Images