Information processing method, program, information processing system, and information processing apparatus

Abstract

To improve the convenience of a user while reducing the personal information leakage risk of the user in the use of a service for recording the transaction or operation of the user in a block chain.SOLUTION: An information processing method executed by an information processing system 1 that provides a wallet connected to a service using a blockchain technology includes a generation step of generating and providing a dedicated wallet different for each activity of the service in association with one user, and a providing step of providing the dedicated wallet so as to be connectable to the service.SELECTED DRAWING: Figure 7

Description

[Technical Field]

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

[0002] Conventionally, DApps (Decentralized Applications) have been known to issue users with NFTs (Non-Fungible Tokens) that prove the uniqueness and ownership of digital content such as digital art and game items, and to provide services that support the trading of such digital content using FTs (Fungible Tokens) such as virtual currencies.

[0003] When using DApps services, users connect their cryptocurrency wallets (hereinafter sometimes simply referred to as wallets) and record the issuance and transactions of NFTs on the blockchain using the user's private key and public key pair managed by the wallet. For example, Patent Document 1 describes a processing system that connects to a wallet when executing various processes such as the issuance of NFTs and the transfer of ownership. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2024-57690 Summary of the Invention [Problem to be solved by the invention]

[0005] Currently, many users of services provided by DApps that utilize blockchain technology use a single cryptocurrency wallet, and in the case of a public blockchain, the history of all services used by the user is recorded and made public along with the wallet address, which is an identifier for the wallet. This record cannot be deleted or changed.

[0006] Here, the wallet address itself is anonymized, but if the address and the individual's correspondence can be identified for some reason, the address's activity history will be linked to personal information. As blockchain services become more widespread among both providers and users, it is inevitable that the above-mentioned risks to personal information will become a social issue.

[0007] It is possible for a user to have multiple wallets (wallet addresses), but this can pose a security vulnerability as it requires the user to switch wallets for each service they use, and as the number of wallets increases, it becomes more difficult for the user to manage them.

[0008] Therefore, the present disclosure aims to provide an information processing method, program, information processing system, and information processing device that can improve user convenience while reducing the risk of personal information leakage when using a service that records user transactions and operations on a blockchain. [Means for solving the problem]

[0009] The information processing method disclosed herein is an information processing method executed by an information processing system that provides a wallet that connects to a service that uses blockchain technology, and includes a generation step that generates and provides a different dedicated wallet for each activity of the service, associated with one user, and a provision step that provides the dedicated wallet so that it can be connected to the service.

[0010] The program disclosed herein is a program executed by an information processing system that provides a wallet that connects to a service that uses blockchain technology, and executes a generation step of generating a different dedicated wallet for each activity of the service, associated with one user, and a provision step of providing the dedicated wallet so that it can be connected to the service.

[0011] The information processing system according to the present disclosure is an information processing system that provides a wallet that connects to a service that uses blockchain technology, and includes a generation unit that generates a different dedicated wallet for each activity of the service, associated with one user, and a provision unit that provides the dedicated wallet so that it can be connected to the service.

[0012] The information processing device according to the present disclosure is an information processing device that provides a wallet that connects to a service that uses blockchain technology, and includes a generation unit that generates a different dedicated wallet for each activity of the service, associated with one user, and a provision unit that provides the dedicated wallet so that it can be connected to the service. [Effects of the Invention]

[0013] According to the present disclosure, when using a service that records user transactions and operations on a blockchain, it is possible to improve user convenience while reducing the risk of personal information leakage. [Brief explanation of the drawings]

[0014] [Figure 1] 1 is a diagram illustrating a configuration of an information processing system according to an embodiment of the present disclosure. [Figure 2] A block diagram showing the functional configuration of a wallet management server according to an embodiment of the present disclosure. [Figure 3] A diagram showing information stored in a memory unit of a wallet management server according to an embodiment of the present disclosure. [Figure 4] FIG. 1 is a block diagram illustrating a functional configuration of a DApps server according to an embodiment of the present disclosure. [Figure 5] FIG. 2 is a block diagram illustrating a functional configuration of a user terminal according to an embodiment of the present disclosure. [Figure 6] FIG. 2 is a block diagram illustrating a functional configuration of a service providing server according to an embodiment of the present disclosure. [Figure 7] FIG. 10 is a sequence diagram showing the operation of a dedicated wallet provision process according to an embodiment of the present disclosure. [Figure 8] FIG. 10 is a sequence diagram illustrating an operation of a possession proof process according to an embodiment of the present disclosure. [Figure 9] FIG. 9 is a block diagram showing the basic hardware configuration of a computer 900. [Figure 10] FIG. 1 illustrates the conventional relationship between a single wallet and the recording of transactions related to service usage. [Figure 11] FIG. 10 is a diagram showing the relationship between the dedicated wallet of the present disclosure and records of transactions related to service usage. [Figure 12] FIG. 10 is a diagram illustrating types of activity identifiers and characteristics of each type according to an embodiment of the present disclosure. [Figure 13] FIG. 10 is a sequence diagram showing the operation of a dedicated wallet provision process according to a modified example of an embodiment of the present disclosure. [Figure 14] 10 is an example of a screen displayed on a user terminal in a transfer process according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0015] The embodiments of the present disclosure will be described with reference to the drawings, in which the same or similar parts are designated by the same or similar reference numerals.

[0016] <Configuration of Information Processing System 1> FIG. 1 is a diagram showing the configuration of an information processing system 1 according to an embodiment. The information processing system 1 according to this embodiment is a system for providing a wallet management service for generating and using a dedicated wallet, which is a crypto-asset wallet dedicated to each service that uses blockchain technology (hereinafter referred to as a BC service). Crypto-assets are all assets that are digitally held using blockchain technology. Crypto-assets include virtual currencies, digital securities (security tokens), utility tokens, NFTs, etc. Virtual currencies are a part of crypto-assets and are digital assets that are primarily used as currency.

[0017] In the present disclosure, a unit of use of a BC service that uses a dedicated wallet is defined as an activity. That is, the information processing system 1 according to this embodiment is a system for using a dedicated wallet for each activity.

[0018] In this embodiment, the information processing system 1 will be described assuming that activities are NFTs managed by DApps, and that a dedicated wallet is generated and managed for each NFT. DApps are decentralized applications that use blockchain technology, and in the following explanation, they are also used to refer to service providers that provide blockchain services. A single DApp can contain multiple NFTs. Note that the use of NFTs includes, for example, the transfer (purchase) and verification of ownership of digital assets using NFTs, as well as the execution of smart contracts to issue and manage NFTs.

[0019] The information processing system 1 includes a wallet management server 100 (information processing device), a DApps server 200, a user terminal 300, a blockchain network 400 (hereinafter simply referred to as blockchain 400), and a service providing server 500. The wallet management server 100, the DApps server 200, the user terminal 300, the blockchain 400, and the service providing server 500 are connected to a network 5 and can communicate with each other via the network 5. The network 5 includes the Internet. The network 5 may include a LAN (Local Area Network) and / or a WAN (Wide Area Network).

[0020] The wallet management server 100, the DApps server 200, the user terminal 300, the blockchain 400, and the service providing server 500 each comprise one or more computers. The basic configuration of a computer will be described later.

[0021] The user sets up the wallet management service and DApps in advance so that they can be used on the user terminal 300 they use. In the following explanation, it is assumed that the user uses only one user terminal 300, and that the wallet management app (which may be a browser extension) provided by the wallet management service and the DApps app (or similar) provided by the DApps are installed on that user terminal 300.

[0022] The information processing system 1 generates and provides a dedicated wallet for each user for each activity related to the blockchain 400. It also automatically switches between dedicated wallets for multiple activities. Specifically, the information processing system 1 generates and provides a dedicated wallet for each user for each NFT on the blockchain 400. It also automatically switches between dedicated wallets for multiple NFTs.

[0023] FIG. 2 is a block diagram showing the functional configuration of the wallet management server 100 according to this embodiment. The wallet management server 100 is a server device that provides a wallet management service that generates a dedicated wallet, which is a cryptocurrency wallet dedicated to each NFT, and switches between the dedicated wallets depending on the NFT being used. The wallet management server 100 of this embodiment includes a communication unit 110, a storage unit 120, and a processing unit 130.

[0024] The storage unit 120 includes an application program 121 and a database 122 .

[0025] The application program 121 is executed by the processing unit 130 and is a program that mainly implements each functional unit of the processing unit 130.

[0026] FIG. 3 is a diagram showing an example of various types of information stored in the database 122 of the wallet management server 100. The database 122 stores various types of information necessary for providing the wallet management service. The database 122 includes a user table 122A and a wallet table 122B. The user table 122A includes a user ID (user identifier) ​​for uniquely identifying a user of the wallet management service. The wallet table 122B includes a wallet address of a dedicated wallet generated by the generation unit 132 (described later) and held NFT information, which is information about NFTs held by the dedicated wallet. The wallet table 122B can also include various types of information managed by the dedicated wallet, such as a private key and a public key (not shown). Note that the held NFT information may include information about FTs (fungible tokens) held by the dedicated wallet in addition to NFTs.

[0027] Returning now to Fig. 2, the processing unit 130 includes, as functional units, a user management unit 131, a generation unit 132, a selection unit 133, a provision unit 134, and a transfer unit 135. The processing unit 130 executes an application program 121 stored in the storage unit 120, thereby realizing each functional unit and performing a dedicated wallet provision process and a possession proof process. The dedicated wallet provision process and the possession proof process each include at least one of an authentication process, a generation process, a selection process, a provision process, and a transfer process.

[0028] The user management unit 131 manages users of the wallet management service. The user management unit 131 performs service registration processing for new users, issues a user ID, and stores it in the storage unit 120. The user management unit 131 also executes authentication processing for authenticating login to the wallet management service using the user ID from users who have already registered for use.

[0029] The generation unit 132 executes a generation process to generate a dedicated wallet for each NFT for one user. The generation unit 132 generates a wallet address of the dedicated wallet based on the user ID, the activity identifier (the contract address of the NFT for which the dedicated wallet is to be generated), and an index. The index may be an incremental number, which the generation unit 132 acquires when generating the dedicated wallet.

[0030] A dedicated wallet is a type of cryptocurrency wallet, and has functions such as managing private keys and generating signatures, generating cryptocurrency addresses using public keys, and generating and sending transactions. A dedicated wallet has a wallet address (externally owned account) that uniquely identifies the dedicated wallet on the blockchain 400. All dedicated wallets in this embodiment are created with transaction generation and sending functions disabled by default, and only the signing function is enabled. A dedicated wallet can refer not only to a statically existing private key, but also to a general signing processing system.

[0031] The generation unit 132 may generate multiple dedicated wallets using any one or a combination of MPC (Multi Party Computing), TSS (Threshold Signing Scheme), and HD wallet (Hierarchical Deterministic Wallet).

[0032] The selection unit 133 executes a selection process to select and switch the user's dedicated wallet depending on the NFT used by the user.

[0033] The providing unit 134 connects the dedicated wallet selected by the selecting unit 133 to the DApps that manage NFTs, and executes a providing process that provides an environment in which the dedicated wallet can be used on the DApps. The providing unit 134 can issue proof of possession (signature) in that environment. Note that, although a user can normally use DApps without knowing the wallet address of the connected dedicated wallet itself, to prevent leakage of the wallet address, when the user views the address, the providing unit 134 may present the user with information about the risks of sharing the address with a third party.

[0034] The transfer unit 135 executes a transfer process to transfer crypto assets in a first dedicated wallet corresponding to an NFT to a second dedicated wallet corresponding to the same NFT. When a transaction related to an NFT held in the first dedicated wallet is sent by identifying an externally owned account of the first dedicated wallet, the transfer unit 135 causes the generation unit 132 to newly generate a second dedicated wallet corresponding to the NFT and transfers all or part of the crypto assets held in the first dedicated wallet to the second dedicated wallet. The transfer unit 135 updates the database 122 as necessary. Prior to sending the transaction, the user at least temporarily enables the transaction sending function of the first dedicated wallet. Types of transactions related to NFTs include minting, transfer, approval, bulk approval, token URI setting, burning, sale, and transaction history. The transfer unit 135 may execute a transfer process when certain types of transactions are sent.

[0035] 4 is a block diagram showing the functional configuration of the DApps server 200 according to this embodiment. The DApps server 200 according to this embodiment is a server device that provides front-end and back-end functions for DApps, which are decentralized applications that run on the blockchain 400. The DApps server 200 includes a communication unit 210, a storage unit 220, and a processing unit 230.

[0036] The processing unit 230 includes, as functional units, a user management unit 231, an activity execution unit 232, a wallet connection unit 233, and a recording unit 234. The processing unit 230 realizes each functional unit by executing an application program (not shown) stored in the storage unit 220.

[0037] The user management unit 231 manages users of DApps. The user management unit 231 performs user registration for new users. In addition, the user management unit 231 performs login authentication for users who have already registered for use, as necessary.

[0038] The activity execution unit 232 allows a user to use one or more NFTs provided by DApps to the user in response to the user's request. For example, in the case of NFT art, the use of NFTs includes purchasing NFT art (including free transfer) and viewing art images after purchase.

[0039] The wallet connection unit 233 manages the connection between the user's crypto asset wallet and DApps. The wallet connection unit 233 requests the user to connect to the user's crypto asset wallet in response to a request from the user to use an NFT managed by the DApp, or at any time. Specifically, the wallet connection unit 233 sends a wallet connection request to the user terminal 300. At this time, the wallet connection unit 233 also sends to the user terminal 300 the contract address of the NFT for which usage has been requested by the user.

[0040] In this embodiment, the wallet connection unit 233 displays the wallet connection request on the DApps application on the user terminal 300 and sends the contract address of the NFT as an activity identifier as information that can be used by the user terminal 300.

[0041] The functionality of the wallet connection unit 233 can be realized using, for example, the WalletConnect standard. When using the WalletConnect standard, the wallet connection unit 233 can send proposer information to the user terminal 300 in response to a request from a user, a request from an external application (including a wallet management service or other crypto asset wallet) connecting to the DApps, or spontaneously. The proposer information includes the URL (Uniform Resource Locator) of the DApps server 200. The URL includes the contract address of the DApps' NFT. If the DApps provides multiple NFTs, for example, when the NFT being accessed by the user is switched, proposer information including the contract address of the NFT to be switched to may be sent in response to a request from an external application or spontaneously.

[0042] The recording unit 234 records user operations and transactions related to NFTs in the blockchain 400 using the signature of the connected crypto asset wallet. In this embodiment, the recording is performed using a signature with the private key of a dedicated wallet that is automatically selected and connected by the wallet management service depending on the NFT.

[0043] 5 is a block diagram showing the functional configuration of a user terminal 300 according to this embodiment. The user terminal 300 according to this embodiment includes a communication unit 310, a storage unit 320, an input unit 330, an output unit 340, and a processing unit 350.

[0044] The user terminal 300 is a terminal used by a user who uses the wallet management service, and is configured by any computer such as a smartphone, tablet terminal, personal computer, etc. In the following description, the user terminal 300 is assumed to be a smartphone.

[0045] The storage unit 320 has an application program 321 and a user ID 322. The application program 321 may be stored in advance in the storage unit 320, or may be configured to be downloaded from a web server operated by a service provider via the communication unit 310. The application program 321 includes various application formats such as an extended function for a web browser or a mobile app.

[0046] The application program 321 includes a wallet management app for using the wallet management service and a DApps app for using DApps.

[0047] The user ID 322 includes authentication information of the user for using various services, such as a user ID for logging in to the wallet management service.

[0048] The input unit 330 includes an input device. The input unit 330 may include a camera 331 as an input device. When a user uses DApps on a user terminal other than the user terminal 300, the camera 331 can be used to scan a two-dimensional code that is issued by the DApps server 200 in response to a wallet connection request and displayed on the other user terminal.

[0049] The output unit 340 includes at least a display as an output device.

[0050] The processing unit 350 includes, as a functional unit, an inter-application link unit 351. The processing unit 350 realizes each functional unit by executing the application program 321. The function of the inter-application link unit 351 will be described in detail later.

[0051] Let's now return to Figure 1. The blockchain 400 of this embodiment is a network of multiple computers connected peer-to-peer. There are three types of blockchains: public chains without a specific administrator, private chains managed by a single organization, and consortium chains managed by multiple organizations. Although the blockchain 400 of this embodiment is primarily focused on public chains, the blockchain 400 may also be a private chain or a consortium chain. In a typical example, the blockchain 400 may be a public chain such as the Bitcoin network, the Ethereum network, or the Polygon network, or a private chain such as Hyperledger Fabric, Quorum, or the LINE blockchain.

[0052] Users of the blockchain 400 use the blockchain 400 via accounts on the blockchain 400 called externally owned accounts. The blockchain 400 is also configured to be able to record various smart contracts (programs). Externally owned accounts are identified by the "wallet address" of the cryptocurrency wallet owned by the user, and smart contracts are identified by the "account contract address."

[0053] The blockchain 400 is configured to be able to record various transactions in a blockchain (specifically, a ledger). Such a ledger is maintained by each computer connected peer-to-peer, and is also called a distributed ledger. These various transactions include an issuance transaction for issuing a new account, smart contract, or token, a transfer transaction for transferring ownership of a token, etc.

[0054] FIG. 6 is a block diagram showing a functional configuration of the service providing server 500 according to an embodiment of the present disclosure. The service providing server 500 includes a communication unit 510, a storage unit 520, and a processing unit 530. The service providing server 500 is a server through which an unspecified number of entities, such as businesses, provide some kind of convenience to holders of a predetermined crypto asset. The service providing server 500 may be a DApp, or may be a server built on an existing Web2 that does not involve recording to the blockchain 400. The predetermined crypto asset includes, for example, an NFT or a DID (Decentralized Identifier). The service providing server 500 of this embodiment requests proof of possession (so-called token gate) of a predetermined NFT as a crypto asset from the user, and provides the user with a predetermined service once the proof of possession is confirmed.

[0055] The processing unit 530 includes, as functional units, a user management unit 531, a proof request unit 532, a wallet connection unit 533, and a service providing unit 534. The processing unit 530 realizes each functional unit by executing an application program (not shown) stored in the storage unit 520.

[0056] The proof request unit 532 checks whether a user holds a predetermined NFT when using a service provided by the service providing server 500. Specifically, the proof request unit 532 requests proof of possession of the predetermined NFT from the user, and if proof of possession is obtained, the user is permitted to use the predetermined service.

[0057] When the service providing server 500 provides a predetermined service to a user, the wallet connection unit 533 manages the connection between the user's crypto asset wallet and the service providing server 500. The main operation of the wallet connection unit 533 is the same as that of the DApps server 200, so a description thereof will be omitted.

[0058] The service providing unit 534 provides the predetermined services provided by the service providing server 500 to the user.

[0059] <Operation of Information Processing System 1 (Information Processing Method)> Each process of the information processing system 1 will be described below. 7 is a flowchart showing the operation of the dedicated wallet provision process of the information processing system 1. As a premise, user A is logged in to and able to use DApps on the user terminal 300.

[0060] In step S101, user A starts the wallet management application on the user terminal 300, and accesses and logs in to the wallet management server 100 using user A's user ID (A). Specifically, the wallet management application of the user terminal 300 accesses the wallet management server 100 and requests authentication of user A using the user ID (A) of the wallet management service stored in the storage unit 320. The wallet management server 100 confirms the authority of user A based on the user ID (A) and permits authentication (authentication process).

[0061] In step S102, user A identifies an NFT and requests its purchase on the DApps app on the user terminal 300. Hereinafter, the NFT identified by user A will be referred to as NFT (A1). Purchase refers to the transfer of ownership, regardless of whether it is paid or free. The user terminal 300 receives contract address Y.

[0062] In step S103, the wallet connection unit 233 of the DApps server 200 sends a connection request to User A's crypto asset wallet (hereinafter simply referred to as a wallet connection request) to the DApps application of the user terminal 300. The connection request includes transmission of the contract address Y of the NFT (A1).

[0063] In step S104, user A calls the wallet management app from the DApps app on the user terminal 300 as a response operation to the connection request in step S103. Specifically, when the DApps app in the user terminal 300 receives the connection request in step S103, it uses the function of the inter-app link unit 351 of the user terminal 300 to search for linkable apps present in the user terminal 300 and displays them on the user terminal 300 so that user A can select them. In this embodiment, the wallet management app is displayed so that user A can select it. When user A selects the wallet management app, the inter-app link unit 351 links the DApps app and the wallet management app, enabling the exchange of information between the two apps in accordance with predetermined rules.

[0064] In step S105, in the user terminal 300, the wallet management app obtains the contract address Y received from the DApps app in step S103, and transmits it to the wallet management server 100. The wallet management server 100 receives the contract address Y.

[0065] In step S106, the generation unit 132 of the wallet management server 100 generates a wallet address from user A's user ID (A), contract address Y, and index (1), and generates a new first dedicated wallet Way (1) having the wallet address (generation process).

[0066] In step S107, the provider 134 of the wallet management server 100 permits the first dedicated wallet Way(1) generated in step S106 to be connected to the DApps (provision process). This completes the connection between the DApps and the first dedicated wallet Way(1).

[0067] In step S108, the recording unit 234 of the DApps server 200 requests a signature to be recorded in the blockchain 400 on the DApps app of the user terminal 300 regarding User A's purchase of the NFT (A1) on the DApps.

[0068] In step S109, the wallet management app in the user terminal 300 accepts input from user A regarding the generation and transmission of a signature for the purchase of NFT (A1) (provision process). At this time, a notice to warn the user may be displayed on the user terminal 300, for example, stating, "Performing this operation poses a risk of theft of the private key by a quantum computer for the wallet of this address." The service management app generates a signature S for the first dedicated wallet Way(1) and transmits it to the DApps server 200 via the DApps app (provision process). The recording unit 234 of the DApps server 200 receives the signature S from the user terminal 300. Here, all dedicated wallets generated by the generation unit 132 have the transaction generation and transmission functions disabled by default at the time of generation, with only the signature generation function enabled. When purchasing NFT(A), it is necessary to record the transaction in the blockchain 400 using the signature S of the first dedicated wallet Way(1), so the transfer unit 136 changes the transaction generation and transmission functions for the first dedicated wallet Way(1) to enabled.

[0069] In step S110, the DApps server 200 requests the blockchain 400 to record the purchase of user A's NFT (A1) based on the signature S received in step S109.

[0070] In step S111, the blockchain 400 performs the recording requested in step S110, and when the recording is complete, it sends a recording completion notification to the DApps server 200. The DApps server 200 receives the recording completion notification and displays the recording in the DApps app of the user terminal 300. The notification is shared with the wallet management server 100 via the inter-app link.

[0071] In step S112, the transfer unit 135 of the wallet management server 100 determines whether a transaction related to an NFT held by the first dedicated wallet Way (1) has been sent (transfer process). If the determination result is true (Yes), that is, if a transaction has been sent, the process proceeds to step S113. On the other hand, if the determination result is false (No), that is, if a transaction has not been sent, the process ends.

[0072] In step S113, the transfer unit 135 of the wallet management server 100 causes the generation unit 132 to generate a second dedicated wallet Way(2) corresponding to the NFT(A1) (transfer process). At this time, the generation unit 132 generates a wallet address of the second dedicated wallet Way(2) from the user ID(A), the contract address Y, and the incremented index(2).

[0073] In step S114, the transfer unit 135 transfers the NFT (A1) held by the first dedicated wallet Way (1) to the second dedicated wallet Way (2) (transfer process).

[0074] Steps S112 and after are executed for each transaction that occurs after the first dedicated wallet (1) is generated.

[0075] 8 is a flowchart showing the operation of the possession proof process of the information processing system 1. Note that user A is in a state where he or she can use the service providing app provided by the service providing server 500 on his or her user terminal 300.

[0076] Step S201 is the same as step S101 in the dedicated wallet provision process, and therefore a description thereof will be omitted.

[0077] In step S202, user A requests the provision of service T, which requires the possession of a specific NFT, on the service provision app on the user terminal 300. Hereinafter, the specific NFT will be referred to as NFT(A2). Situations in which possession of an NFT is required include, for example, viewing NFT art linked to the NFT or using it as a token gate.

[0078] In step S203, the service providing server 500 transmits a proof of possession request for the NFT (A2) to the service providing app of the user terminal 300. The proof of possession request includes the contract address Z of the NFT (A2).

[0079] Step S204 is the same as step S104 in the dedicated wallet provision process, and therefore a description thereof will be omitted.

[0080] In step S205, in the user terminal 300, the wallet management application obtains the contract address Z of the NFT (A2) from the service providing server 500 and transmits it to the wallet management server 100. The wallet management server 100 receives the contract address Z.

[0081] In step S206, the wallet management server 100 identifies the wallet address using the contract address Z received in step S205. Specifically, the selection unit 133 of the wallet management server 100 generates a group of wallet addresses from the user ID (A) of user A, the contract address Z, and an index within a predetermined range. The predetermined range of the index is, for example, from 1 to 10.

[0082] In step S207, the selection unit 123 refers to the wallet table 122B of the database 122 and queries the wallet address group. If any wallet address in the wallet address group is found in the wallet table 122B, the selection unit 133 selects that wallet address as the dedicated wallet for the NFT (A2). If there are multiple wallet addresses, the selection unit 133 selects the wallet address with the highest index value as the dedicated wallet for the NFT (A2). If there is no dedicated wallet, the selection unit 133 notifies the user terminal 300 that there is no dedicated wallet that holds the NFT of contract address Z, and ends the proof-of-possession process.

[0083] Step S208 is the same as step S109 in the dedicated wallet provision process, and therefore a description thereof will be omitted.

[0084] In step S209, at user terminal 300, the user transmits the signature that can be generated by the dedicated wallet selected in step S207 and connected in step S208 as proof of possession to service providing server 500. Service providing server 500 receives the signature as proof of possession.

[0085] In step S210, the service providing server 500 in the user terminal 300 provides the user A with the service requested in step S202.

[0086] <Basic computer configuration> 9 is a block diagram showing the basic hardware configuration of a computer 900. The computer 900 has a processing unit 901, a storage unit 902, a communication unit 903, an input unit 904, and an output unit 905. The processing unit 901, the storage unit 902, the communication unit 903, the input unit 904, and the output unit 905 are electrically connected to one another via a communication bus 910.

[0087] The processing unit 901 includes a CPU (Central Processing Unit, also called a processor), and is a device that controls each unit of the computer 900 and reads and executes various programs stored in the storage unit 902 .

[0088] The storage unit 902 includes a main storage device such as a DRAM (Dynamic Random Access Memory) and an auxiliary storage device such as a hard disk, and is a device that stores various programs for executing the operating system and various applications of the computer 900, as well as data used by these programs. The processing shown in the various flowcharts described above is realized by the processing unit 901 of each of the computers constituting the wallet management server 100, the DApps server 200, the user terminal 300, and the blockchain 400 executing the programs stored in their respective storage units 902.

[0089] The communication unit 903 is a device for communicating with external devices, and transmits and receives data according to instructions from the processing unit 901. Each of the computers constituting the wallet management server 100, the DApps server 200, the user terminal 300, the blockchain 400, and the service providing server 500 uses this communication unit 903 to communicate with other devices, including the network 5 shown in FIG.

[0090] The input unit 904 is a device that receives input from outside and supplies it to the processing unit 901, and is configured to include, for example, a keyboard, a mouse, a touch panel, and a camera. The output unit 905 is a device that outputs the processing results of the processing unit 901 to the outside, and is configured to include, for example, a display and a speaker.

[0091] <Program> Here, the programs for realizing the functions constituting the wallet management server 100 according to this embodiment will be described in detail.

[0092] The wallet management server 100 is implemented in a computer 900. The operation of each component of the wallet management server 100 is stored in the form of a program in the auxiliary storage device of the storage unit 902. The processing unit 901 reads the program from the auxiliary storage device of the storage unit 902, loads it into the main storage device of the storage unit 902, and executes the above-mentioned processing in accordance with the program. The processing unit 901 also allocates a storage area corresponding to the above-mentioned storage unit 120 in the main storage device of the storage unit 902 in accordance with the program.

[0093] Specifically, the program is a program executed by an information processing system on a computer 900 that provides a wallet that connects to a service that uses blockchain technology, and causes a computer having a processor and a memory unit to execute a generation step of generating a different dedicated wallet for each activity of the service, in association with one user, and a provision step of providing the dedicated wallet so that it can be connected to the service.

[0094] The auxiliary storage device of storage unit 902 is an example of a non-transitory tangible medium. Other examples of non-transitory tangible media include a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, and a semiconductor memory connected via input unit 904. Furthermore, when this program is distributed to computer 900 via network 5, computer 900 that receives the program may load the program into the main storage device of storage unit 902 and execute the above-described processing.

[0095] The program may also be a program for realizing some of the above-described functions. Furthermore, the program may be a so-called differential file (differential program) that realizes the above-described functions in combination with another program already stored in the auxiliary storage device of the storage unit 902.

[0096] <Effects of the embodiment> As explained above, the wallet management server 100 acquires the contract address corresponding to the NFT that the user requests to use (accesses), generates a dedicated wallet for each NFT, and automatically selects the dedicated wallet corresponding to the contract address, allowing the user to use a dedicated wallet for each NFT. In this way, by using an NFT using a dedicated wallet for each NFT, it becomes difficult to check the usage history of anything other than the NFT, which is the unit of service usage. Furthermore, by automatically switching dedicated wallets seamlessly for users, user convenience can be improved.

[0097] FIG. 10 is a diagram showing the conventional relationship between a single wallet and the recording of transactions related to the use of a service that uses blockchain technology. FIG. 11 is a diagram showing the relationship between a dedicated wallet according to the first embodiment of the present disclosure and the recording of transactions related to the use of the service. Note that Service 1, Service 2, and Service 3 are common between FIG. 10 and FIG. 11. NFTs correspond to activities. Furthermore, each service is, for example, a DApp, and has one or more NFTs.

[0098] In the conventional example of FIG. 10 , a user has one wallet Wa and one wallet address WAa corresponding to wallet Wa, and connects wallet Wa to three different services: Service 1, Service 2, and Service 3. When a user requests a transaction or operation related to NFT1, for example, in Service 1, Service 1 records information including the address of NFT1 and the user's wallet address WAa in Data 1 on the blockchain. Similarly, when a user requests a transaction or operation related to NFT2, for example, in Service 2, Service 2 records information including the address of NFT2 and the user's wallet address WAa in Data 2 on the blockchain. Similarly, when a user requests a transaction or operation related to NFT3 and NFT4, for example, in Service 3, Service 3 records information including the address of NFT3 and wallet address WAa in Data 3 on the blockchain, and information including the address of NFT4 and wallet address WAa in Data 4. As shown in Figure 10, with the conventional method, all usage history can be confirmed simply by looking at the records on the blockchain for the user's wallet address WAa, even if it is provided by different service providers or for different activities.

[0099] In this embodiment shown in Figure 11, a user can have multiple dedicated wallets for each NFT (each activity). That is, the user can have dedicated wallet W1 and its wallet address WA1 for NFT1 of service 1, dedicated wallet W2 and its wallet address WA2 for NFT2 of service 2, dedicated wallet W3 and its wallet address WA3 for NFT3 of service 3, and dedicated wallet W4 and its wallet address WA4 for NFT4 of service 3. When a user requests a transaction or operation related to each NFT, the wallet address of each dedicated wallet and the address of each NFT are recorded on the blockchain. As described above, in the present embodiment illustrated in FIG. 11, a different dedicated wallet is used for each activity, making it difficult to grasp the entire usage history of user A's BC service.

[0100] Furthermore, according to the information processing system 1 of this embodiment, even if a BC service other than the DApps that manage NFTs requests proof of ownership to confirm that user A owns an NFT, the contract address of the NFT can be used to select a dedicated wallet corresponding to the NFT and provide a signature as proof of ownership.

[0101] In this embodiment, the dedicated wallet is created with the transaction generation and sending functions disabled by default, and only the signature function enabled, making the dedicated wallet secure against quantum threats, as described below.

[0102] The quantum threat refers to the threat that, as quantum computers continue to be developed, it may become possible to recover private keys from the signatures of cryptographic methods used in major blockchains, exposing the risk of theft of cryptographic assets and other assets stored in wallets linked to private keys. All transactions written to the blockchain require a signature from the externally owned account that initiated the transaction, and this signature and the externally owned account are accessible to anyone, so if a transaction has been initiated and written even once, it could be exposed to a quantum threat. Conversely, wallets that have never written a transaction will remain safe even after a quantum threat.

[0103] Each dedicated wallet disclosed in this disclosure holds only one or a small number of specific assets. In particular, for NFTs, the majority of usage scenarios involve receiving assets in a specific dedicated wallet and simply verifying ownership using that wallet, so no transaction writes occur. Furthermore, since transaction writes are disabled by default in the dedicated wallets generated in this disclosure, no transaction writes occur unless the user performs any voluntary action (voluntarily enabling the disablement).

[0104] In the conventional wallet usage pattern shown in Figure 10, an unspecified number of FTs and NFTs are held in a single wallet, so the probability of no write transactions occurring is extremely low, and as a result, all assets are subject to quantum threats. On the other hand, in the case of the present disclosure, as described above, because asset holdings are separated and assets for which write transactions occur are rare, only a specific small number of assets are subject to quantum threats, and other assets are protected. In particular, for assets used for public authentication such as DID, using a dedicated wallet with default settings will enable permanent operation of signatures without being affected by quantum computers.

[0105] In addition, the dedicated wallet of this embodiment is generated using any one or a combination of MPC (Multi Party Computing), TSS (Threshold Signing Scheme), and HD Wallet (Hierarchical Deterministic Wallet), which makes it possible to (1) achieve signatures using a large number of different private keys at low cost, (2) achieve high security by managing them separately among multiple entities, and (3) utilize existing ecosystems as they are by implementing them using existing standard interfaces. Users also benefit from the following: (5) wallets can be managed in an integrated manner using existing sign-ins; (6) dedicated wallets are automatically assigned to NFTs when acquiring or inquiring about them, allowing users to use them without being aware of the dedicated wallet; (7) unauthorized use is impossible if only the information stored on the user's side is leaked; (8) operation is possible if the device (app) itself is in a state where it can be operated, but subsequent leakage can be prevented by deactivating or resetting the information on the server side; (9) unauthorized use is impossible if only the information stored on the service provider's side is leaked; and (10) a backup processing system is provided, making it possible to issue new signature data in the event of loss.

[0106] According to the information processing system 1 of this embodiment, when a transaction related to an NFT corresponding to a first dedicated wallet is recorded in the blockchain 400 using the wallet address of the first dedicated wallet, a second dedicated wallet is generated and the NFT is transferred.

[0107] In this way, the information processing system 1 according to the present disclosure can improve user convenience while reducing the risk of personal information leakage when using a service that records user transactions and operations on a blockchain.

[0108] <Modification> Although the embodiments of the present disclosure have been described above, these embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are intended to be included in the scope of the inventions and their equivalents as defined in the claims, as well as in the scope and spirit of the inventions.

[0109] For example, in the above-described embodiment, multiple wallets can be generated for each activity based on the user ID, activity identifier, and index, but only a single dedicated wallet may be generated for an activity based only on the user ID and activity identifier. Also, a single dedicated wallet may be generated initially, and then switched to generate multiple dedicated wallets as needed. Switching between single and multiple may be based on, for example, the occurrence of a transaction being recorded on the blockchain 400, the type and importance of the crypto assets held in the dedicated wallet, the type of BC service that manages the crypto assets, etc. This will increase the flexibility in designing and operating wallet management services.

[0110] In the above-described embodiment, the transfer unit 135 transfers the NFT from the first dedicated wallet to the second dedicated wallet, but it may also transfer some or all of the other crypto assets held in the first dedicated wallet. For example, it may transfer only the NFT without transferring the FT.

[0111] In the above-described embodiment, the activity is an NFT, and the activity identifier is the contract address of the NFT. A unit of activity may be the DApp itself, an NFT project within the DApp, or an NFT (Non-Fungible Token) or digital asset issued and managed by the DApp, or an externally owned account (EOA) corresponding to such an NFT or digital asset.

[0112] 12 is a diagram showing types of activity identifiers and characteristics of each type. The types of activity identifiers can be classified into, for example, URLs, NFT project identifiers, and NFT identifiers.

[0113] The URL treats the DApp website as the unit of use for the dedicated wallet, and the URL itself can be reused as a unique activity identifier. This has the advantage that there is no need to change the specifications or programs on the DApp side when applying the wallet management service. On the other hand, if multiple NFTs or other digital assets are provided using the same URL, it has the disadvantage that all of these transaction records on the blockchain can be tracked. The URL can be obtained using JavaScript or as a standard message when connecting to a website. When the type is URL, the NFT information held in database 122 can include information on multiple NFTs for one dedicated wallet.

[0114] The NFT project identifier is used as the unit of use for the dedicated wallet for the DApp's NFT project, and the NFT project identifier assigned by the DApp can be used as an activity identifier. The NFT project can be used as the distribution unit for NFTs. Using the NFT project as the unit of use for the service has the advantage that it is suitable for issuing and distributing multiple NFTs related to the project within the NFT project. On the other hand, as with URLs, it has the disadvantage that tracking between NFTs within the NFT project is unavoidable. When the type is an NFT project, the NFT information held in database 122 can include information about multiple NFTs for one dedicated wallet.

[0115] The NFT identifier uses the NFT as the unit of use for the dedicated wallet, and the NFT contract address can be used as the identifier. Since a dedicated wallet is assigned to each NFT, this has the advantage of making it easy to avoid tracking between NFTs. On the other hand, it has the disadvantage that if the NFT specifications are not yet finalized, the type cannot be selected. When the type is NFT, the NFT information held in database 122 contains information about one NFT for one dedicated wallet.

[0116] The type of activity identifier may be the URL or NFT project identifier described above, or a combination of these. However, if the granularity of the activity identifier is greater than that of an NFT, the risk of personal information leakage and quantum threats increases compared to creating a dedicated wallet for each NFT.

[0117] 13 is a sequence diagram showing the operation of the dedicated wallet provision process according to a modified example of an embodiment of the present disclosure. Specifically, this is a sequence diagram showing the operation of the dedicated wallet provision process when the activity identifier is a URL or an NFT project identifier (when the granularity of the activity identifier is larger than that of an NFT). In this case, one dedicated wallet can hold multiple NFTs.

[0118] The sequence diagram in FIG. 13 will be described in the case where the activity identifier is a URL. In the dedicated wallet provision process of this modified example, in step S302, a purchase request can be sent by specifying multiple NFTs in the URL. Alternatively, after one NFT is purchased and a first dedicated wallet (1) is generated, one or more NFTs can be purchased using the first dedicated wallet (1). The first dedicated wallet (1) is generated using the activity identifier as a URL. In step S312, it is determined whether a transaction has been sent for at least one NFT in the first dedicated wallet (1). In step S314, for example, NFTs other than the NFT for which a transaction was sent in step S312 may be transferred to the second dedicated wallet (2). The other steps are the same as those in the embodiment shown in FIG. 7, and therefore description thereof will be omitted.

[0119] Figure 14 is an example of a screen displayed on the user terminal 300 during the transfer process. Specifically, this is an example of a screen when the type of activity identifier is a URL or an NFT project identifier, and NFTs other than the NFT for which the transaction transmission occurred are transferred to the second dedicated wallet (2) in step S314 of Figure 13. The example screen shown in FIG. 14(a) is a screen displayed on the wallet management app on user A's user terminal 300 when a transfer process is executed. In the example shown in FIG. 14, user A's existing first dedicated wallet W1 holds NFTs (A) through (D), and user A transfers ownership of NFT (A) to a third party. On the screen shown in FIG. 14(a), the wallet address of the first dedicated wallet W1 used to record the transaction is displayed under "Source Wallet Address," and the wallet address of the third-party wallet to which the NFT is to be transferred is displayed under "Destination Wallet Address." When user A selects "Confirm" on this screen, the screen transitions to the screen shown in FIG. 14(b). The screen shown in FIG. 14(b) displays a note stating that the NFT (A) that user A wishes to transfer will be sent to the third-party wallet address displayed on the previous screen, and the other NFTs will be transferred to the wallet address of the newly created second dedicated wallet W2. When user A selects "Execute transfer" on the screen of Fig. 14(b), the process of transferring the asset illustrated in Fig. 14(c) (the process indicated by the note in Fig. 14(b)) is executed by the information processing system 1, and when the process is completed, the screen changes to the screen shown in Fig. 14(d). The screen of Fig. 14(d) notifies user A that the transfer process has been completed. This allows the transferred NFTs (B) to (D) to be managed in a dedicated wallet, W2, which has never initiated a transaction with the crypto assets held, and also protects them from quantum threats. If a service that only reads the authentication system is used in the same wallet as a recording service, the private key can be restored by a quantum computer, preventing "spoofing."

[0120] In the above embodiment, the wallet management server 100 obtained an existing NFT contract address determined independently of the wallet management service as an activity identifier from the DApps server 200 (via the user terminal 300), but the activity identifier may also be one that the wallet management service has pre-assigned to each activity of the DApps. Specifically, the operator of each DApp embeds the assigned activity identifier in the HTML header of the DApp. The activity identifier can be, for example, a UUID (Universally Unique Identifier). A UUID is a 128-bit identifier that is randomly and uniquely generated in a standardized format, and can be generated, for example, based on the UUID v4 standard, which uses random values.

[0121] Assigning an activity identifier to a DApps activity and obtaining an activity identifier from a DApps activity may be performed, for example, by the following procedure. (1) Each DApps operator registers their DApp (URL, description, NFT contract address, etc.) on the management screen of the wallet management service and applies for review. (2) The wallet management service will examine the content of the DApps and determine whether they comply with laws, regulations, and public order and morals. After that, it will determine and assign an activity identifier and display the specified message on the management screen. (3) Each DApps operator embeds the specified message in the HTML header of the DApp. This allows you to crawl the registered URL of a DApp in advance via the wallet management app when a wallet connection request is made from the DApp, or after the DApp is launched, and obtain the activity identifier in the HTML header.

[0122] Alternatively, a database relating to the URL of a DApp, the NFT (or NFTs) handled by that URL, and the activity identifier assigned by the wallet management server 100 may be generated in advance, and the wallet management server 100 may voluntarily obtain the URL of the DApp, identify the activity identifier, and provide a dedicated wallet. The database may be updated during service operation. (1) The wallet management server 100 extracts and lists the URLs (or groups of URLs) of DApps with many users. (2) For each listed DApp URL, the wallet management server 100 obtains the details of the DApp and the NFT contract address of the NFT handled by the DApp, assigns a unique activity identifier to each URL, and stores the information in a database. As a result, when a DApp makes a wallet connection request to the wallet management service, the wallet management server 100 can obtain the URL of the DApp and identify the activity identifier corresponding to that URL. Also, by providing dedicated wallets only to DApps registered as whitelists using the above procedure, abuse of dedicated wallets can be prevented.

[0123] NFTs held in the dedicated wallet of the wallet management service in the above-described embodiment may also be transferred to an external party. The wallet management server 100 uses a service that references data on the blockchain 400, such as an explorer or remote procedure call (RPC), to inquire about NFT receipt information linked to the wallet address of each user's existing dedicated wallet (or differentials in the case of updates), link each wallet address with the held NFT / FT information, and update the database 122. This improves user convenience.

[0124] Furthermore, some or all of the functions of the wallet management server 100 in the above-described embodiment may be implemented in a wallet management application running on the user terminal 300.

[0125] In step S207 of the above-described embodiment, if the index value is the maximum value in the predetermined range, the process may return to step S206, generate a set of wallet addresses for the next predetermined range, and proceed to step S207 to query the set of wallet addresses in the next predetermined range. This reduces the amount of calculation required for the set of wallet addresses, while enabling selection even for dedicated wallets that undergo a large number of transfer processes.

[0126] In the above-described embodiment, the transaction recording function of all generated dedicated wallets is disabled by default, and only the signature function is enabled. However, this is not limited to this. For example, if the transaction recording function is also enabled by default, and a user who owns a dedicated wallet needs to record a transaction that transfers crypto assets (assets) held in the dedicated wallet to a third party, a notice such as that in step S110 described above may be presented to the user to warn them, and the transaction recording may be performed only after obtaining the user's consent.

[0127] The operational flows and operational examples in the above-described embodiments do not necessarily have to be executed in chronological order according to the order shown in the flow diagrams. For example, steps in the operations may be executed in an order different from that shown in the flow diagrams, or may be executed in parallel. Furthermore, some steps in the operations may be deleted, or additional steps may be added to the process.

[0128] <Additional Notes> The matters explained above are further noted below. (Appendix 1) An information processing method executed by an information processing system that provides a wallet connected to a service using blockchain technology, a generation step of generating a dedicated wallet associated with one user and different for each activity of the service; a providing step of providing the dedicated wallet so that it can be connected to the service; An information processing method comprising: This allows for activity-specific records to be separated on the blockchain. (Appendix 2) and a selection step of switching the wallet for connecting to the service to the dedicated wallet according to the activity. 1. The information processing method described in Appendix 1. This allows users to automatically switch between dedicated wallets for each activity. (Appendix 3) the generating step uniquely generates the dedicated wallet based on a user identifier of the user and an activity identifier that identifies the activity; 10. The information processing method according to claim 1 or 2. This makes it easy to create and manage dedicated wallets for each user and activity. (Appendix 4) The generating step further includes uniquely generating the plurality of dedicated wallets based on an index. 1. The information processing method described in Appendix 3. This makes it easy to create and manage multiple dedicated wallets for each activity. (Appendix 5) a transfer step of transferring assets held in a first dedicated wallet corresponding to the activity to a second dedicated wallet corresponding to the activity, 1. The information processing method described in Appendix 4. This allows you to manage your assets in multiple dedicated wallets that have different wallet addresses but correspond to the same activity. (Appendix 6) the generating step uniquely generates the dedicated wallet based on a user identifier of the user and an activity identifier that identifies the activity; The selecting step acquires an activity identifier of an activity used by the user, and switches the dedicated wallet of the user corresponding to the activity used by the user from among the existing dedicated wallets of the user based on the activity identifier. 1. The information processing method described in Appendix 2. This allows users to automatically switch between dedicated wallets for each activity. (Appendix 7) The determining step acquires the activity identifier from a URL of the service. 1. The information processing method described in Appendix 6. This allows the activity identifier to be easily obtained. (Appendix 8) the generating step generates the dedicated wallet with a transaction sending function disabled; 8. An information processing method according to any one of appendices 1 to 7. This allows for the signature to operate in perpetuity while protecting against quantum threats. (Appendix 9) the transfer step, when a transaction is sent for a non-fungible token held in the first dedicated wallet, generates the second dedicated wallet and transfers the crypto asset held in the first dedicated wallet to the second dedicated wallet; 1. The information processing method described in Appendix 5. This allows assets to be managed in dedicated wallets that never record transactions on the blockchain, protecting them from quantum threats. (Appendix 10) The providing step provides proof of asset possession using the second dedicated wallet. 10. The information processing method according to claim 9. This will enable the permanent operation of signatures without being affected by quantum computers. (Appendix 11) The generating step generates the dedicated wallet using any one or a combination of MPC (Multi Party Computing), TSS (Threshold Signing Scheme), and HD wallet (Hierarchical Deterministic Wallet). 11. An information processing method according to any one of appendices 1 to 10. This makes it easy to create and manage a large number of dedicated wallets. (Appendix 12) A program executed by an information processing system that provides a wallet connected to a service using blockchain technology, a generation step of generating a dedicated wallet associated with one user and different for each activity of the service; a providing step of providing the dedicated wallet so that it can be connected to the service; A program that causes a computer to execute the following. (Appendix 13) An information processing system that provides a wallet connected to a service that uses blockchain technology, a generation unit that generates a dedicated wallet that is associated with one user and that differs for each activity of the service; a providing unit that provides the dedicated wallet so that the dedicated wallet can be connected to the service; An information processing system comprising: (Appendix 14) An information processing device that provides a wallet connected to a service using blockchain technology, a generation unit that generates a dedicated wallet that is associated with one user and that differs for each activity of the service; a providing unit that provides the dedicated wallet so that the dedicated wallet can be connected to the service; An information processing device comprising: [Explanation of symbols]

[0129] 1: Information processing system 5: Network 100: Wallet management server 110: Communications Department 120: Storage section 122: Database 130: Processing section 131: User Management Department 132 :Generation part 133: Selection section 134:Providing Department 135: Transfer section 200: DApps server 230: Processing section 231: User Management Department 232: Activity execution unit 233: Wallet connection part 234: Recording section 300: User terminal 400: Blockchain Network 500: Service provider server

Claims

1. An information processing method executed by an information processing system that provides a wallet connected to a service using blockchain technology, a generating step of generating and providing a dedicated wallet that is associated with one user and that differs for each activity of the service; a providing step of providing the dedicated wallet so that it can be connected to the service; An information processing method comprising:

2. and a selection step of switching the wallet for connecting to the service to the dedicated wallet according to the activity. The information processing method according to claim 1 .

3. the generating step uniquely generates the dedicated wallet based on a user identifier of the user and an activity identifier that identifies the activity; The information processing method according to claim 1 .

4. The generating step further includes uniquely generating the plurality of dedicated wallets based on an index. The information processing method according to claim 3 .

5. a transfer step of transferring assets held in a first dedicated wallet corresponding to the activity to a second dedicated wallet corresponding to the activity, The information processing method according to claim 4.

6. the generating step uniquely generates the dedicated wallet based on a user identifier of the user and an activity identifier that identifies the activity; The selecting step acquires an activity identifier of an activity used by the user, and switches the dedicated wallet of the user corresponding to the activity used by the user from among the existing dedicated wallets of the user based on the activity identifier. The information processing method according to claim 2 .

7. The selecting step includes obtaining the activity identifier from a URL of the service. The information processing method according to claim 6.

8. the generating step generates the dedicated wallet with a transaction sending function disabled; The information processing method according to claim 1 or 5.

9. the transferring step, when a transaction is sent for a non-fungible token held in the first dedicated wallet, generates the second dedicated wallet and transfers the crypto asset held in the first dedicated wallet to the second dedicated wallet; The information processing method according to claim 5 .

10. The providing step includes providing proof of asset possession using the second dedicated wallet. The information processing method according to claim 9.

11. The generating step generates the dedicated wallet using any one or a combination of MPC (Multi Party Computing), TSS (Threshold Signing Scheme), and HD wallet (Hierarchical Deterministic Wallet). The information processing method according to claim 1 .

12. A program executed by an information processing system that provides a wallet connected to a service using blockchain technology, a generation step of generating a dedicated wallet associated with one user and different for each activity of the service; a providing step of providing the dedicated wallet so that it can be connected to the service; A program that causes a computer to execute the following.

13. An information processing system that provides a wallet connected to a service that uses blockchain technology, a generating unit that generates a different dedicated wallet for each activity of the service in association with one user; a providing unit that provides the dedicated wallet so that the dedicated wallet can be connected to the service; An information processing system comprising:

14. An information processing device that provides a wallet connected to a service using blockchain technology, a generating unit that generates a different dedicated wallet for each activity of the service in association with one user; a providing unit that provides the dedicated wallet so that the dedicated wallet can be connected to the service; An information processing device comprising:

Images