KR102262618B1 - Method for high speed transaction processing on blockchain and apparatus for using the method - Google Patents

Abstract

The present invention relates to a high-speed transaction processing method on a block chain and an apparatus using such a method. The high-speed transaction processing method on the block chain includes the steps of the block chain platform receiving the requested transaction from the user device, the block chain platform determining whether the requested transaction can be processed based on the cache, and the block chain platform writing on the cache It may include transmitting a response transaction to the request transaction without access to the blockchain based on the received information.

Description

Method for high speed transaction processing on blockchain and apparatus for using the method

The present invention relates to a high-speed transaction processing method on a block chain and an apparatus using such a method. More specifically, it relates to a method and apparatus for high-speed processing of transactions that require processing without generating unnecessary load on the blockchain platform.

A blockchain may be a digital ledger in which transaction information that occurs in a public network or a private network is encrypted and shared between members of the corresponding network.

A copy of the transaction ledger is distributed to each network member, so that whenever a new transaction occurs, the authentication process for the transaction can proceed with the consent of the members.

Since transaction information based on the block chain cannot be arbitrarily changed, the reliability of the transaction increases and information tracking is easy. In particular, in the field of financial services, efforts are being made to increase work efficiency and establish a new service base by applying block chain technology.

Transparent transactions through a distributed ledger system can reduce security, supervision, and regulatory costs. Blockchain technology can be applied not only to the financial field, but also to logistics, distribution, and even government public administrative services.

In an existing public blockchain network such as Bitcoin, participating nodes can operate on a blockchain network with the same authority, but a private blockchain network or a permissioned blockchain network network), differential privileges are set for each node and can be operated within the blockchain.

If there are many attempts to access specific information recorded on the block chain, a load on the block chain may occur, and the access speed to information on the block chain may become slow due to the load.

Therefore, it is necessary to study a method to accurately obtain the information recorded on the block chain but not generate unnecessary load on the block chain.

An object of the present invention is to solve all of the above problems.

Another object of the present invention is to improve the transaction processing speed on the blockchain by reducing unnecessary access to the blockchain on the blockchain platform.

In addition, the present invention groups transactions on a blockchain platform to perform transaction verification based on the transaction group, and to prevent unnecessary transmission of transactions for managing information stored in the blockchain. .

A representative configuration of the present invention for achieving the above object is as follows.

According to an aspect of the present invention, a high-speed transaction processing method on a block chain includes the steps of: receiving a request transaction from a user device by a block chain platform; and determining whether the block chain platform can process the requested transaction based on a cache and sending, by the blockchain platform, a response transaction to the request transaction without access to the blockchain based on the information recorded in the cache.

According to another aspect of the present invention, the blockchain platform for high-speed transaction processing determines whether the request transaction can be processed based on the recorded information and the communication unit implemented to receive the requested transaction from the user device, and a cache implemented to transmit a response transaction to the request transaction without access to the blockchain based on recorded information.

According to the present invention, transaction processing speed on the blockchain can be improved by reducing unnecessary access to the blockchain on the blockchain platform.

In addition, according to the present invention, transaction verification is performed based on the transaction group by grouping the transactions on the block chain platform, and the transmission of the transaction for management of information stored in the block chain may not be made unnecessary.

1 is a conceptual diagram illustrating a high-performance blockchain platform according to an embodiment of the present invention.
2 is a conceptual diagram illustrating a high-performance blockchain platform according to an embodiment of the present invention.
3 is a conceptual diagram illustrating a high-performance blockchain platform according to an embodiment of the present invention.
4 is a conceptual diagram illustrating a high-performance blockchain platform according to an embodiment of the present invention.
5 is a conceptual diagram illustrating an access determination operation for a record on a block chain according to an embodiment of the present invention.
6 is a conceptual diagram illustrating an operation of a data streaming unit according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0023] Reference is made to the accompanying drawings, which show by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the present invention. It should be understood that the various embodiments of the present invention are different but need not be mutually exclusive. For example, certain shapes, structures, and characteristics described herein may be implemented with changes from one embodiment to another without departing from the spirit and scope of the present invention. In addition, it should be understood that the location or arrangement of individual components within each embodiment may be changed without departing from the spirit and scope of the present invention. Accordingly, the detailed description given below is not to be taken in a limiting sense, and the scope of the present invention should be taken to cover the scope of the claims and all equivalents thereto. In the drawings, like reference numerals refer to the same or similar elements throughout the various aspects.

Hereinafter, various preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings in order to enable those of ordinary skill in the art to easily practice the present invention.

Hereinafter, in an embodiment of the present invention, a high-performance blockchain platform for storing a distributed ledger in the form of a block chain and allowing a large number of transactions (or transactions) to be made simultaneously or in a short time is disclosed.

The high-performance blockchain platform according to an embodiment of the present invention can support a level of transaction volume and speed that can be transacted by millions or more at the same time by dramatically increasing the transaction speed while reducing the load on the blockchain.

Hereinafter, in an embodiment of the present invention, for convenience of explanation, a procedure for depositing and withdrawing money from a user account and confirming the user account is disclosed. However, the high-performance blockchain platform according to the embodiment of the present invention can be used below for the procedure of transmitting or receiving an object having a certain value, such as a digital security, on the user's wallet and confirming the user's wallet, and the rights of the present invention may be included in the scope.

That is, the user account may be used as a meaning including various online value storage means including an object with a value, and the amount may be used as a meaning including an object with a value.

1 is a conceptual diagram illustrating a high-performance blockchain platform according to an embodiment of the present invention.

In Figure 1, a high-performance blockchain platform that dramatically increases the transaction speed so that a large number of transactions can be made simultaneously in a short time while storing the distributed ledger in the form of a block chain is disclosed.

1 , a high-performance blockchain platform according to an embodiment of the present invention is a ledger application programming interface (API) 100, a cache 110, a ledger invoker 130, and data streaming. (data streaming) (or data streaming unit) 120, block chain (blockchain) 140, notifier (notifier) 150, ledger manager (ledger manager) (160) may include have.

The Ledger API 100 may be an interface for connecting a user device and a blockchain (or blockchain platform) 140 to provide a blockchain-based service. A user device may access information on the blockchain 140 via the Ledger API 100 . For example, the user may request deposit, withdrawal, transaction, etc. through the ledger API 100 and receive a result value for the request.

The cache 110 may be implemented to quickly provide data on the blockchain 140 without access to the blockchain 140 . The cache 110 may store information recorded on the block chain 140 (block chain record information), information that changes information recorded on the block chain 140 (block chain record change information), and the like.

The cache 110 may store data related to a transaction when a user generates a transaction for access on the block chain 140 . For example, a transaction that changes user account information, such as a transaction for depositing a certain amount of money into a user account (or wallet) (or a specific account) or withdrawing a certain amount from the user account, may occur through the user device. . Alternatively, a transaction that does not change user account information, such as a transaction for confirmation of a user account (or wallet), may be generated through the user device. In this case, deposit information/withdrawal information related to the user account, user account balance information, and the like may be recorded in the cache.

Based on the record of the cache 110 , the user can check information about the current user account without separate access. For example, if it is determined that there is no additional user account-related information change on the block chain 140 through checking the information stored in the cache 110, the cache 110 without access to the block chain 140 The recorded information may be used to transmit current user account information to the user device. That is, when a read request for data written on the blockchain 140 that is not simply changed from a user occurs, the data written on the cache 110 is immediately transferred without unnecessary access to the blockchain 140 . may be transmitted to the user device.

Through this method, unnecessary transactions/agreements for data recording on the block chain 140 can be reduced, and the data processing speed of the block chain 140 can be improved. The operation of the cache 110 will be described in more detail later.

The data streaming unit 120 may be implemented to sequentially transmit a transaction transmitted through the Ledger API 100 to the Ledger Invoker 130 without losing the transaction. A plurality of transactions generated from a plurality of user devices may include timestamps, and may be transmitted to the cache 110 and the data streaming unit 120 through the ledger API 100 . The timestamp may include information about the time when the transaction occurred. The data streaming unit 120 may be implemented as a queue. The plurality of transaction data accumulated in the data streaming unit 120 may be transmitted to the ledger invoker 130 .

For example, the Ledger Invoker 130 may scrape and organize a plurality of (eg, 100 to 1000) transactions stored in the data streaming unit 120 at least at once and transmit it to the blockchain 140 . According to an embodiment of the present invention, a plurality of transactions in the data streaming unit 120 may be grouped, and the grouped transaction group may be recognized and processed as one transaction. For example, a transaction group including 1000 transactions may be regarded as one transaction, and a transaction verification operation may be performed. Grouping of transactions will be described in detail later.

The ledger invoker 130 may be implemented to invoke the chaincode of the block chain 140 based on the transaction received from the data streaming unit 120 . Various types of chain codes may be executed by the ledger invoker 130 . The ledger invoker 130 executes the chaincode of the blockchain 140 , and a transaction (or transaction group) may be transmitted onto the blockchain 140 through the ledger invoker 130 . For example, a transaction is transmitted on the blockchain 140 through the Ledger Invoker 130, and the data (or data) included in the transaction through the mining of the block is on the block connected to the blockchain 140. can be recorded.

The notifier 150 may recognize a change occurring on the block chain 140 and transmit change information on the block chain 140 to another component (or module). Also, the notifier 150 may play a role in checking the data consistency between the block chain 140 and the cache 110 and automatically recovering the data consistency when the consistency is damaged. For example, the notifier 150 may 1) when a transaction related to deposit/withdrawal to a user account is recorded on the blockchain 140, 2) a transaction related to a settlement request by the ledger manager 160, which will be described later. Information about changes that have occurred on the blockchain 140, such as when (account cleanup request transaction) is recorded on the blockchain 140, is stored on a high-performance blockchain platform such as the cache 110 and the ledger manager 160. It can be passed to the component.

The ledger manager 160 may be implemented for managing/updating data stored on the blockchain 140 . For example, the ledger manager 160 performs a data update request transaction requesting update of the user account balance information based on the user's account balance information and account change information recorded on the block chain 140 (for example, , account cleanup request transaction) may be transmitted on the block chain 140 . When an account reorganization request transaction is transmitted on the block chain 140, the user's account information is updated to the latest based on the user's account information and account change information recorded on the block chain 140, and the block chain 140 ) may be performed. A detailed operation of the ledger manager 160 will be described later.

2 is a conceptual diagram illustrating a high-performance blockchain platform according to an embodiment of the present invention.

In Fig. 2, a flow of data write operation on a high-performance blockchain platform is disclosed. In particular, a data write flow related to writing (or writing) data that changes data on a blockchain is disclosed. A transaction that changes data on the blockchain can be expressed in terms of a data change request transaction.

2, in the embodiment of the present invention, for convenience of explanation, user account information (or user account information, user wallet information) will be described as an example, but reading, writing, The present invention may be applied to a change alarm, and such an embodiment may also be included in the scope of the present invention.

It is assumed that 10,000 won is currently deposited in the user account, and information about the user account (10,000 won) is recorded on the block chain 240 . Thereafter, it is assumed that the user 1) requests a withdrawal of 3,000 won, and 2) requests a deposit of 5,000 won.

In this case, a first transaction (3000 won withdrawal request) (first timestamp) may be generated, and thereafter, a second transaction (5000 won deposit request) (second timestamp) may be generated.

In this case, the first transaction (3000 won withdrawal request) (first timestamp) and the second transaction (5000 won deposit request) (second timestamp) are stored in the cache 210, and the data streaming unit simultaneously or sequentially It may also be transmitted and stored in 220 .

The data streaming unit 220 may store a first transaction (3,000 won withdrawal request) (first timestamp) and a second transaction (5,000 won deposit request) (second timestamp) in chronological order.

Thereafter, the Ledger Invoker 230 receives the first transaction (3000 won withdrawal request) (first timestamp) and the second transaction (5000 won deposit request) (second timestamp) stored in the data streaming unit 220 . can do. The first transaction (3000 won withdrawal request) (first timestamp) and the second transaction (5000 won deposit request) (second timestamp) may be stored on a block on the blockchain 240 .

On the block chain 240, 1) user account balance information (10,000 won), 2) user account withdrawal information (3,000 won), and 3) user account deposit information (5000 won) may be recorded.

According to an embodiment of the present invention, when the account cleanup request transaction of the ledger manager 260 is not transmitted, the user account balance information may not be updated. An identifier (or mark) indicating non-reflected information may be added to 2) user account withdrawal information (3,000 won) and 3) user account deposit information (5,000 won), which is information that changes user account balance information.

Thereafter, when the account reorganization request transaction is transmitted by the ledger manager 260, the user account balance information is updated to 12,000 won, and 2) user account withdrawal information (3,000 won), which is information that changes the user account balance information, 3 ) for the user account transfer information (5,000 won), an identifier (mark) indicating that it is reflected information may be displayed.

That is, it may be checked whether information that changes the user account balance is reflected in the user account balance by the account reorganization request transaction through a separate identifier.

3 is a conceptual diagram illustrating a high-performance blockchain platform according to an embodiment of the present invention.

In FIG. 3, a data change alarm flow notifying a change in data on the block chain is started.

Referring to FIG. 3 , a data change alarm flow may be generated when a data change occurs on the block chain 340 . For example, in the data write flow, the second transaction (5000 KRW deposit request) (2nd timestamp) and the first transaction (3000 KRW withdrawal request) (1st timestamp) and the second transaction (5000 KRW deposit request) ( When the deposit request data and the withdrawal request data are recorded on the block chain 340 due to the second timestamp), a change may occur on the block chain.

In this case, the notifier 350 recognizes a change on the block chain, and transmits information (or information related to the change) informing the change on the block chain to components on the high-performance block chain platform such as the cache, the ledger manager 360, etc. have. Information notifying changes on the blockchain 340 (or information related to changes) may be expressed in terms of blockchain change alarm information.

For example, the ledger manager 360 may transmit an account cleanup request transaction onto the blockchain 340 . In this case, the user account may be cleared to the final value. Specifically, 1) user account balance information (10000 won), 2) user account withdrawal information (3,000 won), 3) user account deposit information (5000 won) stored on the block chain 340 are all organized, and the blockchain ( 340), the user account balance information may be updated to 12,000 won and stored.

Likewise, changes due to the account cleanup request transaction sent by the ledger manager 360 may be notified by the notifier 350 to the ledger manager 360 and the cache 310 .

The ledger manager 360 may receive change information from the notifier 350 , and transmit an account cleanup request transaction back to the block chain 340 . The ledger manager 360 transmits an account cleanup request transaction, receives block chain change alarm information due to the account cleanup request transaction from the notifier 350, and sends an account cleanup request transaction again. may not be continuously transmitted. Accordingly, unnecessary transmission of account cleanup request transactions on the block chain can be prevented, and as a result, the overload on the block chain 340 can be reduced, and the processing speed of the block chain 340 can be improved.

Also, according to an embodiment of the present invention, a cycle for the account cleanup request transaction is set, and the ledger manager 360 may transmit the account cleanup request transaction at every set cycle.

The cache 310 may receive block chain change alarm information from the notifier 350, and depending on whether the block chain change alarm information is received, a response to a transaction generated from the user device based on the information recorded in the cache It is possible to determine whether to provide the information in the block chain 340 or not based on the information recorded on the block chain 340 . Such a cache 310-based response method will be described later.

4 is a conceptual diagram illustrating a high-performance blockchain platform according to an embodiment of the present invention.

In FIG. 4, a data read flow related to data read on a block chain is disclosed. Transactions that do not change data on the blockchain, such as reading data, can be expressed in terms of data no-change request transactions.

Referring to FIG. 4 , for example, when a transaction requesting confirmation of the account balance from the user device (user account balance confirmation transaction) occurs, the user account-related information is primarily checked through the cache 410 . After this is performed, it may be determined whether the user account balance information in the cache 410 can be directly provided to the user. Thereafter, when the user account balance information on the cache 410 can be directly provided to the user, the user account balance information on the cache 410 can be provided to the user device without access to the block chain 440 . Conversely, when the user account balance information in the cache 410 cannot be provided to the user immediately, the user account balance information may be provided to the user device through access to the block chain.

Determination of whether the user account balance information in the cache 410 can be directly provided to the user will be described later.

If it is possible to provide user account balance information through the cache 410 , the user account balance information may be directly provided without accessing the block chain 440 . Conversely, if it is not possible to provide user account balance information through the cache 410, access to the block chain 440 and user account balance related information (user account balance information) among the data recorded on the block chain 440 , user account deposit information, user account withdrawal information, etc.) may organize the user account balance and provide it to the user.

For example, in the above example, the user account balance information (user account balance information (10000 won), user account withdrawal information (3,000 won), user account deposit information (5000 won)) stored on the block chain is collected in the above example, Based on the collected information, the user account balance may be calculated (10,000 won - 3,000 won + 5000 won = 12,000 won) and provided to the user device.

If the transaction requesting account cleanup of the ledger manager 460 is not transmitted, the user account balance cleared by the user's request may not be stored on the block chain 440 . That is, only by the account cleanup request transaction of the ledger manager 460, each of the plurality of user account balances of the plurality of users is cleaned up, and finally the updated information on the plurality of user account balances of the plurality of users is stored in the blockchain It can be written on 440 .

Alternatively, according to an embodiment of the present invention, when an account balance check transaction is generated by the user device even when the account cleanup request transaction of the ledger manager 460 is not transmitted, separate account cleanup for the user account balance of the corresponding user is performed, the user account balance information is updated, and an identifier (mark) indicating that the user account withdrawal information and the user account deposit information are reflected information may be displayed. That is, when an individual account balance confirmation transaction for a specific user occurs, separate account cleanup is performed only on the user account balance for the corresponding user and may be recorded on the block chain as user account balance information.

5 is a conceptual diagram illustrating an access determination operation for a record on a block chain according to an embodiment of the present invention.

In FIG. 5, when a data read operation (or a transaction related to data read) occurs by the user device, a method for providing data to the user device only by accessing the cache without access to the block chain is disclosed.

Referring to FIG. 5, based on user transaction information recorded in the cache and/or block chain change alarm information received from the notifier, it is determined whether to provide data to the user device only by accessing the cache without access to the block chain. can be decided.

According to an embodiment of the present invention, the blockchain platform may receive the request transaction from the user device, and the blockchain platform may determine whether to process the request transaction based on the cache. The request transaction may be a transaction (eg, account balance confirmation transaction, user account deposit/withdrawal related transaction, etc.) for reading/writing data on the aforementioned block chain.

If possible, the blockchain platform may send a response transaction to the request transaction without access to the blockchain based on the information recorded in the cache. If the blockchain platform is unable to process the request transaction based on the cache, it can transmit the request transaction to the data streaming unit for transmission on the blockchain.

The cache stores information related to the request transaction, and the request transaction may include a time stamp. The data streaming unit stores a request transaction different from the request transaction, but the other request transaction may include a transaction before receiving the request transaction from the user device or another user device and transmitting it on the block chain. As described above, the blockchain platform can transmit the request transaction and other request transaction on the blockchain based on the Ledger Invoker's invoking to the blockchain.

Whether the request transaction can be processed based on the cache may be determined based on the characteristics of the request transaction and the characteristics of the previous request transaction previously transmitted on the cache in relation to the user device. The characteristics of the request transaction and the previous request transaction may be one of a data no change request transaction 550 and a data change request transaction 570 .

Specifically, the transaction sent from the user device is a data non-change request transaction that does not change data on the block chain (eg, the account confirmation request transaction 500), and after the latest update of the data to be provided, the data on the block chain is changed If only the data no change request transaction 550 that is not requested is recorded on the cache 520 , the data stored in the cache 520 may be transmitted as the response transaction 580 without access to the block chain 540 .

Conversely, the transaction sent from the user device is a data no change request transaction that does not change the data on the blockchain 540 (eg, the account confirmation request transaction 500), and after the latest update of the data to be provided, the blockchain ( When at least one data change request transaction 570 that changes data on 540 is recorded on cache 520 , based on the data written on blockchain 540 through access onto blockchain 540 . A response transaction 580 may be transmitted.

For example, it may be determined whether to provide user account balance information directly from the cache 520 or based on data recorded on the block chain 540 . For example, when user account balance information that changes user account balance information is not stored after the user account balance information is recorded in the cache 520 , information related to a transaction related to user account withdrawal and/or user account deposit is not stored (withdrawal from user account) information and/or user account deposit information has not been generated), the user account balance information stored in the cache 520 may be determined as the latest updated account information. In this state, when the account verification request transaction 500 is generated from the user device, the user account balance information stored in the cache can be provided without the need to access the block chain 540 to read the data.

Conversely, after the user account balance information is recorded on the cache 520 , when user account balance change information such as user account withdrawal information and/or user account deposit information that changes the user account balance information occurs (or on the cache) information related to transactions related to user account withdrawals and/or user account deposits that change user account balance information) may be assumed. In this case, the user account balance information may be confirmed on the block chain 540 .

The user account balance related information recorded on the block chain 540 is extracted, and the information recorded on the block chain 540 is the user account balance information ( Alternatively, in the case of data no change information 590), the user account balance information recorded on the block chain 540 may be provided to the user. Conversely, when the information recorded on the block chain 540 after transmission of a data update transaction such as an account cleanup request transaction is user account balance change information (or data change information 595), the most recent user account balance information and its The account balance change information generated thereafter may be searched for, and a separate account arrangement may be performed for the corresponding user and provided to the user device. The extracted user account balance-related information on the blockchain 540 may be stored again in the cache. That is, whether a data change request transaction occurred in relation to the provision request data (or whether the data change information 590 was stored in relation to the provision request data) or a data change request transaction occurred (or provided) even on the block chain 540 By determining whether data change information 595 is stored in relation to the requested data), a response transaction based on the data on the block chain may be generated.

Through this method, when the user can obtain information only by accessing the cache 520 without access to the block chain 540, the occurrence of unnecessary transactions on the block chain 540 can be reduced, and the user can Accurately obtain the desired information faster.

In other words, after the last update of the data on the blockchain 540 , when only the data no change request transaction 550 that does not change the data is recorded on the cache 520 , the cache 520 without access on the blockchain 540 . ), only a response transaction to a request transaction related to reading data can be sent to the user device.

Conversely, if a data change request transaction 570 that changes at least one data after the last update of data on the blockchain 540 is recorded on the cache 520 , the data through access on the blockchain 540 is A response transaction to the request transaction related to the read may be transmitted to the user device.

6 is a conceptual diagram illustrating an operation of a data streaming unit according to an embodiment of the present invention.

In FIG. 6, an operation of grouping transactions in the data streaming unit is started.

Referring to FIG. 6 , the data streaming unit 600 may create a transaction group 650 for grouping transactions to be processed. The verification of the transaction group 650 may be performed on a group basis, thereby increasing the processing speed on the block chain 660 .

Transactions generated from a plurality of user devices may include timestamps, and the plurality of transactions may be sequentially stored in the data streaming unit 600 based on the timestamps.

According to an embodiment of the present invention, transactions may be individually verified and recorded on the blockchain 660 based on the invoking of the Ledger Invoker 620, but are grouped and verified in units of transaction groups and verified by the Ledger Invoker ( It may be recorded on the blockchain 660 based on the invoking (or calling) of 620 .

A transaction group 650 including a plurality of transactions stored in the data streaming unit 600 may be determined in various ways. First, when a transaction of the ledger invoker 620 is invoked, all transactions existing in the data streaming unit 600 at the time of invoking may be grouped into one transaction group 650 . In this case, a subgroup may be formed separately for each related account. For example, when a transaction is made between user A, user B, and user C, the transaction related to user A, user B, and user C may be separately set as a sub-transaction group.

Alternatively, according to an embodiment of the present invention, a transaction group 650 may be formed according to the characteristics of a transaction and a verification procedure may be performed. For example, an operation performed based on a transaction, such as a transaction group for reading simple data that does not change data on the block chain 660 (hereinafter, a data no-change transaction group), and a transaction group that generates data change on the block chain Accordingly, a transaction group (data change transaction group) may be formed. Different verification procedures may be performed for the data immutable transaction group and the data change transaction group.

The data change transaction group and the data change transaction group perform the same basic verification, but for the data change transaction group, the verification of whether data can be changed may be additionally performed.

For example, the data change transaction group may be divided into a data change (deposit) transaction group that is a data change for deposit and a data change (withdraw) transaction group that is a data change (withdrawal) transaction group that is a data change for withdrawal.

In the case of a data change (deposit) transaction group, it may be necessary to verify whether a deposit is possible in the depositing user account. In the case of a data change (withdrawal) transaction group that is a data change, it may be necessary to verify whether a withdrawal is possible from the user account making the withdrawal.

According to an embodiment of the present invention, a plurality of transactions may form a transaction group 650 according to the characteristics of a transaction, and may be recorded on a block by performing a separate verification procedure for each transaction group 650 . When a plurality of transactions included in the transaction group 650 are recorded on the block chain, the transaction group 650 is not considered and may be stored based on a timestamp. Specifically, when recording on the block chain, the transaction group 650 is released, and the timestamp of the transaction is considered so that a plurality of transactions can be recorded. Alternatively, identification information for the transaction group 650 that is recorded on a block in consideration of the transaction group 650 or grouped during verification may be displayed in individual transactions.

The embodiments according to the present invention described above may be implemented in the form of program instructions that can be executed through various computer components and recorded in a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the computer-readable recording medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software. Examples of computer-readable recording media include hard disks, magnetic media such as floppy disks and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and magneto-optical media such as floppy disks. medium), and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. A hardware device may be converted into one or more software modules to perform processing in accordance with the present invention, and vice versa.

In the above, the present invention has been described with reference to specific matters such as specific components and limited embodiments and drawings, but these are provided to help a more general understanding of the present invention, and the present invention is not limited to the above embodiments, and the present invention is not limited to the present invention. Those of ordinary skill in the art to which the invention pertains can make various modifications and changes from these descriptions.

Therefore, the spirit of the present invention should not be limited to the above-described embodiments, and the scope of the spirit of the present invention is not limited to the scope of the scope of the present invention. will be said to belong to

Claims (8)

The high-speed transaction processing method on the blockchain is:
receiving, by the blockchain platform, the requested transaction from the user device;
determining, by the blockchain platform, whether to process the request transaction based on the cache; and
Transmitting, by the blockchain platform, a response transaction to the request transaction without access to the blockchain based on the information recorded in the cache,
Whether the request transaction can be processed based on the cache is determined based on a transaction characteristic of the request transaction and a transaction characteristic of a previous request transaction previously transmitted on the cache in connection with the user device;
The transaction characteristic is a data no change request transaction or a data change request transaction,
The data change request transaction includes an account confirmation request transaction,
The method of claim 1, wherein the data change request transaction includes a user account withdrawal transaction and/or a transaction related to a user account deposit. According to claim 1,
When the block chain platform is unable to process the requested transaction based on the cache, the method further comprising: transmitting the requested transaction to a data streaming unit for transmission of the requested transaction on the block chain;
The cache stores information related to the request transaction,
the request transaction includes a timestamp;
The data streaming unit stores a request transaction different from the request transaction,
The method of claim 1, wherein the other request transaction includes a transaction received prior to receipt of the request transaction from the user device or another user device and transmitted on the blockchain. 3. The method of claim 2,
The method further comprising the step of, by the blockchain platform, storing the request transaction and the other requested transaction on the blockchain based on the invoking of the ledger invoker to the blockchain. 4. The method of claim 3,
each of the request transaction and the other request transaction is included in a transaction group for storage on the blockchain;
wherein the transaction group includes a data no-change transaction group including the data no-change transaction and a data change transaction group including the data change transaction;
The blockchain platform performs verification on each of the data non-change transaction group and the data change transaction group, and performs additional verification on whether data change is possible for the data change transaction group,
The block chain platform records the plurality of transactions included in the transaction group in consideration of the timestamps of each of the plurality of transactions when recording on the block chain. A blockchain platform for high-speed transaction processing,
a communication unit configured to receive a request transaction from the user device; and
and a cache implemented to determine whether processing of the request transaction determined based on recorded information is possible, and to transmit a response transaction to the request transaction without access to the block chain based on the recorded information. and,
Whether the request transaction can be processed based on the cache is determined based on a transaction characteristic of the request transaction and a transaction characteristic of a previous request transaction previously transmitted on the cache in connection with the user device;
The transaction characteristic is a data no change request transaction or a data change request transaction,
The data change request transaction includes an account confirmation request transaction,
The data change request transaction includes a user account withdrawal transaction and/or a transaction related to user account deposit. 6. The method of claim 5,
When processing of the request transaction is impossible based on the cache, further comprising a data streaming unit configured to receive the request transaction for transmission on the block chain of the request transaction,
The cache stores information related to the request transaction,
the request transaction includes a timestamp;
The data streaming unit stores a request transaction different from the request transaction,
and the other request transaction includes a transaction received prior to receipt of the request transaction from the user device or another user device and transmitted on the blockchain. 7. The method of claim 6,
The blockchain platform according to claim 1, further comprising a ledger invoker configured to store the request transaction and the other requested transaction on the block chain based on the invoking for the block chain. 8. The method of claim 7,
each of the request transaction and the other request transaction is included in a transaction group for storage on the blockchain;
wherein the transaction group includes a data no-change transaction group including the data no-change transaction and a data change transaction group including the data change transaction;
The blockchain platform performs verification on each of the data non-change transaction group and the data change transaction group, and performs additional verification on whether data change is possible for the data change transaction group,
The block chain platform records a plurality of transactions included in the transaction group in consideration of the timestamps of each of the plurality of transactions when recording on the block chain.

Images