KR102812835B1 - Method and system for providing transaction status information - Google Patents

Abstract

A method and system for providing transaction status information are disclosed. The method for providing transaction status information according to one embodiment may include: a step of obtaining transaction progress information including information on a status before the transaction conclusion of a transaction identified by a transaction identifier is completed; a step of storing, by at least one processor, the transaction progress information in a database in association with the transaction identifier; a step of receiving, by at least one processor, an inquiry request for the transaction identified by the transaction identifier from a user; a step of searching, by at least one processor, transaction progress information of the transaction for which an inquiry is requested from the database; and a step of providing, by at least one processor, information on the status of the transaction identified by the transaction identifier to the user using the searched transaction progress information.

Description

METHOD AND SYSTEM FOR PROVIDING TRANSACTION STATUS INFORMATION

The following description relates to a method and system for providing transaction status information.

A cryptocurrency exchange is a marketplace where users can trade their cryptocurrency for fiat currency or other cryptocurrencies.

In these cryptocurrency exchanges, when depositing or withdrawing cryptocurrencies such as coins or tokens, cryptocurrency deposits or withdrawals are made based on the confirmation of a transaction that includes status change information between the user account address of the public blockchain and the account address of the exchange. At this time, cryptocurrency deposits or withdrawals are not made immediately according to the creation or distribution of the transaction, but rather based on the confirmation of the transaction, so the user's cryptocurrency deposits or withdrawals are bound to be significantly delayed. This is because the stability of the transaction improves as blocks accumulate after the creation and distribution of a specific transaction.

Confirmation of a transaction is done by creating a transaction, for example, to transfer bitcoin from address A to address B, signing it with your own 'private key' and propagating it to the network, where the transaction is stored in the queue of each node's memory, and the miner receives the stored transaction, inserts it into the block that he mines and issues, and then propagates it. After the transaction is confirmed in this way, if a new block is additionally formed and connected to the previous blockchain with the blockhead hash value, the number of confirmations becomes 2 or more. Each cryptocurrency exchange sets the number of such confirmations and approves or settles (settlement) deposits.

Accordingly, for example, coin deposits and withdrawals from Exchange A to Exchange B proceed in the following steps. Step 1 is the withdrawal approval step at Exchange A. In order to transfer coins from Exchange A to Exchange B, withdrawal approval from Exchange A must first be obtained. If Exchange A suspects financial fraud such as voice phishing, it will reject the withdrawal approval. Step 2 is the confirmation step on the blockchain network. Once the withdrawal approval is completed at Exchange A, the coins are transferred to the blockchain network to be confirmed. At this time, if the fee to be paid is low and the miner avoids approval, the approval may be delayed or canceled. Step 3 is the deposit approval step at Exchange B. When the number of confirmations for deposit approval set by the exchange to which you are depositing is met, approval is automatically made. The number of confirmations required for approval varies by coin and exchange.

In addition, users of existing cryptocurrency services only received information that the remittance was completed when requesting a remittance. However, unlike general financial transactions, cryptocurrency transactions take a relatively long time to conclude, so users cannot help but feel anxious about whether their transactions are proceeding smoothly.

[Prior literature number]

Korean Publication Patent No. 10-1952420

Embodiments of the present invention provide a method and system for adjusting the number of confirmations, which allows a user to specify the number of confirmations for approval of a deposit or withdrawal from an exchange in relation to a transaction in a cryptocurrency service.

Other embodiments of the present invention provide a method and system for providing transaction status information, which can provide users with information on transaction status related to deposits and withdrawals of cryptocurrency currently in progress.

Still other embodiments of the present invention provide a method and system for monitoring delayed transactions, which can monitor the delay of transactions on a cryptocurrency wallet platform side and provide information on the delay in processing the corresponding transactions to an exchange side.

A method for providing transaction status information, performed by a computer device including at least one processor, comprises: a step of obtaining, by the at least one processor, transaction progress information including information on a status before completion of a transaction for a transaction identified by a transaction identifier; a step of storing, by the at least one processor, the transaction progress information in a database in association with the transaction identifier; a step of receiving, by the at least one processor, an inquiry request for a transaction identified by the transaction identifier from a user; a step of searching, by the at least one processor, transaction progress information of the transaction for which an inquiry is requested from the database; and a step of providing, by the at least one processor, information on the status of the transaction identified by the transaction identifier to the user using the searched transaction progress information.

According to one aspect, the step of acquiring the transaction progress information may be characterized by acquiring transaction progress information including at least one of a state in which a transaction request from the user is received, a state in which information about the transaction is provided to nodes of a blockchain network for confirmation of the transaction identified by the transaction identifier, a state in which transaction information is transmitted but not stored as a block, a state in which transaction information is stored as a block, and a state in which the number of confirmations required for the transaction request is satisfied.

According to another aspect, the step of obtaining the transaction progress information may be characterized by obtaining transaction progress information including the number of confirmations achieved to date for the transaction.

According to another aspect, the step of providing information on the status of the transaction may be characterized by providing at least one of the current status of the transaction and the current confirmation number of the transaction.

According to another aspect, the step of providing information on the status of the transaction may be characterized by displaying the overall status of the transaction through a page provided to the user in connection with the cryptocurrency service, while displaying the current status of the transaction separately from the remaining statuses among the overall statuses.

According to another aspect, the step of providing information on the status of the transaction may be characterized by displaying the current number of confirmations through a page provided to the user in connection with the cryptocurrency service.

According to another aspect, the step of providing information on the status of the transaction may be characterized by displaying the current confirmation number in conjunction with the number of confirmations required for approval of a deposit or withdrawal of the transaction.

According to another aspect, the method for providing transaction status information may further include a step of providing a notification of a changed transaction status to the user by the at least one processor.

According to another aspect, the step of obtaining the transaction progress information may be characterized by receiving the transaction progress information from a cryptocurrency wallet platform that manages the user's wallet.

A computer program stored on a computer-readable recording medium is provided for executing the above method on the computer device by being combined with a computer device.

A computer-readable recording medium having recorded thereon a program for executing the above method on a computer device is provided.

A computer device is provided, comprising at least one processor implemented to execute instructions readable by a computer device, characterized in that the computer device obtains, by the at least one processor, transaction progress information including information on a status before completion of a transaction for a transaction identified by a transaction identifier, stores the transaction progress information in a database in association with the transaction identifier, receives a query request for a transaction identified by the transaction identifier from a user, searches the database for transaction progress information of the requested query transaction, and provides the user with information on the status of the transaction identified by the transaction identifier using the searched transaction progress information.

In relation to transactions on cryptocurrency services, users can specify the number of confirmations required for approval of deposits or withdrawals from the exchange.

Additionally, the exchange may provide users with information about the transaction status related to the current cryptocurrency transaction deposit and withdrawal.

Additionally, the cryptocurrency wallet platform can monitor transaction delays and provide information about delays in processing such transactions to the exchange.

FIG. 1 is a diagram illustrating an example of a network environment according to one embodiment of the present invention.
FIG. 2 is a block diagram illustrating an example of a computer device according to one embodiment of the present invention.
FIG. 3 is a diagram illustrating a general example of a cryptocurrency system according to one embodiment of the present invention.
FIG. 4 is a flowchart illustrating an example of a method for adjusting the number of confirmations according to one embodiment of the present invention.
FIGS. 5 to 8 are drawings illustrating examples of a user interface for receiving a desired confirmation number according to one embodiment of the present invention.
FIG. 9 is a flowchart illustrating an example of a method for providing transaction status information according to one embodiment of the present invention.
FIG. 10 is a drawing illustrating an example of a user interface that provides transaction status information according to one embodiment of the present invention.
FIG. 11 is a flowchart illustrating an example of a delayed transaction monitoring method according to one embodiment of the present invention.
FIG. 12 is a drawing illustrating an example of providing delayed transaction information according to one embodiment of the present invention.

Hereinafter, the present invention will be described in detail with reference to the attached drawings.

The cryptocurrency system according to embodiments of the present invention may be implemented by at least one computer device. At this time, the computer device may have a computer program according to an embodiment of the present invention installed and run, and the computer device may perform the method according to embodiments of the present invention under the control of the run computer program. The above-described computer program may be stored in a computer-readable recording medium in order to be combined with the computer device and cause the computer to execute the method according to embodiments of the present invention.

FIG. 1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention. The network environment of FIG. 1 represents an example including a plurality of electronic devices (110, 120, 130, 140), a plurality of servers (150, 160), and a network (170). FIG. 1 is an example for explaining the invention, and the number of electronic devices or servers is not limited to FIG. 1. In addition, the network environment of FIG. 1 merely describes one example of environments applicable to the present embodiments, and the environment applicable to the present embodiments is not limited to the network environment of FIG. 1.

The plurality of electronic devices (110, 120, 130, 140) may be fixed terminals or mobile terminals implemented as computer devices. Examples of the plurality of electronic devices (110, 120, 130, 140) include smart phones, mobile phones, navigation devices, computers, laptops, digital broadcasting terminals, PDAs (Personal Digital Assistants), PMPs (Portable Multimedia Players), tablet PCs, etc. For example, in FIG. 1, the shape of a smart phone is shown as an example of the electronic device (110), but in the embodiments of the present invention, the electronic device (110) may actually mean one of various physical computer devices that can communicate with other electronic devices (120, 130, 140) and/or servers (150, 160) via a network (170) using a wireless or wired communication method.

The communication method is not limited, and may include not only a communication method that utilizes a communication network (for example, a mobile communication network, a wired Internet, a wireless Internet, a broadcasting network) that the network (170) may include, but also a short-range wireless communication between devices. For example, the network (170) may include any one or more of a network such as a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), and the Internet. In addition, the network (170) may include any one or more of a network topology including, but not limited to, a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree, or a hierarchical network.

Each of the servers (150, 160) may be implemented as a computer device or a plurality of computer devices that communicate with a plurality of electronic devices (110, 120, 130, 140) through a network (170) to provide commands, codes, files, contents, services, etc. For example, the server (150) may be a system that provides a service (for example, a cryptocurrency service, a virtual exchange service, a social network service, a payment service, a risk monitoring service, an instant messaging service, a game service, a group call service (or a voice conference service), a messaging service, a mail service, a map service, a translation service, a financial service, a search service, a content provision service, etc.) to a plurality of electronic devices (110, 120, 130, 140) connected through a network (170).

FIG. 2 is a block diagram illustrating an example of a computer device according to an embodiment of the present invention. Each of the plurality of electronic devices (110, 120, 130, 140) or servers (150, 160) described above can be implemented by the computer device (200) illustrated in FIG. 2.

The computer device (200) may include a memory (210), a processor (220), a communication interface (230), and an input/output interface (240), as illustrated in FIG. 2. The memory (210) may be a computer-readable storage medium, and may include a random access memory (RAM), a read only memory (ROM), and a permanent mass storage device such as a disk drive. Here, the permanent mass storage devices such as the ROM and the disk drive may be included in the computer device (200) as a separate permanent storage device distinct from the memory (210). In addition, the memory (210) may store an operating system and at least one program code. These software components may be loaded into the memory (210) from a computer-readable storage medium separate from the memory (210). The separate computer-readable storage medium may include a computer-readable storage medium such as a floppy drive, a disk, a tape, a DVD/CD-ROM drive, a memory card, etc. In another embodiment, the software components may be loaded into the memory (210) via a communication interface (230) other than a computer-readable recording medium. For example, the software components may be loaded into the memory (210) of the computer device (200) based on a computer program that is installed by files received over a network (170).

The processor (220) may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input/output operations. The instructions may be provided to the processor (220) by the memory (210) or the communication interface (230). For example, the processor (220) may be configured to execute instructions received according to program code stored in a storage device such as the memory (210).

The communication interface (230) may provide a function for the computer device (200) to communicate with other devices (for example, the storage devices described above) via the network (170). For example, requests, commands, data, files, etc. generated by the processor (220) of the computer device (200) according to program codes stored in a recording device such as the memory (210) may be transmitted to other devices via the network (170) under the control of the communication interface (230). Conversely, signals, commands, data, files, etc. from other devices may be received by the computer device (200) via the communication interface (230) of the computer device (200) via the network (170). Signals, commands, data, etc. received via the communication interface (230) may be transmitted to the processor (220) or the memory (210), and files, etc. may be stored in a storage medium (the permanent storage device described above) that the computer device (200) may further include.

The input/output interface (240) may be a means for interfacing with an input/output device (250). For example, the input device may include a device such as a microphone, a keyboard, or a mouse, and the output device may include a device such as a display or a speaker. As another example, the input/output interface (240) may be a means for interfacing with a device that integrates input and output functions, such as a touchscreen. At least one of the input/output devices (250) may be configured as a single device with the computer device (200). For example, a touchscreen, a microphone, a speaker, etc. may be implemented in a form included in the computer device (200), such as a smartphone.

Also, in other embodiments, the computer device (200) may include fewer or more components than the components of FIG. 2. However, it is not necessary to explicitly illustrate most of the conventional components. For example, the computer device (200) may be implemented to include at least some of the input/output devices (250) described above, or may further include other components such as a transceiver, a database, etc.

FIG. 3 is a diagram illustrating a general example of a cryptocurrency system according to an embodiment of the present invention. FIG. 3 illustrates a first user (310), a second user (320), a third user (330), a first exchange (340), a second exchange (350), a third exchange (360), a cryptocurrency wallet platform (370), a first blockchain network (380), and a second blockchain network (390).

The first user (310), the second user (320), and the third user (330) may represent some of a plurality of users utilizing the cryptocurrency service, and the first exchange (340), the second exchange (350), and the third exchange (360) may represent some of a plurality of exchanges providing the cryptocurrency service. In the present disclosure, a user may refer to a user terminal including electronic devices (110, 120, 130, 140). For example, the first user (310), the second user (320), and the third user (330) may be a first user terminal, a second user terminal, and a third user terminal, respectively, which are electrically connectable to the first exchange (340), the second exchange (350), and the third exchange (360).

Adjust the number of confirmations

In the embodiment of Fig. 3, it is assumed that a first user (310) transfers a first type of coin to a third user (330) through a first exchange (340) and a third exchange (360). At this time, a withdrawal request from the wallet of the first user (310) may be made from the first exchange (340) to the cryptocurrency wallet platform (370) through the withdrawal approval step of the first exchange (340). Thereafter, as the withdrawal approval of the first exchange (340) is made, the confirmation of the transaction may be processed in the first blockchain network (380) that processes the confirmation for the first type of coin.

If the number of confirmations made in the first blockchain network (380) meets a preset confirmation number, the first exchange (340) can approve a withdrawal from the first exchange (340), and accordingly, the first type of coin can be deposited to the third user (330) in the third exchange (360). In this case, the preset confirmation number can be replaced with the desired confirmation number input by the user when requesting a transaction for withdrawal from the first exchange (340), if the user inputs a desired confirmation number for the first type of coin.

In other words, in the present embodiment, when a remittance request is made from a first user (310), the first exchange (340) can provide a user interface for receiving a desired confirmation number from the first user (310) and can receive the desired confirmation number through this user interface. In this case, the first exchange (340) can check the generation of a block related to the transaction request in the first blockchain network (380), and when the number of blocks generated related to the transaction request (e.g., the number of blocks for the transaction and blocks generated subsequent to this block) reaches the desired confirmation number, the first exchange (340) can process approval for withdrawal of the transaction. Accordingly, after the desired confirmation number of the first user (310) is reached, the third exchange (360) can process approval for deposit according to the transaction of the first user (310). In another example, the third exchange (360) may directly receive input from the user for a desired confirmation number as a setting value for a deposit, or may receive the desired confirmation number input from the user through the cryptocurrency wallet platform (370) and/or the first exchange (340). In this way, if there is input or transmission of a desired confirmation number for a deposit from the user, the third exchange (360) may process the deposit approval based on the desired confirmation number for the deposit.

As the number of confirmations decreases, the time required to complete a transaction decreases, but the risk of blockchain reorganization increases. Conversely, as the number of confirmations increases, the time required to complete a transaction increases, but the risk of blockchain reorganization decreases. Here, blockchain reorganization can mean that the blockchain containing the transaction information falls behind in the competition between blockchains, and another blockchain becomes the winner. In this case, the transaction information must be included again in the new block of the other blockchain that becomes the winner, so the time required to complete a transaction increases dramatically.

In other words, each exchange can provide an opportunity to lower the desired confirmation number for users who want to shorten the time required for transaction execution despite the increased risk of blockchain restructuring. For example, if the time required for one block to be created (or confirmed) in the first blockchain network (380) is 10 minutes and the preset confirmation number in the third exchange (360) is 6, the expected time required for the execution of the corresponding transaction is 1 hour (10 minutes * 6). Therefore, users who need faster transaction execution despite the increased risk of blockchain restructuring can reduce the time required for transaction execution by lowering the desired confirmation number to less than 6. Conversely, users who want to reduce the risk of blockchain restructuring can lower the actual risk of blockchain restructuring by increasing the desired confirmation number to 7 or more. The expected time required as described above may be the time required when there is no delay in processing deposit approval. Even if the exchange processes the deposit approval when the preset number of confirmations and/or the desired number of confirmations are reached, the time required may increase if there is a delay in the processing of the deposit approval. Therefore, the time required to reach a certain number of confirmations and the time required to execute a transaction can be distinguished.

The time for a block to be created (or confirmed) may vary depending on the type of transaction currency (BTC, LN, etc.). To this end, the first exchange (340) may receive a selection of a priority transaction currency from the first user (310) and may present a confirmation number for the selected transaction currency. The presented confirmation number may be a confirmation number (for example, 6) preset by the first user (310) as a setting value for remittance, or a confirmation number preset according to the type of transaction currency, but may also be a confirmation number dynamically calculated by considering the current transaction complexity of the corresponding transaction currency.

In addition, the first exchange (340) may provide the first user (310) with a user interface through which the first user (310) may input a desired confirmation number. The exchange may determine whether the desired confirmation number input through the user interface is within an acceptable range for the corresponding transaction currency, and may induce or force the first user (310) to input a desired confirmation number within the acceptable range.

In addition, the exchange can calculate and display the time taken to reach the desired confirmation number. For example, if the time taken to create (or confirm) one block for the type of transaction currency selected by the first user (310) is 10 minutes, and the desired confirmation number entered by the user is 3, the estimated time taken to reach the desired confirmation number may be 30 minutes. The calculated time may be displayed, for example, through the user interface described above. The time taken to reach the desired confirmation number and the time taken to actually execute a transaction may differ due to reasons such as blockchain restructuring.

Additionally, the exchange may calculate and display the probability of a blockchain reorganization occurring based on the number of desired confirmations. This probability may be displayed as a risk for the input number of desired confirmations via the user interface described above.

In the embodiment of FIG. 3, a transaction in which a first user (310) sends money to a third user (330) through a first exchange (340) and a third exchange (360) is described, but the use of the desired confirmation number can be applied to all exchanges that adopt it.

Provide transaction status information

Meanwhile, the exchange according to the present embodiment can provide information on the status of the transmitted transaction.

For example, an exchange (for example, the first exchange (340)) can obtain information related to a transaction identified by a transaction identifier (transaction ID). This information can be directly confirmed by the exchange through blocks of a blockchain network (for example, the first blockchain network (380)) or can be received through a cryptocurrency wallet platform (370). As a more specific example, the cryptocurrency wallet platform (370) can periodically store information related to a transaction identifier of a propagated transaction in a message queue, and the exchange can receive information related to a transaction identifier of a specific transaction from this message queue.

The exchange can store and manage changes to the transaction status related to each of these transaction identifiers in a database and provide users with notifications of the changed status. For example, the exchange can provide a push notification to the user's terminal regarding the changed status.

Meanwhile, a user may request an exchange to inquire about his or her transaction history. A specific transaction history between a user and an exchange may be identified using a request identifier (Request ID). In this case, the exchange may find a transaction identifier matching the request identifier and provide the user with information about the transaction status stored in connection with the transaction identifier. For example, the exchange may inquire from the database whether the transaction identified by the transaction identifier has been broadcast, whether it has been mined, and/or the current number of confirmations for the transaction, and may provide the user with information about the settlement status of the transaction based on the inquired information.

Therefore, users can obtain real-time transaction status information on how their transaction is progressing without having to wait for their transaction to be completed.

Delayed Transaction Monitoring

Meanwhile, the cryptocurrency wallet platform (370) can receive transaction requests from each of multiple exchanges (multiple transaction servers) and process data for remittance between wallets within the cryptocurrency wallet platform (370) or between wallets within the cryptocurrency wallet platform (370) and wallets outside the cryptocurrency wallet platform (370).

At this time, the cryptocurrency wallet platform (370) can check whether there is a transaction (hereinafter, 'unfinished transaction') that has not been completed even after a certain period of time has passed since the time when the transaction request was received. If there is an unfinished transaction, the cryptocurrency wallet platform (370) can provide a notification of the delay of the transaction to the transaction partner who requested the transaction. Here, the certain period of time can be set by the cryptocurrency wallet platform (370) or can be determined according to the options for the transaction request of the exchange. For example, exchanges can set a period of time when requesting a transaction to the cryptocurrency wallet platform (370) and request the cryptocurrency wallet platform (370) to provide a notification of an unfinished transaction for the set period.

In addition, as already explained, the cryptocurrency wallet platform (370) may provide information related to the transaction identifier (transaction ID) of the transmitted transaction to each exchange through a message queue, etc. In this case, each exchange can obtain information on the progress status of the transaction as well as information on the transaction delay through the cryptocurrency wallet platform (370).

FIG. 4 is a flowchart illustrating an example of a method for adjusting the number of confirmations according to an embodiment of the present invention. The method for adjusting the number of confirmations according to the present embodiment may be performed by a computer device (200) implementing an exchange. At this time, the processor (220) of the computer device (200) may be implemented to execute a control instruction according to a code of an operating system included in a memory (210) or a code of at least one computer program. Here, the processor (220) may control the computer device (200) to perform steps (410 to 460) included in the method of FIG. 4 according to a control instruction provided by a code stored in the computer device (200).

In step (410), the computer device (200) may receive a selection of the type of transaction currency from the user. For example, the computer device (200) may provide a user interface for receiving a request for a transaction from the user. This user interface may be provided to the user through a webpage or an app. Since the types of cryptocurrencies are diverse, such as BTC, LN, etc., the computer device (200) may provide a currency type selection function for receiving a selection of the type of currency the user wishes to trade through the provided user interface. In this case, the computer device (200) may receive information on the type of transaction currency selected through the currency type selection function.

In step (420), the computer device (200) may present a confirmation number for the selected type of transaction currency. At this time, the presented confirmation number may be a confirmation number preset by the type of transaction currency or by the exchange. For example, the computer device (200) may store the confirmation number by type of transaction currency and/or by exchange in advance, and may check the confirmation number by type of transaction currency selected by the user and/or the confirmation number by the user's settings and present it to the user. As another example, the computer device (200) may dynamically calculate and present the confirmation number by considering the current transaction complexity of the selected transaction currency. For example, the computer device (200) may determine and present the confirmation number so that the number of confirmations to be presented decreases or increases as the transaction complexity increases. This confirmation number may be presented to the user by being displayed through the user interface described above.

In step (430), the computer device (200) may receive an input for a desired confirmation number from the user. For example, the computer device (200) may provide a desired confirmation number input function for receiving a desired confirmation number from the user through a user interface provided to the user for generating a transaction request. In this case, the computer device (200) may receive a desired confirmation number input from the user through the desired confirmation number input function.

At this time, the computer device (200) can determine whether the number of desired confirmations received is within the range allowed for the corresponding type of transaction currency, and can induce or force the user to input the number of desired confirmations within the range.

In addition, the computer device (200) can calculate and display the expected time taken to reach the desired confirmation number. For example, if the time taken to create (or confirm) one block for the first type of transaction currency is 10 minutes and the desired confirmation number input by the user is 6, the expected time taken to reach the desired confirmation number may be 60 minutes. The calculated time may be displayed through the user interface described above. The time taken to reach the desired confirmation number and the time taken to actually conclude a transaction may differ due to reasons such as blockchain restructuring.

In addition, the computer device (200) may calculate the probability of blockchain restructuring based on the desired confirmation number and display information about the calculated probability. This probability may be displayed as a risk for the input desired confirmation number through the user interface described above. For example, the computer device (200) may display the risk in preset level units such as three levels of "high", "medium", and "low", or five levels of 1 to 5.

When a user inputs a desired number of confirmations, the expected time and risk can be dynamically displayed, and when the user changes the desired number of confirmations, the expected time and risk for the changed desired number of confirmations can also be dynamically displayed. Accordingly, the user can determine an appropriate desired number of confirmations that is suitable for him/her by considering both the expected time and risk.

In step (440), the computer device (200) can process confirmation for the transaction request using the received desired confirmation number. For example, if the desired confirmation number is received together with the transaction request for withdrawal, the computer device (200) can check the generation of a block related to the transaction request in the blockchain network, and if the number of blocks generated related to the transaction request (e.g., the number of blocks for the transaction and blocks generated subsequent to this block) reaches the desired confirmation number, the confirmation for the transaction (withdrawal) can be processed. The exchange can set the desired confirmation number according to the type of transaction currency, and in this case, the withdrawal approval can be processed if the desired confirmation number is satisfied. In step (450), the computer device (200) can receive a transaction request from an exchange different from the exchange implemented by the computer device (200). When a transaction on a blockchain network is related to an exchange implemented by a computer device (200), the computer device (200) may receive a transaction request transmitted from another exchange. Depending on the embodiment, the transaction request may be received by the computer device (200) via a cryptocurrency wallet platform (370). Here, the transaction request from the other exchange may be a deposit request.

In step (460), the computer device (200) can process approval of a deposit for a transaction request according to the user's desired confirmation number for the received transaction request. For example, the computer device (200) can receive an input for a desired confirmation number as one setting value for a deposit from the user. In this case, if the user's setting value for the first type of transaction currency includes 3 as the desired confirmation number, the computer device (200) can process approval of a deposit if the confirmation number 3 is satisfied.

FIGS. 5 to 8 are drawings illustrating examples of a user interface for receiving a desired confirmation number according to one embodiment of the present invention.

Figure 5 shows an example of a page (a webpage or a page provided by an app) for a user to request a remittance transaction.

The first dotted box (510) shows an example of a function that allows a user to select a type of transaction currency. As the user selects a specific type of transaction currency, the user may be provided with information about total assets, assets in use, and available assets for that type of transaction currency.

The second dotted box (520) shows an example of a function for receiving a withdrawal address for a remittance transaction from a user.

The third dotted box (530) shows an example of a function for receiving a desired confirmation number from a user. The third dotted box (530) prompts the user to input a number between 1 and 30. Here, the numbers 1 and 30 may be adjusted to acceptable numbers depending on the type of the corresponding transaction currency. In this case, the adjusted numbers may be a means for forcing the user to input an acceptable desired confirmation number. Alternatively, after allowing the input of any number, if the number exceeds the acceptable number, information may be provided to the user to prompt the input of an acceptable number.

The fourth dotted box (540) shows an example of a function that dynamically calculates and displays the risk corresponding to the desired confirmation number input by the user and the expected time to reach the desired confirmation number. In this fourth dotted box (540), as shown in the third dotted box (530), when the user inputs the desired confirmation number as 6, the risk "Medium" corresponding to the desired confirmation number 6 and the expected time to reach the desired confirmation number "about 1 hour" are displayed to the user. Here, as described above, the risk may mean the risk of blockchain restructuring. In this way, by displaying the risk and the expected time to reach the desired confirmation number, it is possible to help the user set the desired confirmation number.

The fifth dotted box (550) shows an example of a function for receiving a deposit address for a remittance transaction from a user.

The sixth dotted box (560) shows an example of a function for receiving input from a user for a transaction quantity. When a user inputs a specific quantity, information such as whether there is a shortage of assets, fees, and total sum can be provided to the user.

Figures 6 and 7 illustrate examples of inputting the number of confirmations through a user interface in the form of a bar. In this case, as the user moves the bar to set the desired number of confirmations, the risk and the expected time to reach the desired number of confirmations can be dynamically calculated and displayed. In this case, the embodiments of Figures 6 and 7 consider a case where the time for one block to be created (or confirmed) is 1 minute.

Fig. 8 shows an example of a user interface for setting a desired confirmation number by type of currency (coin) in the settings. As shown in the seventh dotted box (810), a user can add a desired currency type and then set a desired confirmation number for the added currency. In this way, the desired confirmation number set through the settings can be used to automatically set a desired confirmation number even if the user does not set a desired confirmation number when sending money, or can be utilized to set a confirmation number for approval of a withdrawal or deposit as the desired confirmation number. For example, an exchange can approve a withdrawal or deposit of a user's currency if the desired confirmation number, not the confirmation number set systematically by the exchange, is satisfied.

FIG. 9 is a flowchart illustrating an example of a method for providing transaction status information according to an embodiment of the present invention. The method for providing transaction status information according to the present embodiment may be performed by a computer device (200) implementing an exchange. At this time, the processor (220) of the computer device (200) may be implemented to execute a control instruction according to a code of an operating system included in a memory (210) or a code of at least one computer program. Here, the processor (220) may control the computer device (200) to perform steps (910 to 960) included in the method of FIG. 9 according to a control instruction provided by a code stored in the computer device (200).

In step (910), the computer device (200) can obtain transaction status information including information on a status before the transaction settlement of the transaction identified by the transaction identifier is completed. This transaction status information can be received through the cryptocurrency wallet platform (370), but at least some of the transaction status information can be directly confirmed by the exchange through blocks of the blockchain network. As a more specific example, the cryptocurrency wallet platform (370) can periodically store information related to a transaction identified by a specific transaction identifier in a message queue, and the computer device (200) can receive transaction status information for a transaction of a specific transaction identifier from this message queue.

In step (920), the computer device (200) may store transaction status information in a database by associating it with a transaction identifier. For example, a transaction may sequentially change its status, such as a “transaction request” status, a “broadcast” status, a “pending” status, a “mining” status, a “confirmation” status, and a “complete” status. The “transaction request” status may mean a status in which a transaction request is received from a user, the “broadcast” status may mean a status in which information about the transaction is provided to nodes of a blockchain network for confirmation of the transaction, the “pending” status may mean a status in which transaction information is broadcast but not stored as a block, the “mining” status may mean a status in which transaction information is stored as a block, the “confirmation” status may mean a status in which the number of confirmations required for the transaction request is satisfied, and the “complete” status may mean a status in which the transaction is completed. The computer device (200) may store the changed contents in a database whenever the status of a transaction changes, thereby maintaining the latest information about the status of the transaction. The type and number of transaction statuses may vary depending on the embodiment. In addition, the computer device (200) may further store the current number of confirmations as transaction status information. This number of confirmations may mean the number of confirmations made in relation to the transaction to date in the blockchain network.

In step (930), the computer device (200) may provide a notification to the user regarding the changed transaction status. The computer device (200) may provide the user with information regarding the change in the transaction status in response to recognizing that the transaction status has changed. For example, the computer device (200) may provide information regarding the change in the transaction status in the form of a push notification to the user's terminal. In other words, the computer device (200) may notify the user of each transaction status. In addition, the computer device (200) may provide a notification each time the number of confirmations increases.

In step (940), the computer device (200) may receive an inquiry request from the user for a transaction identified by a transaction identifier. In addition to the computer device (200) directly providing a notification, the computer device (200) may provide information on the status of the transaction according to the user's inquiry request. Step (940) may be a process in which the computer device (200) receives the user's inquiry request from the user's terminal through a network (for example, the network (170)).

In step (950), the computer device (200) can retrieve transaction status information of a transaction for which a query is requested from a database. For example, the transaction status information retrieved may include at least one of information on the current status of the transaction and the number of confirmations to date.

In step (960), the computer device (200) may provide the user with information about the status of the transaction identified by the transaction identifier using the retrieved transaction status information. For example, the computer device (200) may provide at least one of the current status of the transaction and the current confirmation number of the transaction. As a more specific example, the computer device (200) may display the overall status of the transaction to the user through a page provided in connection with the cryptocurrency service, but may display the current status of the transaction separately from the remaining statuses among the overall statuses. As another example, the computer device (200) may display the current confirmation number to the user through a page provided in connection with the cryptocurrency service. In this case, the computer device (200) may also display the current confirmation number in conjunction with the confirmation number required for approval of the deposit or withdrawal of the transaction.

Therefore, users can obtain information about where their transaction is in the overall transaction status, how many confirmations it has, and how many more confirmations are required.

In addition, the computer device (200) may provide information such as the reason for the delay, the delay time, and the average time when a delay occurs in each state according to an embodiment, thereby reducing users' anxiety about cryptocurrency transactions that take a relatively long time compared to the conclusion of general financial transactions.

FIG. 10 is a diagram illustrating an example of a user interface that provides transaction status information according to an embodiment of the present invention. FIG. 10 shows an example in which, in response to an inquiry request for a transaction identified by a transaction identifier "AAAAA", the entire states that a transaction can have are displayed, including a "transaction request" state, a "broadcast" state, a "pending" state, a "mining" state, a "confirmation" state, and a "complete" state, and then the current state of the transaction, which is a "mining" state, is distinguished and displayed. In addition, FIG. 10 shows information indicating that the current number of confirmations is 3 out of 6 confirmations for deposit approval. If the state of the transaction is a "broadcast" state, the current number of confirmations can be 0.

In a more specific embodiment, the first user (310) may access his/her cryptocurrency wallet provided by the cryptocurrency wallet platform (370) for cryptocurrency transactions, and may execute a desired cryptocurrency transaction in the accessed cryptocurrency wallet. For example, the user may request a transaction to transfer n cryptocurrencies to a third user (330). When the transaction request is transmitted, the first exchange (340) may display the “transaction request” status through a user interface accessible to the first user (310) to distinguish it from other statuses. In this case, the first user (310) may be able to recognize that his/her transaction is in the “transaction request” status through the user interface.

In order to confirm a transaction based on such a transaction request, the first exchange (340) can transmit information about the transaction to nodes of the blockchain network and can display the “transmission” status through the user interface to distinguish it from other statuses. In this case, the first user (310) can identify that his/her transaction is in the “transmission” status through the user interface.

In addition, if the first exchange (340) confirms that information about a transaction is being transmitted between nodes, but the transaction is confirmed to be not stored in a block, the user interface can display the "pending" status separately from other statuses. In this case, the first user (310) can identify that his or her transaction is in the "pending" status through the user interface.

At this time, if it is confirmed that at least one node has added a block containing information about the transaction to its blockchain, the first exchange (340) can display the “mining” status through the user interface to distinguish it from other statuses. In this case, the first user (310) can identify that his/her transaction is in the “mining” status through the user interface.

In addition, the first exchange (340) can display the "confirmed" status through the user interface to distinguish it from other statuses when the required number of confirmations for the transaction is satisfied. In this case, the first user (310) can identify that his/her transaction is in the "confirmed" status through the user interface.

Meanwhile, when the first exchange (340) confirms that the transaction is completed by processing the deposit approval at the third exchange (360) as the number of confirmations required for the transaction is satisfied, the first exchange (340) can display the "complete" status separately from other statuses through the user interface. In this case, the first user (310) can identify that his/her transaction is in the "complete" status through the user interface.

Although not shown, in another embodiment, the first exchange (340) may display the "Confirmed" status by omitting it and switching directly to the "Completed" status when the required number of confirmations for the transaction is satisfied.

Additionally, the first exchange (340) may provide the first user (310) with a notification of the current status of the transaction when there is a change in each status, even if the first user (310) does not access the user interface.

In this way, the first user (310) can check the current status of his/her transaction through the notification or user interface provided by the first exchange (340), thereby reducing anxiety about cryptocurrency transactions that take a relatively long time to conclude.

Meanwhile, although not shown, the exchange may provide detailed information related to each state. For example, if a user does not change from a certain state to the next state, he or she can click on the current state displayed on the user interface to view detailed information such as whether the transaction is delayed.

FIG. 11 is a flowchart illustrating an example of a delayed transaction monitoring method according to an embodiment of the present invention. The delayed transaction monitoring method according to the present embodiment may be performed by a computer device (200) implementing a cryptocurrency wallet platform (370). At this time, the processor (220) of the computer device (200) may be implemented to execute a control instruction according to a code of an operating system included in the memory (210) or a code of at least one computer program. Here, the processor (220) may control the computer device (200) to perform steps (1110 to 1130) included in the method of FIG. 11 according to a control instruction provided by a code stored in the computer device (200).

In step (1110), the computer device (200) may receive a transaction request from each of a plurality of transaction servers. Here, the plurality of transaction servers may correspond to a plurality of exchanges. For example, the computer device (200), as a cryptocurrency wallet platform (370) of FIG. 3, may receive a transaction request from a transaction server of a first exchange (340) and a transaction server of a second exchange (350). As described above, the computer device (200) may further receive an option related to whether to monitor delayed transactions together with the transaction request from each of the plurality of transaction servers. This option may include information about the period. According to one embodiment, the computer device (200) may receive an option that is applied collectively to transaction requests occurring in the corresponding transaction server from one or more of the transaction servers.

In step (1120), the computer device (200) can monitor whether a transaction corresponding to a transaction request is concluded. For example, the computer device (200) can periodically determine whether there is an incomplete transaction, which is a transaction that has not been concluded until a certain period of time has passed from the time when the transaction request is received. Here, the certain period of time may be a period preset in the computer device (200), but if information about the period is received through the above-described option, it may be set in response to the received period. For example, the computer device (200) can set the above-described certain period of time according to at least one of the type of transaction currency associated with the transaction request and the number of confirmations associated with the transaction request. As another example, the computer device (200) can set the above-described certain period of time according to a period requested by the transaction server. For example, the computer device (200) can receive 30 minutes as a set value for Bitcoin (BTC) from the first exchange (340) and check whether there is a transaction request that has not been completed for more than 30 minutes among the Bitcoin transaction requests requested from the first exchange (340).

In step (1130), if there is an incomplete transaction, the computer device (200) may transmit a notification about the incomplete transaction to the corresponding transaction server. This notification may include information about the delay in processing the incomplete transaction. For example, the computer device (200) may include information about the time elapsed since the corresponding transaction request was received in the notification and transmit it to the corresponding transaction server. In addition, the computer device (200) may provide information about the delay in processing the incomplete transaction by comparing it with other transaction requests that satisfy a certain time condition in relation to the time at which the corresponding transaction request was received. Here, satisfying a certain time condition may be within a certain range from the time (the first time) at which the corresponding transaction request was received (for example, a range from (the first time - n minutes) to the first time, a range from the first time to (the first time + m minutes), or a range from (the first time - n minutes) to (the first time + m minutes), etc.) or within a certain time interval (for example, a time interval of k minutes from every hour on the hour). At this time, the other transaction requests may be some of the transaction requests for the same type of transaction currency as the corresponding transaction request and may be received from different transaction servers. The computer device (200) may analyze some or all of the other transaction requests received within a certain time range or a certain time interval from the time at which the corresponding transaction request was received, and may calculate transaction statistics information including the ratio of completed transactions within the set time for the transaction request. The computer device (200) may include the calculated transaction statistics information in a notification and transmit it to the corresponding transaction server. For example, the computer device (200) may determine that one of the BTC transaction requests from the first exchange (340) has been incomplete for more than 30 minutes. At this time, the computer device (200) may calculate the average transaction processing time of the BTC transaction requests received from the first exchange (340) and/or the second exchange (350) during the same time period as the transaction in question, for which the transaction has been completed, and transmit this average transaction processing time to the transaction server of the first exchange (340).

Meanwhile, the incomplete notification may include notifications for all incomplete transaction requests related to the corresponding transaction server, or may include notifications for individual transactions. For example, when the computer device (200) provides an incomplete notification for one transaction to the transaction server, it may simultaneously transmit notifications for all incomplete transaction requests related to the corresponding transaction server. In this case, the number of notifications transmitted may increase for some incomplete transactions. As another example, the computer device (200) may transmit notifications only for transactions for which a set time has passed.

In addition, the computer device (200) can receive a set value for the number of repetitions of the incomplete notification from each transaction server, and can repeatedly provide notifications to the transaction server based on the set value. For example, the number of repetitions of the incomplete notification applied collectively to the exchange or applied to each case can be set to 1 or multiple values. The computer device (200) can repeatedly transmit an incomplete notification to the transaction server once or for a specific number of times at set intervals according to the set value, or repeatedly transmit an incomplete notification at set intervals until the transaction is completed. Through this, the transaction server can identify delays in the transactions for which it has requested a transaction, and can provide information about such delays to the user.

Fig. 12 is a diagram illustrating an example of providing delayed transaction information according to an embodiment of the present invention. Fig. 12 illustrates an example in which a first exchange (340) determines 30 minutes for a first cryptocurrency (BTC) and 10 minutes for a second cryptocurrency (ETH) as the time for delay recognition, and a second exchange (350) determines 1 hour for a first cryptocurrency (BTC) and 10 minutes for a second cryptocurrency (ETH) as the time for delay recognition.

At this time, the cryptocurrency wallet platform (370) can receive and store information for each set time as a set value, and monitor whether there is a delay in transactions for the first cryptocurrency and transactions for the second cryptocurrency at the first exchange (340) and the second exchange (350).

As a more specific example, it is assumed that a second user (320) requests a transaction A (for example, transaction request number 'RQ11001' of table (1210) of FIG. 12) for a first cryptocurrency through a second exchange (350). In this case, if transaction A is not completed within 1 hour from the time the transaction request for transaction A is received, the cryptocurrency wallet platform (370) may provide a notification of the delayed transaction to the second exchange (350). If the number of repeat notifications is set, the cryptocurrency wallet platform (370) may provide a notification repeatedly every hour until transaction A is completed. FIG. 12 shows an example in which the number of repeat notifications for transaction A corresponding to transaction request number RQ11001 is set to 5. In this case, if transaction A is not completed, the cryptocurrency wallet platform (370) may provide a notification repeatedly a total of 5 times every hour. Although not described, the cryptocurrency wallet platform (370) may additionally or alternatively manage the cumulative number of notifications, which is the number of times a notification is sent to the exchange for each transaction request number. Based on the cumulative number of notifications and the number of repeated notifications, the cryptocurrency wallet platform (370) may determine whether to send a notification to the exchange for the relevant case.

At this time, the cryptocurrency wallet platform (370) may provide information on the delay in processing of the incomplete transaction by comparing it with other transaction requests (comparison group) that satisfy a certain time condition. In Fig. 12, the comparison group average processing time may mean the average time taken for transactions belonging to the comparison group to be completed, and the comparison group processing rate may mean the ratio of completed transactions among the transactions belonging to the comparison group. When providing a notification about a delayed transaction, the cryptocurrency wallet platform (370) may provide additional comparative information such as the comparison group average processing time and/or the comparison group processing rate.

As previously explained, the cryptocurrency wallet platform (370) may transmit information about all pending transactions associated with a given exchange at once for a notification for one exchange, or may transmit notifications for corresponding transactions only when a set time has elapsed for each transaction.

According to an embodiment, the computer device (200) may further monitor information on the status of the transaction and provide it to the corresponding transaction server. This information on the status of the transaction may correspond to the transaction status information described above through FIG. 9. For example, the information on the status of the transaction may include information on the status before the transaction is completed and/or the current number of confirmations of the transaction.

In this way, according to embodiments of the present invention, in relation to transactions in cryptocurrency services, a user may specify the number of confirmations for a transaction request for withdrawal from an exchange or for a deposit. In addition, the exchange may provide the user with information on the transaction status related to the current cryptocurrency transaction deposit/withdrawal. In addition, the cryptocurrency wallet platform may monitor the delay in the transaction and provide the exchange with information on the delay in processing the transaction.

The systems or devices described above may be implemented as hardware components, or a combination of hardware components and software components. For example, the devices and components described in the embodiments may be implemented using one or more general-purpose computers or special-purpose computers, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing instructions and responding to them. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. In addition, the processing device may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing device is sometimes described as being used alone, but those skilled in the art will appreciate that the processing device may include multiple processing elements and/or multiple types of processing elements. For example, the processing device may include multiple processors, or a processor and a controller. Other processing configurations, such as parallel processors, are also possible.

The software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing device to perform a desired operation or may, independently or collectively, command the processing device. The software and/or data may be embodied in any type of machine, component, physical device, virtual equipment, computer storage medium, or device for interpretation by the processing device or for providing instructions or data to the processing device. The software may be distributed over network-connected computer systems and stored or executed in a distributed manner. The software and data may be stored on one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program commands, data files, data structures, etc. alone or in combination. The medium may be a means for continuously storing a computer-executable program or temporarily storing it for execution or downloading. In addition, the medium may be various recording means or storage means in the form of a single or multiple hardware combinations, and is not limited to a medium directly connected to a computer system, and may be distributed on a network. Examples of the medium may include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and ROMs, RAMs, flash memories, etc., configured to store program commands. In addition, examples of other media may include recording media or storage media managed by app stores that distribute applications or other sites, servers, etc. that supply or distribute various software. Examples of program instructions include machine language code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

Although the embodiments have been described above by way of limited examples and drawings, those skilled in the art can make various modifications and variations from the above description. For example, appropriate results can be achieved even if the described techniques are performed in a different order than the described method, and/or components of the described system, structure, device, circuit, etc. are combined or combined in a different form than the described method, or are replaced or substituted by other components or equivalents.

Therefore, other implementations, other embodiments, and equivalents to the claims are also included within the scope of the claims.

Claims (16)

A method for providing transaction status information performed by a computer device including at least one processor,
A step of periodically obtaining transaction progress information, which includes information about a state before the transaction settlement of a transaction identified by a transaction identifier is completed, by at least one processor, indicating the state of a currently ongoing transaction as one of a plurality of preset states;
A step of storing the transaction progress information in a database by associating the transaction identifier with the transaction progress information by at least one processor;
A step of receiving, by said at least one processor, a query request for said currently ongoing transaction identified by said transaction identifier from a user;
A step of retrieving transaction progress information of the requested transaction from the database by at least one processor; and
A step of providing a user with information about the status of the currently ongoing transaction identified by the transaction identifier by using the queried transaction progress information by at least one processor.
Including,
The above multiple states include at least two states among a state in which a transaction request from the user is received, a state in which information about the transaction is provided to nodes of the blockchain network for confirmation of the transaction identified by the transaction identifier, a state in which transaction information is transmitted but not stored as a block, a state in which transaction information is stored as a block, and a state in which the number of confirmations required for the transaction request is satisfied.
A method for providing transaction status information characterized by: delete In the first paragraph,
The steps for obtaining the above transaction progress information are:
A method for providing transaction status information, characterized by obtaining transaction progress information including the number of confirmations achieved to date for the above transaction. In the first paragraph,
The step of providing information on the status of the above transaction is:
A method for providing transaction status information, characterized in that it provides at least one of the current status of the transaction and the current confirmation number of the transaction. In the first paragraph,
The step of providing information on the status of the above transaction is:
A method for providing transaction status information, characterized in that the entire status of the transaction is displayed to the user through a page provided in connection with the cryptocurrency service, and the current status of the transaction is displayed separately from the remaining statuses among the entire statuses. In the first paragraph,
The step of providing information on the status of the above transaction is:
A method for providing transaction status information, characterized in that the current number of confirmations is displayed through a page provided in connection with a cryptocurrency service to the user. In Article 6,
The step of providing information on the status of the above transaction is:
A method for providing transaction status information, characterized in that the current confirmation number is displayed in conjunction with the number of confirmations required for approval of deposit or withdrawal of the transaction. In the first paragraph,
A step of providing a notification to the user about the changed transaction status by at least one processor.
A method of providing transaction status information including: In the first paragraph,
The step of obtaining the above transaction status information is:
A method for providing transaction status information, characterized by receiving the transaction status information from a cryptocurrency wallet platform that manages the wallet of the user. A computer program stored on a computer-readable recording medium for executing the method of any one of claims 1 to 9 on a computer device by being combined with a computer device. At least one processor implemented to execute instructions readable by a computer device
Including,
By at least one processor,
Periodically obtain transaction progress information indicating the status of a transaction currently in progress as one of multiple preset states, including information on the status before the transaction settlement of said transaction is completed for a transaction identified by a transaction identifier;
Store the above transaction progress information in a database by linking it to the above transaction identifier,
Receive a query request from a user for the currently ongoing transaction identified by the transaction identifier;
Retrieve transaction status information of the transaction for which the query was requested from the above database,
Using the transaction progress information retrieved above, information is provided to the user about the status of the currently in-progress transaction identified by the transaction identifier,
The above multiple states include at least two states among a state in which a transaction request from the user is received, a state in which information about the transaction is provided to nodes of the blockchain network for confirmation of the transaction identified by the transaction identifier, a state in which transaction information is transmitted but not stored as a block, a state in which transaction information is stored as a block, and a state in which the number of confirmations required for the transaction request is satisfied.
A computer device characterized by: delete In Article 11,
To obtain the above transaction progress information, by at least one processor,
Obtain transaction progress information including the number of confirmations achieved to date for the above transaction.
A computer device characterized by: In Article 11,
To provide information about the status of said transaction, by said at least one processor,
Providing at least one of the current status of said transaction and the current confirmation count of said transaction.
A computer device characterized by: In Article 11,
To provide information about the status of said transaction, by said at least one processor,
Displaying the overall status of the transaction to the user through a page provided in connection with the cryptocurrency service, but displaying the current status of the transaction separately from the remaining statuses among the overall statuses
A computer device characterized by: In Article 11,
To provide information about the status of said transaction, by said at least one processor,
Displaying the current number of confirmations and the number of confirmations required to approve the deposit or withdrawal of the transaction in conjunction with each other through a page provided to the above user in connection with the cryptocurrency service.
A computer device characterized by:

Images