How to mediate cryptocurrency transfers

Abstract

To provide a crypto-asset transmission mediation method that more reliably verifies a recipient when crypto-assets are transmitted from a crypto-asset service provider (sender VASP) to a recipient VASP node.SOLUTION: A method is used in transmitting crypto-assets from a sender (sender VASP) having a transmission account in a crypto-asset service provider of the sender to a recipient (recipient VASP) having a reception account in a crypto-asset service provider of the recipient. After verifying that the reception account of the recipient VASP is valid, a verification node determines whether the transmission has been recorded on a blockchain network. After a determination is made that the transmission has been recorded on the blockchain network, the verification node transmits, to the recipient VASP, a reception account update request for the recipient VASP regarding the transmission of the crypto-assets from the sender to the recipient. The verification node does not belong to any of the sender VASP or the recipient VASP.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE Embodiments described herein relate to methods for brokering crypto asset transmissions. More specifically, embodiments relate to methods for securely brokering crypto asset transmissions between a recipient crypto asset service provider (VASP) and a sender VASP. [Background technology]

[0002] Crypto assets, such as Bitcoin, are recognized as assets without borders, and the number of places where they can be used (e.g., offline stores, online stores, etc.) is increasing. Crypto assets can be exchanged for real assets, and their values ​​fluctuate frequently. Furthermore, the types of crypto assets are diversifying, and the number of VASPs (Vault Service Providers) that handle crypto asset transactions and management on behalf of users is also increasing.

[0003] These cryptocurrency transactions are sometimes anonymous and used to hide the source of funds. Therefore, in order to prevent money laundering and terrorist financing using cryptocurrency, the FATF (Financial Action Task Force on Money Laundering) has imposed obligations on the information that VASPs should provide when transmitting cryptocurrency, and requires VASPs to comply with said obligations.

[0004] However, there is a problem that in order for VASPs to comply with FATF obligations, the design of their current systems would have to be changed, and if each VASP were to modify their systems separately to comply with FATF obligations, this could lead to protocol compatibility issues between VASPs. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments described herein provide a method of mediating the transmission of crypto assets that more reliably verifies the recipient as the crypto assets are transmitted from a sender VASP node to a recipient VASP node.

[0006] The embodiments described herein may provide a more secure way to mediate the transmission of crypto assets by increasing security when transmitting and receiving recipient information.

[0007] The embodiments described herein may provide a method for intermediating crypto asset transmissions that can consolidate, reconcile, and manage crypto asset transmissions occurring at each VASP node while complying with obligations proposed by FATF.

[0008] The embodiments described herein may provide a method of mediating the transmission of crypto assets that can selectively update a recipient's crypto assets through matching results and prevent the crypto assets from being handed over to criminal groups or the like.

[0009] It should be appreciated from the following description that the embodiments described herein provide other methods and apparatus thereof not described above. [Means for solving the problem]

[0010] According to an embodiment, a method for mediating the transmission of crypto assets may include the steps of receiving first information about crypto assets to be transmitted from a first user to a second user from a first crypto asset service provider (VASP) server that manages the first user's crypto assets, sending a verification request to a second VASP server that manages the second user's crypto assets regarding whether the information about the second user included in the received first information is correct, receiving a verification result from the second VASP server indicating that the information about the second user is correct in response to the verification request, transmitting the received verification result to the first VASP server, determining whether a transaction corresponding to the transmission of the crypto asset to be transmitted is recorded in the blockchain as a result of the first VASP server's response to the transmission of the verification result, and sending a crypto asset update request for the second user to the second VASP server if it is determined that the transaction is recorded in the blockchain.

[0011] According to an embodiment, the step of determining whether the transaction is recorded in the blockchain may include the steps of preparing a first identifier for the crypto asset to be transmitted; determining whether a transaction including metadata including information corresponding to the first identifier is recorded in the blockchain after the transmission of the matching result; if it is determined that the transaction including the metadata is recorded in the blockchain, obtaining second information about the transaction including the metadata from the blockchain; comparing whether at least one or more specific first items included in the first information correspond to at least one or more specific second items included in the obtained second information; and if it is determined that at least one or more first items and at least one or more second items correspond to each other, determining that a transaction corresponding to the transmission of the crypto asset to be transmitted is recorded in the blockchain.

[0012] According to an embodiment, determining whether a transaction including metadata is recorded on the blockchain may comprise obtaining metadata included in at least one of the transactions recorded on the blockchain, verifying whether the obtained metadata includes information corresponding to a first identifier, and using a result of the verification to find a transaction including metadata including information corresponding to the first identifier.

[0013] According to an embodiment, the step of checking whether at least one or more first items and at least one or more second items correspond to each other may include a step of preparing, as the at least one or more first items, at least one of information about the type of crypto asset to be sent, information about the amount, and information about the recipient; a step of preparing, as the at least one or more second items, at least one of information about the type of crypto asset, information about the amount, and information about the recipient in the transaction including metadata; and a step of determining whether the prepared at least one or more first items and the prepared at least one or more second items correspond to each other.

[0014] According to an embodiment, the step of determining whether the transaction is recorded in the blockchain may include the steps of receiving a second identifier of the transaction corresponding to the transmission of the crypto asset to be transmitted from the first VASP server in response to the transmission of the matching result, determining whether the transaction corresponding to the received second identifier is recorded in the blockchain, obtaining third information about the transaction corresponding to the second identifier from the blockchain if the transaction corresponding to the second identifier is recorded in the blockchain, comparing whether at least one or more specific first items included in the first information correspond to at least one or more specific third items included in the obtained third information, and determining that the transaction corresponding to the transmission of the crypto asset to be transmitted is recorded in the blockchain when it is matched that at least one or more first items and at least one or more third items correspond to each other.

[0015] According to an embodiment, the step of determining whether a transaction corresponding to the second identifier is recorded in the blockchain may include the steps of obtaining a third identifier for each of at least one or more transactions recorded in the blockchain, verifying whether the obtained third identifier corresponds to the second identifier, and using a result of the verification to find the transaction corresponding to the second identifier.

[0016] According to another embodiment, a method for mediating the transmission of crypto assets may include the steps of receiving first information about a crypto asset to be transmitted from a first user to a second user from a first crypto asset service provider (VASP) server that manages the first user's crypto asset; determining whether a transaction corresponding to the transmission of the crypto asset to be transmitted is recorded on a blockchain; reserving verification of the second user if the transaction is recorded on the blockchain and it is determined that the second VASP server that manages the crypto asset of the second user is not a member; proceeding to verify the reserved second user, and if the second VASP server joins as a member, sending a verification request to the second VASP server regarding whether the information about the second user included in the first information is correct; and if a verification result indicating that the information about the second user is correct is received from the second VASP server in response to the verification request, sending a crypto asset update request for the second user to the second VASP server.

[0017] According to another embodiment, a method for mediating the transmission of crypto assets may include the steps of receiving information about a crypto asset to be transmitted from a first user to a second user, sending a verification request regarding whether the information about the second user is correct through a verification node to a second VASP server that manages the second user's crypto assets, and when a verification result indicating that the information about the second user is correct is received from the verification node, recording a transaction corresponding to the transmission of the crypto asset to be transmitted on a blockchain.

[0018] According to another embodiment, a method for mediating the transmission of crypto assets may include, when crypto assets are scheduled to be transmitted from a first user to a second user, the steps of providing a public key through a verification node to a crypto asset service provider server that manages the first user's crypto assets; receiving information about the second user encrypted with the public key by the crypto asset service provider server from the verification node; verifying whether the information about the second user is correct by decrypting the received encrypted information about the second user using a private key; transmitting the verification result to the verification node; and, when a crypto asset update permission signal is received in response, updating the second user's crypto assets by reflecting the amount of the transmitted crypto asset. [Brief description of the drawings]

[0019] [Figure 1] FIG. 1 is a diagram illustrating a crypto asset intermediation system according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a diagram illustrating public keys for each security level referenced in some embodiments of this disclosure and its application. [Diagram 3] FIG. 3 is a signal flow diagram for obtaining a VASP identification code according to another embodiment of the present disclosure. [Figure 4] FIG. 4 is a signal flow diagram illustrating a method for verifying a recipient of a crypto asset according to another embodiment of the present disclosure. [Diagram 5] FIG. 5 is a signal flow diagram illustrating a method for mediating the transmission of crypto assets according to another embodiment of the present disclosure. [Figure 6] FIG. 6 is a signal flow diagram illustrating a method for mediating the transmission of crypto assets according to another embodiment of the present disclosure. [Figure 7] FIG. 7 is a signal flow diagram illustrating a method for storing a transaction in a blockchain according to another embodiment of the present disclosure. [Figure 8]FIG. 8 is a signal flow diagram illustrating a method for mediating the transmission of crypto assets according to another embodiment of the present disclosure. [Figure 9] FIG. 9 is a signal flow diagram illustrating a method for mediating the transmission of crypto assets according to another embodiment of the present disclosure. [Figure 10] FIG. 10 is an exemplary hardware diagram that may be used to implement a computing device in various embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] Hereinafter, the embodiments of the present disclosure will be described with reference to the accompanying drawings. The advantageous effects and features of the present disclosure and the method of achieving the same can be more easily understood by referring to the detailed description of the embodiments below and the accompanying drawings. However, the present disclosure can be realized in many different forms and should not be construed as being limited to the embodiments described herein. Rather, these embodiments may be provided so that this disclosure will be comprehensive and complete, and will fully convey the concept of the disclosure to those skilled in the art, and the present disclosure will be defined by the following claims.

[0021] In addition, when assigning reference numerals to components in each drawing, it is noted that the same reference numerals may be assigned to the same components as much as possible, even if the same components may be illustrated in different drawings. Furthermore, in describing the present disclosure, detailed descriptions of related well-known configurations or functions are omitted on the basis that such detailed descriptions may obscure the gist of the present disclosure.

[0022] Unless otherwise specified, all terms (including technical and scientific terms) used in this disclosure may be used in a commonly understood sense by those skilled in the art. Furthermore, terms defined in commonly used dictionaries may not be interpreted ideally or excessively unless they are clearly and specifically defined. The technical terms used herein are for the purpose of describing the embodiments and may not be intended to limit the present disclosure. In this specification, unless otherwise specified in the text, the singular form includes the plural form.

[0023] Furthermore, when describing components of the present disclosure, terms such as first, second, A, B, (a), (b), etc. may be used. These terms are intended to distinguish a component from other components, and the nature or order of the components may not be limited by the terms. Based on a description of a component being "connected," "coupled," or "contacted" to another component, it should be understood that the component may be directly connected or in contact with the other component, but the other components may also be "connected," "coupled," or "contacted" between each component.

[0024] According to the Travel Rule, when transferring crypto assets, a crypto asset service provider (hereinafter referred to as a "VASP") sending crypto assets is required to provide the following information to the VASP receiving the crypto assets: -Caller name -Caller's account number (sender's account number) - Originator's physical address (the sender's physical address) - National identification number, customer identification number or other unique identification number - Date and place of birth

[0025] In addition, the information obligation requires a VASP receiving crypto assets to provide the following information to a VASP sending crypto assets: -Recipient name - Recipient's crypto wallet account number

[0026] On the other hand, as the use of crypto assets increases rapidly, crypto assets are distributed all over the world, and crypto assets are used for money laundering by taking advantage of the anonymity of crypto assets. Furthermore, when sending crypto assets, even if the transaction for sending is successfully matched, the recipient can remain anonymous. As in the above information provision obligation, only the recipient's name and crypto wallet account number are required, so the recipient can remain anonymous in the transaction history.

[0027] The core of the obligation to provide information may be information sharing, but due to relatively loose regulation in the cryptocurrency industry, many VASPs have had to develop AML (anti-money laundering) solutions to identify users’ ownership information.

[0028] Therefore, the FATF (Financial Action Task Force on Money Laundering) has recommended the following characteristics that an information provision solution should have: - The solution should be easily integrated into existing AML / CFT programs with minimal regulatory impact and implementation barriers. -It should be cheap and open source for use by small VASPs and innovative start-ups. -It should comply with global regulatory standards for crypto asset transfers. - It should be flexible to accommodate future technological innovations and sophistication. - It should complement the efforts of law enforcement agencies to proactively detect suspicious activity and prosecute money launderers and terrorists. - It should be scalable, sustainable and have broad support from the industry.

[0029] An embodiment is proposed that can address the characteristics of the solution proposed by the FATF.

[0030] Some embodiments will now be described in detail with reference to the accompanying drawings.

[0031] Within this disclosure, the sender may be referred to as the "sender" and the recipient may be referred to as the "recipient."

[0032] FIG. 1 is a diagram illustrating a crypto asset intermediation system according to an embodiment of the present disclosure.

[0033] As shown in Fig. 1, the cryptocurrency brokerage system according to the embodiment described herein may include a user node 100, multiple VASP nodes 210 and 220, and matching nodes 300 and 400. These components may communicate with each other through a communication network 500. The communication network 500 includes a mobile communication network and a wired communication network, and corresponds to a well-known conventional technology, so a detailed description thereof will be omitted.

[0034] The user node 100 is a communication device such as a mobile terminal or a personal computer owned by a user, and can transmit crypto assets to a recipient by connecting to any one of the VASP nodes 210 or 220 that manages its own crypto assets. The user node 100 can be equipped with a dedicated application for managing crypto assets.

[0035] The blockchain network 400 is a network involving multiple nodes 410-N, and each node 410-N included in the blockchain network 400 may share a blockchain having blocks connected to each other. The block may consist of a block header and a transaction. The block header may include a previous block hash, a Merkle root, a nonce, and a timestamp. The second identifier of the previous block may indicate a second identification reference value for the previous block (i.e., the parent block) in the master blockchain structure. The Merkle root may be a second identifier (e.g., a hash) for the Merkle tree root. The timestamp may record the creation time of the block. Transaction information of the cryptocurrency may be recorded in the transaction. That is, the transaction may include transaction information such as the electronic wallet address of the sender of the cryptocurrency, the electronic wallet address of the recipient, the type of cryptocurrency, and the amount of cryptocurrency sent to the recipient.

[0036] The VASP nodes 210 and 220 can manage cryptocurrency transactions of subscribers. It can be a computing device such as a server (i.e., a VASP server) constructed by a service provider that manages cryptocurrency. The VASP nodes 210 and 220 can store and manage subscriber information to perform cryptocurrency transaction services. The subscriber information can include a name, an account number, a physical address, a user identification information, a date of birth and a place of birth. As the user identification information, an authorized identification information given only to a corresponding user, such as a national identification number (e.g., a Korean resident registration number) and a customer identification number used in a corresponding country, can be used. In addition, the VASP nodes 210 and 220 can store the electronic wallet address, the amount of cryptocurrency, and cryptocurrency transaction details (e.g., deposit and withdrawal details) of each subscriber.

[0037] VASP nodes 210 and 220 can apply various security levels to cryptocurrency transmissions and transmit encrypted personal data to counterparty VASP nodes 210 and 220 according to the security levels. The security levels may be divided into three types. In some embodiments, any one of a plurality of security levels may be selected and applied to a corresponding transmission according to the amount of cryptocurrency to be transmitted. In this case, the first security level may be the highest level applied when the amount of cryptocurrency to be transmitted exceeds a first amount, the second security level may be an intermediate level applied when the amount of cryptocurrency is equal to or less than the first amount and exceeds a second amount, and the third security level may be the lowest level applied when the amount of cryptocurrency is equal to or less than the second amount. Here, the first amount is greater than the second amount.

[0038] In some embodiments, a security policy may be prepared in advance, and any one of a plurality of security levels may be selected and applied to the transmission of the corresponding crypto asset according to the currently applied security policy. For example, the security policy may be set by an administrator, or may be automatically generated based on the time period, date, frequency of hacking incidents, etc.

[0039] FIG. 2 is a diagram illustrating public keys for each security level referenced in some embodiments of this disclosure and its application.

[0040] Referring to Figure 2, when a first security level is applied, a public key to be applied to each transaction (i.e., sending crypto assets) is generated, and a private key corresponding to the corresponding public key may also be generated. Furthermore, when a second security level is applied, a public key and a corresponding private key to be applied to a counterparty user (i.e., a sender or receiver) may be used. When a third security level is applied, a public key and a corresponding private key to be applied to a counterparty VASP node (i.e., a receiver VASP node or a sender VASP node) may be used.

[0041] The first security level may be the strongest but the narrowest in scope. In other words, even if the private key applied to the first security level is leaked, only the personal data related to one transaction can be decrypted by the corresponding private key, so that the decryption of the personal data related to other transactions may be impossible. Conversely, the third security level may be the weakest among the security levels but may have the widest scope of application. In other words, if the private key applied to the third security level is leaked, the personal data transmitted and received between the sender VASP node and the receiver VASP node by the corresponding private key may be leaked.

[0042] Based on this security level, the VASP nodes 210 and 220 can obtain a public key that applies to a specific security level from among multiple public keys, and encrypt personal data including recipient information and sender information with the obtained public key. That is, when the first security level is applied, the VASP nodes 210 and 220 can generate a private key and a public key dedicated to the transaction that is used only for the corresponding transaction (i.e., the corresponding transmission), and can encrypt or decrypt personal data including recipient information and sender information with the corresponding private or public key. The private key and the public key generated according to the first security level can be a kind of one-time encryption key and decryption key that cannot be reused for other transactions. When the second security level is applied, the VASP nodes 210 and 220 can generate a private key and a public key dedicated to the recipient (or sender) that is used only for the specific recipient or sender, and can encrypt or decrypt personal data including recipient information and sender information with the corresponding private or public key. The private key and the public key generated according to the second security level can be reused when a transaction with the same recipient (or sender) occurs again. When the third security level is applied, VASP nodes 210 and 220 can generate private and public keys dedicated to the VASP node that manages the recipient's (or sender's) assets and use the corresponding private or public keys to encrypt or decrypt personal data, including recipient and sender information. The private and public keys generated according to the third security level can be reused if a transaction involving the corresponding VASP occurs again.

[0043] The verification node 300 can mediate crypto asset transmissions between the VASP nodes 210 and 220, verify crypto asset transmissions, and store transaction verification results. For this purpose, the verification node 300 can store VASP member information including each VASP name and identification code that joins as a member, IP address, institution address, nationality, and institution identification information registered in the country (e.g., business registration number). The verification node 300 can assign an identification code for each VASP node 210 and 220 that joins as a member, provide it to the corresponding VASP node 210 and 220, and then record the identification code in the VASP member information. The identification code is unique information given to the VASP nodes 210 and 220, and may be a number string or a character string, or a combination of numbers and letters. In some embodiments, the verification node 300 may store a security policy based on one or more of the frequency, time, date, etc. of hacking. The verification node 300 can determine a security level based on the security policy and obtain public keys that apply to the determined security level from the VASP nodes 210 and 220.

[0044] The verification node 300 can verify transactions for crypto asset transactions by obtaining a transaction to be verified from the blockchain network 400 and comparing information contained in the obtained transaction with information contained in transactions received from the VASP nodes 210 and 220. The verification node 300 can also provide public keys received from a particular VASP node to other VASP nodes.

[0045] The verification node 300 can store verification information including the first identifier, the identification code of the VASP node that sent the crypto asset, the identification code of the VASP node that received the crypto asset, the sender verification result, the recipient verification result, the transaction verification result, the sender VASP public key, and the recipient VASP public key. The sender VASP public key is a type of encryption key used to encrypt personal data and may be generated in the VASP node that manages the sender's crypto asset. Furthermore, the recipient VASP public key is a key used to encrypt personal data and may be generated in the VASP node that manages the recipient's crypto asset. Meanwhile, the verification information may include the encrypted personal data and may further include the transaction stored in the blockchain network 400.

[0046] 1 shows the verification node 300 and the VASP nodes 210 and 220 as being separate from the blockchain network 400, at least one of the verification node 300 or the VASP nodes 210 and 220 may be a node participating in the blockchain network 400. In this case, the verification node 300 or the VASP nodes 210 and 220 may share and store the blockchain.

[0047] A method of mediating the transmission of crypto assets in a crypto asset intermediation system including a verification node 300 and VASP nodes 210 and 220 will be described with reference to Figs.

[0048] In the explanation referring to Figures 3 to 9, the VASP #1 node 210 is a sender VASP node that manages the sender's (i.e., the user's) crypto asset and transmits the crypto asset on behalf of the sender, and the VASP #2 node 220 is a receiver VASP node that manages the receiver's crypto asset and receives the crypto asset on behalf of the receiver.

[0049] FIG. 3 is a signal flow diagram for obtaining a VASP identification code according to another embodiment of the present disclosure.

[0050] 3, after the user node 100 connects to the VASP #1 node 210 and succeeds in user authentication (e.g., login authentication or digital signature authentication), the name of the VASP #2 node 220 that manages the recipient's assets is input by the user. That is, in order to send his / her crypto assets to the recipient, the user logs into the VASP #1 node 210 using the user node 100, and then inputs the name of the VASP #2 node 220 that manages the recipient's crypto assets to the user node 100. In this case, the user node 100 may send the name of the VASP #2 node 220 to the VASP #1 node 210 (S201).

[0051] Next, the VASP #1 node 210 may determine whether or not an identification code of the VASP #2 node 220 mapped to the name of the VASP #2 node 220 has already been stored. If an identification code of the VASP #2 node 220 has not been stored, the VASP #1 node 210 may send an identification code request message including the name of the VASP #2 node 220 to the verification node 300 (S203).

[0052] The matching node 300 may determine whether a member with the name of the VASP #2 node 220 exists in the VASP member information, and if so, may identify the identification code of the VASP #2 node 220 in the VASP member information and send it to the VASP #1 node 210 (S205, S207).

[0053] Next, the VASP #1 node 210 may map and store the name of the VASP #2 node 220 together with the identification code of the VASP #2 node 220 received from the matching node 300 (S209). Furthermore, the VASP #1 node 210 may send a transmittable message to the user node 100 indicating that transmission to the VASP #2 node 220 is available for transfer (S211).

[0054] On the other hand, if the VASP #1 node 210 has already stored the identification code of the VASP #2 node 220 mapped to the name of the VASP #2 node 220, the VASP #1 node 210 may send a sendable message directly to the user node 100 without sending an identification code request message to the verification node 300.

[0055] If it is determined in step S205 that a member with the name of the VASP #2 node 220 does not exist in the VASP member information, the verification node 300 may send a message to the VASP #1 node 210 indicating that an identification code cannot be provided (e.g., may return 0). In this case, the VASP #1 node 210 may send a message to the user node 100 indicating that it is not possible to send crypto assets to the VASP #2 node 220.

[0056] According to this embodiment, the matching node 300 acquires and manages information of each authenticated VASP 210 and 220, and prevents the transmission of crypto assets to VASPs that are not registered as members, thereby preventing unauthorized use of crypto assets.

[0057] Meanwhile, once the identification code of the VASP #2 node 220 is obtained and a ready to send notification message is received, the user node 100 may send the user's (i.e., the sender's) crypto assets to the recipient based on information input from the user.

[0058] FIG. 4 is a signal flow diagram illustrating a method for verifying a recipient of a crypto asset according to another embodiment of the present disclosure.

[0059] Referring to Figure 4, the user node 100 may receive the type of crypto asset to be sent, the amount of crypto asset to be sent, and the recipient's electronic wallet address, etc. from the user (i.e., the sender), and transmit the sender's address, the type of crypto asset, the amount of crypto asset to be sent, and the recipient's electronic wallet address to the VASP #1 node 210 (S301).

[0060] Thereafter, the VASP#1 node 210 may perform sender verification (S303). The VASP#1 node 210 may perform sender verification using the sender's (i.e., the user's) electronic wallet address and the sender's authentication information. At this time, the VASP#1 node 210 may verify the sender by obtaining the sender's name as the sender's authentication information and determining whether or not subscriber information having the sender's name and the sender's address is stored. As another embodiment, the VASP#1 node 210 may verify the sender by receiving the sender's biometric information (e.g., fingerprint data, iris data, etc.) from the user node 100 and comparing the received sender's biometric information with the sender's biometric information stored in advance. The sender (i.e., the user) may be verified using various other authentication methods. On the other hand, if the login authentication of the user (sender) has already been successful before step S303, the VASP#1 node 210 may process the sender's verification result as successful.

[0061] If the match is successful, the VASP#1 node 210 may generate a first identifier (S305) and map and store the match result of the first identifier and the sender. The first identifier may be a match ID used to identify the match information of the crypto asset. The first identifier may be generated using the current date and time, a random number, etc. The VASP nodes 210 and 220 may use the first identifier to query the match information stored in the match node 300.

[0062] Next, the VASP #1 node 210 may determine a security level to be applied to the transmission of the crypto asset from among a plurality of security levels (S307). At this time, the VASP #1 node 210 may identify the amount of crypto asset included in the transmission request message, identify which of the security levels the amount of crypto asset belongs to, and determine the security level to be applied to the transmission. Thereafter, the VASP #1 node 210 may generate a new key pair (i.e., a private key and a public key) or extract a key pair already generated according to the determined security level, and map and store the key pair and the first identifier (S309).

[0063] If the security level is determined according to the amount of crypto assets, the VASP#1 node 210 may apply a first security level when the amount of crypto assets exceeds a first amount, apply a second security level when the amount of crypto assets is equal to or less than the first amount and exceeds a second amount, and apply a third security level when the amount of crypto assets is equal to or less than the second amount. If it is determined to apply the first security level, the VASP#1 node 210 may generate a private key and a public key dedicated to the transaction that are applied only to the transmission of crypto assets. Furthermore, if it is determined to apply the second security level, the VASP#1 node 210 may identify the recipient based on the recipient's electronic wallet address and determine whether a key pair dedicated to the recipient that is used only for the recipient has already been generated. If a key pair dedicated to the recipient has not been generated, the VASP#1 node 210 may generate a private key and a public key dedicated to the recipient. On the other hand, if it is determined to apply the third security level, the VASP#1 node 210 may extract a key pair dedicated to the VASP#2 node 220 that is used only for the VASP#2 node 220 that manages the recipient's crypto assets. If a dedicated key pair has not been generated for the VASP #2 node 220, the VASP #1 node 210 may generate a dedicated key pair for the VASP #2 node 220.

[0064] Next, the VASP#1 node 210 may send a message (hereinafter referred to as a "public key request message") to the verification node 300 to request the recipient's public key for the verification of the recipient (S311). At this time, the VASP#1 node 210 may send a public key request message to the verification node 300 including the first identifier, the verification result of the sender, the applied security level, and the identification code of the VASP#2 node 220 that manages the recipient's crypto asset. Furthermore, if the security level is the second level, the VASP#1 node 210 may additionally include the sender's identification information (e.g., the sender's electronic wallet identification information) in the public key request message, and transmit to the verification node 300 the public key (i.e., the public key of the VASP#1 node 210) generated or extracted according to the security level.

[0065] The verification node 300 can then identify the first identifier, the sender verification result, the identification code of the VASP #2 node 220, and the public key of the VASP #1 node 210 included in the public key request message, and further identify the identification code of the VASP #1 node 210 that sent the public key request message. The verification node 300 then includes the identification code of the VASP #1 node 210 as the identification code of the sender VASP, and includes the identification code of the VASP #2 node 220 as the identification code of the recipient VASP. Furthermore, it can generate and store verification information including the first identifier, the sender verification result, and the public key of the VASP #1 node 210. The verification node 300 can then transmit the public key request message to the VASP #2 node 220 (S313).

[0066] When the VASP#2 node 220 receives the public key request message, the VASP#2 node 220 may identify the security level included in the public key request message (S315). Next, the VASP#2 node 220 may generate a new key pair (i.e., a private key and a public key) or extract an already generated key pair according to the identified security level (S317). If the security level is a first security level, the VASP#2 node 220 may generate a transaction-specific private key and public key that are applied only to sending. Furthermore, if the security level is a second security level, the VASP#2 node 220 may identify the sender's identification information (e.g., the sender's electronic wallet address) in the public key request message, determine whether a sender-specific key pair that is used only by the sender has already been generated, and if so, extract the sender-specific public key. If a sender-specific key pair has not been generated, the VASP#2 node 220 may generate and store the sender-specific private key and public key. On the other hand, if the security level is the third security level, the VASP #2 node 220 may determine whether a key pair dedicated to the VASP #1 node 210 has already been generated for use only by the VASP #1 node 210, and if so, may extract a public key dedicated to the VASP #1 node 210. If a key pair dedicated to the VASP #1 node 210 has not been generated, the VASP #2 node 220 may generate and store a private key and a public key dedicated to VASP #1.

[0067] The VASP #2 node 220 may map and store the first identifier and the corresponding key pair, and may send the extracted or generated public key together with the first identifier to the verification node 300 (S319). The verification node 300 may then forward the received public key and the first identifier to the VASP #1 node 210 (S321), and may store the public key received from the VASP #1 node 210 in the verification information having the first identifier.

[0068] In some embodiments, the verification node 300 may determine the security level based on a security policy or the amount of crypto assets to be transmitted. In this case, the verification node 300 may transmit the determined security level to the VASP #1 node 210 and the VASP #2 node 220, and receive the public key of the VASP #2 node 220 and provide it to the VASP #1 node 210, so that the public key and private key used at that security level are obtained at each of the VASP #1 node 210 and the VASP #2 node 220.

[0069] In some embodiments, the verification node 300 may determine the security level based on the amount of crypto assets to be transmitted or a security policy. In this case, the verification node 300 may transmit the determined security level to each of the VASP #1 node 210 and the VASP #2 node 220, and obtain the public key obtained from the VASP #2 node 220 and transmit it to the VASP #1 node 210, so that the public key and private key used at that security level are obtained at each of the VASP #1 node 210 and the VASP #2 node 220.

[0070] Next, the VASP#1 node 210 may identify the private key (i.e., the private key extracted or generated in step S309) mapped to the first identifier. Then, the VASP#1 node 210 may use the private key to encrypt personal data including the recipient information and the sender information to generate first encrypted data, and use the public key received from the verification node 300 to encrypt the user personal data to generate second encrypted data (S323). The sender information may include the sender name, account number, physical address, the sender's identification information registered in the country, and the sender's date of birth and place of birth. The VASP#1 node 210 may have previously acquired and stored the sender information when the sender joins as a member. The recipient information may also include the recipient's name and the recipient's account number (e.g., the address of an electronic wallet). The first encrypted data may be data that can be normally decrypted and used in the VASP#1 node 210 corresponding to the sender, and the second encrypted data may be data that can be normally decrypted and used in the VASP#2 node 220 corresponding to the recipient.

[0071] Next, the VASP #1 node 210 may transmit information about the crypto asset to be sent to the recipient to the verification node 300 (S325). In some embodiments, the VASP #1 node 210 may transmit the first encrypted data, the encrypted second encrypted data, and the first identifier to the verification node 300 as information about the crypto asset.

[0072] The verification node 300 may then include the first encrypted data and the encrypted second encrypted data in the verification information including the first identifier. The verification node 300 may then request verification of the recipient by forwarding the second encrypted data and the first identifier to the VASP#2 node 220 (S327).

[0073] Next, the VASP#2 node 220 may identify the private key mapped to the first identifier (i.e., the private key extracted or generated in step S317) and use the private key to decrypt the second encrypted data to obtain the personal data (S329). Next, the VASP#2 node 220 may verify the recipient by identifying the recipient information in the personal data and determining whether the subscriber information managed by the VASP#2 node 220 matches the recipient information (S331). At this time, the VASP#2 node 220 may identify the address (e.g., electronic wallet address) and the name of the recipient in the recipient information, and may process the recipient verification as successful if the subscriber information having both the recipient address and name has already been stored, and may process the verification as unsuccessful otherwise. The VASP#2 node 220 may transmit the recipient verification result and the first identifier to the verification node 300 (S333).

[0074] The matching node 300 may then further include the recipient's matching result in the matching information having the first identifier, store the recipient's matching result (S335), and further transfer the recipient's matching result to the VASP #1 node 210 (S337).

[0075] If the recipient verification result is determined to be unsuccessful, the VASP #1 node 210 may send a message to the user node 100 informing the user node 100 that the crypto asset transmission cannot proceed due to failure of the recipient authentication. On the other hand, if the recipient verification result is determined to be successful, the VASP #1 node 210 may proceed to transmit the crypto asset according to the method shown in FIG.

[0076] According to this embodiment, it is possible to obtain an effect of enhancing the security of the recipient information, since the recipient information is encrypted using the public key used in the applied security level and transmitted to the VASP#2 node 220. Furthermore, according to this embodiment, it is possible to obtain an effect of strictly verifying the recipient information when transferring crypto assets.

[0077] FIG. 5 is a signal flow diagram illustrating a method for mediating the transmission of crypto assets according to another embodiment of the present disclosure.

[0078] Referring to FIG. 5, if the matching result of the receiver is successful, the VASP #1 node 210 may prepare transaction data including the second identifier and cryptocurrency transmission-related information in response to the successful matching, and send a transaction record request message including the transaction data to the blockchain network 400 (S401). That is, if the matching result of the receiver is successful, the VASP #1 node 210 may send a transaction record request message to the blockchain network 400 in response thereto, so that a transaction corresponding to the transmission of the cryptocurrency to be sent to the receiver is recorded in the blockchain. The second identifier may be a hash of the transaction related to the transmission. The transmission-related information may include one or more items of the sender's address (e.g., electronic wallet address), the receiver's electronic wallet address, the type of cryptocurrency, and the amount of the cryptocurrency to be sent.

[0079] Next, each node 410-N of the blockchain network 400 performs mining and connects a new block including the second identifier and transaction data to an existing block, thereby storing the transaction for the transmission of the cryptocurrency in the blockchain (S403).

[0080] When mining is stabilized, the VASP #1 node 210 may send a transaction matching request message including the transaction data and the first identifier to the matching node 300 (S405). Stabilization of mining may be that the transaction is successfully stored in the blockchain.

[0081] Then, the matching node 300 may store the transaction data in the matching information having the first identifier. Furthermore, since the transaction matching request message is received, the matching node 300 may identify a second identifier from the transaction data included in the transaction matching request message and inquire whether a transaction corresponding to the second identifier is found in the blockchain network 400, thereby determining whether a transaction related to the transmission of the crypto asset is recorded in the blockchain (S407, S409). At this time, the matching node 300 may obtain a third identifier (e.g., a hash) for each of at least one or more transactions recorded in the blockchain, check whether the obtained third identifier corresponds to the second identifier, and use the check result to find a transaction corresponding to the second identifier. In some embodiments, the matching node 300 may determine whether a transaction related to the transmission of the crypto asset is recorded in the blockchain without receiving a transaction matching request message. That is, when the VASP #1 node 210 responds to the transmission of the matching result (i.e., the successful matching of the recipient) by recording a transaction corresponding to the transmission of the cryptocurrency to be transmitted in the blockchain, the matching node 300 may determine whether or not the transaction related to the transmission of the cryptocurrency to be transmitted has been recorded in the blockchain as a result of the response. If it is determined that the transaction corresponding to the second identifier has been recorded in the blockchain, the matching node 300 may extract the transmission-related information from the transaction corresponding to the second identifier. Next, the matching node 300 may identify one or more specific first items from the transmission-related information included in the transaction data received from the VASP #1 node 210 in step S405, identify one or more specific second items in the transmission-related information extracted from the transaction in the blockchain, and then determine whether the first item and the second item correspond to each other, thereby matching whether or not the transaction corresponding to the transmission of the cryptocurrency has been recorded in the blockchain (S411).The matching node 300 may determine that the transaction matching is successful if the first item and the second item correspond to each other, and may determine that the transaction matching is unsuccessful if the first item and the second item do not correspond to each other. The specified item may be one or more items preset in the transmission-related information. For example, the specified item may be at least one of the amount of cryptocurrency, the sender's address, and the recipient's electronic wallet address. If the first item and the second item match, or if the first item and the second item are mapped and recorded in the matching information, the matching node 300 may determine that the first item and the second item correspond to each other.

[0082] The transaction matching result may be stored separately by further including the matching result of the transaction in the matching information having the first identifier (S413). Subsequently, if the transaction matching result is successful, the matching node 300 may send a signal to the VASP#2 node 220 to allow the update of the crypto asset (S415). In this case, the matching node 300 may send transaction data including the second identifier, the sender's address, the recipient's electronic wallet address, the type of crypto asset, and the amount of crypto asset to the VASP#2 node 220. Also, if the transaction matching result is unsuccessful, the matching node 300 may send a crypto asset update pending signal to the VASP#2 node 220.

[0083] When the VASP #2 node 220 receives a crypto asset update permission signal from the verification node 300, the VASP #2 node may update the recipient's crypto asset by adding the amount of crypto asset to the recipient's crypto asset corresponding to the type of received crypto asset based on the recipient's electronic wallet address and the type and amount of crypto asset included in the transaction data (S417). On the other hand, when the VASP #2 node 220 receives a crypto asset update hold signal, the VASP #2 node 220 may hold off on updating the recipient's crypto asset without increasing the recipient's crypto asset.

[0084] According to the above embodiment, if sender verification, receiver verification, and transaction verification are all successful, the crypto assets are sent to the receiver normally and the receiver's crypto assets are updated, thereby preventing the transfer of crypto assets to criminal groups such as terrorists and for money laundering.

[0085] In some embodiments, matching node 300 performs transaction matching and recipient matching, stores and manages matching information, and allows VASP nodes 210 and 220 to join as members, thereby having the effect of consolidating and managing virtual currency transactions conducted between VASP nodes while complying with obligations required by the FATF.

[0086] In another embodiment, metadata including the first identifier may be stored in the blockchain of the crypto asset. In this case, the VASP #1 node 210 may transmit transaction data including the metadata including the first identifier, the second identifier, and transmission-related information to the blockchain network 400 and transmit a transaction record request for transmitting the crypto asset to the blockchain network 400.

[0087] FIG. 6 is a signal flow diagram illustrating a method for mediating the transmission of crypto assets according to another embodiment of the present disclosure.

[0088] Referring to FIG. 6, if the matching result of the receiver is successful, the VASP#1 node 210 may prepare transaction data including metadata including the first identifier, the second identifier, and the transmission-related information as a response to the successful matching, and send a transaction record request message including the transaction data to the blockchain network 400 (S501). The first identifier may be an ID for the matching information. The second identifier may be a hash of the transaction related to the transmission. Furthermore, the transmission-related information may include one or more items of the sender's address (e.g., electronic wallet address), the receiver's electronic wallet address, the type of cryptocurrency, and the amount of cryptocurrency to be sent.

[0089] Thereafter, each node 410-N of the blockchain network 400 connects the new block containing the metadata, the second identifier, and the transaction data to the existing block, thereby enabling the transaction, including the metadata, related to the transmission of the cryptocurrency to be stored in the blockchain (S503).

[0090] Next, the verification node 300 will identify the first identifier from the stored verification information (S505) and query one or more transactions in the blockchain that include metadata corresponding to the first identifier (S507). That is, when the VASP#1 node 210 responds to the transmission of the verification result (i.e., the successful verification of the recipient) by recording a transaction corresponding to the transmission of the crypto asset to be transmitted in the blockchain, the verification node 300 can determine whether the transaction related to the transmission of the crypto asset to be transmitted has been recorded in the blockchain as a result of the response. The verification node 300 may obtain metadata included in at least one transaction among the transactions recorded in the blockchain and check whether the obtained metadata includes information corresponding to the first identifier, thereby finding a transaction in the blockchain that includes metadata including information corresponding to the first identifier.

[0091] Next, when it is determined that a transaction corresponding to the metadata is recorded in the blockchain, the matching node 300 may extract transmission-related information from the transaction including the metadata. Thereafter, the matching node 300 may identify one or more specific first items in the information of the cryptocurrency to be transmitted received from the VASP#1 node 210, identify one or more specific second items in the transmission-related information extracted from the transaction in the blockchain, and then determine whether the first item and the second item correspond to each other, thereby verifying whether the transaction corresponding to the transmission of the cryptocurrency is recorded in the blockchain (S509). The matching node 300 may determine that the transaction matching is successful when the first item and the second item correspond to each other, and may determine that the transaction matching is unsuccessful when the first item and the second item do not correspond to each other. At this time, when the first item and the second item match, or when the first item and the second item are mapped and recorded in the matching information, the matching node 300 may determine that the first item and the second item correspond to each other.

[0092] Next, the matching node 300 may separately store the transaction matching result by further including the transaction matching result in the matching information having the first identifier (S511). Next, if the transaction matching result is successful, the matching node 300 may send a signal to the VASP#2 node 220 to allow the update of the receiver's crypto asset (S513). In this case, the matching node 300 may send transaction data including the second identifier, the sender's address, the receiver's electronic wallet address, the type of crypto asset, and the amount of crypto asset to the VASP#2 node 220. Also, if the transaction matching result is unsuccessful, the matching node 300 may send a crypto asset update pending signal to the VASP#2 node 220.

[0093] Next, when the VASP #2 node 220 receives a crypto asset update permission signal from the verification node 300, the VASP #2 node may update the recipient's crypto asset by adding the amount of crypto asset to the recipient's crypto asset corresponding to the type of the received crypto asset based on the recipient's electronic wallet address and the type and amount of crypto asset included in the transaction data (S515). On the other hand, when the VASP #2 node 220 receives a crypto asset update hold signal, it may hold off on updating the crypto asset without increasing the recipient's crypto asset.

[0094] According to this embodiment, transaction matching can be easily performed using the first identifier, and an effect of simplifying the protocol between nodes can be achieved.

[0095] On the other hand, if the VASP#2 node 220 that manages the recipient's crypto assets is not a member, verification of the recipient may be performed later.

[0096] FIG. 7 is a signal flow diagram illustrating a method for storing a transaction in a blockchain according to another embodiment of the present disclosure.

[0097] 7, the user node 100 may initiate a transmission procedure when the VASP #2 node 220 is not yet a member of the verification node 300. That is, the user node 100 may receive the type of crypto asset to be transmitted, the amount of crypto asset, and the recipient's electronic wallet address from the user (i.e., the sender), and may transmit a transmission request message including the sender's address, the type of crypto asset, the amount of crypto asset, and the recipient's electronic wallet address to the VASP #1 node 210 (S601). In this case, the user node 100 may transmit the name of the VASP #2 node 220, which is not registered as a member, to the VASP #1 node 210.

[0098] When the VASP #1 node 210 receives the transmission request message, it may perform sender verification (S603). As described above, the VASP #1 node 210 may verify the sender using various authentication methods. If the verification is successful, the VASP #1 node 210 may generate a first identifier (S605). Next, the VASP #1 node 210 may determine a security level to be applied to the transmission of the crypto asset from among a plurality of security levels (S607). Furthermore, the VASP #1 node 210 may generate a new key pair (i.e., a private key and a public key) according to the determined security level, or may extract an already generated key pair (S609). The VASP #1 node 210 may map and store the first identifier and the key pair.

[0099] Next, the VASP #1 node 210 may encrypt personal data including the recipient information and sender information using the generated or extracted private key (S611). The VASP #1 node 210 may then prepare transaction data including the crypto asset and the transmission-related information of the second identifier, and send a transaction record request message including the transaction data to the blockchain network 400 (S613). The transmission-related information may include the sender's address, the recipient's electronic wallet address, the type of crypto asset, and the amount of the crypto asset. In some embodiments, the VASP #1 node 210 may send a transaction record request message including metadata including the first identifier, the second identifier, and the transmission-related information to the blockchain network 400.

[0100] Next, each of the nodes 410-N of the blockchain network 400 performs mining and connects the new block containing the transaction data to an existing block, thereby storing the transaction data in the blockchain (S615).

[0101] Once mining has stabilized, the VASP #1 node 210 may send a transaction matching request message including the transaction data, the first identifier, the second identifier, the security level, the encrypted personal data and the generated or extracted public key, as well as the sender's matching result, to the matching node 300 (S617).

[0102] The verification node 300 may generate and store verification information including the sender's verification result, the transaction data, the public key (i.e. the public key of the VASP#1 node 210), the encrypted personal data, a first identifier and a second identifier, the first identifier including the identification code of the VASP#1 node 210 as the sender VASP identification code. Since the VASP#2 node 220 is not a member and members are not assigned to the VASP#2 node 220, the identification code of the recipient VASP node will not be recorded in the verification information.

[0103] Next, the verification node 300 may identify a second identifier in the transaction data included in the transaction verification request message, and inquire about a transaction corresponding to the second identifier in the blockchain network 400 to verify whether the transaction is recorded in the blockchain (S619, S621). If it is determined that the transaction corresponding to the second identifier is recorded in the blockchain, the verification node 300 may extract transmission-related information from the transaction corresponding to the second identifier. Next, the verification node 300 may identify one or more specific first items in the transmission-related information included in the transaction data received from the VASP#1 node 210, identify one or more specific second items in the transmission-related information extracted from the transaction in the blockchain, and then determine whether the first items and the second items correspond to each other, thereby verifying whether the transaction corresponding to the transmission of the crypto asset is recorded in the blockchain.

[0104] In another embodiment, the verification node 300 may identify a first identifier from the transaction data and query one or more transactions in the blockchain that include metadata corresponding to the first identifier. At this time, the verification node 300 may obtain metadata included in at least one transaction among the transactions recorded in the blockchain and check whether the obtained metadata includes information corresponding to the first identifier, thereby finding a transaction in the blockchain that includes metadata that includes information corresponding to the first identifier. Then, when it is determined that a transaction corresponding to the metadata is recorded in the blockchain, the verification node 300 may extract transmission-related information from the transaction that includes the metadata. Furthermore, the verification node 300 may extract one or more specific first items from the transmission-related information included in the transaction data received from the VASP#1 node 210 and extract one or more specific second items in the transmission-related information extracted from the transaction in the blockchain. The verification node 300 may then identify one or more specific second items from the transmission-related information extracted from the transaction in the blockchain and determine whether the first item and the second item correspond to each other, thereby verifying whether a transaction corresponding to the transmission of the cryptocurrency is recorded in the blockchain. The verification node 300 may determine that the transaction verification is successful if the first item and the second item correspond to each other, and may determine that the transaction verification is unsuccessful if the first item and the second item do not correspond to each other.

[0105] The matching node 300 may then store the transaction matching result by further including the matching result of the transaction in the matching information including the first identifier (S623). The matching node 300 may then record the first identifier and the security level in the recipient matching reservation list (S625).

[0106] According to this embodiment, when a transmission to a non-member VASP #2 node 220 is requested, the transaction data is stored in the blockchain and data related to a later recipient match may be stored in a match reservation list of the matching node 300. The recipient match will then be performed when the VASP #2 node 220 becomes a member.

[0107] FIG. 8 is a signal flow diagram illustrating a method for mediating the transmission of crypto assets according to another embodiment of the present disclosure.

[0108] Referring to Figure 8, when the verification node 300 receives a member registration request from the VASP#2 node 220, the membership registration procedure for the VASP#2 node 220 will proceed by receiving the requested member data (nationality, IP address, physical address, identification number, etc.) from the VASP#2 node 220, storing it, and assigning an identification code for the VASP#2 node 220 (S701).

[0109] Next, when the member registration procedure is successfully completed, the verification node 300 may record the identification code of the recipient VASP node not recorded in the verification information as the identification code of the VASP #2 node 220, and may also identify the first identifier recorded in the verification node 300. Next, the verification node 300 may identify the security level recorded in association with the identified first identifier from the recipient verification reservation list (S703). Furthermore, the verification node 300 may send a public key request message including the security level and the first identifier to the VASP #2 node 220 (S705).

[0110] The VASP#2 node 220 may then identify the security level included in the public key request message (S707). The VASP#2 node 220 may then generate a new key pair or extract an existing key pair according to the identified security level (S709). The VASP#2 node 220 may then send the public key from the extracted or generated key pair together with the first identifier to the verification node 300 (S711), and may map and store the first identifier and the key pair.

[0111] The verification node 300 may include the public key as a recipient public key in the verification information having the first identifier. Then, the verification node 300 may transmit the public key and the first identifier to the VASP#1 node 210 (S713).

[0112] Thereafter, the VASP #1 node 210 may extract the public key mapped to the first identifier and encrypt the extracted public key (i.e., the public key of the VASP #1 node 210) using the received public key (i.e., the public key of the VASP #2 node 220) as an encryption key (S715). The VASP #1 node 210 may then transmit the encrypted public key and the first identifier to the verification node 300 (S717).

[0113] The verification node 300 may then extract the encrypted personal data from the verification information having the first identifier (S719) and send a recipient verification request message including the encrypted personal data, the first identifier and the encrypted public key to the VASP #2 node 220 (S721).

[0114] The VASP#2 node 220 may decrypt the encrypted public key included in the recipient verification request message using the private key mapped with the first identifier (S723). Furthermore, the VASP#2 node 220 may decrypt the encrypted personal data using the decrypted public key (S725). The VASP#2 node 220 may then identify the recipient information in the decrypted personal data and verify the recipient by determining whether the subscriber information managed by the VASP#2 node 220 matches the recipient information (S727). The VASP#2 node 220 may identify the recipient's electronic wallet address and name in the recipient information, and if subscriber information having both the electronic wallet address and the name is stored, process the recipient verification as successful, otherwise process the recipient verification as unsuccessful. The VASP#2 node 220 may then transmit the recipient verification result and the first identifier to the verification node 300 (S729).

[0115] The verification node 300 that has received the recipient matching result and the first identifier may store the recipient matching result by including it in the matching information having the first identifier (S731), and may further transmit the recipient matching result to the VASP#1 node 210. Next, if the recipient matching result is successful, the verification node 300 may transmit a signal to the VASP#2 node 220 to permit the update of the recipient's crypto asset (S733). In this case, the verification node 300 may transmit transaction data to the VASP#2 node 220, including the second identifier, the sender's address, the recipient's electronic wallet address, the type of crypto asset, and the amount of crypto asset. Furthermore, if the recipient matching result is unsuccessful, the verification node 300 may transmit a crypto asset update hold signal to the VASP#2 node 220.

[0116] When the VASP #2 node 220 receives a crypto asset update permission signal from the verification node 300, the VASP #2 node 220 may update the recipient's crypto asset by adding the amount of crypto asset to the recipient's crypto asset corresponding to the received crypto asset type based on the recipient's electronic wallet address, crypto asset type, and amount of crypto asset included in the transaction data (S735). On the other hand, when the VASP #2 node 220 receives a crypto asset update hold signal, the VASP #2 node 220 may hold the recipient's crypto asset without increasing it.

[0117] In the embodiment referring to Figure 8, the VASP #1 node 210 encrypts the public key generated by the VASP #2 node 220 using the public key generated by the VASP #2 node 220 as an encryption key and transmits it to the verification node 300. However, the VASP #1 node 210 may also encrypt personal data using the public key of the VASP #2 node 220 received from the verification node 300 and provide the encrypted personal data to the VASP #2 node 220, as described below with reference to Figure 9.

[0118] According to this embodiment, the recipient can be reliably verified even if the recipient VASP#2 node 220 joins as a member later. Furthermore, according to this embodiment, the personal data is encrypted using the public key used at that security level and transmitted to the VASP#2 node 220, which has the effect of enhancing data security.

[0119] FIG. 9 is a signal flow diagram illustrating a method for mediating the transmission of crypto assets according to another embodiment of the present disclosure.

[0120] In FIG. 9, steps S701 to S713 having the same reference numerals as those in FIG. 8 are substantially the same as those described with reference to FIG. 8, and therefore descriptions of the steps having the same reference numerals will be omitted and only the steps having different reference numerals will be described.

[0121] 9, when the VASP #1 node 210 receives the public key of the VASP #2 node 220, the VASP #1 node 210 may encrypt personal data including the recipient information and the sender information using the received public key (S815). The VASP #1 node 210 may then transmit the encrypted personal data and the first identifier to the verification node 300 (S817).

[0122] Thereafter, the verification node 300 may store the verification information having the first identifier further including the encrypted personal data (S819). Furthermore, the VASP#1 node 210 may send a recipient verification request message to the VASP#2 node 220 including the personal data encrypted by the public key of the VASP#2 node 220 and the first identifier (S821).

[0123] The VASP#2 node 220 may then decrypt the encrypted personal data using the private key mapped to the first identifier (S823). The VASP#2 node 220 may then identify the recipient information in the decrypted personal data and determine whether the decrypted recipient information matches the subscriber information managed by itself, thereby verifying the recipient (S825). The VASP#2 node 220 may then transmit the recipient verification result and the first identifier to the verification node 300 (S827).

[0124] The verification node 300 that has received the recipient matching result and the first identifier may store the recipient matching result in the matching information having the first identifier (S829), and may further transmit the recipient matching result to the VASP #1 node 210. Next, if the recipient matching result is successful, the verification node 300 may transmit a signal to the VASP #2 node 220 to permit the update of the crypto asset (S831). In this case, the verification node 300 may transmit transaction data to the VASP #2 node 220, including the second identifier, the sender's address, the recipient's electronic wallet address, the type of crypto asset, and the amount of crypto asset. Furthermore, if the recipient matching result is unsuccessful, the verification node 300 may transmit a crypto asset update hold signal to the VASP #2 node 220.

[0125] When the VASP #2 node 220 receives a crypto asset update permission signal from the verification node 300, the VASP #2 node 220 may update the recipient's crypto asset by adding the amount of crypto asset to the recipient's crypto asset corresponding to the type of crypto asset based on the recipient's electronic wallet address, type of crypto asset, and amount of crypto asset included in the transaction data (S833). On the other hand, when the VASP #2 node 220 receives a crypto asset update hold signal, the VASP #2 node 220 may hold the recipient's crypto asset without increasing it.

[0126] The technical features of the above-described embodiments may be realized as computer-readable codes in a computer-readable medium. The computer-readable medium may be, for example, a removable recording medium (CD, DVD, Blu-ray (registered trademark) disk, USB storage device, removable hard disk) or a fixed recording medium (ROM, RAM, computer-mounted hard disk). The computer program recorded in the computer-readable medium may be transmitted to another computing device via a network such as the Internet, or may be installed in the other computing device and used in the other computing device.

[0127] Referring now to FIG. 10, an exemplary computing device capable of implementing apparatus and systems according to various embodiments will now be described.

[0128] Fig. 10 is an exemplary hardware configuration diagram that may realize a computing device in various embodiments. As shown in Fig. 10, the computing device 1000 may include one or more processors 1100, a bus 1600, a communication interface 1200, a memory 1400 that reads a computer program 1500 to be executed by the processor 1100, and a storage 1300 for storing the computer program 1500. However, Fig. 10 shows only components related to the embodiment of the present disclosure. It should be understood by those skilled in the art that the present disclosure may further include other general-purpose components in addition to the components shown in Fig. 10.

[0129] The processor 1100 may control the overall operation of each component of the computing device 1000. The processor 1100 may be configured to include at least one of a central processing unit (CPU), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), or any type of processor known in the art. The processor 1100 may also execute operations on at least one application or program to perform methods / operations according to various embodiments of the present disclosure. The computing device 1000 may include one or more processors 1100.

[0130] The memory 1400 may store various data, instructions, and / or information. The memory 1400 may load one or more computer programs 1500 from the storage 1300 to execute methods / operations according to various embodiments of the present disclosure. An example of the memory 1400 is, but is not limited to, a RAM.

[0131] The bus 1600 can provide communication between components of the computing device 1000. The bus 1600 can be implemented as various buses such as an address bus, a data bus, and a control bus. The communication interface 1200 supports wired and wireless Internet communication of the computing device 1000. The communication interface 1200 can support various communication methods other than Internet communication. To this end, the communication interface 1200 can be configured to include a communication module known in the art of this disclosure. The storage 1300 can non-temporarily store one or more computer programs 1500. The storage 1300 can be configured to include a non-volatile memory such as a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a flash memory, a hard disk, a removable disk, or any type of computer-readable recording medium known in the art.

[0132] The computer program 1500 may include one or more instructions that may implement the method / operation according to various embodiments of the present disclosure. Based on the computer program 1500 being loaded into the memory 1400, the processor 1100 may execute the one or more instructions to implement the method / operation according to various embodiments.

[0133] The computer program 1500 may include instructions for performing the operations of the above-mentioned VASP #1 node 210, VASP #2 node 220, or verification node 300. That is, the computer program 1500 may include one or more instructions for performing a method / operation associated with the VASP #1 node 210, one or more instructions for performing a method / operation associated with the VASP #2 node 220, or one or more instructions for performing a method / operation of the verification node 300.

[0134] Although all components constituting the embodiments of the present disclosure are described above as being combined or operated as one, the technical features of the present disclosure are not limited to these embodiments, that is, within the scope of the present disclosure, all components may be selectively combined and operated in one or more combinations.

[0135] Although the operations are shown in a certain sequence in the drawings, those skilled in the art should understand that numerous variations and modifications can be made to the embodiments without substantially departing from the principles of the present disclosure. The disclosed embodiments of the present disclosure can be used in a general and explanatory sense, not for the purpose of limitation. The scope of protection of the present disclosure should be interpreted by the following claims, and all technical ideas within the scope of equivalents thereto should be interpreted as being included in the scope of the technical ideas defined by the present disclosure.

Claims

1. A method for use in transmitting crypto assets from a sender having a sending account at a crypto asset service provider (sender VASP) on the sender's side to a recipient having a receiving account at a crypto asset service provider (recipient VASP) on the recipient's side, comprising: After verifying that the receiving account of the recipient VASP is valid, determining by a verification node whether the transmission of the crypto asset has been recorded on a blockchain network; After determining that the transmission has been recorded on the blockchain network, sending, by the verification node, to the recipient VASP, a recipient VASP receiving account update request for the transmission of the crypto asset from the sender to the recipient; The method, wherein the verification node does not belong to either the sender VASP or the recipient VASP.

2. The verification node stores in at least one storage device a transaction record including two or more selected from the group consisting of the type of crypto asset, the amount of the crypto asset, the name of the sender, the nationality of the sender, the address of the sender, the account number of the sending account of the sender at the sender VASP, the date of birth of the sender, the place of birth of the sender, the name of the recipient, and the account number of the receiving account at the recipient VASP; The method of claim 1 , wherein at least one of the storage devices does not belong to either the sender VASP or the recipient VASP.

3. 2. The method of claim 1, wherein the sender VASP initiates record keeping for the transmission of the crypto asset from the sender to the recipient on the blockchain network following verification that the receiving account at the recipient VASP is valid.

4. Following verification that the receiving account at the recipient VASP is valid, a transaction record is recorded on the blockchain network regarding the transmission of the crypto asset from the sender to the recipient; 2. The method of claim 1, wherein the transaction record for the sending includes two or more selected from the group consisting of the type of crypto asset, the amount of the crypto asset, the name of the sender, the nationality of the sender, the address of the sender, the account number of the sending account of the sender at the sender VASP, the date of birth of the sender, the place of birth of the sender, the name of the recipient, and the account number of the receiving account at the recipient VASP.

5. 5. The method of claim 4, wherein the transaction record is recorded on the blockchain network in response to a request to maintain the transaction record on the blockchain network.

6. 6. The method of claim 5, wherein a blockchain transaction identifier for identifying the transaction record is generated using at least a portion of data included in a request to persist the transaction record on the blockchain network.

7. the request to maintain the transaction record is made by the sender VASP; 7. The method of claim 6, wherein the blockchain transaction identifier is generated by the sender VASP.

8. Following verification that the receiving account at the recipient VASP is valid, the sender VASP sends a request to the verification node to verify a blockchain record relating to the transmission of the crypto asset from the sender to the recipient; the request to verify the blockchain record includes the blockchain transaction identifier; The verification node determines whether to communicate with the blockchain network to receive at least a portion of the transaction records and to process at least a portion of the transaction records received from the blockchain network; 7. The method of claim 6, wherein the verification node determines that the transmission of the crypto asset has been recorded in the blockchain network if at least a portion of the transaction record generates a code identical to the blockchain transaction identifier.

9. 2. The method of claim 1, further comprising the step of: prior to the sender VASP verifying that the receiving account at the recipient VASP is valid, the sender VASP assigns a unique identifier to a then-future transaction for the transmission of the crypto asset from the sender to the recipient, and then transmitting information regarding the receiving account and the unique identifier to the recipient VASP.

10. Prior to verifying that the receiving account at the recipient VASP is valid, the verifying node receives information regarding the receiving account from the sender VASP; 2. The method of claim 1, wherein information regarding the receiving account is encrypted, and the verifying node transmits the encrypted information regarding the receiving account to the recipient VASP to provide information for verifying the receiving account.

11. Prior to verifying that the receiving account at the recipient VASP is valid, the verifying node receives information regarding the receiving account from the sender VASP; 2. The method of claim 1, wherein the verification node, prior to receiving information regarding the receiving account, sends to the recipient VASP a request for a public key to be used for the then-current future transaction for the transmission of the crypto asset, receives from the recipient VASP the public key for the then-current future transaction, and forwards the public key to the sender VASP.

12. 12. The method of claim 11, wherein the public key request includes a security level, and the public key generated by the recipient VASP corresponds to the security level and encrypts information about the receiving account.

13. The information regarding the receiving account from the sender VASP is encrypted using the public key; the verification node transmits encrypted information regarding the receiving account to the recipient VASP to verify the receiving account; 13. The method of claim 12, wherein the recipient VASP uses the public key to decrypt encrypted information and process the receiving account verification.

14. 13. The method of claim 12, wherein the security level is dedicated to a then-current future transaction, and depending on the security level, the public key is used to encrypt one or more information selected from the group consisting of information dedicated to the then-current future transaction, information dedicated to the sender, information dedicated to the receiver, information dedicated to the sender VASP, and information dedicated to the receiver VASP.

15. 1. A method for use in transmitting crypto assets from a sender to a receiver, comprising: receiving, by a verification node, information regarding the recipient's receiving account at a recipient crypto asset service provider (recipient VASP) and a unique identifier assigned to the transaction for the transmission of the crypto asset from the sender to the recipient; a step by said verification node for verifying information regarding said receiving account; Following verification that the information regarding the receiving account is valid, communicating with a blockchain network by the verification node to determine whether the transaction has been recorded on the blockchain network using a unique identifier assigned to the transaction; and upon determining that the transaction has been recorded on the blockchain network, sending a request by the verification node to the recipient VASP to update the receiving account with the transaction of the transfer of the crypto asset from the sender to the recipient; The method, wherein the verification node does not belong to either the recipient VASP or the sending crypto asset service provider (sender VASP) where the sender holds a sending account.

16. The verification node stores in at least one storage device a transaction record including two or more selected from the group consisting of the type of crypto asset, the amount of the crypto asset, the name of the sender, the nationality of the sender, the address of the sender, the account number of the sending account of the sender at the sender VASP, the date of birth of the sender, the place of birth of the sender, the name of the recipient, and the account number of the receiving account at the recipient VASP; 16. The method of claim 15, wherein at least one of the storage devices does not belong to either the sender VASP or the recipient VASP.

17. 16. The method of claim 15, wherein after the matching and before sending the request, the sender VASP initiates record keeping of the transaction on the blockchain network.

18. After said verification and before sending the request, the transaction is recorded on said blockchain network; 16. The method of claim 15, wherein the transaction record of the transaction includes a unique identifier and includes two or more selected from the group consisting of the type of crypto asset, the amount of the crypto asset, the name of the sender, the nationality of the sender, the address of the sender, the account number of the sending account of the sender at the sender VASP, the date of birth of the sender, the place of birth of the sender, the name of the recipient, and the account number of the receiving account at the recipient VASP.

19. 20. The method of claim 18, wherein the transaction record is recorded on the blockchain network in response to a request by the sender VASP to maintain the transaction record on the blockchain network.

20. 16. The method of claim 15, wherein the information regarding the receiving account received from the sender VASP is encrypted, and the verification node transmits the encrypted information regarding the receiving account to the recipient VASP for verifying the information regarding the receiving account.

21. 16. The method of claim 15, wherein the verification node sends a request for a public key to the recipient VASP prior to receiving information regarding the receiving account, receives the public key for the transaction from the recipient VASP, and forwards the public key to the sender VASP, the transaction being the transmission of the crypto asset from the sender to the recipient.

22. 22. The method of claim 21, wherein the public key request includes a security level, and the public key generated by the recipient VASP corresponds to the security level and encrypts information about the receiving account.

23. The information regarding the receiving account from the sender VASP is encrypted using the public key; the verification node transmits encrypted information regarding the receiving account to the recipient VASP to verify the receiving account; 23. The method of claim 22, wherein the recipient VASP uses the public key to decrypt encrypted information and process the receiving account verification.

24. 23. The method of claim 22, wherein the security level is transaction specific, and depending on the security level, the public key is used to encrypt one or more information selected from the group consisting of information specific to the transaction, information specific to the sender, information specific to the recipient, information specific to the sender VASP, and information specific to the recipient VASP.

Images