Program, server, method, and system
The system addresses security and user burden issues in cryptographic asset management by using multiple servers with fragmented private keys and diverse authentication methods, enhancing security and usability.
Patent Information
- Application Number
- JP2023187475
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-11-01
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2043-11-01
AI Technical Summary
Existing systems for managing cryptographic assets in decentralized networks face security risks due to the potential recovery of private keys through eavesdropping and burden users with key management responsibilities.
A system that includes multiple servers to manage and authenticate user private keys, dividing the keys into fragments and using different authentication methods across servers to reduce security risks and user burden.
The system reduces the risk of cryptographic asset management and eliminates the need for users to manage their own private keys, enhancing security and usability by enabling single sign-on across multiple services.
Smart Images

Figure 0007588364000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a program, a server, a method, and a system. [Background technology]
[0002] There is a technology in which a number of users' node computers and a group of monitoring node computers are connected to an autonomous decentralized network, the users' node computers are equipped with an autonomous decentralized electronic tally wallet execution program that functions as a means of storing virtual currency, and the autonomous decentralized electronic tally wallet execution program generates and divides a private key consisting of a code to protect the stored virtual currency data, and each part of the divided private key is distributed and stored in a number of anonymous node computers randomly selected by one of the monitoring node computers in the group of monitoring node computers, and is regenerated when used (Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2020-155911 A Summary of the Invention [Problem to be solved by the invention]
[0004] The above technology enhances security by storing key fragments in multiple nodes on an autonomous distributed network, so the key fragments are managed in a server under the monitoring of a monitoring node. However, if the communication path of the key fragments is collected by eavesdropping, the private key can be restored, which creates a risk to the management of cryptographic assets. In addition, if the user manages the private key himself, the user is burdened with managing the private key.
[0005] Therefore, the present disclosure provides technology that reduces the management risks of crypto assets and relieves users of the burden of managing private keys. [Means for solving the problem]
[0006] The program of the present disclosure is a system for managing a user's private key used in a blockchain for managing crypto assets, the system including a plurality of servers, the servers having a processor and a memory unit, and a program for operating the servers, the memory unit being configured to store one of the private key encrypted by a user's user terminal and previously divided into a plurality of key fragments, the program causing the processor to execute the steps of receiving a request for the key fragment from the user's user terminal, authenticating the user terminal in response to the request for the key fragment, and transmitting the key fragment to the user terminal in response to successful authentication. Effect of the Invention
[0007] According to the present disclosure, it is possible to reduce the management risks of crypto assets and relieve users of the burden of managing private keys. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a system 1. [Diagram 2] FIG. 2 is a diagram showing the functional configuration of the server 10. As shown in FIG. [Diagram 3] FIG. 3 is a diagram showing the data structure of the database. [Figure 4] FIG. 4 is a diagram showing the data structure of the database. [Diagram 5] FIG. 5 is a diagram showing the functional configuration of the user terminal 20. As shown in FIG. [Figure 6] FIG. 6 is a diagram showing the functional configuration of the storage server 30. As shown in FIG. [Figure 7]FIG. 7 is a diagram showing the data structure of the database. [Figure 8] FIG. 8 is a diagram showing an example of a processing flow in the system 1. [Figure 9] FIG. 9 is a diagram showing an example of a processing flow in the system 1. [Figure 10] FIG. 10 is an image diagram for explaining an example in which the technology of the present disclosure is used. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.
[0010] <1. Embodiment> <1.1. Overall configuration of System 1> System 1 is a system for managing private keys of crypto assets related to the present disclosure.
[0011] As shown in FIG. 1, the system 1 includes a server 10, a user terminal 20, a plurality of storage servers 30 (FIG. 1 shows storage servers 30A and 30B. These are collectively referred to as a server group 3), a provision server 40, and a network 80. The server 10, the user terminal 20, and the provision server 40 are communicatively connected via the network 80. In the present disclosure, an example will be described in which the storage servers 30 included in the server group 3 are servers of different private key management businesses (those who carry out the business of managing private keys of crypto assets). Note that each of the storage servers 30 included in the server group 3 may be configured as belonging to the same private key management business, or some of the storage servers 30 may be configured as belonging to different private key management businesses.
[0012] The server 10 is an information processing device that provides a function for users to log in to services related to crypto assets. The server 10 is realized by a stationary PC (Personal Computer), a laptop PC, etc. The server 10 may also be configured to function as a single server by using multiple servers constructed in a data center or the like.
[0013] As shown in FIG. 1, the server 10 includes a communication IF 12, an input / output IF 13, a memory 15, a storage 16, and a processor 19.
[0014] The communication IF 12 is an interface for inputting and outputting signals so that the server 10 can communicate with an external device. The input / output IF 13 functions as an interface with an input device for receiving an input operation from a user and an output device for presenting information to a user. The input / output IF 13 is for temporarily storing a program and data processed by the program, and is a volatile memory such as a dynamic random access memory (DRAM). The memory 15 is a storage device for saving data, and is a flash memory or a hard disk drive (HDD). The storage 16 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, peripheral circuits, etc. The processor 19 is hardware for executing an instruction set described in a program stored in the memory 15, and is composed of an arithmetic unit, a register, peripheral circuits, etc.
[0015] The user terminal 20 is an information processing device operated by a user who uses the system 1. The user terminal 20 is realized by a mobile terminal such as a smartphone or tablet compatible with a mobile communication system, a stationary PC (Personal Computer), a laptop PC, or the like.
[0016] As shown in FIG. 1, the user terminal 20 includes a communication IF 22, an input / output IF 23, a memory 25, a storage 26, and a processor 29.
[0017] The communication IF 22 is an interface for inputting and outputting signals so that the user terminal 20 can communicate with an external device. The input / output IF 23 functions as an interface with an input device for receiving an input operation from a user and an output device for presenting information to a user. The input / output IF 23 is for temporarily storing a program and data processed by the program, and is a volatile memory such as a dynamic random access memory (DRAM). The memory 25 is a storage device for saving data, and is a flash memory or a hard disk drive (HDD). The storage 26 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, peripheral circuits, etc. The processor 29 is hardware for executing an instruction set described in a program stored in the memory 25, and is composed of an arithmetic unit, a register, peripheral circuits, etc.
[0018] The storage server 30 is an information processing device that exerts a function of managing key fragments obtained by dividing a user's private key. The storage server 30 is realized by a stationary PC (Personal Computer), a laptop PC, or the like. The storage server 30 may also be configured to function as one server by a plurality of servers constructed in a data center or the like.
[0019] As shown in FIG. 1, the storage server 30 includes a communication IF 32, an input / output IF 33, a memory 35, a storage 36, and a processor 39.
[0020] The communication IF 32 is an interface for inputting and outputting signals so that the storage server 30 can communicate with an external device. The input / output IF 33 functions as an interface with an input device for receiving an input operation from a user and an output device for presenting information to a user. The input / output IF 33 is for temporarily storing a program and data processed by the program, and is a volatile memory such as a dynamic random access memory (DRAM). The memory 35 is a storage device for saving data, and is a flash memory or a hard disk drive (HDD). The storage 36 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like. The processor 39 is hardware for executing an instruction set described in a program stored in the memory 35, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.
[0021] The providing server 40 is an information processing device that provides services related to crypto assets. The service in question is, for example, a service that uses a blockchain such as a Web3 wallet. There are various types of blockchain, such as PLT (Palette Token (registered trademark)), ETH (Ethereum), and MATIC (crypto asset polygon). The providing server 40 is realized by a stationary PC (Personal Computer), a laptop PC, or the like. The providing server 40 may also be configured to function as a single server using multiple servers constructed in a data center or the like.
[0022] <1.2. Functional configuration of server 10> 2 is a diagram showing a functional configuration of the server 10. As shown in FIG. 2, the server 10 fulfills the functions of a communication unit 101, a storage unit 102, and a control unit 103.
[0023] The communication unit 101 performs processing for communicating with an external device.
[0024] The storage unit 102 stores data and programs to be used.
[0025] Specifically, the storage unit 102 stores a first DB (database) 121, a second DB 122, and the like.
[0026] The following describes the data structures of the first DB 121 and the second DB 122 stored in the server 10 shown in Figures 3 and 4. Figures 3 and 4 are diagrams showing the data structures of each database.
[0027] The first DB 121 is a database that holds information necessary for authentication regarding services for the user's crypto assets. As shown in Fig. 3, the first DB 121 includes an item "ID", an item "email address", an item "wallet ID", and an item "service ID".
[0028] The item "ID" is information for identifying a user.
[0029] The item "email address" is the user's email address.
[0030] The item "wallet ID" is the wallet ID for the user's cryptocurrency. Specifically, the wallet ID is, for example, a wallet address.
[0031] The item "service ID" is information for identifying a service for which the wallet ID can be used. Specifically, the item "service ID" stores one or more service IDs for one wallet ID.
[0032] The second DB 122 is a database that holds information necessary for authenticating a user's key fragment. As shown in Fig. 4, the second DB 122 includes an item "ID", an item "authentication information", and an item "access token".
[0033] The item "ID" is information for identifying a user.
[0034] The item "authentication information" is information used when performing authentication for exchanging key fragments between the server 10 and the user terminal 20. Specifically, if the authentication is OIDC authentication, the item "authentication information" stores data required for performing OIDC authentication between the OIDC provider's server (not shown) and the user terminal. The item "Access Token" stores information required to issue an access token. The access token may be issued by any method.
[0035] The control unit 103 exerts functions shown as various modules by the processor of the server 10 performing processes according to the programs. The control unit 103 includes a reception control unit 131, a transmission control unit 132, a first authentication unit 133, and the like.
[0036] The reception control unit 131 controls the processing in which the server 10 transmits and receives signals from external devices in accordance with a communication protocol.
[0037] The transmission control unit 132 controls the process in which the server 10 transmits a signal to an external device in accordance with a communication protocol.
[0038] The first authentication unit 133 performs login authentication. Specifically, the first authentication unit 133 receives a login authentication request for a service from the user terminal 20 via the provision server 40 that provides a service related to crypto assets. For example, when the service is accessed from the user terminal 20, the provision server 40 redirects the login authentication to the server 10. The login authentication is login authentication for performing single sign-on for multiple services.
[0039] The first authentication unit 133 requests authentication information required for login authentication from the user terminal 20 based on the login authentication. The authentication information is authentication information used for logging in to the service. Then, when the first authentication unit 133 acquires the authentication information from the user terminal 20, it performs login authentication based on the authentication information. For example, the first authentication unit 133 can use OIDC (OpenID Connect) authentication as the login authentication. In this case, the first authentication unit 133 requests OIDC authentication of the user from an external OIDC provider server (not shown). The first authentication unit 133 performs OIDC authentication by communicating with the OIDC provider server. Then, the first authentication unit 133 acquires an authentication result from the OIDC provider server.
[0040] The first authentication unit 133 transmits a result of the login authentication to the provision server 40. Furthermore, in response to a success of the login authentication, the first authentication unit 133 issues an access token. Then, the first authentication unit 133 transmits the access token to the user terminal 20, thereby requesting the recovery of the private key.
[0041] <1.3. Functional configuration of user terminal 20> Fig. 5 is a diagram showing the functional configuration of the user terminal 20. As shown in Fig. 5, the user terminal 20 includes a communication unit 201 and a storage unit 202, and functions as the storage unit 202.
[0042] The communication unit 201 performs processing for communicating with an external device.
[0043] The storage unit 202 stores data and programs to be used. The storage unit 202 stores in advance, for example, information for logging in to a service, information for performing authentication with each server 10 to obtain key fragments, information required to restore key fragments, a public key corresponding to a private key, and the like.
[0044] The control unit 203 exerts functions shown as various modules by the processor of the user terminal 20 performing processes according to a program. The control unit 203 includes a reception control unit 231, a transmission control unit 232, a service unit 233, a restoration unit 234, an encryption unit 235, and the like.
[0045] The reception control unit 231 controls the processing in which the user terminal 20 transmits and receives signals from external devices in accordance with a communication protocol.
[0046] The transmission control unit 232 controls the process in which the user terminal 20 transmits a signal to an external device in accordance with a communication protocol.
[0047] The service unit 233 exerts a function for allowing the user to use the service provided by the provision server 40. Specifically, the service unit 233 accesses the service in question through a user operation. Next, the service unit 233 logs in to the service in question. By logging in to the service in question, the user becomes able to use the service in question. The service unit 233 executes, for example, a function for logging in to the service in question and the service in question through a browser, an application, or the like.
[0048] The restoration unit 234 restores the private key from the multiple key fragments. Specifically, when logging in to the service, the restoration unit 234 acquires an access token from the server 10. The restoration unit 234 requests the user's key fragment held by each of the multiple storage servers 30 included in the server group 3. At this time, the restoration unit 234 includes the access token in the request for the key fragment. The restoration unit 234 acquires the key fragment from each of the multiple storage servers 30 by succeeding in authentication using the access token. Then, the restoration unit 234 restores the user's private key from the acquired multiple key fragments.
[0049] The restoration unit 234 decrypts the restored private key. Specifically, since the private key restored by the restoration unit 234 is an encrypted private key, the restoration unit 234 decrypts the encrypted private key. At this time, the restoration unit 234 may be configured to perform the decryption process by having the user perform a predetermined operation. The predetermined operation is, for example, an operation in which the user inputs a passcode. In this case, the restoration unit 234 displays a passcode input screen to the user. If the passcode input by the user is correct, the restoration unit 234 decrypts the private key.
[0050] In addition, the restoration unit 234 can also discard the restored private key when the user terminal 20 logs out after logging in through login authentication, or when a predetermined period of time has passed since the private key was restored.
[0051] The encryption unit 235 encrypts the user's private key. Specifically, the encryption unit 235 encrypts the user's private key at any timing using a predetermined encryption method. The encryption unit 235 encrypts the private key, for example, by a user's operation. The encryption unit 235 divides the encrypted private key into key fragments. Then, the encryption unit 235 deposits the key fragments in each storage server 30 that manages the key fragments.
[0052] <1.4. Functional configuration of storage server 30> 6 is a diagram showing the functional configuration of the storage server 30. As shown in FIG. 6, the storage server 30 fulfills the functions of a communication unit 301, a storage unit 302, and a control unit 303.
[0053] The communication unit 301 performs processing for communicating with an external device.
[0054] The storage unit 302 stores data and programs to be used. Specifically, the storage unit 302 stores a third DB (database) 321 and the like.
[0055] The following describes the data structure of the third DB 321 stored in the storage server 30 shown in Fig. 7. Fig. 7 is a diagram showing the data structure of a database. The third DB 321 is a database that holds key fragments of users. As shown in Fig. 7, the third DB 321 includes an item "ID", an item "key fragment", and an item "authentication information".
[0056] The item "ID" is information for identifying a user.
[0057] The item "key fragment" is a key fragment obtained by dividing a private key encrypted by a user and stored in the storage server 30. The private key of the user is encrypted in advance by the user terminal 20. This encrypted private key is divided into key fragments in advance. Any method can be used as the division method.
[0058] The item "authentication information" is information used when performing authentication for exchanging key fragments between the storage server 30 and the user terminal 20. Specifically, the item "authentication information" stores information required to verify whether the access token generated by the server 10 is correct.
[0059] The control unit 303 exerts functions shown as various modules by the processor of the storage server 30 performing processes according to the programs. The control unit 303 includes a reception control unit 331, a transmission control unit 332, a second authentication unit 333, a key management unit 334, and the like.
[0060] The reception control unit 331 controls the processing in which the storage server 30 transmits and receives signals from external devices in accordance with a communication protocol.
[0061] The transmission control unit 332 controls the process in which the storage server 30 transmits a signal to an external device in accordance with a communication protocol.
[0062] In response to a request for a key fragment from a user terminal 20, the second authentication unit 333 performs authentication for the user terminal.
[0063] Specifically, when the second authentication unit 333 receives the request for the key fragment from the user terminal of the user, the second authentication unit 333 verifies the access token included in the request for the key fragment. The second authentication unit 333 verifies whether the access token is a valid one issued by the server 10.
[0064] The second authentication unit 333 may perform authentication with the user terminal 20 by a method other than the access token. In this case, it is preferable that the authentication method is different for each storage server 30. This is because each storage server 30, for example, the storage server 30A and the storage server 30B, are managed by different business operators. Even if the storage server 30A and the storage server 30B are managed by the same business operator, different authentication methods may be used. Also, the storage server 30 may adopt an authentication method different from at least the other storage servers 30. Each storage server 30 and the user terminal 20 may be configured such that information for performing the authentication is stored in advance and the process for performing the authentication can be executed via communication by each authentication method. For example, password authentication can be used as the authentication method. By using a different authentication method for each storage server 30, even if one of the communication between each storage server 30 and the user terminal 20 is eavesdropped, it is difficult for an eavesdropper to restore the private key. This reduces the risk of storing the private key in a single storage server.
[0065] If the authentication by the second authentication unit 333 is successful, the key management unit 334 transmits the key fragment to the user terminal 20.
[0066] Specifically, in response to a successful authentication, the key management unit 334 acquires a key fragment from the third DB 321. Then, the key management unit 334 transmits the key fragment to the user terminal 20.
[0067] <1.5. System 1 processing flow> Next, the process flow of the system 1 will be described.
[0068] 8 and 9 show an example of a processing flow in the system 1. In FIG.
[0069] In step S601, the user terminal 20 accesses the blockchain service to be used. Specifically, the user terminal 20 accesses the providing server 40 that provides the blockchain service to be used by a predetermined application.
[0070] In step S603, the provision server 40 redirects the login authentication to the server 10. Specifically, when a service provided by the provision server 40 is accessed from the user terminal 20, the provision server 40 redirects the login authentication to the server 10 that performs predetermined login authentication.
[0071] In step S605, the server 10 requests the user terminal 20 for authentication information required for login authentication.
[0072] Specifically, when the server 10 is redirected by the provision server 40 for login authentication, the server 10 requests the user terminal 20 for authentication information required for login authentication.
[0073] In step S607, the user terminal 20 transmits the authentication information to the server 10.
[0074] In step S609, the server 10 performs login authentication.
[0075] Specifically, the first authentication unit 133 of the server 10 requests an external OIDC provider server to perform OIDC authentication of the user. The first authentication unit 133 performs OIDC authentication by communicating with the OIDC provider server. Then, the first authentication unit 133 obtains an authentication result from the OIDC provider server. Furthermore, if the authentication is successful, the first authentication unit 133 issues an access token.
[0076] In step S611, the server 10 transmits the result of the login authentication to the provision server 40.
[0077] In step S613, the server 10 transmits the access token to the user terminal 20.
[0078] Specifically, the first authentication unit 133 of the server 10 requests the user terminal 20 to restore the private key by transmitting an access token to the user terminal 20 in response to a successful login authentication result.
[0079] In step S615, the user terminal 20 performs a process of restoring the private key, the details of which will be described later.
[0080] In step S617, in response to the successful login authentication, the provision server 40 provides a service to the user terminal.
[0081] The user can then use the private key restored by the user terminal 20 to use the crypto asset for the blockchain services provided by the provision server 40.
[0082] FIG. 9 is a flowchart showing the private key restoration process in step S615.
[0083] In step S701, the user terminal 20 requests each of the storage servers 30 for the key fragment held by that server 10.
[0084] Specifically, the restoration unit 234 of the user terminal 20 requests the key fragment of the user together with the access token from each of the storage servers 30 included in the server group 3 that manages the key fragments.
[0085] In step S703, the storage server 30 receives the request for the key fragment.
[0086] In step S705, the storage server 30 performs authentication for the user terminal 20.
[0087] Specifically, in response to receiving a request for the key fragment from the user terminal 20, the second authentication unit 333 of the storage server 30 verifies whether the access token is the correct one issued by the server 10.
[0088] In step S707, in response to a successful authentication, the storage server 30 transmits the key fragment to the user terminal.
[0089] Specifically, if the verification result is correct, the second authentication unit 333 of the storage server 30 acquires the key fragment from the third DB 321. Then, the second authentication unit 333 transmits the key fragment to the user terminal 20.
[0090] In step S709, the user terminal 20 obtains the key fragment from each of the multiple storage servers 30.
[0091] In step S711, the user terminal 20 restores the encrypted private key from the multiple key fragments.
[0092] Specifically, the restoration unit 234 of the user terminal 20 restores the encrypted private key in response to acquiring all the key fragments.
[0093] In step S713, the user terminal 20 displays a passcode input screen for the user.
[0094] In step S715, the user terminal 20 accepts input of a passcode from the user.
[0095] In step S717, in response to the input of the correct passcode, the user terminal 20 decrypts the encrypted private key.
[0096] In step S719, the user terminal 20 transmits a restoration success notification to the server 10 in response to the success in restoring the private key. The restoration process in step S615 may be performed at any time after the login authentication is successful.
[0097] <1.6. Examples of using the technology disclosed herein> Next, an example using the technology of the present disclosure will be described with reference to Fig. 10. Fig. 10 is an image diagram for explaining this embodiment.
[0098] 10, user terminal 20 is a user terminal operated by user A. User A has two wallet addresses. Wallet address 0x111111 is used for a blockchain service provided by company X. Wallet address 0x222222 is used for a blockchain service provided by company Y.
[0099] Company X provides multiple blockchain services. The provision server 40A and the provision server 40B correspond to the above-mentioned provision server 40. The provision server 40A provides a blockchain service X1, and the provision server 40B provides a blockchain service X2.
[0100] Company Y provides multiple blockchain services. The provision server 40C corresponds to the above-mentioned provision server 40. The provision server 40C provides a blockchain service Y1.
[0101] In the example of Figure 10, when user A accesses blockchain service X1, server 10 performs login authentication with OIDC provider 50, and the processing described above is performed, so that user terminal 20 automatically obtains key fragments of the private key from server group 3 and restores the private key.
[0102] User A can use the blockchain service X1 by using the restored private key. This allows User A to reduce the management risk of crypto assets and relieve the burden of managing the private key by splitting the private key, which was encrypted in advance by the user terminal 20, into key fragments and managing them on the servers of multiple private key management businesses.
[0103] Furthermore, the login authentication is single sign-on. This login authentication allows user A to use blockchain service X1 and blockchain service X2. While logged in, user A can use blockchain service X2 with the same wallet ID and the restored private key for the same crypto asset.
[0104] The above single sign-on may also be used to allow the use of blockchain service Y1 provided with a different wallet address. In this case, if user A performs a process to switch to blockchain service Y1, he or she can use blockchain service X2 for the same crypto asset while logged in, using the restored private key. This is particularly useful when different companies, such as X and Y companies, require separate management of wallet addresses, since it allows users to switch services without the trouble of managing private keys.
[0105] <1.7.Summary> As described above, the technology of the present disclosure is a system for managing a user's private key used in a blockchain in managing crypto assets, the system including a plurality of the servers. In the technology of the present disclosure, the storage unit of the server is configured to store one key fragment of a private key encrypted by a user's user terminal and previously divided into a plurality of key fragments. In the technology of the present disclosure, the server receives a request for the key fragment from the user's user terminal, and performs authentication of the user terminal in response to the request for the key fragment. In the technology of the present disclosure, the server transmits the key fragment to the user terminal in response to successful authentication. In the technology of the present disclosure, the user terminal requests each of a plurality of servers for a key fragment held by the server, and obtains the key fragment from each of the plurality of servers to restore the private key.
[0106] This eliminates the need for users to manage their own private keys. In addition, because the key fragments are private keys encrypted before being split, it is possible to reduce the risk that the key fragments will be restored by a third party due to eavesdropping on the communication path of the key fragments. Therefore, the technology disclosed herein can reduce the management risks of crypto-assets and relieve users of the burden of managing private keys.
[0107] In addition, the technology disclosed herein performs authentication of a request for a key fragment by a server using an authentication method different from that of at least one of the other servers, thereby improving the security of private key management by using different authentication methods between businesses.
[0108] In addition, in the technology disclosed herein, each of the multiple servers is managed by an entity that manages private keys of different crypto assets. As a result, the technology disclosed herein stores key fragments in servers managed by different entities, thereby reducing the risk of the fragments being managed by a single entity.
[0109] In addition, in the technology disclosed herein, a server receives a login authentication request for a service from a user terminal from a provider server that provides services related to crypto assets, and requests authentication information required for the login authentication from the user terminal based on the login authentication. In the technology disclosed herein, a server obtains the authentication information from the user terminal and performs login authentication based on the authentication information. In addition, the login authentication in the technology disclosed herein is login authentication for performing single sign-on for multiple services. This allows a user to use multiple blockchain services for the same crypto asset with a single login using a restored private key, eliminating the need to manage authentication methods for multiple services. Therefore, the technology disclosed herein can reduce the burden of managing authentication methods on the user.
[0110] <2. Modifications> Although several embodiments of the present disclosure have been described above, these embodiments can be implemented 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 within the scope of the invention and its equivalents as described in the claims, as well as the scope and spirit of the invention.
[0111] In the technology disclosed above, all of the servers in the server group 3 are configured to store key fragments, but the present invention is not limited to this. For example, only some of the servers (two or more) in the server group 3 may be configured to store key fragments.
[0112] Further, the technology disclosed above has been described as an example in which the private key is restored using key fragments from all of the servers in the server group 3, but is not limited to this. For example, the private key may be restored using key fragments from some of the multiple servers. With this configuration, the user can restore the private key even if one of the servers in the server group 3 is unavailable for some reason (for example, a communication failure).
[0113] Also, one of the storage servers 30 in the server group 3 may be configured as the server 10. In this case, the storage server 30 has both the functions of the storage server 30 and the functions of the server 10. For example, the system according to this modification may adopt a configuration in which the storage server 30A has the functions of the storage server 30 and the server 10, and the storage server 30B has only the functions of the storage server 30.
[0114] <Additional Notes> The matters described in the above embodiments will be supplemented below. <Appendix 1> A system for managing a user's private key used in a blockchain for managing crypto assets, the system including a plurality of servers, the servers each including a processor and a storage unit, and a program for operating the servers, the program comprising: the storage unit is configured to store one of the private key encrypted by the user terminal of the user and divided into a plurality of key fragments in advance, The program causes the processor to: receiving a request for the key fragment from the user terminal; in response to the request for the key fragment, authenticating the user terminal; transmitting the key fragment to the user terminal in response to the authentication being successful.
[0115] <Appendix 2> In the step of performing authentication, authentication is performed using an authentication method different from that of at least one other server among the plurality of servers. The program described in <Appendix 1>.
[0116] <Appendix 3> The said business entity is a person engaged in the business of managing private keys of crypto assets. A program described in <Appendix 1> or <Appendix 2>.
[0117] <Appendix 4> The request for the key fragment includes information indicating that the user terminal has successfully completed login authentication for a service related to a crypto asset, performing the authentication using information indicating that the login authentication has been successful in the authentication step; The program described in <Appendix 1> that executes the above.
[0118] <Appendix 5> the information indicating that the login authentication has been successful includes a token issued by a server that performs the login authentication, The program described in <Supplementary Note 4>, wherein in the authentication step, authentication is performed for the user terminal using the token.
[0119] <Appendix 6> The login authentication is login authentication for performing single sign-on for a plurality of the services. The program described in <Appendix 4> or <Appendix 5> that executes the above.
[0120] <Appendix 7> A system for managing a user's private key used in a blockchain for managing crypto assets, the system including a plurality of servers, the servers including a processor and a storage unit, the storage unit is configured to store one of the private key encrypted by the user terminal of the user and divided into a plurality of key fragments in advance, A control unit of the server receiving a request for the key fragment from the user terminal; in response to the request for the key fragment, authenticating the user terminal; and in response to the authentication being successful, transmitting the key fragment to the user terminal.
[0121] <Appendix 8> A system for managing a user's private key for use in a blockchain in managing crypto assets, the system including a plurality of servers, the method being executed by the servers each having a processor and a memory unit, the storage unit is configured to store one of the private key encrypted by the user terminal of the user and divided into a plurality of key fragments in advance, The processor, receiving a request for the key fragment from the user terminal; in response to the request for the key fragment, authenticating the user terminal; In response to the authentication being successful, transmitting the key fragment to the user terminal; How to do it.
[0122] <Appendix 9> A system for managing a user's private key used in a blockchain for managing crypto assets, comprising: The system includes a plurality of servers and a user terminal of the user; the storage unit of the server is configured to store one of a plurality of key fragments, the private key being encrypted by the user terminal of the user, the key fragment being previously divided into the plurality of key fragments; A control unit of the server receiving a request for the key fragment from a user terminal of the user; in response to the request for the key fragment, authenticating the user terminal; In response to the authentication being successful, transmitting the key fragment to the user terminal; A control unit of the user terminal, requesting the key fragment held by each of the plurality of servers; obtaining the key fragment from each of the plurality of servers; recovering the encrypted private key from a plurality of the key fragments; decrypting the encrypted private key; A system that runs [Explanation of symbols]
[0123] 1 system, 3 server group, 10 server, 12 communication IF, 13 input / output IF, 15 memory, 16 storage, 20 user terminal, 22 communication IF, 23 input / output IF, 25 memory, 26 storage, 30 storage server, 32 communication IF, 33 input / output IF, 35 memory, 36 storage, 40 providing server, 80 network, 101 communication unit, 102 memory unit, 103 control unit, 121 first DB, 122 second DB, 131 reception control unit, 132 transmission control unit, 133 first authentication unit, 201 communication unit, 202 memory unit, 203 control unit, 231 reception control unit, 232 transmission control unit, 233 service unit, 234 restoration unit, 235 encryption unit, 301 communication unit, 302 memory unit, 303 control unit, 331 reception control unit, 321 A third DB, 332 a transmission control unit, 333 a second authentication unit, and 334 a key management unit.
Claims
1. A system for managing a user's private key used in a blockchain for managing crypto assets, the system including a plurality of servers, the servers each including a processor and a storage unit, and a program for operating the servers, the program comprising: the storage unit is configured to store one of the plurality of key fragments, the private key being encrypted by the user terminal of the user and previously divided into the plurality of key fragments; The program causes the processor to: receiving a request for the key fragment from the user terminal; in response to the request for the key fragment, authenticating the user terminal; transmitting the key fragment to the user terminal in response to the authentication being successful; The request for the key fragment includes information indicating that the user terminal has successfully completed login authentication for a service related to a crypto asset, the information indicating that the login authentication has been successful includes a token issued by a server that performs the login authentication, a program for performing the authentication by verifying whether the token is issued by a server that performs the login authentication in the step of performing the authentication.
2. In the step of performing authentication, the authentication is performed using an authentication method different from that of at least one other server among the plurality of servers. The program according to claim 1.
3. Each of the plurality of servers is a server managed by an entity engaged in the business of managing private keys of different crypto assets. The program according to claim 1 or 2.
4. The login authentication is login authentication for performing single sign-on for a plurality of the services. The program according to claim 1.
5. A system for managing a user's private key used in a blockchain for managing crypto assets, the system including a plurality of servers, the servers including a processor and a storage unit, the storage unit is configured to store one of the plurality of key fragments, the private key being encrypted by the user terminal of the user and previously divided into the plurality of key fragments; A control unit of the server receiving a request for the key fragment from the user terminal; in response to the request for the key fragment, authenticating the user terminal; in response to the authentication being successful, transmitting the key fragment to the user terminal; The request for the key fragment includes information indicating that the user terminal has successfully completed login authentication for a service related to a crypto asset, the information indicating that the login authentication has been successful includes a token issued by a server that performs the login authentication, A server that performs the authentication by verifying whether the token is issued by a server that performs the login authentication in the step of performing the authentication.
6. A system for managing a user's private key for use in a blockchain in managing crypto assets, the system including a plurality of servers, the method being executed by the servers each having a processor and a memory unit, the storage unit is configured to store one of the plurality of key fragments, the private key being encrypted by the user terminal of the user and previously divided into the plurality of key fragments; The processor, receiving a request for the key fragment from the user terminal; in response to the request for the key fragment, authenticating the user terminal; In response to the authentication being successful, transmitting the key fragment to the user terminal; Run The request for the key fragment includes information indicating that the user terminal has successfully completed login authentication for a service related to a crypto asset, the information indicating that the login authentication has been successful includes a token issued by a server that performs the login authentication, The method according to claim 1, wherein in the step of performing authentication, the authentication is performed by verifying whether the token is issued by a server that performs the login authentication.
7. A system for managing a user's private key used in a blockchain for managing crypto assets, comprising: The system includes a plurality of servers and a user terminal of the user; the storage unit of the server is configured to store one of a plurality of key fragments, the private key being encrypted by the user terminal of the user and previously divided into the plurality of key fragments; A control unit of the server receiving a request for the key fragment from a user terminal of the user; in response to the request for the key fragment, authenticating the user terminal; In response to the authentication being successful, transmitting the key fragment to the user terminal; A control unit of the user terminal, requesting the key fragment held by each of the plurality of servers; obtaining the key fragment from each of the plurality of servers; recovering the encrypted private key from a plurality of the key fragments; decrypting the encrypted private key; Run The request for the key fragment includes information indicating that the user terminal has successfully completed login authentication for a service related to a crypto asset, the information indicating that the login authentication has been successful includes a token issued by a server that performs the login authentication, The system performs the authentication by verifying whether the token is issued by a server that performs the login authentication in the step of performing the authentication.
Citation Information
Patent Citations
System, apparatus and program for secret distribution
JP2007300157A
Electronic tally type storage method and operation system therefor
JP2020155911A
User authentication method and user authentication method
JP2021118406A
Control method, control program and information processing device
JP2021136645A
Certificate management device, certificate management system, and certificate management method
JP2023132485A
