Patent ID: 12244681

DETAILED DESCRIPTION

FIG.1illustrates a structure of a transaction system100including an electronic device, a server, and a blockchain network according to an embodiment of the disclosure.

Referring toFIG.1, the transaction system100may include an electronic device110, a server130, and a blockchain network150.

In an embodiment, the electronic device110(e.g., an electronic device901ofFIG.9) may include a communication circuit112(e.g., a communication module990ofFIG.9), a memory114(e.g., a memory930ofFIG.9), a processor116(e.g., a processor920ofFIG.9), and a display118(e.g., a display device960ofFIG.9). In an embodiment, the communication circuit112may establish a communication channel between the electronic device110and an external electronic device (e.g., the server130) and may transmit and receive data. For example, the communication circuit112may transmit transaction data of the electronic device110performing a transaction to the server130. The server130may include a manufacturer's server of the electronic device110.

In an embodiment, the electronic device110may generate a key pair using an asymmetric key cryptography (e.g., a public key cryptography) to perform the transaction. In an embodiment, the memory114may store the generated private key. The transaction may be generated through a digital signature based on a private key. In an embodiment, the memory114may be a secure memory (e.g., Arm™ TrustZone™), which is a memory for providing a security environment.

In an embodiment, the display118may visually provide information to the outside (e.g., a user) of the electronic device110. For example, the display118may display at least one of transaction generation information, balance information, transaction transmission delay information, transaction transmission completion information, and recommendation fee information of the electronic device110.

In an embodiment, the processor116may calculate a fee based on the transaction data. For example, the processor116may generate transaction data transmitting 1.9Bitcoin (BTC) to a second address from a first address having an unused transaction output value (UTXO) with 2.1 BTC and transmits 0.05 BTC to the first address. The first address and the second address are examples of a BTC address, which is a unique identifier that serves as a virtual location where the cryptocurrency can be sent.

The processor116may calculate that a fee of the transaction data is 0.15 BTC, based on Vin (a set of inputs) and Vout(a set of outputs), which are well known in BTC. In another embodiment, the processor116may generate transaction data, based on determined fee information. For example, the processor116may determine the fee for transaction data to 0.15 BTC. The processor116may transmit the rest of the fee (excluding 0.15 BTC) from the first address having the unused transaction output value (UTXO) with 2.1 BTC to the second address.

In an embodiment, the server130may include a communication circuit132, a memory134, and a processor136. In an embodiment, the communication circuit132may establish a communication channel between the server130and an external device (e.g., the electronic device110, the blockchain network150) to transmit and receive data. For example, the communication circuit132may transmit, to the blockchain network150, transaction data received from the electronic device110. The transmitted transaction data may be stored in the blockchain node152.

In an embodiment, the blockchain node152is an electronic device included in the blockchain network150, and may serve to transmit a transaction in the blockchain network150. The electronic device may be the same as or at least partially similar to the electronic devices901and902ofFIG.9and/or the electronic device110, but without being limited thereto, may be implemented with some of electronic devices or system components (e.g., a processor, a memory).

In an embodiment, the processor136may receive data from the electronic device110via the communication circuit132. In an embodiment, the processor136may monitor the blockchain network150via the communication circuit132. For example, the processor136may use a message exchange library (e.g., jsonRPC, ZeroMQ) between the blockchain node152and the server130to identify new block generation information and transaction information or the like in a memory pool of the blockchain network150. In an embodiment, the memory pool is a space in which unconfirmed transaction information that is not recorded in a block is stored. The memory pool may be located in a memory (e.g., the memory930ofFIG.9) of the blockchain node152. In addition, transaction information in the memory pool may be shared by using the plurality of blockchain nodes152connected via the blockchain network150. According to one embodiment,FIG.1illustrates a transaction system in which data generated in the electronic device110is transmitted to the blockchain network150via the server130. In another embodiment, the data generated in the electronic device110may be directly, without using the server130, transmitted to the blockchain network150. That is, the electronic device110may generate transaction data and directly transmit the generated transaction data to the blockchain network150, and may transmit, to the server130, data indicating that the transaction data was generated by the electronic device110. The server130may start monitoring of the blockchain network150, based on the received data.

FIG.2illustrates an operational flowchart of a transaction system according to an embodiment.

Referring toFIG.2, in operation210, the electronic device110may generate first transaction data. For example, the electronic device110may generate the first transaction data including at least a first piece of transaction data for transferring a part of unused transaction output values of a first address from the first address to a second address. In an embodiment, the first transaction data includes a plurality of pieces of transaction data that may include different pieces of fee information. For example, the electronic device110may generate the first transaction data including the plurality of pieces of transaction data by setting a fee range (e.g., 1 to 3 satoshi/byte). In an embodiment, the fee range may be set by a user. In another embodiment, the fee range may be set based on a recommendation fee received from the server.

According to an embodiment, in operation203, the electronic device110may transmit the first transaction data to the server130. In an embodiment, the electronic device110may transmit transaction data to the server130, based on a digital signature based on a private key.

According to an embodiment, in operation205, the server130may detect a transmission delay status of the first transaction data, which occurs in the blockchain network150. However, when the first transaction data includes the plurality of pieces of transaction data, before performing the operation205, the server130may perform an operation of sequentially transmitting the first transaction data to the blockchain network150, based on fee information.

In an embodiment, the server130may start monitoring of the blockchain network150, based on the first transaction data received from the electronic device110. In an embodiment, the transmission delay status may indicate a status in which even any one piece of transaction data of first transaction data (including at least the first piece of transaction data) is not recorded in a new block and is waiting in a memory pool of the blockchain network150. For example, the first transaction data may include transaction data #1-1 (first part of the first transaction data) having fee information of 1 satoshi/byte, transaction data #1-2 (second part of the first transaction data) having fee information of 2 satoshi/byte, and transaction data #1-3 (third part of transaction data) having fee information of 3 satoshi/byte. The transaction data #1-1 (first part of the first transaction data) having lowest fee information (herein, 1 satoshi/byte) may be transmitted first to the blockchain network150among the pieces (parts) of first transaction data. In this case, when the transaction data #1-1 (first part of the first transaction data) is waiting in the memory pool of the blockchain network150, it may be determined that the transaction data #1-1 (first part of the first transaction data) is in a 0-confirmation status. When a new block is created according to a specific time interval (e.g., 10 minutes), transaction data may be recorded in the new block sequentially starting from transaction data including a highest fee. It may be determined that the transaction data recorded in the new block is in a 1-confirmation status. Since there is a large amount of transaction data having higher fee information (e.g., 10 satoshi/byte) than that (the fee information) of the first transaction data in the memory pool of the blockchain network150, the first transaction data may be present in a waiting status in the memory pool for a long period of time (e.g., 30 minutes). It may be determined that the transaction data waiting in the memory pool of the blockchain network150is in the 0-confirmation status. When a time for which the first transaction data is in the 0-confirmation status in the memory pool exceeds a threshold transmission time (e.g., 10 minutes), the server130may determine a status of the transaction data #1-1 (first part of the first transaction data) as the transmission delay status. The threshold transmission time may be randomly set in the server130and/or the electronic device110, or may be set according to the user's setting.

Thereafter, as the transaction data #1-1 (first part of the first transaction data) determined to be in the transmission delay status is deleted from the memory pool, the transaction data #1-2 (second part of the first transaction data) having higher fee information (e.g., 2 satoshi/byte) than that (the fee information) of the transaction data #1-1 (first part of the first transaction data) may be transmitted to the blockchain network150. When a time for which the transaction data #1-2 (second part of the first transaction data) is in the 0-confirmation status in the memory pool exceeds a threshold transmission time, a status of the transaction data #1-2 (second part of the first transaction data) may be determined as the transmission delay status. As such, when a status of the transaction data #1-3 (third part of transaction data) transmitted after the transaction data #1-2 (second part of the first transaction data) is deleted from the memory pool is determined as the transmission delay status, the server130may determine that the first transaction data (e.g., the transaction data #1-1 (first part of the first transaction data), the transaction data #1-2 (second part of the first transaction data), and the transaction data #1-3 (third part of transaction data) is in the transmission delay status.

According to an embodiment, in operation207, the server130may transmit status information of the first transaction data to the electronic device110. The status information of the first transaction data may indicate that the first transaction data is in the transmission delay status. In an embodiment, the server130may transmit the status information of the first transaction data to the electronic device110through a push notification. For example, a specific application (e.g., decentralized application (DApp)) generating the first transaction data may interwork with the server130. The server130may transmit the status information of the first transaction data detected by monitoring the blockchain network150to the specific application of the electronic device110through the push notification. The push notification may have a form of a message (Firebase Cloud Messaging (FCM)) transmitted on an app basis.

According to an embodiment, in operation209, the server130may calculate recommendation fee information, for example, on transmission of the first transaction data. In an embodiment, the server130may identify (e.g., monitor) transaction information in the memory pool of the blockchain network150via the communication circuit132. In an embodiment, the server130may calculate a recommendation fee, based on fee information of unconfirmed transactions which are waiting in the memory pool. For example, the server130may arrange the unconfirmed transactions waiting in the memory pool in a descending order of fee information of the transactions. The server130may calculate recommendation fee information having a ‘fast’ transfer rate, based on fee information of unconfirmed transactions having high fee information (e.g., unconfirmed transactions having top 25% fee information). The server130may calculate recommendation fee information having a ‘normal’ transfer rate, based on fee information of unconfirmed transactions having intermediate fee information (e.g., unconfirmed transactions having fee information of the top 25 to 50%). The server130may calculate recommendation fee information having a ‘slow’ transfer rate, based on fee information of unconfirmed transactions having ‘low’ fee information (e.g., unconfirmed transactions having fee information of the top 50 to 75%). In an embodiment, reference values (e.g., top 25%, 50%, and 75%) for ‘fast,’ ‘normal,’ and ‘slow’ transfer rates may vary, based on parameter values set in the server.

In an embodiment, the recommendation fee information may indicate a single fee value (e.g., 0.00005 BTC) calculated based on a plurality of unconfirmed transactions. In another embodiment, the recommendation fee information may indicate a range of fees (e.g., 0.00004 BTC to 0.00006 BTC) calculated based on the plurality of unconfirmed transactions. In another embodiment, the recommendation fee information may indicate at least one of a fee having a ‘fast’ transfer rate, a fee having a ‘normal’ transfer rate, and a fee having a ‘slow’ transfer rate.

In an embodiment, the operation209may be performed sequentially after the operation207, or may be performed in parallel with the operation207. For example, the server130may calculate the recommendation fee, after transmitting the status information to the electronic device110in response to detecting of the transmission delay status of the first transaction data. As another example, the server130may transmit the status information to the electronic device110after calculating the recommendation fee information based on the detected transmission delay status of the first transaction data. In this case, the recommendation fee information may be transmitted to the electronic device110together with the status information.

According to an embodiment, in operation211, the server130may transmit the recommendation fee information to the electronic device110. In an embodiment, the server130may transmit the recommendation fee information to the electronic device110through a push notification.

According to an embodiment, in operation213, the electronic device110may generate second transaction data. For example, the electronic device110may generate the second transaction data including at least a second piece of transaction data for transferring a part of unused transaction output values of the first address from the first address to the second address. In an embodiment, the electronic device110may generate the second transaction data, based on received recommendation fee information. For example, the electronic device110may identify a range of fees (e.g., 0.00004 BTC to 0.00006 BTC) based on the recommendation fee information having a ‘fast’ transfer rate. The electronic device110may generate the second transaction data including the range of fees, by performing a digital signature based on a private key.

According to an embodiment, in operation215, the electronic device110may transmit the second transaction data to the server130.

According to an embodiment, when the second transaction data includes a plurality of pieces of transaction data, in operation217, the server130may sequentially transmit the second transaction data to the blockchain network150, based on the fee information. In an embodiment, when any one piece of transaction data (e.g., transaction data corresponding to priority) of second transaction data is recorded in a new block after transaction data is transmitted sequentially starting from transaction data including lowest fee information to the blockchain network150among the pieces of second transaction data, the server130may obtain status information indicating a transmission completion status.

FIG.3illustrates an operational flowchart of an electronic device according to an embodiment. In regard to the description ofFIG.3, the same or similar description described above may be omitted. In an embodiment, operations301to309ofFIG.3may be performed by a processor (e.g., the processor116ofFIG.1) of an electronic device (e.g., the electronic device110ofFIG.1).

Referring toFIG.3, in operation301, the electronic device110may generate first transaction data. For example, the first transaction data may include transaction data #1-1 (first part of the first transaction data) including first fee information (e.g., 0.00000003 BTC (3satoshi)) and transaction data #1-2 (second part of the first transaction data) including second fee information (e.g., 0.00000005 BTC (5satoshi)) of a fee higher than that of the first fee information. In an embodiment, the first fee information and the second fee information may be set by a user. In another embodiment, the first fee information and the second fee information may be received from a server (e.g., the server130ofFIG.1).

According to an embodiment, in operation303, the electronic device110may transmit the first transaction data to the server. In an embodiment, as the first transaction data is generated based on a digital signature through a private key, the electronic device110may transmit the first transaction data to the server (e.g., the server130ofFIG.1).

According to an embodiment, in operation305, the electronic device110may receive status information of the first transaction data from the server130. In an embodiment, the electronic device110may use a display (e.g., the display118ofFIG.1) to display that the first transaction data is in a transmission delay status. For example, the electronic device110may display to a notification bar disposed at an upper portion of the display118a notification indicating that the first transaction data is in the transmission delay status. In an embodiment, the notification may include a notification suggesting a fee change.

According to an embodiment, in operation307, the electronic device110may receive recommendation fee information from the server130. In an embodiment, the electronic device110may receive a recommendation fee, based on real-time transaction information of a blockchain network (e.g., the blockchain network150ofFIG.1). For example, the recommendation fee may indicate a range of fees that is recordable in a new block to be created within a short period of time (e.g., 10 minutes) at a current time point. In an embodiment, the operation307may be performed sequentially after the operation305, or may be performed in parallel with the operation305.

According to an embodiment, in operation309, the electronic device110may generate the second transaction data, based on the recommendation fee information. For example, the second transaction data may include transaction data #2-1 (first part of the second transaction data) including third fee information (e.g., 0.0000002 BTC (20satoshi)) and transaction data #2-2 (second part of the second transaction data) including fourth fee information (e.g. 0.0000003 BTC (30satoshi)) higher than the third fee information. The third fee information and the fourth fee information may be included in a recommendation fee (e.g., 0.0000002 BTC to 0.0000003 BTC) recordable in a new block to be created within a short period of time at a current time point.

FIG.4illustrates a User Interface (UI) status of an electronic device which has received transaction status information and recommendation fee information according to an embodiment. In regard to the description ofFIG.4, the same or similar description described above may be omitted.

Referring toFIG.4, an electronic device (e.g., the electronic device110ofFIG.1) may provide a first UI400including a transmission delay notification of transaction data through a display (e.g., the display118ofFIG.1). The transmission delay notification may be displayed through a notification bar on the display118, or may be displayed through a pop-up window. In an embodiment, the transmission delay notification may include information (e.g., “Click retransmission”) suggesting retransmission of transaction data. In an embodiment, the electronic device110may receive a touch input402for a region displaying the transmission delay notification.

In an embodiment, the electronic device110may display a second UI410including newly generated transaction data through the display118. In an embodiment, the electronic device110may display newly generated transaction data412through a layer popup which may be superimposed on the first UI400. For example, the transaction data412may include a Transaction ID (TXID), a remittance amount, a fee, and a total amount. In an embodiment, the transaction data412may be generated based on recommendation fee information414received from a server (e.g., the server130ofFIG.1). For example, transaction data in a transmission delay status may include a remittance amount of “1,022,019 KRW”, a fee of “60,820 KRW”, and a total amount of “1,082,839 KRW.” As the electronic device110receives the touch input402for the region displaying the transmission delay notification, the transaction data412may be generated by reflecting “74,915 KRW” which is the recommendation fee information414received from the server130. InFIG.4, the remittance amount is changed from “1,022,019 KRW” to “1,007,924 KRW,” due to the increased fee, from “60,820 KRW” to “74,915 KRW.”

FIG.5illustrates an operational flowchart of a server which detects a transmission delay status of a transaction, when first transaction data includes a plurality of pieces of transaction data according to an embodiment. Operations ofFIG.5may be associated with the operation205ofFIG.2. In regard to the description ofFIG.5, the same or similar description described above may be omitted. In an embodiment, operations501to509ofFIG.5may be performed by a processor (e.g., the processor136ofFIG.1) of a server (e.g., the server130ofFIG.1).

Referring toFIG.5, in operation501, the server130may receive first transaction data including a plurality of pieces of transaction data from an electronic device (e.g., the electronic device110ofFIG.1). For example, the first transaction data may include transaction data #1-1 (first part of the first transaction data) including first fee information (e.g., 0.00000003 BTC (3satoshi)) and transaction data #1-2 (second part of the first transaction data) including second fee information (e.g., 0.00000005 BTC (5satoshi)) of a fee higher than that of the first fee information.

According to an embodiment, in operation503, the server130may transmit the transaction data #1-1 (first part of the first transaction data) including first fee information to a blockchain network (e.g., the blockchain network150ofFIG.1). In an embodiment, the server130may arrange fee information of the first transaction data in an ascending order, and may transmit transaction data to the blockchain network150sequentially starting from transaction data including lowest fee information. For example, the server may transmit the transaction data #1-1 (first part of the first transaction data) including a fee of 0.00000003 BTC (3 satoshi) to the blockchain network150before the transaction data #1-2 (second part of the first transaction data) including a fed of 0.00000005 (5 satoshi).

According to an embodiment, in operation505, the server130may identify a transmission delay status of the transaction data #1-1 (first part of the first transaction data). In an embodiment, when the transaction data #1-1 (first part of the first transaction data) is not recorded in a new block during a threshold transmission time (e.g., 20 minutes), for example, which is set by a user, the server130may determine that the transaction data #1-1 (first part of the first transaction data) is in the transmission delay status.

According to an embodiment, in operation507, the server130may transmit to the blockchain network150the transaction data #1-2 (second part of the first transaction data) including second fee information higher than the first fee information. In an embodiment, after transmitting the transaction data #1-1 (first part of the first transaction data) including lowest fee information of the first transaction data, the server130may sequentially transmit the transaction data #1-2 (second part of the first transaction data) including second lowest fee information. Although the first transaction data includes only two pieces or parts of transaction data (the first part of the first transaction data and the second part of the first transaction data) for convenience of description, the number of pieces of transaction data is not limited to two and may vary depending on setting of a fee range.

According to an embodiment, in operation509, the server130may identify the transmission delay status of the transaction data #1-2 (second part of the first transaction data). In an embodiment, when the transaction data #1-2 (second part of the first transaction data) is not recorded in a new block during a threshold transmission time, for example, which is set by the user, the server130may determine that the transaction data #1-2 (second part of the first transaction data) is in the transmission delay status. In another embodiment, when the transaction data #1-2 (second part of the first transaction data) is recorded in the new block within the threshold transmission time set by the user, the server130may determine that the transaction data #1-2 (second part of the first transaction data) is in a transmission completion status. In this case, operations subsequent to the operation205ofFIG.2may be omitted.

FIG.6illustrates an operational flowchart for determining status information of transaction data, based on a threshold transmission time for fee information according to an embodiment. Operations ofFIG.6may be associated with the operation205ofFIG.2. In regard to the description ofFIG.6, the same or similar description described above may be omitted. In an embodiment, the operations601to611ofFIG.6may be performed by a processor (e.g., the processor136ofFIG.1) of a server (e.g., the server130ofFIG.1).

Referring toFIG.6, in operation601, the server130may receive, from an electronic device (e.g., the electronic device110ofFIG.1), information on a first threshold transmission time for first fee information and a second threshold transmission time for second fee information of a fee higher than that of the first fee information. For example, when the first fee information corresponds to a fee having a ‘normal’ transfer rate, the first threshold transmission time may correspond to a 3-confirmation time (approximately 30 minutes). When the second fee information of a fee higher than that of the first fee information corresponds to a fee having a ‘fast’” transfer rate, the second threshold transmission time may correspond to a 1-confirmation time (approximately 10 minutes). The confirmation time may be used to calculate a time required to record transaction data in a new block, based on a time required to generate the new block.

According to an embodiment, in operation603, the server130may transmit transaction data #1-1 (first part of the first transaction data) to a blockchain network (e.g., the blockchain network150ofFIG.1). Descriptions on the operation603may correspond to the descriptions on the operation503ofFIG.5.

According to an embodiment, in operation605, the server130may identify whether a waiting time of the transaction data #1-1 (first part of the first transaction data) in a memory pool exceeds the first threshold transmission time (e.g., a 3-confirmation time (30 minutes)). For example, the server130may measure the waiting time of transaction data #1-1 (first part of the first transaction data) in the memory pool from a time at which the transaction data #1-1 (first part of the first transaction data) starts to be transmitted to the blockchain network150. In an embodiment, when the waiting time of transaction data #1-1 (first part of the first transaction data) in the memory pool exceeds the first threshold transmission time (Yes in operation605), in operation607, the server130may transmit transaction data #1-2 (second part of the first transaction data) to the blockchain network150.

According to an embodiment, in operation609, the server130may identify whether a waiting time of the transaction data #1-2 (second part of the first transaction data) in a memory pool exceeds a second threshold transmission time (e.g., a 1-confirmation time (10 minutes)). In an embodiment, when the waiting time of transaction data #1-2 (second part of the first transaction data) in the memory pool exceeds the second threshold transmission time (Yes in operation609), in operation611, the server130may determine status information of the first transaction data. The status information of the first transaction data may indicate that the transaction data #1-1 (first part of the first transaction data) and the transaction data #1-2 (second part of the first transaction data) are in a transmission delay status.

According to an embodiment, when the waiting time of transaction data #1-1 (first part of the first transaction data) in the memory pool does not exceed the first threshold transmission time as a result of executing the operation605(No in operation605), the server130may determine that the transaction data #1-1 (first part of the first transaction data) is in the transmission completion status. According to another embodiment, when the waiting time of transaction data #1-2 (second part of the first transaction data) in the memory pool does not exceed the second threshold transmission time as the result of executing the operation609(No in operation609), the server130may determine that the transaction data #1-2 (second part of the first transaction data) is in the transmission completion status.

FIG.7Aillustrates a first UI status of an electronic device which sets a fee range according to an embodiment.FIG.7Billustrates a second UI status of an electronic device which sets a fee range according to an embodiment.FIG.7Cillustrates a third UI status of an electronic device which sets a fee range according to an embodiment.FIG.7AtoFIG.7Cmay correspond to a UI status corresponding to the operation201or213ofFIG.2.

Referring toFIG.7A, an electronic device (e.g., the electronic device110ofFIG.1) may display a first UI700for generating transaction data through a display (e.g., the display118ofFIG.1). The first UI700may include transaction data including a fee, a remittance amount, and a recipient address for receiving the remittance amount. In an embodiment, the electronic device110may display recommendation fee information (e.g., “fast: 0.000078 BTC”, “normal: 0.000041 BTC”, and “slow: 0.000005 BTC”) received from a server (e.g., the server130ofFIG.1) in a region in which a fee is displayed. In an embodiment, the electronic device110may receive a touch input702for a “fee range setting” region disposed to at least a portion of the region in which the fee is displayed. Upon receiving the touch input702for the “fee range setting” region, the electronic device110may display a UI (e.g., a second UI710ofFIG.7B) capable of setting a fee range through the display118.

Referring toFIG.7B, the electronic device110may display the second UI710capable of setting the fee range through the display118. In an embodiment, the fee range may be calculated based on a recommendation fee received from the server130. For example, at a time at which the second UI710is first displayed, the electronic device110may display a recommendation fee (e.g., the lowest fee value of 00004 BTC and the greatest fee value of 0.00006 BTC) received from the server130in a first region712indicating the lowest fee value and a second region714indicating the greatest fee value. In an embodiment, the electronic device110may change the fee range, based on a user input for the first region712indicating the lowest fee value and the second region714indicating the greatest fee value. For example, upon receiving the user input through the first region712indicating the lowest fee value and the second region714indicating the greatest fee value, the electronic device110may display an input window (e.g., a text box) and an input UI (e.g., a keyboard UI) to allow the user to input a value. Alternatively, the electronic device110may display values in a predetermined range, based on the indicated fee value in the form of a list (e.g., a drop-down list). For example, the electronic device110may change the lowest fee value to 0.00003 BTC and the greatest fee value to 0.00007 BTC, based on the user input. In an embodiment, the electronic device110may receive a touch input716for determining the fee range as the recommendation fee or the fee range set by the user.

Referring toFIG.7C, the electronic device110may display a third UI720including information related to a plurality of pieces of transaction data through the display118. In an embodiment, the third UI720may include information related to a plurality of pieces of transaction data generated based on the determined fee range. For example, the electronic device110may generate transaction data TX9a13nincluding the lowest fee value of 0.00004 BTC and transaction data TX9c21dincluding the highest fee value of 0.00006 BTC. In addition, the electronic device110may generate a plurality of pieces of transaction data, based on a fee value corresponding to a value between the lowest fee value and the highest fee value. For example, the electronic device110may generate the transaction data TX9b23pincluding 0.00005 BTC belonging to the determined fee range. Although the plurality of pieces of transaction data are generated with an interval of 0.00001 BTC (1000 satoshi) for the fee range, the interval value may vary depending on a user's setting or any setting in the electronic device. For example, when the plurality of pieces of transaction data are generated with an interval of 0.000001BTC (100 satoshi), the electronic device110may generate a plurality of pieces of transaction data including fees of 0.00004 BTC, 0.000041 BTC, 0.000042 BTC, . . . , 0.000059 BTC, 0.00006 BTC. The electronic device110may display information (e.g., TX ID, fee information) related to the generated plurality of pieces of transaction data through the display118by including the information in the third UI720.

FIG.8Aillustrates a memory pool800of the blockchain network150according to an embodiment.

Referring toFIG.8A, the memory pool800may be a space in which unconfirmed transactions not recorded in a block are stored. In an embodiment, the memory pool800may be temporarily located in a memory of a blockchain node (e.g., the blockchain node152ofFIG.1). In an embodiment, the blockchain node152may verify validity of received transaction data and then add only validated transaction data to the memory pool800. In an embodiment, the unconfirmed transaction stored in the memory pool800may include a plurality of transactions including a first transaction802, a second transaction804, a third transaction806, and an n-th transaction808. In an embodiment, transactions recordable in a newly created block among the plurality of transactions may be determined based on a fee. In an embodiment, the memory pool800may arrange and store the plurality of transactions in a descending order of a fee. For example, the memory pool800may arrange and store the second transaction804having a fee812of 0.00004 BTC, the first transaction802having a fee810of 0.00001 BTC, and the third transaction802having a fee814of 0.000008 BTC, in that order.

FIG.8Billustrates a virtual block for calculating recommendation fee information according to an embodiment.

Referring toFIG.8B, some transactions among a plurality of transactions arranged in a memory pool may be included in a block to be created by a miner. After some transactions are included in the block to be created, the miner may create a block by sequentially substituting nonce values, and may propagate the created block to the blockchain node152only when the nonce value is matched. In an embodiment, some transactions may consist of transactions corresponding to a priority among the plurality of transactions.

In an embodiment, a server (e.g., the server130ofFIG.1) may identify the memory pool800of a blockchain network (e.g., the blockchain network150ofFIG.1), and may create a virtual block824. For example, the server130may create the virtual block824having a size of 1 MB, and may add upper parts of transaction data of the memory pool800, arranged in a descending order of a fee. The server130may add the transaction data until a size of the transaction data added to the virtual block824reaches 1 MB. In an embodiment, the server130may calculate a recommendation fee, based on a transaction speed and fee information of the transaction data added to the virtual block824. For example, the server130may calculate an upper-50% fee recordable in a block to be created later, based on a current transaction speed and fee information of a plurality of transactions (e.g., the second transaction, the first transaction, the third transaction, etc.) included in the virtual block824as the recommendation fee.

FIG.9is a block diagram illustrating an electronic device901in a network environment900according to various embodiments.

Referring toFIG.9, the electronic device901in the network environment900may communicate with an electronic device902via a first network998(e.g., a short-range wireless communication network), or an electronic device904or a server908via a second network999(e.g., a long-range wireless communication network). According to an embodiment, the electronic device901may communicate with the electronic device904via the server908. According to an embodiment, the electronic device901may include a processor920, memory930, an input device950, a sound output device955, a display device960, an audio module970, a sensor module976, an interface977, a haptic module979, a camera module980, a power management module988, a battery989, a communication module990, a subscriber identification module(SIM)996, or an antenna module997. In some embodiments, at least one (e.g., the display device960or the camera module980) of the components may be omitted from the electronic device901, or one or more other components may be added in the electronic device901. In some embodiments, some of the components may be implemented as single integrated circuitry. For example, the sensor module976(e.g., a fingerprint sensor, an iris sensor, or an illuminance sensor) may be implemented as embedded in the display device960(e.g., a display).

The processor920may execute, for example, software (e.g., a program940) to control at least one other component (e.g., a hardware or software component) of the electronic device901coupled with the processor920, and may perform various data processing or computation. According to one embodiment, as at least part of the data processing or computation, the processor920may load a command or data received from another component (e.g., the sensor module976or the communication module990) in volatile memory932, process the command or the data stored in the volatile memory932, and store resulting data in non-volatile memory934. According to an embodiment, the processor920may include a main processor921(e.g., a central processing unit (CPU) or an application processor (AP)), and an auxiliary processor923(e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operable independently from, or in conjunction with, the main processor921. Additionally or alternatively, the auxiliary processor923may be adapted to consume less power than the main processor921, or to be specific to a specified function. The auxiliary processor923may be implemented as separate from, or as part of the main processor921.

The auxiliary processor923may control at least some of functions or states related to at least one component (e.g., the display device960, the sensor module976, or the communication module990) among the components of the electronic device901, instead of the main processor921while the main processor921is in an inactive (e.g., sleep) state, or together with the main processor921while the main processor921is in an active state (e.g., executing an application). According to an embodiment, the auxiliary processor923(e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., the camera module980or the communication module990) functionally related to the auxiliary processor923.

The memory930may store various data used by at least one component (e.g., the processor920or the sensor module976) of the electronic device901. The various data may include, for example, software (e.g., the program940) and input data or output data for a command related thereto. The memory930may include the volatile memory932or the non-volatile memory934.

The program940may be stored in the memory930as software, and may include, for example, an operating system (OS)942, middleware944, or an application946.

The input device950may receive a command or data to be used by other component (e.g., the processor920) of the electronic device901, from the outside (e.g., a user) of the electronic device901. The input device950may include, for example, a microphone, a mouse, a keyboard, or a digital pen (e.g., a stylus pen).

The sound output device955may output sound signals to the outside of the electronic device901. The sound output device955may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or playing record, and the receiver may be used for an incoming calls. According to an embodiment, the receiver may be implemented as separate from, or as part of the speaker.

The display device960may visually provide information to the outside (e.g., a user) of the electronic device901. The display device960may include, for example, a display, a hologram device, or a projector and control circuitry to control a corresponding one of the display, hologram device, and projector. According to an embodiment, the display device960may include touch circuitry adapted to detect a touch, or sensor circuitry (e.g., a pressure sensor) adapted to measure the intensity of force incurred by the touch.

The audio module970may convert a sound into an electrical signal and vice versa. According to an embodiment, the audio module970may obtain the sound via the input device950, or output the sound via the sound output device955or a headphone of an external electronic device (e.g., an electronic device902) directly (e.g., wiredly) or wirelessly coupled with the electronic device901.

The sensor module976may detect an operational state (e.g., power or temperature) of the electronic device901or an environmental state (e.g., a state of a user) external to the electronic device901, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module976may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface977may support one or more specified protocols to be used for the electronic device901to be coupled with the external electronic device (e.g., the electronic device902) directly (e.g., wiredly) or wirelessly. According to an embodiment, the interface977may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

A connecting terminal978may include a connector via which the electronic device901may be physically connected with the external electronic device (e.g., the electronic device902). According to an embodiment, the connecting terminal978may include, for example, a HDMI connector, a USB connector, a SD card connector, or an audio connector (e.g., a headphone connector).

The haptic module979may convert an electrical signal into a mechanical stimulus (e.g., a vibration or a movement) or electrical stimulus which may be recognized by a user via his tactile sensation or kinesthetic sensation. According to an embodiment, the haptic module979may include, for example, a motor, a piezoelectric element, or an electric stimulator.

The camera module980may capture a still image or moving images. According to an embodiment, the camera module980may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module988may manage power supplied to the electronic device901. According to one embodiment, the power management module988may be implemented as at least part of, for example, a power management integrated circuit (PMIC).

The battery989may supply power to at least one component of the electronic device901. According to an embodiment, the battery989may include, for example, a primary cell which is not rechargeable, a secondary cell which is rechargeable, or a fuel cell.

The communication module990may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device901and the external electronic device (e.g., the electronic device902, the electronic device904, or the server908) and performing communication via the established communication channel. The communication module990may include one or more communication processors that are operable independently from the processor920(e.g., the application processor (AP)) and supports a direct (e.g., wired) communication or a wireless communication. According to an embodiment, the communication module990may include a wireless communication module992(e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module994(e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules may communicate with the external electronic device via the first network998(e.g., a short-range communication network, such as Bluetooth™, wireless-fidelity (Wi-Fi) direct, or infrared data association (IrDA)) or the second network999(e.g., a long-range communication network, such as a cellular network, the Internet, or a computer network (e.g., LAN or wide area network (WAN)). These various types of communication modules may be implemented as a single component (e.g., a single chip), or may be implemented as multi components (e.g., multi chips) separate from each other. The wireless communication module992may identify and authenticate the electronic device901in a communication network, such as the first network998or the second network999, using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module996.

The antenna module997may transmit or receive a signal or power to or from the outside (e.g., the external electronic device) of the electronic device901. According to an embodiment, the antenna module997may include an antenna including a radiating element composed of a conductive material or a conductive pattern formed in or on a substrate (e.g., PCB). According to an embodiment, the antenna module997may include a plurality of antennas. In such a case, at least one antenna appropriate for a communication scheme used in the communication network, such as the first network998or the second network999, may be selected, for example, by the communication module990(e.g., the wireless communication module992) from the plurality of antennas. The signal or the power may then be transmitted or received between the communication module990and the external electronic device via the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as part of the antenna module997.

At least some of the above-described components may be coupled mutually and communicate signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)).

According to an embodiment, commands or data may be transmitted or received between the electronic device901and the external electronic device904via the server908coupled with the second network999. Each of the electronic devices902and904may be a device of a same type as, or a different type, from the electronic device901. According to an embodiment, all or some of operations to be executed at the electronic device901may be executed at one or more of the external electronic devices902,904, or908. For example, if the electronic device901should perform a function or a service automatically, or in response to a request from a user or another device, the electronic device901, instead of, or in addition to, executing the function or the service, may request the one or more external electronic devices to perform at least part of the function or the service. The one or more external electronic devices receiving the request may perform the at least part of the function or the service requested, or an additional function or an additional service related to the request, and transfer an outcome of the performing to the electronic device901. The electronic device901may provide the outcome, with or without further processing of the outcome, as at least part of a reply to the request. To that end, a cloud computing, distributed computing, or client-server computing technology may be used, for example.

The electronic device according to various embodiments may be one of various types of electronic devices. The electronic devices 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. According to an embodiment of the disclosure, the electronic devices are not limited to those described above.

It should be appreciated that various embodiments of the present disclosure and the terms used therein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment. With regard to the description of the drawings, similar reference numerals may be used to refer to similar or related elements. It is to be understood that a singular form of a noun corresponding to an item may include one or more of the things, unless the relevant context clearly indicates otherwise. As used herein, each of such phrases 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,” may include any one of, or all possible combinations of the items enumerated together in a corresponding one of the phrases. As used herein, such terms as “1st” and “2nd,” or “first” and “second” may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively”, as “coupled with,” “coupled to,” “connected with,” or “connected to” another element (e.g., a second element), it means that the element may be coupled with the other element directly (e.g., wiredly), wirelessly, or via a third element.

As used herein, the term “module” may include a unit implemented in hardware, software, or firmware, and may interchangeably be used with other terms, for example, “logic,” “logic block,” “part,” or “circuitry”. A module may be a single integral component, or a minimum unit or part thereof, adapted to perform one or more functions. For example, according to an embodiment, the module may be implemented in a form of an application-specific integrated circuit (ASIC).

Various embodiments as set forth herein may be implemented as software (e.g., the program940) including one or more instructions that are stored in a storage medium (e.g., internal memory936or external memory938) that is readable by a machine (e.g., the electronic device901). For example, a processor (e.g., the processor920) of the machine (e.g., the electronic device901) may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. This allows the machine to be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include a code generated by a complier or a code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Wherein, the term “non-transitory” simply means that the storage medium is a tangible device, and does not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium.

According to an embodiment, a method according to various embodiments of the disclosure may be included and provided in a computer program product. The computer program product may be traded as a product 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 be distributed (e.g., downloaded or uploaded) online via an application store (e.g., PlayStore™), or between two user devices (e.g., smart phones) directly. If distributed online, at least part of the computer program product may be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as memory of the manufacturer's server, a server of the application store, or a relay server.

According to various embodiments, each component (e.g., a module or a program) of the above-described components may include a single entity or multiple entities. According to various embodiments, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, according to various embodiments, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. According to various embodiments, operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added.