Digital asset transaction system and method for operating same

Abstract

The present invention relates to a digital asset transaction system for supporting transactions of digital assets and to a method for operating same. An electronic device included in the digital asset transaction system may: generate a temporary identifier for identifying a digital transaction and provide the temporary identifier to a counterpart device; and identify whether a recipient address for performing the digital transaction is valid by using digital signature data obtained by querying an address-signature database on the basis of a substitute identifier and a random personal identification number provided by the counterpart device in response to the temporary identifier.

Description

Digital asset trading system and its operation method

[0001] The present disclosure relates to a digital asset trading system that supports trading of digital assets and a method for operating the same.

[0002] Digital assets, which are intangible assets, may include digital currency (hereinafter referred to as "digital currency"). These digital assets collectively refer to currencies that store monetary value in digital form, rather than physical form, and can be used as a means of payment. These digital assets may include virtual currency, electronic currency, digital private currency, or digital legal tender.

[0003] The aforementioned virtual currency may be a digital asset whose use is restricted to local communities or specific organizations, such as specific businesses, and is not legally recognized. The aforementioned virtual currency may also correspond to internet or mobile coupons, for example. The aforementioned electronic currency may be an electronic payment method where monetary value is stored in the form of electronic symbols, or digital information, on a card with an embedded IC chip or on an electronic device connected to a network, and then used for payment.

[0004] To use the above digital assets as a means of payment, they must be secure enough to prevent financial losses due to erroneous transactions and provide convenience to users.

[0005] According to one embodiment of the present disclosure, a method for trading digital assets based on a blockchain in an electronic device including a digital wallet comprises the steps of: generating a first temporary identifier (Nonce#1) to be shared with a first counterpart device capable of trading digital assets in order to verify a blockchain address; obtaining a first alternative identifier (NN#1: first nick name) and a first random personal identification number (RPIN#1: Random PIN#1 (first personal identification number)) for the first counterpart device; receiving a first encrypted public key (Enc_Pkey#1) and first digital signature data (SIG#1) from an address signature database in response to a query based on the first alternative identifier (NN#1); and decrypting the first encrypted public key (Enc_Pkey#1) using the first random personal identification number (RPIN#1) to obtain a first public key (Pub#1: first public key) of the first counterpart device. The method may include: converting the first public key (Pub#1) into a first recipient address (first crypto address); and identifying whether the first recipient address (first crypto address) is valid based on a first data set including first hash verification data, the first digital signature data (SIG#1), and the first public key (Pub#1). Here, the first hash verification data may be a hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address), and the first temporary identifier (Nonce#1).

[0006] According to one embodiment of the present disclosure, an electronic device may include at least one processor including a communication circuit, a memory including one or more storage media storing instructions, and a processing circuit. Here, the electronic device generates a first temporary identifier (Nonce#1) to be shared with a first counterpart device capable of digital asset trading to verify a blockchain address when the instructions are individually or collectively executed by at least one processor, obtains a first alternative identifier (NN#1: first nick name) and a first random personal identification number (RPIN#1: Random PIN#1 (first personal identification number)) for the first counterpart device, receives a first encrypted public key (Enc_Pkey#1) and first digital signature data (SIG#1) from an address signature database through the communication circuit in response to a query based on the first alternative identifier (NN#1), and decrypts the first encrypted public key (Enc_Pkey#1) using the first random personal identification number (RPIN#1) to obtain a first public key (Pub#1: first public key) of the first counterpart device, and A first public key (Pub#1) may be converted into a first recipient address (first crypto address), and a first data set including first hash verification data, the first digital signature data (SIG#1), and the first public key (Pub#1) may be configured to identify whether the first recipient address (first crypto address) is valid. The first hash verification data may be a hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address), and the first temporary identifier (Nonce#1).

[0007] In connection with the description of the drawings, the same or similar reference numerals may be used for the same or similar components.

[0008] Figure 1 is a schematic diagram of an exemplary digital asset trading system capable of performing the operations described in this document.

[0009] FIG. 2 is a block diagram of an exemplary electronic device capable of performing the operations described in this document.

[0010] FIG. 3 is a signaling flowchart for performing a digital asset transaction based on recipient address verification in a digital asset transaction system according to one embodiment of the present disclosure.

[0011] FIG. 4 is a state transition diagram for performing a digital asset transaction based on recipient address verification in a transmitting device according to one embodiment of the present disclosure.

[0012] FIG. 5 is a state transition diagram for performing a digital asset transaction in a receiving device according to one embodiment of the present disclosure.

[0013] FIG. 6 is a control flowchart for performing a digital transaction in an electronic device according to one embodiment of the present disclosure.

[0014] FIG. 7 is a control flow diagram for performing a digital asset transaction based on recipient address verification in a transmitting device according to one embodiment of the present disclosure.

[0015] FIG. 8 is a control flow diagram for performing a digital asset transaction based on recipient address verification in a receiving device according to one embodiment of the present disclosure.

[0016] FIG. 9 is a block diagram of an electronic device according to one embodiment of the present disclosure.

[0017] FIG. 10 is an example diagram of a user interface screen that may be displayed on a display according to a situation during a digital transaction in a transmitting device according to one embodiment of the present disclosure.

[0018] FIG. 11 is a control flowchart for verifying a new address during a P2P transaction in an electronic device according to one embodiment of the present disclosure.

[0019] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In connection with the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Furthermore, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and conciseness.

[0020] In various embodiments of the present disclosure, a digital asset transaction system and its operating method for verifying a recipient address based on pseudonymization for performing a digital transaction can be provided.

[0021] According to various embodiments of the present disclosure, a digital asset transaction system can verify recipient addresses based on pseudonymization to enable secure digital transactions, thereby preventing financial damage from occurring due to incorrect input of blockchain addresses, etc.

[0022] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned above can be derived from the exemplary embodiments of the present disclosure by a person having ordinary knowledge in the relevant technical field.

[0023] The effects that can be achieved by the exemplary embodiments of the present disclosure can be clearly derived and understood by those skilled in the art to which the exemplary embodiments of the present disclosure pertain, from the following description. In other words, unintended effects resulting from the implementation of the exemplary embodiments of the present disclosure can also be derived by those skilled in the art from the exemplary embodiments of the present disclosure.

[0024] FIG. 1 is a configuration diagram of an exemplary digital asset trading system (100) capable of performing the operations described in this document.

[0025] Referring to FIG. 1, a digital asset transaction system (100) may include at least one electronic device (110, 120) or at least one server that provides use of digital assets, such as trading (hereinafter referred to as “digital transaction”) or distribution of digital assets in a network environment (150). The at least one server (130) may include an address signature database (DB) server (130). The address signature DB server (130) may operate an address signature DB corresponding to a substitute identifier (NN: nick name) in which a recipient address (crypto address) of an electronic device (110, 120) is configured in a pseudonymized format, and an encrypted public key (Enc_Pkey) and digital signature data (SIG) are registered. The address signature DB may create and / or delete a signature table in which an encrypted public key (Enc_Pkey) and digital signature data (SIG) are registered for each substitute identifier (NN).

[0026] The blockchain main network (140) included in the digital asset transaction system (100) may have a structure capable of recording transactions in which digital assets enter and exit for each blockchain address on a distributed ledger (hyper ledger). All nodes of the blockchain main network (140) may be connected via the Internet. The nodes of the blockchain main network (140) may include the first and second electronic devices (110, 120). Nodes participating in the blockchain main network (140) may have equal authority. Since the nodes of the blockchain main network (140) store the same ledger, even if a single node is hacked or disappears, the transparency of information recorded in the ledger can be guaranteed.

[0027] For example, multiple nodes constituting the blockchain main network (140) may correspond to hosts that can execute an application (or app) (e.g., a digital wallet app for a personal account) in response to a specific event (e.g., a request for deposit, remittance, or withdrawal of digital assets). The specific event may, for example, be an event that can occur based on synchronization, with data processing being on-demand. The multiple nodes may perform processing through direct interaction with the user in the logic for performing digital wallet functions in response to the occurrence of the specific event (backend processing). The digital assets may be used as an electronic means of payment for purchasing or renting goods or using services. The amount (or unit of quantity) used for purchasing the goods or using the services may be deducted from the remaining amount (or remaining quantity) of the digital assets held.

[0028] When a digital transaction is performed in the digital asset transaction system (100), at least one transmitting device (e.g., a first electronic device (110)) and at least one receiving device (e.g., a second electronic device (120)) may exist. In this case, the first electronic device (110) may perform an operation for sending a digital asset, and the second electronic device (120) may perform an operation for receiving a digital asset.

[0029] The first or second electronic device (110, 120) may execute a wallet app for a personal account that manages digital assets, and perform a transaction using digital assets (hereinafter referred to as a "digital transaction operation") through the executed wallet app. The digital transaction operation may include, for example, an operation for paying for a purchase of goods with digital assets based on a network (150) (e.g., based on long-distance communication) or transferring digital assets to another account.

[0030] The first and / or second electronic devices (110, 120) may include a user terminal (e.g., a smart phone, a mobile phone, or a tablet device) that can be carried by a user, a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. The electronic devices in this document are not limited to the aforementioned devices. The first and / or second electronic devices (110, 120) may have an application program installed to provide various functions. The first and / or second electronic devices (110, 120) may execute the installed application program in response to a user's operation. The first and / or second electronic devices (110, 120) may display information according to the execution of the application program through a display.

[0031] According to an example, a transmitting device (e.g., a first electronic device (110)) may generate a temporary identifier (Nonce) as information for identifying a digital transaction. The temporary identifier may be a temporary value. The temporary value may be a random number having a predetermined number of bits that can be cryptographically randomly generated. Hereinafter, the temporary identifier will be used in the sense of including a temporary value.

[0032] The temporary identifier may be a one-time identifier for the digital transaction. The first electronic device (110) may randomly generate the temporary identifier. For example, when transferring a certain digital asset (e.g., 100BTS) to a counterpart device (e.g., a second electronic device (120)), the first electronic device (110) may randomly generate a temporary identifier indicating the digital transaction. The method for generating the temporary identifier may be defined in advance between the parties conducting the digital transaction.

[0033] The first electronic device (110) may perform validity verification on a recipient address to be used for a digital transaction based on an encrypted public key and digital signature data obtained by querying an address signature DB server (130). As an example, the first electronic device (110) may obtain a hash value for an alternative identifier (NN), a random personal identification number (RPIN (Random PIN (personal identification number)), a recipient address (Crypto Addr), and a temporary identifier (Nonce) as hash verification data (Hash(NN|Crypto Addr|RPIN|Nonce)). The random personal identification number (RPIN) may be a personal password or may include a personal password. The random personal identification number (RPIN) may be generated by a randomly selected number.

[0034] The first electronic device (110) can identify whether a recipient address (crypto address) is valid based on a data set including the hash verification data, digital signature data (SIG), and a public key (Pub). For example, the first electronic device (110) can determine the validity of a recipient address based on a return value of a predetermined digital signature verification function. The first electronic device (110) can use hash verification data, digital signature data (SIG), and a public key (Pub) as input values ​​of the digital signature verification function.

[0035] The first electronic device (110) may perform a procedure for a digital transaction to a recipient address corresponding to a pseudonymized substitute identifier. For example, the first electronic device (110) may transfer a desired amount of digital assets to the second electronic device (120) based on the pseudonymized substitute identifier. The first electronic device (110) may request the blockchain main network (140) to record the digital transaction details in a distributed ledger corresponding to a validated recipient address. The distributed ledger may be a ledger that records transactions involving incoming and outgoing digital assets on the blockchain.

[0036] According to one example, when a receiving device (e.g., a second electronic device (120)) receives a temporary identifier (Nonce) obtained from a second electronic device (110) that is a transmitting device, the receiving device may generate a key pair including a private key (Priv) and a public key (Pub). The second electronic device (120) may not generate a key pair every time it receives a temporary identifier from the first electronic device (110). If the second electronic device (120) already has a valid key pair, it may not generate a key pair even if it receives the temporary identifier, but may use the already generated key pair.

[0037] The second electronic device (120) can generate a substitute identifier (NN: nick name) corresponding to the temporary identifier. The second electronic device (120) can generate a random personal identification number (RPIN) corresponding to the temporary identifier. The second electronic device (120) can generate nickname data using the substitute identifier and the random personal identification number, and transmit the generated nickname data to the first electronic device (110).

[0038] The second electronic device (120) may generate digital signature data (SIG) for verifying a recipient address. For example, the second electronic device (120) may generate the digital signature data (SIG) using the alternative identifier (NN), the random personal identification number (RPIN), the recipient address (crypto address), and the temporary identifier (Nonce).

[0039] The second electronic device (120) may encrypt the public key (Pub) to generate an encrypted public key (Enc_Pkey) as a protective measure to prevent exposure of the public key (Pub) included in the key pair it has generated. The second electronic device (120) may encrypt the public key (Pub) using a password-based encryption method using, for example, a random personal identification number (RPIN) to generate the encrypted public key (Enc_Pkey = PBENC(Pub)). RPIN ) can be obtained. The second electronic device (120) can transmit the replacement identifier, the digital signature data, and the encrypted public key to the address signature DB server (130).

[0040] If the second electronic device (120) succeeds in verifying the validity of the recipient address by the first electronic device (110), the second electronic device (120) can perform a procedure for a digital transaction with the first electronic device (110).

[0041] FIG. 2 is a block diagram of an exemplary electronic device (e.g., the first or second electronic device (110 or 120) of FIG. 1) capable of performing the operations described in this document.

[0042] Referring to FIG. 2, the electronic device (200) may be one of various forms of electronic devices, such as a notebook (290), smartphones (291) having various form factors (e.g., a bar-type smartphone (291-1), a foldable-type smartphone (291-2), or a sliderable (or rollable) type smartphone (291-3)), a tablet (292), a cellular phone (not shown), and other similar computing devices (not shown). The components, their relationships, and their functions illustrated in FIG. 2 are exemplary only and do not limit the implementations described or claimed in this document. The electronic device (200) may be referred to as a mobile device, a user device, a multi-function device, a portable device, or a server.

[0043] The electronic device (200) may include components including at least one processor (210) (hereinafter referred to as processor (210)), at least one memory (220) (hereinafter referred to as memory (220)), at least one display (240) (hereinafter referred to as display (240)), at least one image sensor (250) (hereinafter referred to as image sensor (250)), at least one communication circuit (260) (hereinafter referred to as communication circuit (260)), and / or at least one sensor (270) (hereinafter referred to as sensor (270)). The above components are merely exemplary. For example, the electronic device (200) may include other components (e.g., power management integrated circuitry (PMIC), audio processing circuitry, an antenna, a rechargeable battery, or an input / output interface). For example, some components may be omitted from the electronic device (200). For example, some components may be integrated into one component.

[0044] The processor (210) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing. The processor (210) may include at least one electrical circuit and may individually or collectively perform distributed processing of instructions (or programs, data, etc.) stored in the memory (220). The processor (210) may include a processor assembly including one or more processing circuits. The processor (210) may include any processing circuit operative to control the performance and operations of one or more components (e.g., the memory (220), the display (240), the image sensor (250), the communication circuit (260), and / or the sensor (270)) of the electronic device (200). For example, the processor (210) (e.g., the application processor (AP)) may be implemented as a system on chip (SoC) (e.g., a single chip or a chipset). For example, the processor (210) may be implemented with multiple cores (or at least one core circuit), multiple chips, or multiple chipsets. For example, the processor (210) may include one or more processing circuits. For example, the processor (210) may include one or more processing circuits configured to individually and / or collectively perform various functions of the present disclosure. As a non-limiting example, at least a portion of the processor (210) may be included in a first chip of the electronic device (200), and at least another portion of the processor (210) may be included in a second chip of the electronic device (200) that is different from the first chip of the electronic device (200).

[0045] For example, the processor (210) may include a central processing unit (CPU) (211), a graphics processing unit (GPU) (212), a neural processing unit (NPU) (213), an image signal processor (ISP) (214), a display controller (215), a memory controller (216), a storage controller (217), a communication processor (CP) (218), and / or a sensor interface (219). These components of the processor (210) are merely exemplary. For example, the processor (210) may further include other components. For example, some components of the processor (210) may be omitted from the processor (210). For example, some components of the processor (210) may be included as separate components of the electronic device (200) outside the processor (210). For example, some components of the processor (210) (e.g., memory controller (216)) may be included within other components (e.g., at least a portion of memory (220), an interface (e.g., available for connection to at least one component of the electronic device (100)), a display (240) and / or an image sensor (250)).

[0046] The processor (210) may cause other components of the electronic device (200) to perform various operations by executing instructions stored in the memory (220). The CPU (211) (or central processing circuit) may be configured to control components of the processor (210) based on the execution of instructions stored in the memory (220) (e.g., volatile memory (221) and / or non-volatile memory (222)). The GPU (212) (or graphics processing circuit) may be configured to execute parallel operations (e.g., rendering). The NPU (213) (or neural processing circuit, or artificial intelligence (AI) chip) may be configured to execute operations for an artificial intelligence model (e.g., convolution computation). The ISP (214) (or image signal processing circuit) may be configured to process a raw image acquired through the image sensor (250) into a format suitable for a component within the electronic device (200) or a component of the processor (210). The display controller (215) (or display control circuit, or display processing unit (DPU)) may be configured to process an image acquired from the CPU (211), the GPU (212), the ISP (214), or the memory (220) (e.g., the volatile memory (221)) into a format suitable for the display (240). The memory controller (216) (or memory control circuit) may be configured to control reading data from the volatile memory (221) and writing data to the volatile memory (221). The storage controller (217) (or storage control circuit) may be configured to control reading data from the nonvolatile memory (222) and writing data to the nonvolatile memory (222).The CP (218) (communication processing circuit) may be configured to process data obtained from a component of the processor (210) into a format suitable for transmission to another electronic device via the communication circuit (260), or to process data obtained from another electronic device via the communication circuit (260) into a format suitable for processing by the component of the processor (210). For example, the communication circuit (260) may include one or more communication circuits. The sensor interface (219) (or sensing data processing circuit, sensor hub) may be configured to process data on the state of the electronic device (200) and / or the state of the surroundings of the electronic device (200), obtained via the sensor (270), into a format suitable for the component of the processor (210).

[0047] The memory (220) may include one or more storage media (or one or more storage devices). For example, the memory (220) may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory (e.g., non-volatile memory (222)) such as a hard drive, flash memory, read-only memory (ROM), semi-permanent memory (e.g., volatile memory (221)) such as random access memory (RAM), any other suitable type of storage (or storage assembly), or any combination thereof. The memory (220) may include cache memory, which is one or more different types of memory used to temporarily store data for a function or feature of the electronic device (200). As a non-limiting example, the cache memory may be included within the processor (210). The memory (220) may be fixedly embedded within the electronic device (200) or incorporated into one or more suitable types of components (e.g., a subscriber identity module (SIM) card and / or a secure digital (SD) card) that may be repeatedly inserted into and removed from the electronic device (200).

[0048] For example, the memory (220) may store one or more software applications, such as an operating system (or system) software application, a firmware software application, a driver software application, a plug-in (e.g., add-in, add-on, and / or applet) software application, and / or any other suitable software applications. For example, the one or more software applications may include instructions executable by the processor (210). For example, the memory (220) may store instructions callable by an application programming interface (API). For example, the memory (220) may store instructions within a library.

[0049] FIG. 3 is a signaling flowchart for performing a digital asset transaction based on recipient address verification in a digital asset transaction system (e.g., digital asset 10 of FIG. 1 ), according to one embodiment of the present disclosure. Although the signaling flowchart of FIG. 3 illustrates a first electronic device (e.g., the first electronic device (110) of FIG. 1 ) and / or a second electronic device (the second electronic device (120) of FIG. 1 ), it can be understood that the actual operations are performed by a digital wallet activated in the first electronic device (110) and / or the second electronic device (120). The first electronic device (110) is a transmitting device for digital transactions. The second electronic device (120) is a receiving device for digital transactions.

[0050] Referring to FIG. 3, a first electronic device (110) may generate a temporary identifier (Nonce) (operation 311). The first electronic device (110) may be a transmitting device that processes a predetermined digital transaction. The first electronic device (110) may generate the temporary identifier as information for identifying a digital transaction targeting a counterpart device (e.g., a second electronic device (120)), for example. The temporary identifier may be a one-time identifier for the digital transaction. The first electronic device (110) may randomly generate the temporary identifier. For example, when transferring a predetermined digital asset (e.g., 100BTS) to a counterpart device (e.g., a second electronic device (120)), the first electronic device (110) may randomly generate a temporary identifier indicating the digital transaction. The method for generating the temporary identifier may be defined in advance between the parties that will perform the digital transaction.

[0051] The first electronic device (110) can transmit the temporary identifier to the second electronic device (120). The first electronic device (110) can establish a communication link with the second electronic device (120), which is a counterpart device to which the temporary identifier will be transmitted. The communication link can be established based on a short-range communication method or a long-range communication method, and is not limited to the communication method. The short-range communication method can be based on a communication protocol such as Bluetooth, WiFi direct, or IrDA. The long-range communication method can be based on a communication protocol such as legacy cellular, 5G, next-generation communication, the Internet, or a computer network (e.g., LAN or WAN). As an example, the first electronic device (110) can transmit the temporary identifier as OOB data based on an out-of-band (OOB) method. The OOB method can be a data transmission method that is easy to transmit urgent data.

[0052] The second electronic device (120) may obtain the temporary identifier from the first electronic device (110). The second electronic device (120) may be a receiving device that performs a predetermined digital transaction with the first electronic device (110). For example, the second electronic device (120) may generate a key pair corresponding to the temporary identifier. The second electronic device (120) may not generate a key pair every time it receives the temporary identifier. For example, if the second electronic device (120) possesses a valid key pair, it may use the valid key pair without generating a new key pair. The key pair may include a private key (Priv) and a public key (Pub). The private key may be, for example, a blockchain secret key. The public key may be, for example, a blockchain public key. The public key may be converted into a recipient address (crypto address). The second electronic device (120) can manage the private key and / or the public key using a digital wallet. The digital wallet may be either a software wallet or a hardware wallet. The software wallet operates as software on a host device (e.g., the second electronic device (120)) and can store the private key within an interface. The hardware wallet may be a physical device that stores the private key in an offline state. The proposals in this disclosure can be commonly applied regardless of the type of digital wallet. The private key can define ownership of a digital asset. The second electronic device (120) can access the digital asset on the blockchain using the private key. The public key can be disclosed to a counterpart device (e.g., the first electronic device (110)) for digital transactions.The counterpart device (e.g., the first electronic device (110)) can encrypt predetermined data using the public key and transmit the encrypted data to the second electronic device (120) that is the owner of the public key. The predetermined data may be data for a digital transaction, such as sending or depositing digital assets. The second electronic device (120) can decrypt the encrypted data using a private key that forms a key pair with the public key.

[0053] The second electronic device (120) may generate a substitute identifier (nick name (NN)) corresponding to the temporary identifier (operation 313). The substitute identifier may be generated based on pseudonymization so that the recipient (e.g., the second electronic device (120)) can be identified without additional information through pseudonymization. The pseudonymization may be processed so that a query can be performed using the one-time substitute identifier in an address signature DB server (e.g., the address signature DB server (130) of FIG. 1) so that the target cannot be specified. For example, in order to avoid traceability of the substitute identifier, the substitute identifier may be generated by applying a cryptographic technique so that it is not mapped to the recipient address. The second electronic device (120) may follow a SHA-256, RIPEMD-160, or Base58 Encoding conversion method to generate the substitute identifier. The above-mentioned alternative identifier may be used in place of a recipient address (crypto address) that a counterparty device (e.g., the first electronic device (110)) can use for digital transactions with itself. The recipient address corresponds to an address that the counterparty device (e.g., the first electronic device (110)) will use to send digital assets to itself. The recipient address may be referred to by various terms such as "blockchain address," "cryptocurrency address," "encryption address," or "digital wallet address." In the following description, the term "recipient address" will be used for ease of understanding. The recipient address may be generated based on a public key included in a key pair for digital transactions. For example, the public key may be converted into the recipient address. The recipient address may change for each digital transaction. The recipient address may change in response to a change request. The recipient address may be identified, for example, as an unspent transaction output (UTXO) or a spent transaction output (STXO).The UTXO can be identified as having not been used after being transmitted by a payment transaction (including the issuance of digital assets). The STXO can be identified as having already been used after being transmitted by a payment transaction (including the issuance of digital assets). In other words, the UTXO is a digital asset that has not been used in a digital transaction, and the STXO is a digital asset that has been used in a digital transaction. The recipient address is a random string of English uppercase and lowercase letters or numbers (e.g., 0x2A144B0E4066C7a43d215B2B0841ac3E0b884E2A), which may be difficult to intuitively recognize or remember. In contrast, the alternative identifier may be composed of a combination of numbers and letters that is relatively simplified compared to the recipient address. The alternative identifier may be, for example, "goodboy."

[0054] The second electronic device (120) may generate a random personal identification number (RPIN) corresponding to the temporary identifier (operation 313). The random personal identification number may be a personal password that can be randomly generated to identify the user. The random personal identification number may be a personal password randomly generated based on a predetermined algorithm to confirm the user's identity as the second electronic device (120), a digital wallet, or the owner of the digital wallet. The random personal identification number may be composed of a combination of numbers (0-9) with a predetermined number of digits (e.g., 4 or 6 digits) considering the possibility of human memorization, for example. The algorithm for generating the random personal identification number in the present disclosure is not limited to a specific method.

[0055] The second electronic device (120) can generate digital signature data (SIG) for verifying the recipient address. For example, the second electronic device (120) can generate the digital signature data (SIG) by the alternative identifier (NN), the random personal identification number (RPIN), the recipient address (crypto address), and the temporary identifier (Nonce). For example, the second electronic device (120) can obtain a hash value by using a concatenation data set consisting of the alternative identifier (NN), the recipient address (Crypto Addr), the random personal identification number (RPIN), and the temporary identifier (Nonce) as inputs to a predetermined hash function, as defined by the following <Mathematical Formula 1>, and can generate digital signature data (SIG) by signing the obtained hash value with a private key (Priv).

[0056]

[0057] The second electronic device (120) may encrypt the public key (Pub) to generate an encrypted public key (Enc_Pkey) as a protective measure to prevent exposure of the public key (Pub) included in the key pair it has generated (Operation 313). The second electronic device (120) may encrypt the public key (Pub) using a password-based encryption method using, for example, a random personal identification number (RPIN) to generate the encrypted public key (Enc_Pkey = PBENC(Pub)). RPIN ) can be obtained.

[0058] The second electronic device (120) may transmit the alternative identifier, the digital signature data, and the encrypted public key to the address signature DB server (130) (operation 313). The second electronic device (120) may transmit the alternative identifier, the digital signature data, and the encrypted public key sequentially, in partial bundles, or in batches.

[0059] The second electronic device (120) can generate alias data using the alternative identifier and the random personal identification number, and transmit the generated alias data to the first electronic device (110) (operation 315). That is, the second electronic device (120) can provide the alias data to the first electronic device (110) in place of the recipient address. The second electronic device (120) can transmit the alias data in response to a request from the first electronic device (110). The second electronic device (120) can establish a communication link with a counterpart device (e.g., the first electronic device (110)) to which the alias data will be transmitted. The communication link can be established based on a short-range communication method or a long-range communication method, but is not limited thereto. The short-range communication method or the long-range communication method can be as defined above. The second electronic device (120) may, for example, transmit the alias data as OOB data based on the OOB method.

[0060] As described above, in order to generate the key pair, the alternative identifier, the digital signature data or the encrypted public key, and / or to transmit the alternative identifier, the digital signature data or the encrypted public key, the second electronic device (120) may activate a digital wallet that supports digital transactions.

[0061] The address signature DB electronic device (110 or 120) may receive the alternative identifier, the digital signature data, or the encrypted public key from the second electronic device (120) (operation 313). The address signature DB electronic device (110 or 120) may generate a signature DB table to register the alternative identifier, the digital signature data, or the encrypted public key in the address signature DB (operation 317). The address signature DB electronic device (110 or 120) may register the alternative identifier, the digital signature data, or the encrypted public key in the signature DB table in the form of a tuple. The tuple form may be a form by a collection of attribute values ​​related to a given list in the DB.

[0062] below shows an example of a signature DB table in which the above-mentioned replacement identifier, the above-mentioned digital signature data, or the above-mentioned encrypted public key is registered in the form of a tuple.

[0063] Alternative identifier Digital signature Data encryption Public key goodboy0x784512312...0xabcde1234............

[0064] The first electronic device (110) can receive the alias data from the second electronic device (120) (operation 315). The first electronic device (110) can obtain the alternative identifier and the random personal identification number from the alias data.

[0065] The first electronic device (110) may query the address signature DB electronic device (110 or 120) to obtain the digital signature data and / or the encrypted public key (operation 319). As an example, the first electronic device (110) may query the address signature DB electronic device (110 or 120) using the alternative identifier as a key value.

[0066] The address signature DB electronic device (110 or 120) may receive a query requesting provision of the digital signature data and / or the encryption public key from the first electronic device (110) (operation 319). The address signature DB electronic device (110 or 120) may obtain the alternative identifier through the received query. The address signature DB electronic device (110 or 120) may read the digital signature data and / or the encryption public key, the provision of which is requested by the first electronic device (110), from a signature DB table generated in the address signature DB using the obtained alternative identifier. The digital signature data and / or the encryption public key registered in the signature DB table may be operated in an open query manner. The open query manner is a method of automatically deleting data that has been queried once from the address signature DB. This is to prevent reuse or tracking by limiting the use of data to one time.

[0067] The address signature DB electronic device (110 or 120) can transmit the digital signature data and / or the encrypted public key read from the signature DB table to the first electronic device (110) (operation 321). The address signature DB electronic device (110 or 120) can transmit the digital signature data and / or the encrypted public key sequentially, in partial bundles, or in batches.

[0068] The above address signature DB electronic device (110 or 120) may, in response to the query, transmit the digital signature data and / or the encryption public key to the first electronic device (110), and may discard the signature DB table in which the digital signature data and / or the encryption public key is registered.

[0069] The first electronic device (110) can receive the digital signature data and the encrypted public key from the address signature DB electronic device (110 or 120) (operation 321).

[0070] The first electronic device (110) can perform validation of a recipient address to be used for a digital transaction with the second electronic device (120) based on the encrypted public key and the digital signature data (operation 323).

[0071] According to an example, the first electronic device (110) can decrypt the encrypted public key (Enc_Pkey) using the random personal identification number (RPIN) (Pub = PBDEC (Enc_Pkey) RPIN ). The first electronic device (110) can obtain the public key (Pub) of the counterpart device (e.g., the second electronic device (120)) by decrypting the encrypted public key. The first electronic device (110) can convert the public key (Pub) into a recipient address (crypto address) of the counterpart device (e.g., the second electronic device (120)). Common methods for converting the public key into the recipient address include, for example, the SHA-256 method, the RIPEMD-160 method, or the Base58 Encoding method.

[0072] The first electronic device (110) may generate hash verification data to perform verification on the digital signature data. For example, the first electronic device (110) may obtain hash values ​​for the alternative identifier (NN), the random personal identification number (RPIN), the recipient address (Crypto Addr), and the temporary identifier (Nonce) as the hash verification data (Hash(NN|Crypto Addr|RPIN|Nonce)).

[0073] The first electronic device (110) can identify whether a recipient address (crypto address) is valid based on a data set including the hash verification data, the digital signature data (SIG), and the public key (Pub) (operation 323). For example, the first electronic device (110) can determine the validity of the recipient address based on a return value of a predetermined digital signature verification function. The first electronic device (110) can use the hash verification data, the digital signature data (SIG), and the public key (Pub) included in the data set as input values ​​of the digital signature verification function.

[0074] The following <Mathematical Formula 2> defines an example of the above digital signature verification function.

[0075]

[0076] The first electronic device (110) may output an identification result corresponding to the determination result of the validity of the recipient address. The first electronic device (110) may output the identification result as visual information through a display. The first electronic device (110) may output the identification result as auditory information through a speaker. The first electronic device (110) may output the identification information as visual information through a display and as auditory information through a speaker. If the recipient address is valid, the first electronic device (110) may predict that it will be able to normally process a digital transaction with a counterpart device (e.g., a second electronic device (120)) using the recipient address. If the recipient address is invalid, the first electronic device (110) may predict that it will not be able to normally process a digital transaction with a counterpart device (e.g., a second electronic device (120)) using the recipient address.

[0077] If the first electronic device (110) determines that the recipient address is valid, it can perform a procedure for a digital transaction with the recipient address (operation 325). For example, the first electronic device (110) can transfer a desired amount of digital assets to the recipient address. The first electronic device (110) can request the blockchain main network (e.g., the blockchain main network (140) of FIG. 1) to record the digital transaction details in a distributed ledger (hyper ledger) corresponding to the validated recipient address (operation 325). The distributed ledger may be a ledger that records transactions involving incoming and outgoing digital assets on the blockchain.

[0078] If the first electronic device (110) determines that the recipient address is invalid, it can inform the user through a user interface that the recipient address is not suitable for trading the digital asset. For example, the first electronic device (110) can output visual information through a display indicating that the recipient address is invalid. The first electronic device (110) can output auditory information through a speaker indicating that the recipient address is invalid. The first electronic device (110) can output visual information through the display and auditory information through a speaker indicating that the recipient address is invalid.

[0079] FIG. 4 is a state transition diagram for performing a digital asset transaction based on recipient address verification in a transmitting device (e.g., the first electronic device (110) of FIG. 1 ), according to one embodiment of the present disclosure. The actual operations according to the state transition diagram of FIG. 4 can be understood as being performed by a digital wallet activated in the first electronic device (110), which is the transmitting device.

[0080] Referring to FIG. 4, the transmitting device (110) may perform an operation in one of a plurality of operating states (e.g., waiting (410), verification (420), or transaction (430)) for a digital transaction. The waiting state (410), which is one of the plurality of operating states, may be an operating state before a digital transaction is requested. The verification state (420), which is one of the plurality of operating states, may be an operating state for performing verification on a recipient address in order to process a digital transaction. The transaction state (430), which is one of the plurality of operating states, may be an operating state for performing a digital transaction to a recipient address whose validity has been verified in the verification state (420). The transmitting device (110) may perform an operation according to a digital transaction by transitioning between the plurality of operating states depending on the situation.

[0081] According to an example, the transmitting device (110) may generate a temporary identifier (Nonce) in the standby state (410) (operation 411). The transmitting device (110) may generate the temporary identifier as information for identifying a digital transaction to be processed for a receiving device (e.g., a second electronic device (120)). The temporary identifier may be a one-time identifier for the corresponding digital transaction. The transmitting device (110) may randomly generate the temporary identifier. The method for generating the temporary identifier may be defined in advance between the parties to perform the digital transaction.

[0082] The transmitting device (110) may transmit the temporary identifier to the receiving device (120) in the standby state (410) (operation 411). The transmitting device (110) may establish a communication link with the receiving device (120) to transmit the temporary identifier. The communication link may be established based on a short-range communication method or a long-range communication method, but is not limited to the communication method. As an example, the transmitting device (110) may transmit the temporary identifier as OOB data based on an OOB method.

[0083] The transmitting device (110) may transition from the standby state (410) to the verification state (420) in response to the activation of the digital wallet (operation 413). The digital wallet may be activated by a user executing a corresponding application program. Activation of the digital wallet causes the display of the transmitting device (110) to output a user interface screen corresponding to the digital wallet.

[0084] The transmitting device (110) may receive alias data from the receiving device (120) in the verification state (420) (operation 421). The alias data may include, for example, a substitute identifier (NN) and / or a random personal identification number (RPIN) generated by the receiving device (120).

[0085] The transmitting device (110) can obtain a substitute identifier (NN) from the alias data in the verification state (420). The substitute identifier can be created based on pseudonymization so that the recipient (e.g., the receiving device (120) or the recipient's digital wallet) can be identified without additional information through pseudonymization. The pseudonymization can be processed so that the transmitting device (110) can query an address signature DB server (e.g., the address signature DB electronic device (110 or 120) of FIG. 1) using the one-time substitute identifier so that the target cannot be identified. For example, in order to avoid traceability of the substitute identifier, the substitute identifier can be created by applying a cryptographic technique so that it is not mapped to a recipient address. The substitute identifier can replace a recipient address (crypto address) that a counterparty device (e.g., the first electronic device (110)) can use for digital transactions with itself. The above recipient address corresponds to the address that the sending device (110) will use to send the digital asset to the receiving device (120). Sending the digital asset to the receiving device (120) may actually mean recording it in a distributed ledger on the blockchain main network (e.g., the blockchain main network (140) of FIG. 1). The digital transaction to be described later may also be understood in the same technical sense. The recipient address may be a random string of English uppercase and lowercase letters or numbers (e.g., 0x2A144B0E4066C7a43d215B2B0841ac3E0b884E2A), which may be difficult to intuitively recognize or remember. In contrast, the alternative identifier may be composed of a combination of numbers and letters that is relatively simplified compared to the recipient address. The alternative identifier may be, for example, “goodboy.”

[0086] The transmitting device (110) may obtain a random personal identification number (RPIN (Random PIN (personal identification number))) from the alias data in the verification state (420) (operation 421). The random personal identification number may be randomly generated by the receiving device (120) to identify the receiving device (120). The random personal identification number may be randomly generated based on a predetermined algorithm to confirm the receiving device (120), the digital wallet, or the owner of the digital wallet. The random personal identification number may be composed of a combination of numbers (0 to 9) having a predetermined number of digits (e.g., 4 or 6 digits) considering the possibility of human memorization, for example. The present disclosure will not limit the algorithm for generating the random personal identification number in a specific manner.

[0087] The transmitting device (110) can query an address signature DB server (e.g., the address signature DB electronic device (110 or 120) of FIG. 1) in the verification state (420) to receive digital signature data (SIG) (operation 423). The transmitting device (110) can query the address signature DB electronic device (110 or 120) using the alternative identifier as a key value. The digital signature data can be generated by the receiving device (120) and registered in the address signature DB electronic device (110 or 120). The digital signature data can be generated by signing a hash value obtained by inputting a concatenation data set consisting of an alternative identifier (NN), a recipient address (Crypto Addr), a random personal identification number (RPIN), and a temporary identifier (Nonce) into a predetermined hash function using a private key (Priv) of the receiving device (120). An example of generating the above digital signature data is as defined by the above <Mathematical Formula 1>.

[0088] The transmitting device (110) can query the address signature DB electronic device (110 or 120) in the verification state (420) to receive the encrypted public key (Enc_Pkey) of the receiving device (120) (operation 423). The transmitting device (110) can query the address signature DB electronic device (110 or 120) using the alternative identifier as a key value. The encrypted public key can be generated by encrypting the public key (Pub) as a protection measure to prevent exposure of the public key (Pub) included in the key pair generated by the receiving device (120). As an example, the encrypted public key (Enc_Pkey = PBENC(Pub) RPIN ) can be generated by encrypting the public key (Pub) using a password-based encryption method using a random personal identification number (RPIN).

[0089] The above transmitting device (110) can perform validation of a recipient address to be used for a digital transaction with the receiving device (120) based on the encrypted public key (Enc_Pkey) and the digital signature data (SIG) in the verification state (420) (operation 425).

[0090] According to an example, the transmitting device (110) can decrypt the encrypted public key (Enc_Pkey) using the random personal identification number (RPIN) in the verification state (420) (Pub = PBDEC (Enc_Pkey) RPIN). The transmitting device (110) can obtain the public key (Pub) of the receiving device (120) by decrypting the encrypted public key. The transmitting device (110) can convert the public key (Pub) into a recipient address (crypto address) of the receiving device (120). Common methods for converting the public key into the recipient address include, for example, the SHA-256 method, the RIPEMD-160 method, or the Base58 Encoding method.

[0091] The transmitting device (110) may generate hash verification data to perform verification on the digital signature data in the verification state (420). For example, the transmitting device (110) may obtain hash values ​​for the alternative identifier (NN), the random personal identification number (RPIN), the recipient address (Crypto Addr), and the temporary identifier (Nonce) as the hash verification data (Hash(NN|Crypto Addr|RPIN|Nonce)).

[0092] The transmitting device (110) can identify whether the recipient address (crypto address) is valid based on a data set including the hash verification data, the digital signature data (SIG), and the public key (Pub) in the verification state (420). For example, the transmitting device (110) can determine the validity of the recipient address based on a return value of a predetermined digital signature verification function. The transmitting device (110) can use the hash verification data, the digital signature data (SIG), and the public key (Pub) included in the data set as input values ​​of the digital signature verification function. An example of the digital signature verification function is as defined in the above <Mathematical Formula 2>.

[0093] The transmitting device (110) may output an identification result corresponding to the determination result regarding the validity of the recipient address in the verification state (420). The transmitting device (110) may output the identification result as visual information through a display. The transmitting device (110) may output the identification result as auditory information through a speaker. The transmitting device (110) may output the identification information as visual information through a display and auditory information through a speaker.

[0094] The transmitting device (110) may transition from the verification state (420) to the transaction state (430) in response to the recipient address being valid (operation 427). If the recipient address is valid, the transmitting device (110) can be expected to successfully process a digital transaction with the receiving device (120) using the recipient address.

[0095] The transmitting device (110) may perform a procedure for a digital transaction with the recipient address in the transaction state (430) (operation 431). For example, the transmitting device (110) may transfer a desired amount of digital assets to the recipient address. The transmitting device (110) may request the blockchain main network (140) to record the digital transaction details in a distributed ledger corresponding to the validated recipient address. The distributed ledger may be a ledger that records transactions of digital assets entering and leaving the blockchain. After completing the digital transaction, the transmitting device (110) may deactivate the digital wallet (operation 433). Deactivating the digital wallet may correspond to, for example, terminating an application program corresponding to the digital wallet. In response to the deactivation of the digital wallet, the transmitting device (110) may transition from the transaction state (430) to the standby state (410).

[0096] The transmitting device (110) may predict that, if the recipient address is invalid, it will not be able to normally process a digital transaction with a counterpart device (e.g., the receiving device (120)) using the recipient address. If the transmitting device (110) determines that the recipient address is invalid, it may guide the user through the user interface in the verification state (420) that the recipient address is not suitable for the transaction of the digital asset. For example, the transmitting device (110) may output visual information through a display that the recipient address is invalid. The transmitting device (110) may output auditory information through a speaker that the recipient address is invalid. The transmitting device (110) may output visual information through a display and auditory information through a speaker that the recipient address is invalid.

[0097] The above transmitting device (110) may transition from the verification state (420) to the waiting state (410) after notifying that the recipient address is not suitable for trading the digital asset.

[0098] FIG. 5 is a state transition diagram for performing a digital asset transaction in a receiving device (e.g., the second electronic device (120) of FIG. 1 ), according to one embodiment of the present disclosure. It can be understood that the actual operations according to the state transition diagram of FIG. 5 are performed by a digital wallet activated in the second electronic device (120), which is the receiving device.

[0099] Referring to FIG. 5, the receiving device (120) may perform an operation in one of a plurality of operation states (e.g., waiting (510), registering (520), or trading (530)) for a digital transaction. The waiting state (510), which is one of the plurality of operation states, may be an operation state before a digital transaction is requested. The registering state (520), which is one of the plurality of operation states, may be an operation state for registering a data set to replace a recipient address in an address signature DB server (e.g., the address signature DB server (130) of FIG. 1) in order to process a digital transaction. The transaction state (530), which is one of the plurality of operation states, may be an operation state for performing a digital transaction using a verified recipient address. The receiving device (120) may perform an operation according to a digital transaction by transitioning between the plurality of operation states depending on the situation.

[0100] According to an example, the receiving device (120) may obtain a temporary identifier (Nonce) from the transmitting device (110) in the standby state (510) (operation 511). The temporary identifier may be a one-time identifier for the corresponding digital transaction. The receiving device (120) may establish a communication link with the transmitting device (110) to receive the temporary identifier. The communication link may be established based on a short-range communication method or a long-range communication method, but is not limited to the communication method. As an example, the receiving device (120) may receive the temporary identifier as OOB data based on an OOB method.

[0101] The receiving device (120) may transition from the standby state (510) to the registered state (520) in response to the activation of the digital wallet (operation 513). The digital wallet may be activated by a user executing a corresponding application program. Activation of the digital wallet causes the display of the receiving device (120) to display a user interface screen corresponding to the digital wallet.

[0102] The receiving device (120) can generate a key pair in the registration state (520) (operation 521). For example, when the receiving device (120) receives a temporary identifier (Nonce) from the transmitting device (110), the receiving device (120) can generate a key pair including a private key (Priv) and a public key (Pub). The receiving device (120) may not generate a key pair every time it receives a temporary identifier from the transmitting device (110). If the receiving device (120) already has a valid key pair, it may use the already generated key pair without generating a new key pair even if it receives the temporary identifier.

[0103] The private key may be, for example, a blockchain secret key. The public key may be, for example, a blockchain public key. The public key may be converted into a recipient address (crypto address). The receiving device (120) may manage the private key and / or the public key using a digital wallet. The digital wallet may be either a software wallet or a hardware wallet. The software wallet operates as software on a host device (e.g., the receiving device (120)) and may store the private key within an interface. The hardware wallet may be a physical device that stores the private key in an offline state. The proposals in this disclosure may be commonly applied regardless of the type of digital wallet. The private key may define ownership of a digital asset. The receiving device (120) may access the digital asset on the blockchain using the private key. The receiving device (120) may access the digital asset using the private key only when a transaction that may change the state of the digital asset on the blockchain is performed. The receiving device (120) may not use the private key when accessing a digital asset, for example, to simply query information about the digital asset. The public key may be disclosed to the transmitting device (110) for digital transactions. The transmitting device (110) may use the public key to encrypt certain data and transmit the encrypted data to the receiving device (120), which is the owner of the public key. The certain data may be data for digital transactions, such as sending or depositing digital assets.

[0104] The receiving device (120) may generate a substitute identifier (NN) corresponding to the temporary identifier (operation 523). The substitute identifier may be created based on pseudonymization so that the recipient (e.g., the receiving device (120)) can be identified without additional information through pseudonymization. The pseudonymization may be processed so that the target cannot be specified by allowing a query using the one-time substitute identifier in the address signature DB electronic device (110 or 120). For example, in order to avoid traceability of the substitute identifier, the substitute identifier may be generated by applying a cryptographic technique so that it is not mapped to the recipient address. The receiving device (120) may follow a 'SHA-256', 'RIPEMD-160', or 'Base58 Encoding' conversion method to generate the substitute identifier. The substitute identifier may be used in place of a recipient address (crypto address) that the transmitting device (110) can use for digital transactions with itself. The above recipient address corresponds to the address that the transmitting device (110) will use to send the digital asset to itself. The recipient address is a random string of English uppercase and lowercase letters or numbers (e.g., 0x2A144B0E4066C7a43d215B2B0841ac3E0b884E2A), which may be difficult to intuitively recognize or remember. In contrast, the alternative identifier may be composed of a combination of numbers and letters that is relatively simplified compared to the recipient address. The alternative identifier may be, for example, “goodboy.”

[0105] The receiving device (120) may generate a random personal identification number (RPIN) corresponding to the temporary identifier in the registration state (520) (operation 523). The random personal identification number may be an identification number that can be randomly generated to identify oneself. The random personal identification number may be randomly generated based on a predetermined algorithm to confirm the receiving device (120), the digital wallet, or the owner of the digital wallet. The random personal identification number may be composed of a combination of numbers (0-9) with a predetermined number of digits (e.g., 4 or 6 digits) considering the possibility of human memorization, for example. The algorithm for generating the random personal identification number in the present disclosure is not limited to a specific method.

[0106] The receiving device (120) can generate alias data using the alternative identifier and the random personal identification number in the registration state (520), and transmit the generated alias data to the transmitting device (110) (operation 523). That is, the receiving device (120) can provide the alias data to the transmitting device (110) in place of a recipient address. The receiving device (120) can transmit the alias data in response to a request from the transmitting device (110). The receiving device (120) can establish a communication link with the transmitting device (110) to transmit the alias data. The communication link can be established based on a short-range communication method or a long-range communication method, but is not limited to the communication method. The short-range communication method or the long-range communication method can be as defined above. The receiving device (120) can, for example, transmit the alias data as OOB data based on an OOB method.

[0107] The receiving device (120) may generate digital signature data (SIG) for verifying the recipient address in the registration state (520) (operation 525). For example, the receiving device (120) may generate the digital signature data (SIG) by the alternative identifier (NN), the random personal identification number (RPIN), the recipient address (crypto address), and the temporary identifier (Nonce). An example of generating the digital signature data is as defined by the above <Mathematical Formula 1>.

[0108] The receiving device (120) may encrypt the public key (Pub) to generate an encrypted public key (Enc_Pkey) as a protective measure to prevent the exposure of the public key (Pub) included in the key pair generated by the receiving device (520) in the registration state (520) (operation 525). The receiving device (120) may encrypt the public key (Pub) using a password-based encryption method using, for example, a random personal identification number (RPIN) to generate the encrypted public key (Enc_Pkey = PBENC(Pub)). RPIN ) can be obtained.

[0109] The receiving device (120) may transmit the replacement identifier, the digital signature data, and the encrypted public key to the address signature DB server (130) in the registration state (520) (operation 525). The receiving device (120) may transmit the replacement identifier, the digital signature data, and the encrypted public key sequentially, in partial bundles, or in batches.

[0110] The receiving device (120) may transition from the registration state (520) to the transaction state (530) in response to the occurrence of a digital asset transaction event (operation 527). The digital asset transaction event may occur in response to recognizing that a digital asset from the transmitting device (110) is to be transferred.

[0111] The receiving device (120) may perform a procedure for a digital transaction with the transmitting device (110) in the transaction state (530) (operation 531). For example, the receiving device (120) may receive a desired amount of digital assets to the recipient address. The digital transaction details will be recorded in a distributed ledger corresponding to the recipient address, which is the address of the receiving device (120) whose validity has been confirmed. After completing the digital transaction, the receiving device (120) may deactivate the digital wallet (operation 533). Deactivating the digital wallet may correspond to, for example, terminating an application program corresponding to the digital wallet. In response to the deactivation of the digital wallet, the receiving device (120) may transition from the transaction state (530) to the standby state (510).

[0112] FIG. 6 is a control flowchart for performing a digital transaction in an electronic device (e.g., the first electronic device (110) or the second electronic device (120) of FIG. 1 ) according to one embodiment of the present disclosure. While the following description assumes the first electronic device (110), it should be understood that the same operations can be performed in the second electronic device (120). The actual operations according to the control flowchart of FIG. 6 can be understood as being performed by a digital wallet activated in the first electronic device (110).

[0113] Referring to FIG. 6, the electronic device (110) may activate a digital wallet at operation 611. The electronic device (110) may activate the digital wallet in response to a user executing a corresponding application program. In response to the activation of the digital wallet, the electronic device (110) may output a user interface screen corresponding to the digital wallet through the display.

[0114] The electronic device (110) may determine, in operation 613, whether a digital transaction event corresponding to a withdrawal (or remittance) of a digital asset has occurred. The electronic device (110) may determine, in operation 615, whether a digital transaction event corresponding to a deposit of a digital asset has occurred.

[0115] When a digital event corresponding to the withdrawal of a digital asset occurs, the electronic device (110) may perform a procedure for withdrawing or transferring the digital asset to a predetermined recipient address in operation 617. The detailed operation performed by the electronic device (110) in operation 617 will be described later with reference to FIG. 7.

[0116] When a digital event corresponding to a deposit of a digital asset occurs, the electronic device (110) can perform a deposit procedure using its own address as the recipient address in operation 619. The detailed operation performed by the electronic device (110) in operation 619 will be described later with reference to FIG. 8.

[0117] The electronic device (110) may determine, at operation 621, whether a request to deactivate a digital wallet has been received. The request to deactivate the digital wallet may be, for example, generated by a request to terminate an application corresponding to the digital wallet. If a request to deactivate the digital wallet is generated, the transmitting device (110) may deactivate the digital wallet by terminating the application corresponding to the digital wallet at operation 623.

[0118] As described above, the electronic device (110) can adaptively perform operations as a transmitting device or a receiving device depending on the type of digital transaction.

[0119] FIG. 7 is a control flowchart for performing a digital asset transaction based on recipient address verification in a transmitting device (e.g., the first electronic device (110) of FIG. 1 ), according to one embodiment of the present disclosure. The actual operations according to the control flowchart of FIG. 7 can be understood as being performed by a digital wallet activated in the first electronic device (110), which is the transmitting device.

[0120] Referring to FIG. 7, the transmitting device (110) may generate a temporary identifier (Nonce) in operation 711 and transmit the generated temporary identifier to the receiving device (e.g., the second electronic device (120) of FIG. 1). The transmitting device (110) may generate the temporary identifier as information for identifying a digital transaction to be processed by the receiving device (120). The temporary identifier may be a one-time identifier for the corresponding digital transaction. The transmitting device (110) may randomly generate the temporary identifier. The method for generating the temporary identifier may be defined in advance between the parties to perform the digital transaction. The transmitting device (110) may establish a communication link with the receiving device (120) to transmit the temporary identifier. The communication link may be established based on a short-range communication method or a long-range communication method, but is not limited to the communication method. As an example, the transmitting device (110) may transmit the temporary identifier as OOB data based on an OOB method.

[0121] The above transmitting device (110) can receive alias data from the receiving device (120) in operation 713.

[0122] The transmitting device (110) may, in operation 713, obtain a substitute identifier (NN) from the alias data. The substitute identifier may be created based on pseudonymization so that the recipient (e.g., the receiving device (120) or the recipient's digital wallet) can be identified without additional information through pseudonymization. The pseudonymization may be processed so that a query can be performed using the temporary identifier, which is a one-time thing, in an address signature DB server (e.g., the address signature DB electronic device (110 or 120) of FIG. 1), so that the target cannot be identified. For example, the temporary identifier may be created by applying a cryptographic technique so that it cannot be mapped to a recipient address in order to avoid traceability. The substitute identifier may be used by the transmitting device (110) for digital transactions with the receiving device (120) in place of a recipient address (crypto address). The recipient address may be used by the transmitting device (110) to send a digital asset to the receiving device (120). Sending the digital asset to the receiving device (120) may actually mean recording it in a distributed ledger on the blockchain main network (e.g., the blockchain main network (140) of FIG. 1). The recipient address may be a random string of uppercase and lowercase English letters or numbers (e.g., 0x2A144B0E4066C7a43d215B2B0841ac3E0b884E2A), which may be difficult to intuitively recognize or remember. In contrast, the alternative identifier may be a combination of numbers and letters that is relatively simplified compared to the recipient address. The alternative identifier may be, for example, “goodboy.”

[0123] The transmitting device (110) may, in operation 713, obtain a random personal identification number (RPIN) from the alias data. The random personal identification number may be randomly generated by the receiving device (120) to identify the receiving device (120). The random personal identification number may be randomly generated based on a predetermined algorithm to confirm the receiving device (120), the digital wallet, or the owner of the digital wallet. The random personal identification number may be composed of a combination of numbers (0 to 9) with a predetermined number of digits (e.g., 4 or 6 digits) considering the possibility of human memorization. The present disclosure will not limit the algorithm for generating the random personal identification number in a specific manner.

[0124] The above-mentioned transmitting device (110) can query the address signature DB electronic device (110 or 120) using the alternative identifier as a key value in operation 715.

[0125] The transmitting device (110) may, in operation 717, receive digital signature data (SIG) from the address signature DB electronic device (110 or 120) in response to the query. The digital signature data may be generated by the receiving device (120) and registered in the address signature DB electronic device (110 or 120). The digital signature data may be generated by signing a hash value obtained by inputting a concatenation data set consisting of a substitute identifier (NN), a recipient address (Crypto Addr), a random personal identification number (RPIN), and a temporary identifier (Nonce) into a predetermined hash function with a private key (Priv) of the receiving device (120). An example of generating the digital signature data is as defined by the above <Mathematical Formula 1>.

[0126] The transmitting device (110) may, in operation 717, receive an encrypted public key (Enc_Pkey) of the receiving device (120) from the address signature DB electronic device (110 or 120) in response to the query. The encrypted public key may be generated by encrypting the public key (Pub) as a protective measure to prevent exposure of the public key (Pub) included in the key pair generated by the receiving device (120). As an example, the encrypted public key (Enc_Pkey = PBENC(Pub) RPIN ) can be generated by encrypting the public key (Pub) using a password-based encryption method using a random personal identification number (RPIN).

[0127] The above-mentioned transmitting device (110) can perform validation of a recipient address to be used for a digital transaction with the receiving device (120) based on the encryption public key (Enc_Pkey) and the digital signature data (SIG) in operations 719 to 725.

[0128] According to an example, the transmitting device (110) can decrypt the encrypted public key (Enc_Pkey) using the random personal identification number (RPIN) in operation 719 (Pub = PBDEC (Enc_Pkey) RPIN ). The above transmitting device (110) can obtain the public key (Pub) of the receiving device (120) by decrypting the encrypted public key.

[0129] The above-mentioned transmitting device (110) can, in operation 721, convert the public key (Pub) into a recipient address (crypto address) of the receiving device (120). Common methods for converting the public key into the recipient address include, for example, the SHA-256 method, the RIPEMD-160 method, or the Base58 Encoding method.

[0130] The transmitting device (110) may, in operation 723, generate hash verification data to perform verification on the digital signature data. For example, the transmitting device (110) may obtain hash values ​​for the alternative identifier (NN), the random personal identification number (RPIN), the recipient address (Crypto Addr), and the temporary identifier (Nonce) as the hash verification data (Hash(NN|Crypto Addr|RPIN|Nonce)).

[0131] The transmitting device (110) can verify whether a recipient address (crypto address) is valid based on a data set including the hash verification data, the digital signature data (SIG), and the public key (Pub) in operation 723. The transmitting device (110) can determine the validity of the recipient address based on a return value of a predetermined digital signature verification function in operation 725. The transmitting device (110) can use the hash verification data, the digital signature data (SIG), and the public key (Pub) included in the data set as input values ​​of the digital signature verification function. An example of the digital signature verification function is as defined in the above <Mathematical Formula 2>.

[0132] The transmitting device (110), in response to the validity of the recipient address at operation 727, can normally process a digital transaction with the receiving device (120) using the recipient address. For example, the transmitting device (110) can transfer a desired amount of digital assets to the recipient address. The transmitting device (110) can request the blockchain main network (140) to record the digital transaction details in a distributed ledger corresponding to the recipient address whose validity has been recognized. The distributed ledger may be a ledger that records transactions of digital assets entering and leaving the blockchain.

[0133] The transmitting device (110), in response to the invalidity of the recipient address at step 729, may output an alarm indicating that a digital transaction with the receiving device (120) using the recipient address will not be processed normally. For example, if the transmitting device (110) determines that the recipient address is invalid, it may indicate through a user interface that the recipient address is not suitable for the transaction of the digital asset. The transmitting device (110) may, for example, output visual information indicating that the recipient address is invalid through a display. The transmitting device (110) may, for example, output auditory information indicating that the recipient address is invalid through a speaker. The transmitting device (110) may, for example, output visual information through a display and auditory information through a speaker indicating that the recipient address is invalid.

[0134] FIG. 8 is a control flowchart for performing a digital asset transaction based on recipient address verification in a receiving device (e.g., the second electronic device (120) of FIG. 1 ), according to one embodiment of the present disclosure. The actual operations according to the control flowchart of FIG. 8 can be understood as being performed by a digital wallet activated in the receiving device, the second electronic device (120).

[0135] Referring to FIG. 8, the receiving device (120) may obtain a temporary identifier from a transmitting device (e.g., the first electronic device (110) of FIG. 1) in operation 811. The temporary identifier may be a one-time identifier for a corresponding digital transaction. The receiving device (120) may establish a communication link with the transmitting device (110) to receive the temporary identifier. The communication link may be established based on a short-range communication method or a long-range communication method, but is not limited to the communication method. As an example, the receiving device (120) may receive the temporary identifier as OOB data based on an OOB method.

[0136] The receiving device (120) may, in operation 813, generate a key pair corresponding to the temporary identifier. The key pair may include a private key (Priv) and a public key (Pub). The private key may be, for example, a blockchain secret key. The public key may be, for example, a blockchain public key. The public key may be converted into a recipient address (crypto address). The receiving device (120) may manage the private key and / or the public key using a digital wallet. The digital wallet may be either a software wallet or a hardware wallet. The software wallet operates as software on a host device (e.g., the receiving device (120)) and may store the private key within an interface. The hardware wallet may be a physical device that stores the private key in an offline state. The proposals in the present disclosure may be commonly applied regardless of the type of digital wallet. The private key may define ownership of a digital asset. The receiving device (120) can access digital assets on the blockchain using the private key. The public key can be disclosed to the transmitting device (110) for digital transactions. The transmitting device (110) can encrypt certain data using the public key and transmit the encrypted data to the receiving device (120), which is the owner of the public key. The certain data can be data for digital transactions, such as sending or depositing digital assets. The receiving device (120) can decrypt the encrypted data using the private key that forms a key pair with the public key.

[0137] The receiving device (120) may, in operation 815, generate a substitute identifier (NN) corresponding to the temporary identifier. The substitute identifier may be created based on pseudonymization so that the recipient (e.g., the receiving device (120)) can be identified without additional information through pseudonymization. The pseudonymization may be processed so that a query can be performed using the temporary identifier, which is a one-time thing, in an address signature DB server (e.g., the address signature DB electronic device (110 or 120) of FIG. 1), so that the target cannot be specified. For example, in order to avoid traceability of the temporary identifier, it may be generated by applying a cryptographic technique so that it cannot be mapped to a recipient address. The receiving device (120) may follow a 'SHA-256', 'RIPEMD-160', or 'Base58 Encoding' conversion method to generate the temporary identifier. The substitute identifier may be used in place of a recipient address (crypto address) that the transmitting device (110) can use for digital transactions with itself. The above recipient address corresponds to the address that the transmitting device (110) will use to send the digital asset to itself. The recipient address is a random string of English uppercase and lowercase letters or numbers (e.g., 0x2A144B0E4066C7a43d215B2B0841ac3E0b884E2A), which may be difficult to intuitively recognize or remember. In contrast, the alternative identifier may be composed of a combination of numbers and letters that is relatively simplified compared to the recipient address. The alternative identifier may be, for example, “goodboy.”

[0138] The receiving device (120) may, in operation 815, generate a random personal identification number (RPIN) corresponding to the temporary identifier. The random personal identification number may be an identification number that can be randomly generated to identify oneself. The random personal identification number may be randomly generated based on a predetermined algorithm to confirm the receiving device (120), the digital wallet, or the owner of the digital wallet. The random personal identification number may be composed of a combination of numbers (0 to 9) with a predetermined number of digits (e.g., 4 or 6 digits) considering the possibility of human memorization. In the present disclosure, the algorithm for generating the random personal identification number is not limited to a specific method.

[0139] The receiving device (120), in operation 815, can generate alias data using the alternative identifier and the random personal identification number, and transmit the generated alias data to the transmitting device (110). That is, the receiving device (120) can provide the alias data to the transmitting device (110) in place of the recipient address. The receiving device (120) can transmit the alias data in response to a request from the transmitting device (110). The receiving device (120) can establish a communication link with the transmitting device (110) to transmit the alias data. The communication link can be established based on a short-range communication method or a long-range communication method, but is not limited to the communication method. The short-range communication method or the long-range communication method can be as defined above. The receiving device (120) can, for example, transmit the alias data as OOB data based on an OOB method.

[0140] The receiving device (120) may, in operation 817, generate digital signature data (SIG) for verifying the recipient address. For example, the receiving device (120) may generate the digital signature data (SIG) by the alternative identifier (NN), the random personal identification number (RPIN), the recipient address (crypto address), and the temporary identifier (Nonce). An example of generating the digital signature data is as defined by the above <Mathematical Formula 1>.

[0141] The receiving device (120) may, in operation 819, encrypt the public key (Pub) included in the key pair it has generated as a protective measure to prevent exposure of the public key (Pub) included in the key pair it has generated, thereby generating an encrypted public key (Enc_Pkey). The receiving device (120) may, for example, encrypt the public key (Pub) using a password-based encryption method using a random personal identification number (RPIN) to generate the encrypted public key (Enc_Pkey = PBENC(Pub)). RPIN ) can be obtained.

[0142] The receiving device (120) may, in operation 821, transmit the alternative identifier, the digital signature data, and the encrypted public key to the address signature DB server (130). The receiving device (120) may transmit the alternative identifier, the digital signature data, and the encrypted public key sequentially, in partial bundles, or in batches.

[0143] The receiving device (120) may, at operation 823, perform a procedure for a digital transaction with the transmitting device (110). For example, the receiving device (120) may deposit a desired amount of digital assets into the recipient address. The digital transaction details will be recorded in a distributed ledger corresponding to the recipient address, which is the address of the receiving device (120) whose validity has been confirmed.

[0144] FIG. 9 is a block diagram of an electronic device (e.g., the first electronic device (110) or the second electronic device (120) of FIG. 1) according to one embodiment of the present disclosure.

[0145] Referring to FIG. 9, the electronic device (110 or 120) may include at least one processor (910) (e.g., at least one processor (210) of FIG. 2), a communication circuit (920) (e.g., the communication circuit (260) of FIG. 2), or at least one memory (930) (e.g., at least one memory (220) of FIG. 2). The electronic device (110 or 120) may further include unillustrated components (e.g., a display or a sensor).

[0146] The processor (910) may be implemented as one or more IC chips and may perform various data processing operations. For example, the processor (910) may be implemented as an SoC (e.g., a single chip or chipset). The processor (910) may include sub-components including a CPU, a GPU, an NPU, an ISP, a display controller, a memory controller, a storage controller, a CP, and / or a sensor interface. The sub-components are merely exemplary. The processor (910) may further include other sub-components, or some sub-components may be omitted. For example, some sub-components may be included as separate components of the electronic device (110 or 120) outside the processor (910). For example, some sub-components may be included within other components (e.g., a display, an image sensor).

[0147] The processor (910) may be configured to control sub-components based on the execution of instructions stored in the memory (930) (e.g., volatile memory and / or non-volatile memory). The processor (910) may be configured to execute parallel operations (e.g., rendering). The processor (910) may be configured to execute operations for an artificial intelligence model (e.g., convolution computation). The processor (910) may be configured to process a raw image acquired through an image sensor into a format suitable for a component within the electronic device (110 or 120) or a sub-component within the processor (910). The processor (910) may be configured to edit or process the acquired image into a desired format. The processor (910) may be configured to control reading or writing data from a volatile memory. The processor (910) may be configured to process data obtained from a sub-component into a format suitable for transmitting the data to another electronic device (e.g., the address signature DB server (130) of FIG. 1 or the blockchain main network (140)) via the communication circuit (920), or to process data obtained from another electronic device (e.g., the address signature DB server (130) of FIG. 1 or the blockchain main network (140)) via the communication circuit (920) into a format suitable for processing by the sub-component.

[0148] The above communication circuit (920) may be configured to exchange information with at least one electronic device. The communication circuit (920) may transmit and receive data or signals with a counterpart device (e.g., the second electronic device (120), the first electronic device (110), the address signature DB server (130), or the blockchain main network (140) of FIG. 1) under the control of the processor (910). The communication circuit (920) may include, but is not limited to, a Bluetooth communication unit, a BLE communication unit, a short-range wireless communication unit, a WLAN communication unit, a Zigbee communication unit, an IrDA communication unit, a WFD communication unit, a UWB communication unit, an Ant+ communication unit, or a uWave communication unit, depending on the performance and structure of the electronic device (110 or 120).

[0149] The communication circuit (920) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel with another device and the performance of communication through the established communication channel. The communication circuit (920) may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. The one or more communication processors may operate independently of the processor (910). The communication circuit (920) may include, for example, a wireless communication module (e.g., a cellular communication module, a short-range wireless communication module, or a GNSS communication module) or a wired communication module (e.g., a LAN communication module or a power line communication module). Among these communication modules, a corresponding communication module may communicate with an external electronic device via a network (e.g., a short-range communication network such as Bluetooth, WiFi direct, or IrDA, or a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These different types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips).

[0150] According to an example, the communication circuit (920) may include an upload module (921) or a query module (923). The query module (923) may be used when the electronic device (110) operates as a transmitter. The upload module (921) may be used when the electronic device (120) operates as a receiver. The upload module (921) may transmit digital signature data (SIG) for performing a digital transaction through pseudonymization to the address signature DB server (130). The query module (923) may query the address signature DB server (130) using an alternative identifier (NN) to obtain the digital signature data (SIG) and / or an encrypted public key.

[0151] The memory (930) may store various data (e.g., instructions) used by at least one component (e.g., processor (910)) of the electronic device (110 or 120). The various data may include, for example, software (e.g., a program) and input data or output data for commands related thereto. The memory (930) may include volatile memory or non-volatile memory.

[0152] According to one example, the processor (910) may include a digital wallet (940) that stores a key pair consisting of a public key and a private key for digital transactions and performs signal processing according to digital transactions based on the key pair. The digital wallet (940) may include modules for performing digital transactions based on user address verification. The digital wallet (940) may include a transmission processing unit (9410) for performing a transmission operation, a reception processing unit (9420) for performing a reception operation, or a digital asset transaction module (9430) for performing a digital asset transaction. As an example, the transmission processing unit (9410) may include a temporary identifier generation module (941) and / or a digital signature data verification module (943). For example, the receiving processing unit (9420) may include a key pair generation module (9421), a substitute identifier generation module (9423), a personal identification number generation module (9425), a digital signature data generation module (9427), and / or an encryption public key generation module (9429).

[0153] The temporary identifier generation module (941) may generate a temporary identifier (Nonce) as information for identifying a digital transaction. The temporary identifier may be a one-time identifier for the corresponding digital transaction. The temporary identifier generation module (941) may randomly generate the temporary identifier. For example, when transferring a certain digital asset (e.g., 100BTS) to a counterparty device, the temporary identifier generation module (941) may randomly generate a temporary identifier indicating the corresponding digital transaction. The method for generating the temporary identifier may be defined in advance between the parties performing the digital transaction.

[0154] The digital signature data verification module (943) can perform validity verification on a recipient address to be used for a digital transaction based on an encrypted public key and digital signature data obtained by querying the address signature DB server (130). For example, the digital signature data verification module (943) can obtain hash values ​​for an alternative identifier (NN), a random personal identification number (RPIN), a recipient address (Crypto Addr), and a temporary identifier (Nonce) as hash verification data (Hash(NN|Crypto Addr|RPIN|Nonce)). The digital signature data verification module (943) can identify whether a recipient address (crypto address) is valid based on a data set including the hash verification data, digital signature data (SIG), and a public key (Pub). For example, the digital signature data verification module (943) can determine the validity of a recipient address based on a return value of a predetermined digital signature verification function. The above digital signature data verification module (943) can use hash verification data, digital signature data (SIG), and public key (Pub) as input values ​​for the digital signature verification function. An example of the above digital signature verification function is as defined in <Mathematical Formula 2> above.

[0155] The above key pair generation module (9421) can generate a key pair including a private key and / or a public key for digital transactions.

[0156] The alternative identifier generation module (9423) may generate an alternative identifier based on pseudonymization so that the recipient (e.g., the second electronic device (120)) can be identified without additional information through pseudonymization. The pseudonymization may be processed so that the target cannot be specified by enabling a query using the one-time alternative identifier in an address signature DB server (e.g., the address signature DB server (130) of FIG. 1). For example, in order to avoid traceability of the alternative identifier, the alternative identifier may be generated by applying a cryptographic technique so that it cannot be mapped to a recipient address. The alternative identifier generation module (9423) may follow a SHA-256, RIPEMD-160, or Base58 Encoding conversion method to generate the alternative identifier. The alternative identifier may be used in place of a recipient address (crypto address) that a counterparty device (e.g., the first electronic device (110)) can use for digital transactions with itself.

[0157] The above-mentioned personal identification number generation module (9425) can generate a random personal identification number (RPIN) by combining randomly selected numbers. The random personal identification number may be a personal password or may include a personal password.

[0158] The above digital signature data generation module (9427) can generate digital signature data (SIG) for verifying a recipient address. For example, the digital signature data generation module (9427) can generate the digital signature data (SIG) using the alternative identifier (NN), the random personal identification number (RPIN), the recipient address (crypto address), and the temporary identifier (Nonce).

[0159] The above-mentioned encrypted public key generation module (9429) can generate an encrypted public key (Enc_Pkey) by encrypting the public key (Pub) as a protective measure to prevent the exposure of the public key (Pub) included in the key pair. The above-mentioned encrypted public key generation module (9429) can encrypt the public key (Pub) using a password-based encryption method using, for example, a random personal identification number (RPIN) to generate the encrypted public key (Enc_Pkey = PBENC(Pub) RPIN ) can be obtained.

[0160] The digital asset transaction module (9430) can perform procedures for digital transactions with a recipient address. For example, the digital asset transaction module (9430) can transfer a desired amount of digital assets to a recipient address. The digital asset transaction module (9430) can request the blockchain main network (140) to record digital transaction details in a distributed ledger corresponding to a validated recipient address. The distributed ledger may be a ledger that records transactions involving incoming and outgoing digital assets on the blockchain.

[0161] FIG. 10 is an example diagram of a user interface screen that may be displayed on a display according to a situation during a digital transaction in a transmitting device (e.g., the first electronic device (110) of FIG. 1) according to one embodiment of the present disclosure.

[0162] Referring to FIG. 10, the transmitting device (110) may execute an application program in response to an activation request from a digital wallet to output an initial user interface screen (1010) for a digital transaction. The initial user interface screen (1010) includes areas that display information for each item of total transaction (1011), total received digital assets (1013), total sent digital assets (1015), and / or final balance (1017).

[0163] The above-mentioned transmitting device (110) may output a user interface screen (Quick Send) (1020) for remittance when a digital transaction for remittance is selected. The user interface screen (1020) for remittance may include an area (1021) for entering and / or displaying an alternative identifier (nick name) to replace the recipient address, an area (1023) for entering and / or displaying the amount of digital assets to be remitted, and a function button (SEND) (1025) for requesting remittance of the amount of digital assets using the alternative identifier.

[0164] The above-mentioned transmitting device (110) can verify the validity of the recipient address based on the alternative identifier in response to the selection of the function button (1025). If the transmitting device (110) determines that the recipient address is invalid, the transmitting device (110) can output a user interface screen (1030) including a display window (1031) displaying a notification message (1033) indicating that the blockchain address of the alternative identifier does not match.

[0165] The above-mentioned transmitting device (110), if it determines that the recipient address is valid, can output a user interface screen (1040) including a display window (1041) displaying a notification message (1043) inquiring about remittance of the amount of the digital asset using the alternative identifier and function buttons (1045, 1047) for selecting whether to proceed with the remittance.

[0166] The above-mentioned transmitting device (110) can output a user interface screen (1050) for proceeding with the remittance when the function button “Yes (1045)” for instructing the remittance process is selected. The user interface screen (1050) for proceeding with the remittance process may include an area (1051) where an alternative identifier is displayed, an area (1053) where the amount of digital assets to be remitted is displayed, and an area (1055) where the remittance progress rate is displayed.

[0167] The above-mentioned transmitting device (110) may output a user interface screen (1060) indicating that the remittance has been completed when the remittance process is completed. The user interface screen (1060) indicating that the remittance has been completed may include an area (1061) where the amount of the digital payment remitted (send payment) is displayed.

[0168] FIG. 11 is a control flowchart for verifying a new address during a P2P transaction in an electronic device (e.g., the first electronic device (110) or the second electronic device (120) of FIG. 1) according to one embodiment of the present disclosure. The following description will assume the first electronic device (110), but it is understood that the same operations can be performed in a second electronic device (120).

[0169] Referring to FIG. 11, the electronic device (110) may, in operation 1110, recognize the occurrence of a query request event for the blockchain address of a digital asset transaction target. If the query request event occurs, the electronic device (110) may, in operation 1120, determine whether the address for which the query is requested is a new address. The new address may not be searched in the distributed ledger on the mainnet (e.g., the blockchain main network (140) of FIG. 1).

[0170] If the address at which the inquiry request event occurred is a new address, the electronic device (110) may, in operation 1130, inform the user that the address for which the inquiry request was made is not confirmed on the distributed ledger.

[0171] The electronic device (110), at operation 1140, may inquire whether address verification will be performed after the above guidance, and in response to the inquiry, determine whether an address verification request has occurred. That is, the electronic device (110), at operation 1140, may propose to perform address verification for a new address not confirmed in the distributed ledger.

[0172] The electronic device (110) may skip the address verification procedure if an address verification request is not received. If an address verification request is received, the electronic device (110) may perform a pseudonymization-based address verification procedure at operation 1150. The electronic device (110) may perform the pseudonymization-based address verification spelling as described above with reference to FIGS. 3 to 8.

[0173] The operation described in FIG. 11 above can be applied to verify new recipient addresses not registered in the blockchain ledger. Furthermore, for recipient addresses registered in the blockchain ledger, digital transactions can be performed using the registered recipient addresses without performing an on-device verification process. In other words, the example proposed in FIG. 11 can be applied to recipient addresses registered in the blockchain ledger, but applying it to new recipient addresses may be more efficient.

[0174] According to an example, a method for trading digital assets based on a blockchain in an electronic device (110) including a digital wallet (940) may include an operation (711) of generating a first temporary identifier (Nonce#1) to be shared with a first counterparty device (120) capable of trading digital assets. The method may include an operation (713) of obtaining a first alternative identifier (NN#1: first nick name) and a first random personal identification number (RPIN#1: Random PIN#1 (first personal identification number)) for the first counterpart device (120). The method may include an operation (717) of receiving a first encrypted public key (Enc_Pkey#1) and first digital signature data (SIG#1) from an address signature database (130) in response to a query based on the first alternative identifier (NN#1). The method may include an operation (719) of decrypting the first encrypted public key (Enc_Pkey#1) using the first random personal identification number (RPIN#1) to obtain a first public key (Pub#1: first public key) of the first counterpart device. The method may include obtaining the first public key (Pub#1) by decrypting the first encrypted public key (Enc_Pkey#1). The method may include an operation (721) of converting the first recipient address (first crypto address). The method may include an operation (723) of identifying whether the first recipient address (first crypto address) is valid based on a first data set including first hash verification data, the first digital signature data (SIG#1), and the first public key (Pub#1). Here, the first hash verification data may be a hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address), and the first temporary identifier (Nonce#1).

[0175] As an example, the method may include an operation (729) of outputting an identification result as to whether the first recipient address (first crypto address) is valid.

[0176] As an example, the first encryption public key (Enc_Pkey#1) and the first digital signature data (SIG#1) can be deleted from the address signature database.

[0177] As an example, the identifying operation (723) may include an operation of determining the first hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address), and the first temporary identifier (Nonce#1) as the first hash verification data. The identifying operation (723) may include an operation of obtaining a return value by using the first hash verification data, the first digital signature data (SIG#1), and the first public key (Pub#1) as inputs of a predetermined digital signature verification function. The identifying operation (723) may include an operation of determining whether the first recipient address (first crypto address) is a valid blockchain address based on the return value.

[0178] As an example, the method may include an operation (727) of performing a transaction of the digital asset by the first crypto address in response to the first crypto address being identified as valid.

[0179] As an example, the method may include an operation (729) of notifying the user interface that the first recipient address (first crypto address) is not suitable for trading the digital asset in response to the first recipient address (first crypto address) being identified as invalid.

[0180] As an example, the method may include an operation of deleting the first temporary identifier (Nonce#1), the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first encrypted public key (Enc_Pkey#1), the first digital signature data (SIG#1), the first public key (Pub#1), the first recipient address (first crypto address) and / or the first hash verification data in response to completion of a transaction of the digital asset.

[0181] As an example, the method comprises: an operation (811) of obtaining a second temporary identifier (Nonce#2) generated by a second counterpart device (130); an operation (813) of generating a key pair including a second private key and a second public key; an operation (815) of generating a second alternative identifier (NN#2: second nick name) and a second random personal identification number (RPIN#2: Random PIN#2 (second personal identification number)) to be used in response to the second temporary identifier; an operation (817) of generating second digital signature data (SIG#2) signed with the second private key of the second alternative identifier (NN#2), the second random personal identification number (RPIN#2), the second recipient address (second crypto address) and the hash value of the second temporary identifier (Nonce#2); and an operation (818) of encrypting the second public key to generate a second encrypted public key (Enc_Pkey#2). It may include an operation (819) and an operation (821) of transmitting the second alternative identifier (NN#2), the second digital signature data (SIG#2), and the second encrypted public key (Enc_Pkey#2) to the address signature database (130).

[0182] As an example, the method may include an operation (815) of transmitting the second alternative identifier (NN#2) and / or the second random personal identification number (RPIN#2) to the second counterpart device (130).

[0183] As an example, the method may include an operation (823) of performing a transaction of the digital asset with the second counterparty device (130) by means of the second recipient address (second crypto address).

[0184] According to one example, an electronic device (110) may include a communication circuit (920), a memory (930) including one or more storage media for storing instructions, and at least one processor (910) including a processing circuit. The electronic device (110), when the instructions are individually or collectively executed by at least one processor (910), generates a first temporary identifier (Nonce#1) to be shared with a first counterpart device (120) capable of digital asset trading, obtains a first alternative identifier (NN#1: first nick name) and a first random personal identification number (RPIN#1: Random PIN#1 (first personal identification number)) for the first counterpart device (120), receives a first encrypted public key (Enc_Pkey#1) and first digital signature data (SIG#1) from an address signature database (130) in response to a query based on the first alternative identifier (NN#1) through the communication circuit (920), and decrypts the first encrypted public key (Enc_Pkey#1) using the first random personal identification number (RPIN#1) to decrypt the first encrypted public key (Enc_Pkey#1) to the first counterpart device (120). The device (120) may be configured to obtain a first public key (Pub#1: first public key), convert the first public key (Pub#1) into a first recipient address (first crypto address), and identify whether the first recipient address (first crypto address) is valid based on a first data set including first hash verification data, the first digital signature data (SIG#1), and the first public key (Pub#1). Here, the first hash verification data may be a hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address), and the first temporary identifier (Nonce#1).

[0185] As an example, the electronic device (110) may be configured to output an identification result as to whether the first recipient address (first crypto address) is valid when the instructions are individually or collectively executed by at least one processor (910).

[0186] As an example, the first encryption public key (Enc_Pkey#1) and the first digital signature data (SIG#1) may be deleted from the address signature database (130).

[0187] As an example, the electronic device (110) may be configured to determine the first hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address) and the first temporary identifier (Nonce#1) as the first hash verification data when the instructions are individually or collectively executed by at least one processor (910), obtain a return value by using the first hash verification data, the first digital signature data (SIG#1) and the first public key (Pub#1) as inputs of a predetermined digital signature verification function, and identify whether the first recipient address (first crypto address) is a valid blockchain address based on the return value.

[0188] As an example, the electronic device (110) may be configured to perform a transaction of the digital asset through the communication circuit (920) by the first crypto address in response to the first crypto address being identified as valid when the instructions are individually or collectively executed by at least one processor (910).

[0189] As an example, the electronic device (110) may be configured to, when the instructions are individually or collectively executed by at least one processor (910), in response to the first recipient address (first crypto address) being identified as invalid, provide a user interface indicating that the first recipient address (first crypto address) is not suitable for trading the digital asset.

[0190] As an example, the electronic device (110) may be configured to delete the first temporary identifier (Nonce#1), the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first encrypted public key (Enc_Pkey#1), the first digital signature data (SIG#1), the first public key (Pub#1), the first recipient address (first crypto address) and / or the first hash verification data in response to completion of a transaction of the digital asset when the instructions are individually or collectively executed by at least one processor (910).

[0191] As an example, the electronic device (110), when the instructions are individually or collectively executed by at least one processor (910), obtains a second temporary identifier (Nonce#2) generated by a second counterpart device (120), generates a key pair including a second private key and a second public key, generates a second alternative identifier (NN#2: second nick name) and a second random personal identification number (RPIN#2: Random PIN#2 (second personal identification number)) to be used by the electronic device in response to the second temporary identifier, generates second digital signature data (SIG#2) signed by the second alternative identifier (NN#2), the second random personal identification number (RPIN#2), a second recipient address (second crypto address) and a hash value of the second temporary identifier (Nonce#2) with the second private key, and encrypts the second public key to generate a second encrypted public key (Enc_Pkey#2). and may be configured to generate and transmit the second alternative identifier (NN#2), the second digital signature data (SIG#2), and the second encrypted public key (Enc_Pkey#2) to the address signature database (130) through the communication circuit (920).

[0192] As an example, the electronic device (110) may be configured to transmit the second alternative identifier (NN#2) and / or the second random personal identification number (RPIN#2) to the second counterpart device (120) via the communication circuit (920) when the instructions are individually or collectively executed by at least one processor (910).

[0193] As an example, the electronic device (110) may be configured to perform a transaction of the digital asset with the second counterparty device (120) via the communication circuit (920) by the second recipient address (second crypto address) when the instructions are individually or collectively executed by at least one processor (910).

[0194] According to one embodiment, a computer-readable storage medium may have recorded thereon a program for executing a method of switching an activation function in the first or second electronic device (110 or 120) described above.

[0195] The electronic device (110 or 120) according to various embodiments disclosed in this document may be a variety of devices. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. The electronic device according to the embodiments of this document is not limited to the aforementioned devices.

[0196] The various embodiments of this document and the terminology used herein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C" can each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish the corresponding components from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as being "coupled" or "connected" to another component (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0197] The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0198] Various embodiments of the present document may be implemented as software (e.g., a program) including one or more instructions stored in a storage medium (e.g., a memory (160)) readable by a machine (e.g., an electronic device (110 or 120)). For example, a processor (e.g., the processor (110)) of a machine (e.g., a display device (100)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

[0199] According to one embodiment, the methods according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a commodity between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0200] According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. A method for trading digital assets based on a blockchain in an electronic device (110) including a digital wallet (940), An operation (711) to generate a first temporary identifier (Nonce#1) to be shared with a first counterparty device (120) capable of digital asset trading; An operation (713) of obtaining a first alternative identifier (NN#1: first nick name) and a first random personal identification number (RPIN#1: Random PIN#1 (first personal identification number)) for the first counterpart device (120); An operation (717) of receiving a first encrypted public key (Enc_Pkey#1) and first digital signature data (SIG#1) from an address signature database (130) in response to a query based on the first alternative identifier (NN#1); An operation (719) of decrypting the first encrypted public key (Enc_Pkey#1) using the first random personal identification number (RPIN#1) to obtain the first public key (Pub#1: first public key) of the first counterpart device; An operation (721) of converting the first public key (Pub#1) into a first recipient address (first crypto address); An operation (723) for identifying whether the first recipient address (first crypto address) is valid based on a first data set including the first hash verification data, the first digital signature data (SIG#1), and the first public key (Pub#1), Here, the first hash verification data is a hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address), and the first temporary identifier (Nonce#1).

2. In paragraph 1, A method comprising an operation (729) of outputting an identification result as to whether the first recipient address (first crypto address) is valid.

3. In paragraph 1, A method comprising an action of deleting the first encrypted public key (Enc_Pkey#1) and the first digital signature data (SIG#1) from the address signature database.

4. In any one of paragraphs 1 to 3, The above identifying action (723) is: An operation of determining the first hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address), and the first temporary identifier (Nonce#1) as the first hash verification data; An operation of obtaining a return value by using the first hash verification data, the first digital signature data (SIG#1), and the first public key (Pub#1) as inputs to a predetermined digital signature verification function; and A method comprising an operation of determining whether the first recipient address (first crypto address) is a valid blockchain address based on the return value.

5. In any one of paragraphs 1 to 4, An action (727) of performing a transaction of the digital asset by the first crypto address in response to the first crypto address being identified as valid; In response to the identification of the first recipient address (first crypto address) as invalid, an operation (729) of notifying through a user interface that the first recipient address (first crypto address) is not suitable for trading the digital asset; and A method comprising, in response to completion of a transaction of the digital asset, an operation of deleting the first temporary identifier (Nonce#1), the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first encrypted public key (Enc_Pkey#1), the first digital signature data (SIG#1), the first public key (Pub#1), the first recipient address (first crypto address) and / or the first hash verification data.

6. In paragraph 1, An operation (811) of obtaining a second temporary identifier (Nonce#2) generated by a second counterpart device (130); An action (813) to generate a key pair including a second private key and a second public key; An operation (815) of generating a second alternative identifier (NN#2: second nick name) and a second random personal identification number (RPIN#2: Random PIN#2 (second personal identification number)) to be used in response to the second temporary identifier; An operation (817) of generating second digital signature data (SIG#2) signed with the second private key using the hash value of the second alternative identifier (NN#2), the second random personal identification number (RPIN#2), the second recipient address (second crypto address), and the second temporary identifier (Nonce#2); An operation (819) of encrypting the second public key to generate a second encrypted public key (Enc_Pkey#2); An operation (821) of transmitting the second alternative identifier (NN#2), the second digital signature data (SIG#2), and the second encrypted public key (Enc_Pkey#2) to the address signature database (130); and A method comprising an operation (815) of transmitting the second alternative identifier (NN#2) and / or the second random personal identification number (RPIN#2) to the second counterpart device (130).

7. In paragraph 6, A method comprising an operation (823) of performing a transaction of the digital asset with the second counterparty device (130) by the second recipient address (second crypto address).

8. In the electronic device (110), Communication circuit (920); A memory (930) including one or more storage media for storing instructions; and At least one processor (910) comprising a processing circuit, Here, when the above instructions are individually or collectively executed by at least one processor (910), Generate a first temporary identifier (Nonce#1) to be shared with the first counterparty device (120) capable of digital asset trading, Obtain a first alternative identifier (NN#1: first nick name) and a first random personal identification number (RPIN#1: Random PIN#1 (first personal identification number)) for the first counterpart device (120), In response to a query based on the first alternative identifier (NN#1), a first encrypted public key (Enc_Pkey#1) and first digital signature data (SIG#1) are received from the address signature database (130) through the communication circuit (920). The first encrypted public key (Enc_Pkey#1) is decrypted using the first random personal identification number (RPIN#1) to obtain the first public key (Pub#1: first public key) of the first counterpart device (120), Convert the above first public key (Pub#1) into the first recipient address (first crypto address), It is configured to identify whether the first recipient address (first crypto address) is valid based on the first data set including the first hash verification data, the first digital signature data (SIG#1) and the first public key (Pub#1). Here, the first hash verification data is a hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address), and the first temporary identifier (Nonce#1), in an electronic device (110).

9. In paragraph 8, When the above instructions are individually or collectively executed by at least one processor (910), An electronic device (110) configured to output an identification result as to whether the first recipient address (first crypto address) is valid.

10. In paragraph 8, When the above instructions are individually or collectively executed by at least one processor (910), An electronic device (110) configured to delete the first encryption public key (Enc_Pkey#1) and the first digital signature data (SIG#1) from the address signature database (130).

11. In any one of paragraphs 8 to 10, When the above instructions are individually or collectively executed by at least one processor (910), The first hash value for the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first recipient address (first crypto address) and the first temporary identifier (Nonce#1) is determined as the first hash verification data, The first hash verification data, the first digital signature data (SIG#1) and the first public key (Pub#1) are used as inputs to a predetermined digital signature verification function to obtain a return value. An electronic device (110) configured to identify whether the first recipient address (first crypto address) is a valid blockchain address based on the return value.

12. In any one of paragraphs 8 to 11, When the above instructions are individually or collectively executed by at least one processor (910), In response to the first recipient address (first crypto address) being identified as valid, a transaction of the digital asset is performed through the communication circuit (920) by the first recipient address (first crypto address), In response to the identification of the first recipient address (first crypto address) as invalid, the user interface informs that the first recipient address (first crypto address) is not suitable for trading the digital asset. An electronic device (110) configured to delete the first temporary identifier (Nonce#1), the first alternative identifier (NN#1), the first random personal identification number (RPIN#1), the first encrypted public key (Enc_Pkey#1), the first digital signature data (SIG#1), the first public key (Pub#1), the first recipient address (first crypto address) and / or the first hash verification data in response to completion of a transaction of the digital asset.

13. In paragraph 8, When the above instructions are individually or collectively executed by at least one processor (910), Obtain the second temporary identifier (Nonce#2) generated by the second counterpart device (120), Generate a key pair containing a second private key and a second public key, In response to the above second temporary identifier, generate a second alternative identifier (NN#2: second nick name) and a second random personal identification number (RPIN#2: Random PIN#2 (second personal identification number)) to be used by the user, Generate second digital signature data (SIG#2) by signing the hash value of the second alternative identifier (NN#2), the second random personal identification number (RPIN#2), the second recipient address (second crypto address) and the second temporary identifier (Nonce#2) with the second private key, The second public key is encrypted to generate a second encrypted public key (Enc_Pkey#2). An electronic device (110) configured to transmit the second alternative identifier (NN#2), the second digital signature data (SIG#2), and the second encrypted public key (Enc_Pkey#2) to the address signature database (130) through the communication circuit (920).

14. In paragraph 13, When the above instructions are individually or collectively executed by at least one processor (910), An electronic device (110) configured to transmit the second alternative identifier (NN#2) and / or the second random personal identification number (RPIN#2) to the second counterpart device (120) through the communication circuit (920).

15. In paragraph 13 or 14, When the above instructions are individually or collectively executed by at least one processor (910), An electronic device (110) configured to perform a transaction of the digital asset with the second counterpart device (120) through the communication circuit (920) using the second recipient address (second crypto address).

Images