KR102324155B1 - Method and apparatus for autonomous guarantee verification for p2p loan service based on blockchain - Google Patents

Abstract

The self-assurance verification method performed by the block chain-based service device according to an embodiment of the present invention is information including the creation of a user's block chain account, generation of an authentication 1 key by encrypting the user's unique information, and the authentication 1 key generating an encrypted TxID and storing it in an off-chain DB; storing data including TxID encrypted with an asymmetric key of OPM (operator master), which is a block chain account managed by the device, in DB and uploading it to on-chain; And when a request for a predetermined operation is received from the user, the authentication 1 key is regenerated after the request time, the Key Value stored in the DB is searched based on the Key Value uploaded to the on-chain, and the retrieved Key Value is an asymmetric key It may include the step of determining the execution of the request based on the forgery determination of comparing the authentication 1 key obtained by decrypting the corresponding key of the regenerated authentication 1 key.

Description

Blockchain-based P2P Loan Service Autonomous Guarantee Verification Method and Apparatus

The present invention determines whether or not to perform an operation requested by a legitimate user through a user authentication key based on block chain technology, and proves that the user's request has been completed, and a token that can transfer the right generated when the request is completed. It relates to a technology issued through a user authentication key.

P2P lending refers to an individual signing a loan contract through an online platform without going through a financial institution. The P2P financial platform industry, which relays to receive interest payments, has recently grown significantly.

The existing financial loan is a form of lending to borrowers while the bank manages the amount of money paid from depositors. There is no direct correlation between depositors and borrowers, and the bank bears the risk of not being able to recover the loan. In contrast, the P2P financial platform industry recruits investors and lends money to borrowers in need of funds in the form of investment. Often there are no institutions.

Accordingly, in the P2P financial platform, the rights/liabilities arising from loans and the accompanying risks all directly occur to the investors/borrowers, It is very important to decide whether If the forgery or falsification of the user's request is not accurately identified and the money of investors and borrowers is financed, financial damage may occur to legitimate users.

In fields that require authentication and forgery verification, attempts to apply blockchain technology are increasing recently. However, from the point of view of user convenience, it is important for users to be able to automatically authenticate and perform forgery judgment within the online platform without needing to know the concept of blockchain.

This document intends to propose a technology in which the server and smart contract automatically perform authentication and falsification judgment functions without the user's knowledge of the blockchain technology while using blockchain technology for authentication and forgery verification.

The problem to be solved in the embodiment of the present invention is to implement a technology that can provide users with the advantages of a blockchain that performs authentication and prevents forgery while preventing users from using a blockchain wallet directly.

In addition, it is to relay the credentials and authentication of all transactions occurring in the P2P loan, and to implement a technology to transfer the rights generated when the request is completed while proving that the execution of the user's request is completed.

However, the technical problems to be achieved by the embodiments of the present invention are not limited to the above-mentioned problems, and various technical problems can be derived from the contents to be described below within the scope obvious to those skilled in the art.

The self-assurance verification method performed by the blockchain-based service device according to an embodiment creates a user's block chain account, generates an authentication 1 key encrypted with the user's unique information, and information including the authentication 1 key generating an encrypted TxID and storing it in an off-chain DB; storing the data including the TxID encrypted with an asymmetric key of an operator master (OPM), which is a block chain account managed by the device, in the DB and uploading it to the on-chain; and when a request for a predetermined operation is received from the user, the authentication 1 key is regenerated after the request time, the key value stored in the DB is searched based on the key value uploaded to the on-chain, and the retrieved It may include the step of determining the execution of the request based on a forgery determination that compares the regenerated authentication 1 key with the authentication 1 key obtained by decrypting the key value with the corresponding key of the asymmetric key.

In addition, the user's unique information includes a TokenHolderKey encrypted based on the SHA algorithm by using the user's first login time information as a secret key for a user ID, a user block chain account address, a public key, and a user virtual account number, [ TokenHolderKey=SHA{SecretKey(firstLoginTimeStamp)(UserID, AccountAddress, PublicKey, VirtualBankNum)}], the authentication 1 key is a TokenHolderHashKey generated by encrypting the user ID, the TokenHolderKey, and the time information at which the TokenHolderKey is generated together based on the SHA algorithm may include. {TokenHolderHashKey=Hash(UserID, TokenHolderKey, TokenHolderHashKey Creation Year Month Day Time Minute Second)}

In addition, the user includes an investor and a borrower using the P2P loan service, the request includes a loan request of the borrower and a request to execute an investment of the investor for the loan, and the determining of the execution includes the above when receiving a loan request from the borrower, regenerating the authentication 1 key of the borrower after the loan request time, based on a predetermined loan examination for the borrower, and generating loan information for the borrower; When receiving the investor's investment request for the loan request, the investor's authentication 1 key is regenerated after the investment request time, and stored in the DB based on the investor's Key Value uploaded to the on-chain The investor's authentication 1 key obtained by searching the investor's Key Value and decrypting the OPM's asymmetric key is compared with the regenerated investor's authentication 1 key to determine forgery and forgery to determine whether the investor's investment contract for the loan information to do; and when the investment contract according to the loan request is established, the borrower's Key Value stored in the off-chain DB is retrieved based on the borrower's Key Value uploaded to the on-chain, and the obtained by decrypting the OPM's asymmetric key By comparing the borrower's authentication 1 key with the regenerated borrower's authentication 1 key to determine forgery, borrower information to be recorded on-chain in relation to the loan request and on-chain in relation to the investment request It may include generating investor information.

In addition, the generating of the investor information may be set to be executed only when the amount preset in the loan request is all raised by the investor's investment request.

In addition, in one embodiment, after the step of determining the execution of the request, the token issuance that proves the user's status as the request is executed is performed to a smart contract that manages the execution of the request through the OPM account creating a transaction and creating an OP (operator) account, which is a block chain account with permission to access the DB; transmitting the authentication 1 key obtained by decrypting the key value uploaded to the on-chain through the OPM account to the OP account; and determining, by the OP account, to generate the transaction based on a forgery determination that allows the OP account to compare the authentication 1 key received from the OPM account with the authentication 1 key extracted from the TxID stored in the DB.

In one embodiment, after the step of determining the transaction generation, the OPM account receives the authentication 1 key again from the OP account, and compares the re-transmitted authentication 1 key with the regenerated authentication 1 key. determining the validity of the authentication 1 key possessed by the OP account; if the authentication 1 key is valid, sending, by the OPM account, a token issuance transaction of a predetermined amount to the smart contract so that the token is paid to the OP account; and when the OPM account determines whether the number of tokens received by the OP account matches the predetermined quantity, and records the fact that the token issuance by the OP account in a block.

In one embodiment, after the step of recording the fact about issuance of the token in a block, based on the predetermined information held by the OP account, an authentication 2 key used for transmission of the token is generated and transmitted to the first smart contract to do; When it is determined that the execution of the request has been completed, a contract is set so that an authentication 2 key used for transmission of the token is generated based on the predetermined information stored by the DB, and the first smart contract compares the authentication 2 key transmitting the authentication 2 key generated from the DB to the second smart contract; and when receiving information that the authentication 2 key is the same as a result of comparing the second smart contract, storing the authentication 2 key in the DB and providing a token to the user, wherein the token is the user It can be used to prove that the execution of the request has been completed.

In addition, the predetermined information held by the OP account and the predetermined information stored in the DB are, respectively, the user's public key, the identification information of the token, the user's authentication 1 key, and the predetermined information is the authentication 2 It includes time information when it is input to the key generation function, and the authentication 2 key may be generated by encrypting the predetermined information with the secret key of the OP account.

In addition, in one embodiment, after the step of generating investor information to be recorded in the on-chain, a token that proves the status of borrowers and investors according to the investment contract to a smart contract that manages the execution of the request through the OPM account creating a transaction for issuing issuance and creating an OP (operator) account, which is a block chain account with permission to access the DB; Transmits the investor's authentication 1 key obtained by decrypting the investor's Key Value uploaded to the on-chain through the OPM account to the OP account, and the OP account receives the investor's authentication 1 transmitted from the OPM account a first forgery determination step of comparing the key and the authentication 1 key extracted from the investor's TxID stored in the DB; The borrower's authentication 1 key obtained by decrypting the borrower's Key Value uploaded to the on-chain through the OPM account is transmitted to the OP account, and the OP account receives the borrower's authentication 1 from the OPM account a second forgery determination step of comparing the key and the authentication 1 key extracted from the borrower's TxID stored in the DB; and determining the transaction generation based on the first and second forgery determinations.

In addition, in one embodiment, after the step of determining the transaction generation, the OPM account receives the investor's authentication 1 key from the OP account again, and the re-transmitted investor's authentication 1 key is the regenerated authentication of the investor judging the validity of the investor's authentication 1 key held by the OP account by comparison with the 1 key; if the investor's authentication 1 key is valid, sending, by the OPM account, a token issuance transaction of a predetermined amount to the smart contract so that a first token is paid to the OP account; determining, by the OPM account, whether the number of first tokens received by the OP account matches the predetermined quantity, and recording the fact that the first token issuance by the OP account in a block; The OPM account receives the borrower's authentication 1 key from the OP account again, compares the re-transmitted borrower's authentication 1 key with the borrower's regenerated authentication 1 key, determining the validity of the authentication 1 key; if the borrower's authentication 1 key is valid, sending, by the OPM account, a token issuance transaction of a predetermined amount to the smart contract so that a second token is paid to the OP account; and if the OPM account determines whether the number of second tokens received by the OP account matches the predetermined quantity, recording the fact that the OP account is issuing the second token in a block can do.

In addition, in one embodiment, after the step of recording the fact about the first and second token issuance in a block, for each of the investor and the borrower, the first and second tokens based on predetermined information held by the OP account 2 generating an authentication 2 key used for transmission of the token and sending it to the first smart contract; When it is determined that the execution of the request is completed, an authentication 2 key used for transmission of the first and second tokens is generated based on the predetermined information stored by the DB, and the first smart contract generates the authentication 2 key transmitting the authentication 2 key generated from the DB to the second smart contract with a set protocol for comparison; and if information is received that the authentication 2 key is the same as a result of the comparison of the second smart contract, storing the authentication 2 key in the DB, and providing the first and second tokens to the investor and borrower, respectively. Further comprising, the first token may be used for the purpose of proving the principal and interest receivables of the investor, and the second token may be used for the purpose of proving the loan debt of the borrower.

In addition, the authentication 1 key may be generated by encrypting data including the user's account information by using the time information of the first login by the user as a secret key.

In addition, the Key Value may be generated by encrypting the TxID with an index number specifying the authentication 1 key with a private key or a public key of the OPM.

A block chain-based service device according to an embodiment includes one or more memories for storing instructions to perform a predetermined operation; and one or more processors configured to be operatively connected to the one or more memories to execute the instructions, wherein the one or more processors create a user's block chain account and generate an authentication 1 key encrypted with the user's unique information , and generating an encrypted TxID of information including the authentication 1 key and storing it in an off-chain DB; an operation of encrypting the data including the TxID with an asymmetric key of an operator master (OPM), which is a block chain account managed by the device, in the DB and uploading it to the DB and on-chain; and when a request for a predetermined operation is received from the user, the authentication 1 key is regenerated after the request time, the key value stored in the DB is searched based on the key value uploaded to the on-chain, and the retrieved An operation for determining the execution of the request may be performed based on a forgery determination of comparing the regenerated authentication 1 key with the authentication 1 key obtained by decrypting the key value with the corresponding key of the asymmetric key.

According to an embodiment of the present invention, in performing P2P lending, the block chain-based service device directly manages the user's block chain wallet, so that the user does not use the block chain wallet directly to solve the inconvenience and , it has the effect of providing the advantages of blockchain by relaying the credentials and authentication of all transactions.

In addition, by issuing a transferable user-specific token while proving that the user's request has been completed, the user's rights or debts can be transferred while proving the principal and interest receivables or debt status according to the P2P loan.

Furthermore, it is possible to prove the rights of various assets in the real world with various tokenized digital assets, and provide a reliable and automated notarization function for the relevant participant's credentials, the registration of various assets, and the transaction proof.

In addition, various effects directly or indirectly identified through this document may be provided.

1 is a block diagram illustrating an operating environment of a P2P loan system and a block chain network including a block chain-based P2P loan service autonomous guarantee verification device, an investor terminal, and a borrower terminal according to an embodiment.
2 is a block diagram of a block chain-based P2P loan service autonomous guarantee verification apparatus according to an embodiment.
3 is a conceptual diagram of a process in which a P2P service is performed from an investor's point of view according to an embodiment.
4 is a conceptual diagram of a process in which a P2P service is performed from a borrower's perspective according to an embodiment.
5 is a flowchart of a process for generating keys used for authentication of an investor, according to an embodiment.
6 is a flowchart of a process of being authenticated through an authentication 1 key according to an investment selection of an investor according to an embodiment.
7 is a flowchart of a process in which a borrower loan request is authenticated through an authentication 1 key until the borrower loan request is selected and matched according to an embodiment;
8 is a flowchart of a process of generating and uploading investment information of an investor and loan information of a borrower to a smart contract according to an embodiment.
9A, 9B are flow diagrams of a process for issuing an investor's token and a borrower's token to an OP account according to one embodiment.
10A and 10B are flow diagrams of a process for generating an authentication 2 key and issuing tokens to an investor's account and a borrower's account, according to an embodiment.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but can be implemented in various forms, only these embodiments make the disclosure of the present invention complete, and 　 with ordinary knowledge in the art to which the present invention belongs It is provided to fully inform the person of the scope of the invention.

In describing the embodiments of the present invention, detailed descriptions of well-known functions or configurations will be omitted except when it is actually necessary to describe the embodiments of the present invention. In addition, the terms to be described later are terms defined in consideration of functions in an embodiment of the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

The functional blocks shown in the drawings and described below are merely examples of possible implementations. Other functional blocks may be used in other implementations without departing from the spirit and scope of the detailed description. Also, although one or more functional blocks of the present invention are represented as separate blocks, one or more of the functional blocks of the present invention may be combinations of various hardware and software configurations that perform the same function.

In addition, the expression including certain components is an open expression and merely refers to the existence of the corresponding components, and should not be construed as excluding additional components.

Furthermore, when a component is referred to as being connected or connected to another component, it may be directly connected or connected to the other component, but it should be understood that another component may exist in the middle.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

1 is a P2P loan system ( 1) and a block diagram showing the operating environment of the blockchain network.

Referring to FIG. 1 , the P2P loan system 1 may operate in conjunction with a blockchain network. Hereinafter, the configuration of the P2P loan system 1 according to an embodiment will be first described, and features of the blockchain network interworking with the P2P loan system 1 will be described.

The P2P loan system 1 may include a server 10 , an investor terminal 20 , and a borrower terminal 30 . The server 10 , the investor terminal 20 , and the borrower terminal 30 may be operably connected through a network to transmit and receive information. For example, the network may include a wired/wireless communication network such as a local area network (LAN), a wide area network (WAN), a virtual network, and telecommunication.

The server 10 may provide a P2P loan service function that achieves a loan in a manner that connects an investor's investment to a borrower's loan request without an intermediary function of a financial institution. In the function of this P2P loan service, the server 10 issues an authentication key based on blockchain technology to each of the investors and borrowers, and determines whether to perform the operation of the request generated by the investor and borrower through the authentication key. have. In addition, when the request of the investor and borrower is fulfilled, a unique token is issued to each, thereby proving that the fulfillment of the request of the investor and borrower is completed, while allowing the transfer of the rights generated when the request is completed.

These functions may be performed through an online platform provided by the server 10 , and the online platform may be accessed by investors and borrowers through respective terminals 20 and 30 .

The investor terminal 20 is a terminal used by investors. The investor can check the borrower's loan request list posted on the online platform provided by the server 10, invest in the desired loan conditions, and realize a profit according to a preset interest rate. In addition, when the investor invests in the loan conditions, a right of principal and interest is created, and in the embodiment of the present invention, the principal and interest is implemented as a token unique to the investor and can be transferred to a third party.

The borrower terminal 30 is a terminal used by the borrower. When the borrower applies for a loan to the online platform provided by the server 10 and passes predetermined examination conditions, the borrower may publish his/her loan conditions on the online platform. The loan condition may include information of a loan amount, a loan period, and an interest rate. In such a loan condition, when one or more investors execute an investment and achieve a loan amount within a predetermined period, it can be considered that the loan is established by being connected with the investor according to the loan condition of the borrower. In addition, when the borrower succeeds in lending, a debt obligation is created, and in an embodiment of the present invention, the debt obligation may be implemented as a borrower's own token and transferred to a third party.

Hereinafter, 'investor and borrower' will be collectively referred to as 'user', and 'investor terminal 20 and borrower terminal 30' will be collectively referred to as 'user terminal'.

The server 10 and the user terminals 20 and 30 may be implemented as various types of devices capable of transmitting and receiving information through a network. For example, it may include a portable communication device (eg, a smart phone), a computer device, a portable multimedia device, a notebook computer, a tablet PC, and the like.

The blockchain network is linked with the P2P loan system 1 through a wired/wireless communication network network and can process data generated from the P2P loan system 1 . A blockchain network can be understood as a P2P network system that implements a distributed database of a blockchain structure.

A blockchain network may be understood as a P2P network including a plurality of computing devices (hereinafter, 'nodes') connected to each other, and each node may include one or more processors to perform an operation. The server 10 and the user participating in the P2P loan system 1 may have blockchain account information registered in the blockchain network. The blockchain network can include a public blockchain in which various nodes can participate without restrictions, and a permissioned blockchain in which only authorized nodes can participate and the rights are divided according to the nodes.

Blockchain account information may include a private key and a public key. The secret key is a transaction in the blockchain network (e.g., a transaction that allows a 'digital payment method' to be transferred from the first user account (wallet) to the second user account, a transaction that distributes a smart contract on the blockchain network, a smart contract It can function as a digital signature of the user to cause a transaction to execute, etc.). The public key may also serve as the user's account address.

Encryption and decryption using private and public keys will be described. Assuming that there is some encrypted data, it may be necessary to verify whether the encrypted data is encrypted using a specific secret key. In this case, such verification is possible by using a block chain address corresponding to the secret key, and a method based on a public key infrastructure (PKI) may be used for such verification.

More specifically, when data encrypted using a private key is decrypted using a public key corresponding to the private key, if a value equal to a predetermined value is derived, the encrypted data is said to be encrypted using a specific private key. On the contrary, if a value equal to the predetermined value is not derived, it may be determined that the encrypted data is not encrypted using a specific secret key.

Accordingly, encryption using the private key may be referred to as a "signature", and decryption using the public key may be referred to as "verification" of the corresponding signature. Verification of a signature through a specific private key may be enabled only through decryption using a public key corresponding to the corresponding private key. Such an algorithm is referred to as an "asymmetric key encryption algorithm", and specifically, algorithms such as RSA and ECDSA may be used.

On the other hand, the 'digital payment means' described in the above-described example may include a cryptocurrency (crypto currency). Cryptocurrency is a means of payment that is recorded in a distributed system manner within a blockchain network, and is also used as a term for a concept that includes a digital token (hereinafter, 'token'). For this purpose, we will use 'cryptocurrency' and 'token' separately as follows.

In the description of this document, cryptocurrency refers to a payment method used as a compensation method for data recording and trust maintenance from the moment a blockchain network is created. Also called

In the description of this document, a token may have a predetermined purpose or value (ex. principal and interest receivables, proof of debt) as a digital exchange means additionally generated in one blockchain network. Tokens can be voluntarily generated by nodes participating in the blockchain network, and token generation, transfer, and usage information can be recorded in a distributed system within the blockchain network.

A transaction may be generated by an OPM (Operator Master) or OP (Operator) account, which is a blockchain account managed by the server 10 . A transaction may include information about investors, borrowers, loan information, investment information, information about issuance/transfer of unique tokens, and information about smart contracts. Nodes can check the processing results of transactions through the blockchain.

Transactions that occur on the blockchain network are cryptographically signed by the secret key of the blockchain account of the subject who created the transactions, so they can be recorded as cryptographic proof data that cannot be forged or tampered with on the blockchain network.

When a transaction occurs, the nodes of the blockchain network verify the integrity of the transaction, and based on the consensus algorithm implemented in the blockchain network, create a new block that will follow the previously created block. The transaction can be executed as it is propagated to A block may include a plurality of transaction information.

Block information can be stored in a transaction database shared by nodes. The transaction database may be understood as a public ledger in which a plurality of nodes share the same information. As such, in this document, information uploaded to the blockchain network is expressed as being uploaded on-chain, and information stored in the server 10 without being recorded in the blockchain network is described in general terms that are stored off-chain. decide to do

A blockchain network can deploy and execute various smart contracts provided by various nodes. A smart contract is a protocol written as a digital command, and when an event that follows the conditions of the protocol occurs in the blockchain network, a specific transaction can occur according to the established protocol or other smart contracts can be executed.

A smart contract may hold a contract account. A contract account can be understood as an address where a node or other smart contract included in a blockchain network generates a transaction to operate the smart contract. When a contract account receives a transaction message, the following actions (e.g., token issuance, comparison of information in other smart contracts, creation of a specific transaction, reading a message or sending a message to another account, other create smart contract).

2 is a block diagram of a server 10 according to an embodiment.

Referring to FIG. 2 , the server 10 may include a processor 51 , a memory 52 , and a communication interface 53 .

The processor 51 may control the overall operation of the server 10 . The processor 51 may include an Identify & Key Services Module 80 and an Investment Module 85 . The processor 51 may execute the instructions stored in the memory 52 to drive the Identify & Key Services Module 80 and the Investment Module 85 . The operations performed by the Identify & Key Services Module 80 and the Investment Module 85 may be understood as operations performed by the processor 51 .

In FIG. 2 , the basic function of each module will be described first, and a series of operations performed by the processor will be described with reference to FIGS. 3 to 10 .

Identify & Key Services Module (80) can generate keys such as private key, public key, block chain address, TokenHolderKey, TokenHolderHashKey (authentication 1 key), TokenHolderHashKeyTxID, Exkey (authentication 2 key) and authenticate the user. At this time, the authentication 1 key can be encrypted and stored in each on-chain and off-chain for user authentication. -chain By comparing the stored authentication 1 key with the newly created authentication 1 key, it is possible to determine forgery or falsification of user information at the time of request. The authentication 2 key can be used to transfer a unique token that proves the user's rights or debt status. Detailed descriptions of the authentication 1 key and the authentication 2 key will be described later with reference to FIGS. 3 to 10 . The Identify & Key Services Module 80 can create smart contract related information to be distributed in the blockchain network 20 , create a smart contract according to a specific protocol, and distribute the smart contract to the blockchain network 20 . . In addition, the Identify & Key Services Module (80) can create and control the OPM account and the OP account, which are blockchain accounts managed by the server.

The investment module 85 may generate information about an investment-related investor, information about a borrower related to a loan, and information about a loan completed by matching the investor and the borrower. Information generated by the Investment Module 85 can be used for user authentication, and information generated after authentication can be recorded on-chain. The Investment Module 85 can create smart contract related information to be distributed in the blockchain network 20 , create a smart contract according to a specific protocol, and distribute the smart contract to the blockchain network 20 .

Memory 52 may include TokenIndex DB (Investor Store: 100, Borrower Store: 150), TokenHolderKey DB 200, TokenHolderHashKey DB 300, and Exkey DB (Investor Store: 400, Borrower Store: 450) and , instructions for performing the operation of the processor 51 may be stored.

The TokenIndex DB ( 100 , 150 ) may store investor and borrower keys, loan contract information, and information on key values generated according to the contract. TokenHolderKey DB 200 may store TokenHolderKey of investors and borrowers, TokenHolderHashKey DB 300 may store one authentication key of investors and borrowers, and Exkey DBs 400 and 450 may store two authentication keys of investors and borrowers.

The communication interface 53 communicates with the blockchain network, and enables transmission and reception of information with the components included in the P2P lending system 1 . To this end, the communication interface 53 may include a wireless communication module or a wired communication module.

3 is a conceptual diagram of a process in which a P2P loan service is performed from an investor's point of view according to an embodiment. User1 means an investor.

Referring to FIG. 3, a TokenHolderKey encrypted with user-specific data is generated from the investor-only TokenIndex (FIG. 3-100) that stores information of various authentication keys including all contract transactions and tokens of the investor (FIG. 3-200), OPM (Fig. 3-300, hereinafter authentication 1 key), a block chain account that creates and manages the OP account of the contract manager who manages the investor's investment contract by receiving the TokeyHolderHashKey (Fig. 3-500), and the OP in charge of a specific investment/loan contract (FIG. 3-600) to prove that the investor's distributed investment contract information is not damaged until the final payment of tokens to investors and borrowers, and investment/loan Only for the case where the contract is established, the investor's right to a specific distributed investment proposal after the borrower receives the token from the platform if it is authenticated with the Exkey for pre-authentication (Fig. It relates to an updated investor-only TokenIndex (FIG. 3-700) used for communication with smart contracts and investment management modules such as token information and redemption of principal and interest receivables for proof, information on principal and interest market, etc. .

4 is a conceptual diagram of a process in which a P2P service is performed from a borrower's perspective according to an embodiment. User0 means the borrower.

Referring to Figure 4, in the case of a borrower whose purpose is a loan, unlike the investor process, after the investor's diversification investment contract is in progress, it may not be known which diversified investment case succeeded in attracting investment from a large number of investors ( Looking for a loan of 10 million won - The amount of diversified investment until the end of the investment is 10 million won or the investment is terminated at a price of less than 10 million won) As in the case of the investor, a different characteristic occurs from the process of authentication 1 key - authentication 2 key. . In other words, if investor Hong Gil-dong made 10 diversified investments with 10 million won, only 3, 4, 7, and 9 borrowers out of 10 succeeded in attracting investment (10 million won from several investors who are hoping for a 10 million won loan). Borrower who succeeded in attracting - OP to process authentication 1 key (FIG. 4-300) of borrower who succeeded in lending in OP account (FIG. 4-650) for issuing tokens only (FIG. 4-650) to receivables (FIG. 4-650) An updated exclusive token index file for borrowers that receives and authenticates the authentication 1 key from borrowers who succeeded in lending in the same contract (Fig. 4-450), pays the loan normally, and issues and stores tokens (Fig. 4- 750). In the P2P platform, a blockchain network for permission can be used to use the consensus model between participants with limited and limited qualifications and the transaction platform, and all processes and transactions to pay tokens to participants as an authentication method for this purpose. How tokens can be used for redemption and sale of part of the transaction is described below.

5 is a flowchart of a process for generating keys used for authentication of an investor, according to an embodiment.

Referring to FIG. 5 , User1_TokenIndex is a DB in which the investor's main authentication key value, contract information, and information on token key values according to the contract are stored. As a step corresponding to Fig. 3-100, the investor generates the investor's private key and public key in [Fig. 5-1] Indentity & Key Service Module at the first login after registering as a user member and stores it in the TokenIndex DB (keyfiles) [Fig. 5-2]. When a blockchain account address is created from the public key and the public key is stored in the investor User1_TokenIndex, the state value is updated to PublicKeyState = 1 [Fig. 5-3] and User1_AddressState = 1 [Fig. 5-3], and the investor TokenHolderKey key [Fig. 5- 4] is created.

As a step corresponding to Figure 3-200, TokenHolderKey is one of the authentication key generation elements for user transaction authentication using the user's unique data. used for The creation of TokenHolderKey [Fig. 5-4] takes the user's unique data set of user ID (UserID), Account Address, PublicKey, and virtual account number extracted from the Payload Set (user unique data) of User1_TokenIndex and records the first login time of the user. [HMAC][HMAC] Hashing encryption (SHA256) can be processed as shown in the example below by using the secret key.

When HMAC hashing is processed with TokenHolderKey= SHA256{SecretKey(firstLoginTimeStamp)(UserID, AccountAddress, PublicKey, VirtualBankNum)}], the user's TokenHolderKey value is generated as 2cb96d020dcd6e3ee35b519ff393812220710efced0ab01bebaac3d7905d5032. (This value is more unique and unpredictable because the [HMAC][HMAC] secret key is used to generate the first login time of the user rather than the secret key generated from the user's password.) TokenHolderKey is created and stored in User1_TokenIndex When updated [Fig. 5-5], the state value of TokenHolderKey1State is changed from 0 to 1 [Fig. 5-6] to complete preparation for TokenHolderHashKey creation.

As a step corresponding to FIG. 3-300, TokenHolderHashKey (authentication 1 key) is generated for use in verifying transaction validity by using user authentication of investors and borrowers and signatures (SIG.) when a transaction occurs. That is, before token issuance for each contract, an authentication method is required to proceed with investment and loan contracts. One of two methods for this is to use the authentication 1 key. Generation of authentication 1 key [Fig. 5-7] is a key by hashing using the user ID and the TokenHolderKey generated in [Figs. can create In this case, the hashing method that can be used may include SHA224, SHA256, SHA384, and SHA512. The generated authentication 1 key is updated in THHK_User1H1Key(), which manages the authentication 1 key for investors under the TokenHolderHashKey module [Fig. 5-8], and simultaneously updated in User1_TokenIndex for investors. [Fig. 5-9] When the authentication 1 key is updated in User1_TokenIndex, User1_H1KeyState = 1 [Fig. 5 -10] is returned to module 1 as a state value, and creation of Smart Contract [OPM] TokenHolderHashKeyTxID starts.

[Fig. 5-11] TokenHolderHashKeyTxID is used for virtual account transaction authentication and investment start authentication. After the authentication 1 key is first created, when the authentication 1 key is normally updated in the investor's User1_TokenIndex and the User1_H1KeyState = 1 value is confirmed [Fig. 5-10], the TxID management function of the investor's authentication 1 key in TokenHolderHashKeyTxID() is THHKTxID_User1H1Key( ), the corresponding authentication 1 key and related information are generated as TxID (Transaction ID) and stored in the Input State Reference [Fig. (Transaction) is compared with the authentication 1 key of the user, and if it is matched, it is used for recording in the block.

The structure and encryption for TxID generation is the same as User1_H1KeyTxID = Keccak-256(RLP[User1_ID, H(User1_ID, TokenHolderKey1), User1_H1KeyState, nonce=1]).

The generated TxID is encrypted and stored in the database with the key value and the public key of the OPM account (OPM.P). [Fig. 5-12]: write.User1_H1KeyDB = (TxID, 1, Enc(OPM.P{User1_ID, THHK_User1H1Key, THHK_User1H1KeyState, SigState=0, nonce=1]) When TxID is normally encrypted and stored in the database [Fig. 5- 12], before the transaction values are authenticated and blocked, the input state reference (on-chain) that can be referenced in the smart contract is signed with the private key (OPM.p) of the platform OPM account and stored on the investor side of the on-chain. [Fig. 5-13] write.InputStateReference = Enc(OPM.p[TxID, Index])

6 is a flowchart of a process of being authenticated through an authentication 1 key according to an investment selection of an investor according to an embodiment.

Referring to Figure 6, the investor's authentication key is signed with the investor's private key and a transaction is submitted. If the key is matched, THHK_User1H1KeyState = 1, SigState = 1 (investor electronically signed state) is returned, and the state of the normal authentication 1 key is preserved. It can be used to check the authenticity and integrity of information.

The specific process of FIG. 6 is as follows.

1. After the investor deposits a deposit into the virtual account provided by each user on the platform, selects n bonds for diversified investment with an investment of 10 million won on the screen and clicks the 'Invest button' in the dialog window to confirm the investment execution 'Do you want to execute your investment?' Enter the user login password in to execute the investment.

2. The user's password is input from the User Key (Identity & Key Services) module, which is responsible for user authentication and various authentication keys and encryption, and extracts the investor's secret key (two p), which is encrypted and stored in keyfiles.

3. Generate the authentication 1 key for investment authentication and sign it with the investor's private key (InvestStart_User1H1Key = Enc(twop(User1_H1Key)) key.

4. Investment information received in the first process of investing with the investor's authentication 1 key (InvestStart_User1H1Key) as the investment management module in charge of investment and loan management and the investor ID in the investment and loan management module (Investment Module) The information contained in ContractInfoSetInstance(), an instance containing items (investment amount, selected diversified investment information, investment amount and bonds), is brought into investment contract information [ContractNum(), SubContractNum(), SelectedBondName()].

5. InvestStart_User1H1KeyMethod(): For the authentication method of investment contract information, the user authentication 1 key is placed in ContractNum(SubContractNum()).

6. Investor's authentication 1 key is investment management When the InvestStart_User1H1Key key is updated in the investment management module, the status value that records the start of the contract is changed from InvestState = 0 to InvestState = 1 and the system is updated to indicate that the investment has started.

7. Update the above [4,5,6] process to the entire investment information.

8. InvestState = 1 is updated and when investment starts, [Fig. 5-13] Write.InputStateReference = Enc(OPM.p[TxID, 1]) Dec(OPM.P[TxID,Index]) after receiving the signature with the public key (OPM.P) and decrypting

9. The TxiD of the index 1 value of the TxID (Transaction ID) obtained in the step [8] is obtained.

10. The TxID obtained in the process [8] above is sent to the user key (Identity & Key Services) module.

11. Query the TxID received in step [9] to find a DB corresponding to the TxID as a key, and decrypt the encrypted user ID and user authentication 1 key original stored with the TxID. Dec(OPM.p(TxIDvalue)), TxIdvalue=(User1_ID, THHK_User1H1Key, THHK_User1H1KeyState, SigState, nonce=1)

12. Upon completion of the decryption process in step [10], the investment authentication 1 key InvestStart_User1H1Key() submitted by the investor kept in the investment module during investment is requested to the OPM account.

13. With the platform master account, OPM, in the investment management module, sign with the investor's private key in InvestStart_User1H1Key(), and decrypt the authentication 1 key with the investor's public key and return it to the user key module. At this time, since the signature was normally received, the signature state value is updated to SigState = 1.

14. The investor's authentication 1 key (THHK_User1H1Key) obtained in the process [10] above, that is, the investor's authentication 1 key created right at the time of membership registration and stored in the on-chain, and the authentication 1 key submitted at the time of the investment transaction [Fig. 6-12], it is possible to determine whether the user is authenticated or hacked by checking whether the two keys match after confirming that the user ID is the same.

15. When User1_H1Key0 obtained in step [10] and User1_H1Key1 obtained in step [12] match, it will be used in OPM [Fig. 3-500, Fig. 4-550] and OP [Fig. 3-600] Returns the value of the authenticated authentication 1 key. return User1_ID, User1_H1Key0, THHK_User1H1KeyState = 1, SigState = 1

16. The values returned in the [14] process (User1_ID, User1_H1Key0, THHK_User1H1KeyState = 1, SigState = 1) are transmitted to the TokenHolderHashKey module.

17. Update the investor authentication 1 key management method ValiTHHK_User1H1Key() of the TokenHolderHashKey module.

7 is a flowchart of a process in which a borrower loan request is authenticated through an authentication 1 key until the borrower loan request is selected and matched according to an embodiment;

Referring to FIG. 7 , when the borrower's authentication 1 key 300 is secured in the OP 650, the borrower can proceed with {authentication 2 key 450 authentication -> borrower application loan payment -> token payment order}. , within a specified time in a single contract, it may or may not be 'successful in all n of n diversified investments = achievement of desired loan application amount' for investors' bonds. Just like the investor authentication 1 key process, the process that requires the destruction of the 1 key authentication of the bond, which is a bond in which loan failure occurs even after issuing and receiving authentication 1 key to all borrowers selected for diversification of investors The process of generating the authentication 1 key of the borrower without it is wasted. Therefore, the authentication 1 key corresponding to the name of the bond in the case of failure to raise loans in the investor's diversified investment activities is not issued from the beginning. That is, it is assumed that among the 10 diversified investment bonds of Investor A, there are 6 successful loan bonds (ex:BondName #23994) in which the desired loan amount of 10 million won is diversified from other investors during the investment period designated by the platform (ex: 2 weeks). Then, it is a method and process for normally updating the authentication 1 key of the borrower to the TokenHolderHashKey 300 so that only the authentication 1 keys of the borrower of the six bonds go through the normal authentication and signing operation conditions, and then proceed with the next process. This method can be applied as a process of granting an identification authentication key to various unpredictable transaction results within a set time period.

The specific process of FIG. 7 is as follows.

1. This is the state value (User0_H1KeyState = 1) when the borrower's authentication 1 key is first generated and updated at (150). The borrower's authentication 1 key generation and storage process is the same as that of the investor process (FIGS. 5: 1-10), so a redundant description will be omitted.

2. Immediately after generating the borrower's authentication 1 key, generate a TxID (Transaction ID) to store on-chain (The structure and encryption for TxID generation is User0_H1KeyTxID = Keccak-256(RLP[User0_ID, H(User0_ID, TokenHolderKey0)) , User0_H1KeyState, nonce=1]) ) and (the creation method is the same as described in [Fig. 3-300])

3. The generated TxID as Key Value and the public key (OPM.P) of the platform operator master (OPM) account are encrypted and stored in the database: write.User0_H1KeyDB = (TxID, 1, Enc(OPM.P{User0_ID) , THHK_User0H1Key, THHK_User0H1KeyState, SigState=0, nonce=1])

4. If the TxID is normally encrypted and stored in the database [Fig. 5-1-3], before the transaction values are authenticated and blocked, enter the Input State Reference that can be referred to in the Smart Contract as the secret key of the platform operator master (OPM) account. It is signed and stored on the borrower side. write.InputStateReference = Enc(OPM.p[TxID, Index])

5. Save process #4.

6. When User0_H1KeyState = 1 as the state value of the authentication 1 key of the borrower ID logged in as the first generated state value of the authentication 1 key in step 1, make sure that the borrower’s loan application can be displayed on the investor’s investment list page. Execute and process ValidateLendApply(). When the borrower's initial membership registration -> Loan application page -> After submitting the loan application and receiving approval for loan review from the platform operator, the status value is changed from Lender_Approve = 0 to 1. The borrower's loan application review registration (Lender_Approve = 1 ) has been made, and the borrower. If the authentication 1 key is generated (User0_H1KeyState = 1), a notification (e-mail, App Push) is given to the borrower to inform the investment potential status,

7. When the borrower wants to register for a loan that has received the loan application review registration (Lender_Approve = 1) by clicking the 'Register button' on the loan list page on the 'My Loan Application Page' after logging in, the borrower must log in to check the loan registration. Re-enter the password used when

8. Securely transmits the input borrower's password to the server's user key (Identity & Key Services) module, receives the user's password, and extracts the borrower's secret key, which is encrypted and stored in keyfiles.

9. Regenerate the borrower's authentication 1 key for loan registration authentication (the same as the process of regenerating a new authentication 1 key at the time of investor's investment) and sign the borrower's private key (car.p). (InvestStart_User1H1Key = Enc(P(User0_H1Key))

10. The authentication 1 key (InvestStart_User0H1Key) of the borrower's signature created in step 9 and the loan application information on the borrower's My Loan application page - myBondInstance(), that is, loan application information (loan user information, desired loan amount, existing loan status, credit grade, etc.) to the Investment Module, which is in charge of investment and loan management.

11. When the transfer value is received from the Investment Module in step 10, it is checked whether a previous loan application has been made with the borrower's ID, and if there is no loan application in progress, execute makeNewBondNum() to name a new bond that has never been used ( New BondName) is issued (Ex: new bondName (#334959)), and the displayNewBondList() is updated so that it can be displayed on the investor's investment list page along with the borrower's signed authentication 1 key.

12. Put the borrower's bond name (BondName), loan success status (BondRight = 0), desired loan amount (bondAmount = 10 million won), and the borrower's signed authentication key (InvestStart_User0H1Key) into the list of bonds displayed on the investor's investment page, Update with star code.

13. Do you want to execute the investment after selecting the number of diversified investments, for example 10 bonds, from the list of bonds displayed on the investor's Investing page? in running investments. (Fig. 6-1) explanation and correspondence.

14. Description and correspondence of (FIG. 6-2).

15. Description and correspondence of (Fig. 6-3).

16. Description and correspondence of (Fig. 6-4).

17. Description and correspondence of (Figs. 6-7).

18. (THHK_User1H1KeyState = 1) and signature-confirmed (SigState = 1) in (FIG. 6-16), when the investor's authentication 1 key is updated in TokenHolderHashKey(300), the corresponding authentication 1 key is converted to the authentication 1 key in the OPM (500) Received from OPM_TokenHolderHashKey1(Index, User1_ID, OPM_User1H1Key, OPM_User1H1State) in charge of , and updated to OPM_User1H1State = 1 for investor’s authentication Update the investor's authentication 1 key to OPM_User1H1Key = OP_User1H1Key and update the status value to OP_User1H1KeyState = 1 A possible state begins.

19. Investment started (InvestState=1) from OP(600) to the corresponding investment contract (ContractNum()) as the investor's investment contract (FIG. 6-6), and the investment has not ended yet (OP_InvestDueTimeState=0) In , n of 10 bonds that have been diversified by the investor’s previous contract are filtered and classified only the bonds that have occurred (bondRight=1) in the state where the desired loan collection is completed.

20. Enter the name of the bond (bondName) that has completed 19 desired loan collection (bondRight=1), the borrower ID (User0_ID) connected to it, and the signed borrower’s authentication key (InvestStart_User0H1Key) that the borrower with this ID used when registering for a loan Send to BondRight1User0_ValiH1KeyMethod( ) of the user key module to obtain the verified authentication 1 key and signature status value of the borrower with bondRight=1.

21. BondRight1User0_ValiH1KeyMethod( ): Verifies forgery of borrower authentication 1 key, receives the borrower’s InvestStart_User0H1Key key received in step 20, and signs it with Dec(Difference P(User0_H1Key)) (SigState=1) and sets the secured User0_H1Key to temporary variable k1 keep it in

22. Obtain the TokenHolderHashKeyTxID created in step 2 of 5-1.

23. Acquire (TxID, Index) in on-chain.

24. Send the TxID to the user key module.

25. Query the TxiD received in step 24 from the encrypted database, decrypt the borrower’s authentication key stored in TokenHolderHashKey No. 300 created when the borrower signed up for membership, in the encrypted database, and perform Dec(OPM.p(TxiDvalue)) Find (THHK_User0H1Key) and store it in temporary variable k0.

26. In validateUserH1Key(), verify that the two keys stored in temporary variables k1 and k0 match. When the two keys match, the borrower ID of the corresponding key and the borrower's authentication 1 key (THHK_User0H1Key) stored in No. 300 are stored, THHK_User0H1KeyState = 1 is recorded as the matching state value, and the signature state (SigState = 1) values are stored.

27. No. 300, sent to TokenHolderHashKey.

28. Update the values received above in TokenHolderHashKey.

29. Transfer the borrower's authentication 1 key from TokenHolderHashKey (321) to the account OP (600) in charge of each contract to the OPM (551) that can create an account. (See Fig. 6) It is transmitted to OPM_TokenHolderHashKey0(Index, User0_ID, OPM_User0H1Key, OPM_User0H1State). If the borrower authentication 1 key included in the TokenHolderHashKey DB is updated and THHK_User0H1KeyState = 1, the OPM_User0H1Key value of the OPM responsible for the borrower’s authentication 1 key is updated to the THHK_User0H1Key value of the borrower’s authentication 1 key in the TokenHolderHashKey DB, and the OPM_User0H1Key value is updated ( When OPM_User0H1State=1), a new OP account 600, which is a block chain account, is created, and a new contract number is created and assigned to New ContractNum() and the created new OP account. When a new OP account is created, the borrower ID is used as the key value, the borrower's authentication 1 key value in OPM_TokenHolderHashKey0 in OP_TokenHolderHashKey0(), which manages the borrower authentication 1 key in the OP module, and the OPM_User0H1State=1 state value is checked and OP_TokenHolderHashKey0(Index, User0_ID) , OP_User0H1Key, OP_User0H1KeyState) is obtained and updated, OP_User0H1KeyState = 1 is returned. (See Figures 8-550)

30. OP of investors and borrowers. When the authentication 1 key is updated, the contractUpdateValidator() performs the work of recording the information of the bonds that have succeeded in attracting investment (bondRight = 1) and the information of the investors who have invested in it in the block.

8 is a flowchart of a process of generating and uploading investment information of an investor and loan information of a borrower to a smart contract according to an embodiment.

The specific process of FIG. 8 is as follows.

1. The OPM, which stores the investor's TokenHolderHashKey and state value in module (300) (311 - see Fig. 6-16), acts as the platform master, and when a new investment contract occurs, the new OP (600) account in charge of the contract is created. In order to generate it, a verified investor's authentication key is required. In OPM, check the investor's authentication 1 key in the management function OPM_TokenHolderHashKey1() and check whether the investor's authentication 1 key has been properly verified and updated (THHK_User1H1KeyState = 1) and signed (SIgState = 1) in (No. 311) .

2. In the management function OPM_TokenHolderHashKey1() of the investor's authentication key, the investor's authentication 1 key (OPM_User1H1Key) and the verified and signed investor's authentication 1 key are updated and stored (OPM_User1H1State = 1). When OPM_User1H1State = 1, OPM creates an account for OP No. 600 (OPM_newOPaccountState = 1), and OPM is not used in the Investment Module so that the OP can receive the contract number allocated from the system at the time of investment start. Import the contract number that has not been assigned and assign the contract number to the newly created OP account.

3. When the OP(600) account is created, check that the OP_TokenHolderHashKey1(), which is responsible for the investor authentication 1 key, is updated normally (OP_User1H1KeyState = 1), and then confirm that the contract of the investor's investment contract number is normally started and not closed do.

4. In OPM_TokenHolderHashKey1(Index, User1_ID, OPM_User1H1Key, OPM_User1H1State), the information values corresponding to the investor authentication 1 key in step 501. When the investor authentication 1 key is normally updated in OPM, the state value OPM_User1H1State = 1, the investor authentication 1 with OP_TokenHolderHashKey1() Get the key value from 501 to OPM_TokenHolderHashKey1() -> 600 to OP_TokenHolderHashKey1().

5. Update the investor authentication 1 key value brought in step 4 to step 601. When OP_TokenHolderHashKey1(Index, User1_ID, OP_User1H1Key, OP_User1H1KeyState) is updated, it is updated to OP_User1H1KeyState = 1 as the updated state value of Investor 1 Key for OP.

6. If OP_User1H1KeyState = 1 in No. 601, in order to update the investor authentication 1 key (OP_User1H1Key) to the investment contract information in No. 650 and record the investment contract information according to the transaction occurrence of the investor’s investment start in the block, When OP_User1H1KeyState = 1 state for the purpose of calling the stored investor's authentication 1 key (Cold Version), the entire investment contract number Contract 2342 and the investor's authentication 1 key are transmitted to ContractUpdateValidator() 670, the contract information update management function. (In 650, the total investment contract number is 2342, and if the diversification investment is made 10 times, the list of sub-division investment contract numbers 2342-1~10 is created. When the amount is collected, the status value is updated to BondRight = 1, (650) The principal and interest receivables are formed in a specific sub-diversity investment contract 2342-2, and the status value is changed to InvestSubRight = 1)

7. In order to obtain the cold version of authentication 1 (recorded as a block in Fig. 3-13) stored at the time of investor membership registration in number 1001, the OP account signature, including user ID and full contract number The smart contract requests the authentication 1 key value corresponding to the user ID.

8. To obtain the TxID value recorded in (1001), the OPM received the OP signature received in step 7, indicating whether the OP account was normally issued, and whether the contract assigned to the OP account was successfully started and not yet liquidated. If it is confirmed that the status is still in progress, read the TxID from the block, pass it to (682), and send it to number 670 again.

9. Decrypt the encrypted data corresponding to the TxID obtained in process 8 to secure the version of the investor's authentication 1 key stored off-chain.

10. Temporarily store in u1_0.key and execute #11 when the state value is updated to u1_0keyState = 1.

11. Obtain the investor authentication 1 key by accessing User_TokenHolderHashKey1(), which manages the investor authentication 1 key included in module 100, which is the transaction activity and contract information storage that the investor logs in and accesses, with OP authority. (Since it is in the off-chain area, it is assumed from the beginning that there is forgery and falsification of the authentication 1 key in the entire logic, so it is necessary to check the key value matching. to prevent)

12. If the investor authentication 1 key obtained in step 11 is temporarily stored in u1_1.key and the state value is updated to u1_1keyState = 1, after checking the values of u1_0keyState = 1 and u1_1keyState = 1 in (670), (671) and Check whether the (672) value matches.

13. Record the 675 status value (ContractVali_H1Key1 = 1), update the contract information of 650, and store it encrypted with OP.PublickKey(650 Data) at number 651.

14. Investors who have made multiple diversified investments in a single bond name (#244553) exist. When investor 1's authentication 1 key verification state value, ContractVali_H1Key1 = 1 (675) occurs, invest in this bond (#244553) OP.rePayBook.bondName(677) module that separately manages the authentication 1 key verification status value of multiple investors, the loans of the bonds invested by investors are collected (bondRight=1), and the investors’ diversified investments (2342-2 ) is sent to (677) only when the preliminary principal and interest receipt is secured (InvestSubRight=1) and stores all the verification values of the authentication 1 key of investors who have invested in bonds, OP.rePayBook.bondName(Index, contractNum, contractVali_H1Key1= In 1), if the verification value of the authentication 1 key of all investors who invested in this bond is all 1 (contractVali_H1Key1=1), the status value (allContractVCali_H1key=1) is returned along with the bond name (bondName), and at the time of token payment and redemption later use.

A. In the function to find the SelectedBondName(bondName, bondright=1) of the bond that has succeeded in attracting loan investment from the bond corresponding to the sub-investment contract number in (650), whether the name of the bond has achieved the target investment attraction amount (bondright=1) Check and obtain the 1 key to the borrower's certificate of successful investment attraction.

B. Request 1 key to authenticate the owner of the bond with bondright=1.

C, D The authentication 1 key 321 of the corresponding borrower is updated to No. 551. (same as investor)

E. Description and correspondence of (Fig. 8-3).

F. Description and correspondence of (Fig. 8-4).

G. The information updated in (550) OP_TokenHolderHashKey0() is updated with borrower authentication 1 key in (602), and OP_User0H1KeyState = 1 as the update status value.

H. If the borrower's authentication 1 key state value in (602) is OP_User0H1KeyState = 1, only the successful loan investment attraction (bondRight=1) managed by the OP is filtered (680) The borrower's authentication 1 key (OP_User0H1Key) is ) is updated in the index corresponding to the borrower's bond name, OP.SelectedBondName(Index, OP_bondName, User0_ID, OP_bondRight=1, OP_User0H1Key). If the borrower's authentication 1 key is normally updated in OPM (OP_User0H1KeyState = 1) as shown in #602, the borrower ID (User0_ID), bond name (OP_bondName), and borrower authentication 1 key (OP_User0H1Key) are transmitted to ContractUpdateValidator() #670.

I. Secure the borrower's authentication 1 key version stored off-chain. (FYI: The TxID is used as the TxID obtained in steps 7 and 8)

J. Secure the borrower's authentication 1 key cold version, temporarily store it in u0_0.key #673, and execute K process when the state value is updated to u0_0keyState=1.

K. (752) Access User_TokenHolderHashKey0() with OP authority to obtain borrower's authentication key. (Refer to process 11)

L. If the key obtained in (752) is temporarily stored in u0_1.key and the state value is updated to u0_1keyState = 1, after checking the state value 1 of each u0_1.key and u0_0.key dml in (670) (674) ) and (673) are matched.

M. (676) Record the updateable state value of the bond of the diversified borrower (ContractVali_H1Key0 = 1) and update the 680 contract information.

In process H, when the borrower's authentication 1 key transmitted to 680 and the key 673 match, the information of the bond 680 is finally transmitted to the ContractUpdateValidator() 670. At this time, as in 670, the investor transferred from process 6 is the same. If the authentication 1 key matches the value of the key stored in 671, it is transmitted to 670 and processes O, P, and Q are executed to record the entire contract information in the block. In ContractVali_H1Key1 = 1 state, the purpose of comparing the authentication 1 key deployed in process 6 again is the process of comparing the authentication 1 key stored in the off-chain version with the authentication 1 key deployed at the time of investment again in doubt, and the borrower’s The reason is the same from the point of view.

N. A process for reading or writing previous contract information, which can be used when tokens are transferred from the OPM account to the OP account or when writing information to a block. In the second update, if there is a previous transaction record, it is possible to determine whether to proceed with the update after comparing the index number. (See Figure 8-13 process)

9A and 9B (hereinafter collectively referred to as FIG. 9 ) are flowcharts of a process for issuing an investor's token and a borrower's token to an OP account according to an embodiment.

1. Confirm and receive investor authentication 1 key in OPM: Investor signed (SigState=1) authentication 1 key (Fig. 8-311). In order to include the investor's user authentication and investment transaction in the block, the signed authentication 1 key must be handed over to the OPM 500 so that the OPM account can create an OP account in charge of each contract and the OP account can receive contract information (Fig. See 8-1~4)

2. When the investor 1 key is confirmed in the OPM, the status value is updated (refer to FIGS. 8-1 to 4).

3. OP receives investor authentication 1 key from OPM and updates status value: When OP receives investor authentication 1 key normally through OPM->OP, it is updated to OP_User1H1KeyState = 1. If OP_User1H1KeyState = 1, the contract is responsible. The account OP will be able to start working on contracts in earnest. (See Figures 8-5)

4. Prepare OP to OP contract account: OP_NewContractSet()

In (1) (FIG. 8-2), OPM created a new contract account, OP. (FIG. 9-3) As in the state, OP_User1H1KeyState = 1, the OP normally invests in the authentication 1 key corresponding to the investor ID. If the authentication 1 key module 300 -> OPM -> OP is received, allocation and investment contract number are allocated to the investor's investment contract account in the corresponding OP account.

(2) If OP_User1H1KeyState = 1, which is the state value of the user authentication 1 key (OP_User1H1Key) for the OP stored in the investor authentication 1 key management function OP_TokenHolderHashKey1 (OP_User1H1Key) in OPM->OP, the corresponding OP public account is converted to a contract account (OP_ContractAccountState = 1) and the investor receives the investment contract number received from the investment and loan management module when making an investment and updates the state value (OP_ContractNumState = 1) when the allocation to the investment contract number managed by the OP is completed.

5. Return status value: The OP is in the contract account status, and the status value received by the investment contract number is returned to the OPM.

6. Investor authentication 1-key double check for OPM->OP token delivery: In order to issue tokens for investors to OPs, OPM(500) is an investor who corresponds to the investor ID and investment contract number in the OPM account. Investor of OP by taking the authentication 1 key from (Fig. 6-311). In contrast with the authentication 1 key, in order to determine forgery of the authentication 1 key, if a match is made, a matching state value (OPM_andOP_H1KeySame = 1) is stored according to the investor ID (User1_ID). (Index, User1_ID, ContractNum, OPM_andOP_H1KeySame = 1)

7. When the investor authentication 1 key matching status value (OPM_andOP_H1KeySame = 1) corresponding to the investment contract number is generated, the amount of tokens to be issued by the token OPM is +1 to transmit the tokens for the investor to use,

8. Call the smart contract responsible for issuing tokens. (For reference: The order of token delivery is OPM->OP->investor or borrower, and when the contract status and the conditions of each key match, the tokens are transmitted.)

9. Check whether the contract assigned to the OP to receive the token has started normally (InvestState=1) and has not yet completed the investment (OP_InvestDueTimeState = 0).

10. One token is sent to OPM->OP equal to the token issuance amount of OPM.tokenBePublish(7). (In No. 6, since the initial investor's OPM_andOP_H1KeySame = 1 Index value is 1, only 1 is transmitted.)

11. OPM_OPtokenReceiveMethod(): When the token is received from smart contract 9 (tokenID), update OP_TokenReceiveState from 0 to 1 with the state value

12. (OP.address, OP_TokenReceiveState = 1) is returned as OPM.tokenPublished.

13. Manage issued tokens: When the address and number of tokens issued in step 11 are updated with OPM.tokenPublished(), the amount of tokens to be issued in the future is subtracted by the amount updated in step 12 from No. 7 to control the possibility of token hacking and forgery. .

14. When process 13 sends the status value to the OP that the token issued amount control update is over

15. Deploying the token received in step 11 into the investment contract - OP_opContractTokenDeployInstance( ): The investment contract in which the OP is allocated after confirming that the status value of the investor's authentication 1 key received by the OP is 1, and that no token has been received by the investor ID Investor tokens are placed in the number, and when tokens are placed in the contract, the state value is updated as OP_User1_TokenIDState=1. (The OP later sends the token received here to the OP->investor after checking the contract status and authentication 2 key)

16. Update the total number of tokens placed in the contract information managed by the OP. OP_totalTokenReceiveNum(n) - (Used to prevent forgery of tokens and prevent forgery tokens from intervening in comparison with the total number of tokens issued by OPM later)

17. Transmit the number of tokens managed by the OP in No. 16 to No. 18 (OPM_OPcontractSet.OPM_OPtokenReceived).

18. Update the total number of tokens placed in the OP actual contract (Index, OP_User1_TokenIDState=1). (It can be assumed that external intervention can occur between processes 13 to 15, and the amount of token issuance is important because a large number of diversified investments occur in P2P) The number of OPM.tokenPublished(n) in validateTokenCount() and If the n value of OP_totalTokenReceiveNum(n) matches, the OP contract number and state value are stored in validateTokenCount(OP. Return to ContractUpdateValidator().

19. The status value that matches the OPM token issuance amount and the number of tokens placed in the OP is transmitted to ContractUpdateValidator().

20. Intermediate update of all investment contract information, including token information, and record in block, ContractUpdateValidator(): Write to block using process 670, 671, 672, 651,681,1002 of FIG.

21. Write to the block using processes 670, 671, 672, 651,681,1002 of FIG.

22. Check and receive borrower authentication 1 key from OPM: (corresponding to Fig. 8-321)

23. When the state value (THHK_User0H1KeyState=1) and signature (SigState=1) of the borrower authentication 1 key of (FIG. 8-321) are confirmed in the OPM 550 of FIG. 2, the OPM borrower authentication 1 key management function OPM_TokenHolderHashKey0() Update the borrower authentication 1 key (THHK_User0H1Key) value of No. 22 to the borrower authentication 1 key value of OPM (OPM_User0H1Key = THHK_User0H1Key.User0_H1Key), and when completed, update the state value to OPM_User0H1State = 1. (For reference, OPM. Borrower authentication 1 key -> OP. Borrower authentication 1 key update process. That is, in step 22, when a transaction (investment or loan application event) occurs, the user-signed authentication 1 key value is stored and contracted. Send authentication 1 key to the OPM account that creates a separate OP account - The process of passing the authentication 1 key to the contract manager OP and using it as a user authentication and contract authentication key)

24. Description and correspondence of (FIG. 9-3). The applicable entity is the borrower instead of the investor.

25. Description and correspondence of (Fig. 9-5). The applicable entity is the borrower instead of the investor.

26. Description and correspondence of (Fig. 9-6). The applicable entity is the borrower instead of the investor.

27. Description and correspondence of (Figs. 9-7). The applicable entity is the borrower instead of the investor.

28. Description and correspondence of (Figs. 9-8). The applicable entity is the borrower instead of the investor.

29. Description and correspondence of (FIGS. 9-9). The applicable entity is the borrower instead of the investor.

30. Description and correspondence of (Figs. 9-10). The applicable entity is the borrower instead of the investor.

31. Description and correspondence of (Figs. 9-11). The applicable entity is the borrower instead of the investor.

32. Description and correspondence of (Figs. 9-12). The applicable entity is the borrower instead of the investor.

33. Description and correspondence of (Figs. 9-13). The applicable entity is the borrower instead of the investor.

34. Description and correspondence of (Figs. 9-14). The applicable entity is the borrower instead of the investor.

35. Place the token received in step 31 into the bond (bondName) that has achieved the desired loan amount (bondRight=1), OP_SelectedBondName(bondName, bondRight=1): OP_opContractTokenDeployInstance( ): Status value of the borrower’s authentication 1 key received by the OP is 1 (OP_User0H1KeyState=1), and after checking that the borrower ID has never received a token (UserID.OP_ReveivedTokenID !=null), the OP places the token in the loan contract belonging to the allocated investment contract number (OP_SelectedBondName.OP_User0_TokenID = OP_ReceivedTokenID) ), and when the token is placed, the state value is updated as OP_User0_TokenIDState=1. (For reference, the tokens received by the OP hereafter are sent to the OP->borrower after checking the contract status and authentication 2 keys.)

36. Update the total number of tokens placed in the loan contract information managed by the OP. OP_totalTokenReceiveNum(n): In the case of borrowers, loan success can occur 10 => n times out of 10 diversified investments of investors, so OP_User0_TokenIDState = 1 Since the value (35 times) is generated, the number of tokens of the borrower who succeeded in lending in a single investment case is counted by cumulatively increasing the value of n by this value (i).

37. Description and correspondence of (Figs. 9-17).

38. Description and correspondence of (Figs. 9-18).

39. Description and correspondence of (Figs. 9-19).

40. Description and correspondence of (Figs. 9-20).

10A and 10B (hereinafter collectively referred to as FIG. 10 ) are flowcharts of a process of generating an authentication 2 key and issuing tokens to an investor's account and a borrower's account, according to an embodiment.

1. Investor 1’s diversification investment contract 123 gives the borrowers tokens when the desired loan is paid.

2. When borrowers receive tokens, Investor 1 is given the right to receive principal and interest in the case of the diversified investment contract, and Investor 1 also receives tokens as proof of the right. Conversely, it is important to prevent other users from receiving tokens for principal and interest receivables or being hacked.

3. In the embodiment of this document, tokens are used so that i) investors can use them for proof of digital assets such as principal and interest receivables, installment sales of the corresponding digital assets, and ii) borrowers can use them for proof of repayment of loans do. (In order to reflect the amortization of the borrower to the investor's assets in an exchange that trades digital assets in which many P2P companies participate, P2P lending companies using heterogeneous platforms participate in the exchange, so borrowers using blockchain-based tokens The proof of redemption makes it possible to provide the advantages of blockchain without data corruption)

4. For token transmission, the token (tokenId=23452) ID issued by the system (OPM - 500) can be used for transmission. [Example: _transferTokenTo(to, tokenId)]

5. To make this possible, careful transmission of tokens for borrowers and participants is required. Using the token ID, a unique authentication 2 key is generated and ported to each contract information of contract participants (borrowers, investors). The purpose of the overall development is to generate, update, and verify the state value of the authentication 2 key (reExshKey2) in each contract step with the contract information so that the correct participant can receive the corresponding token in the normal contract state. If the corresponding token (tokenId) is not a token that has a close relationship with each investment or loan contract (status value according to verification) and has passed the contract information, there is a possibility that other actors may transmit arbitrary tokens to prove their rights. Therefore, the use of two authentication keys is necessary to prove and transact digital assets with blockchain-based tokens.

6. How to configure and generate the authentication 2 key (ExKey): Explained from the borrower's point of view (same for investors). : When the borrower's bond status in the OP has secured the desired loan as a diversified investment (bondName, bondRight=1), the same key values corresponding to the components below are first created and sent to the first smart contract (Smart Contract1) (S0. key), when it is time to pay the loan due to successful distributed investment recruitment to the borrower, the borrower side 150 uses the borrower information stored in the off-chain to generate an authentication 2 key -> 2nd smart contract ( Send (S1.key) to Smart Contract2). In the second smart contract, if the S0.key and S1.key keys are matched and matched, the matching success status value (OP_andUser0exKey0same = 1) is stored in the receivable information page in charge of the OP, the loan is normally deposited to the borrower, and the OP is The borrower token stored in the bond information is transferred to the borrower.

7. Authentication Two-Key Component

(1) The component on the OP side of the authentication 2 key is OP_ExkeySet[(User0_PublicKey, User0_TokenID, OP_User0H1Key, OP_PublicKey, OP_ExSetTime]. Using this component, the Hash value is created by Singing with the private key of the OP account in charge. > Transfer to Smart Contract1.

1) User0_PublicKey: Borrower public key

2) User0_TokenID: Token ID for borrowers placed in OP's investment bond contract

3) OP_User0H1Key: Borrower authentication 1 key

4) OP_PublicKey: the public key of the contract OP account

5) OP_ExSetTime: It is system.time() when the components are imported to OP_ExkeySet() to generate the authentication 2 key in the system for the first time. That is, system.time() is the time when the above 1) to 4) information is input to the authentication 2 key generation function OP_ExkeySet().

(2) The components of the borrower's side of the authentication 2 key are also the same as in 1, but when paying the borrower for a loan application, among the components of the authentication 2 key, (1)-1) above in the borrower's User0_Tokenindex(150), (1)-3) is taken from the Identity & Key Services module and combined with (1)-2), (1)-4), and (1)-5) on the OP side to create a hash value by signing with the private key. -> This is the process of executing the matching operation after transmitting to the second smart contract (Smart Contract2). (Basically, in the block chain, all data stored off-chain is based on the assumption that it is not trusted as time passes, so (1)-1), (1)-3) of borrowers in User0_Tokenindex(150) are damaged. assumes and proceeds with the process of authentication 2 key)

According to the above-described embodiment, in performing P2P lending, the block chain-based service device directly manages the user's block chain wallet, so that the user does not directly use the block chain wallet, thereby solving the inconvenience, It has the effect of providing the advantages of blockchain by relaying the credentials and authentication of all transactions.

In addition, by issuing a transferable user-specific token while proving that the user's request has been completed, the user's rights or debts can be transferred while proving the principal and interest receivables or debt status according to the P2P loan.

Furthermore, it is possible to prove the rights of various assets in the real world with various tokenized digital assets, and provide a reliable and automated notarization function for the relevant participant's credentials, the registration of various assets, and the transaction proof.

The above-described embodiments of the present invention may be implemented through various means. For example, embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.

In the case of implementation by hardware, the method according to embodiments of the present invention may include one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), and Programmable Logic Devices (PLDs). , FPGAs (Field Programmable Gate Arrays), processors, controllers, microcontrollers, microprocessors, and the like.

In the case of implementation by firmware or software, the method according to the embodiments of the present invention may be implemented in the form of a module, procedure, or function that performs the functions or operations described above. A computer program in which a software code or the like is recorded may be stored in a computer-readable recording medium or a memory unit and driven by a processor. The memory unit may be located inside or outside the processor, and may send and receive data to and from the processor by various known means.

Also, combinations of each block in the block diagram attached to the present invention and each step in the flowchart may be performed by computer program instructions. These computer program instructions may be embodied in an encoding processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions executed by the encoding processor of the computer or other programmable data processing equipment may correspond to each block of the block diagram or Each step of the flowchart creates a means for performing the functions described. These computer program instructions may also be stored in a computer-usable or computer-readable memory which may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. The instructions stored in the block diagram may also produce an item of manufacture containing instruction means for performing the functions described in each block in the block diagram or in each step in the flowchart. The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for carrying out the functions described in each block of the block diagram and each step of the flowchart.

In addition, each block or each step may represent a module, segment, or part of code including one or more executable instructions for executing a specified logical function. It should also be noted that in some alternative embodiments it is also possible for the functions recited in blocks or steps to occur out of order. For example, it is possible that two blocks or steps shown one after another may in fact be performed substantially simultaneously, or that the blocks or steps may sometimes be performed in the reverse order according to the corresponding function.

As such, those skilled in the art to which the present invention pertains will understand that the present invention may be embodied in other specific forms without changing the technical spirit or essential characteristics thereof. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. The scope of the present invention is indicated by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present invention. .

Claims (15)

In the self-assurance proof method performed by the blockchain-based service device,
Create a blockchain account for users including investors and borrowers who use the P2P loan service, create an authentication 1 key that encrypts the user's unique information, and generate a TxID that encrypts information including the authentication 1 key, storing in an off-chain DB;
storing the data including the TxID encrypted with an asymmetric key of an operator master (OPM), which is a block chain account managed by the device, in the DB and uploading it to the on-chain; and
When receiving a request for a predetermined operation from the user, including the borrower's loan request and the investor's investment execution request for the loan, the authentication 1 key is regenerated after the request time, and the on-chain Based on the forgery determination of retrieving the Key Value stored in the DB based on the uploaded Key Value, and comparing the authentication 1 key obtained by decrypting the retrieved Key Value with the corresponding key of the asymmetric key with the regenerated authentication 1 key. determining performance of the request;
The step of deciding to perform the
when receiving the loan request from the borrower, regenerating the authentication 1 key of the borrower after the time of the loan request based on a predetermined loan examination for the borrower, and generating loan information for the borrower;
When receiving the investor's investment request for the loan request, the investor's authentication 1 key is regenerated after the investment request time, and stored in the DB based on the investor's Key Value uploaded to the on-chain The investor's authentication 1 key obtained by searching the investor's Key Value and decrypting the OPM's asymmetric key is compared with the regenerated investor's authentication 1 key to determine forgery and forgery to determine whether the investor's investment contract for the loan information to do; and
When the investment contract according to the loan request is established, the borrower's Key Value stored in the off-chain DB is retrieved based on the borrower's Key Value uploaded to the on-chain, and the obtained by decrypting the OPM's asymmetric key The borrower's authentication 1 key is compared with the regenerated borrower's authentication 1 key to determine forgery, and borrower information to be recorded on-chain in relation to the loan request and the investor to be recorded on-chain in relation to the investment request generating information;
How to prove self-assurance.
According to claim 1,
The user's unique information is
User ID, user block chain account address, public key, and user virtual account number including TokenHolderKey encrypted based on the SHA algorithm using the user's first login time information as a secret key,
How to prove self-assurance.
3. The method of claim 2,
The authentication 1 key is,
Containing a TokenHolderHashKey generated by encrypting the user ID, the TokenHolderKey and the time information at which the TokenHolderKey was created together based on the SHA algorithm,
How to prove self-assurance.
4. The method of claim 3,
The Key Value is,
Generated by encrypting the TxID with an index number specifying the authentication 1 key with an OPM private key or public key,
How to prove self-assurance.
delete According to claim 1,
The step of generating the investor information includes:
Set to be executed only when the amount preset in the loan request is all raised by the investor's investment request,
How to prove self-assurance.
According to claim 1,
After determining to perform the request,
OP (a block chain account with permission to access the DB and create a transaction that allows token issuance to prove the user's status as the request is executed is performed in the smart contract that manages the execution of the request through the OPM account operator) creating an account;
transmitting the authentication 1 key obtained by decrypting the key value uploaded to the on-chain through the OPM account to the OP account; and
Further comprising the step of determining, by the OP account, to create the transaction based on a forgery determination that allows the OP account to compare the authentication 1 key transmitted from the OPM account with the authentication 1 key extracted from the TxID stored in the DB,
How to prove self-assurance.
8. The method of claim 7,
After determining to create the transaction,
The OPM account receives the authentication 1 key again from the OP account, and compares the re-transmitted authentication 1 key with the regenerated authentication 1 key to determine the validity of the authentication 1 key held by the OP account; ;
if the authentication 1 key is valid, sending, by the OPM account, a token issuance transaction of a predetermined amount to the smart contract so that the token is paid to the OP account; and
The OPM account determines whether the number of tokens received by the OP account matches the predetermined quantity, and if they match, the OP account records the fact about the token issuance in a block,
How to prove self-assurance.
9. The method of claim 8,
After the step of recording the fact about the token issuance in a block,
generating an authentication 2 key used for transmission of the token based on predetermined information held by the OP account and sending it to a first smart contract;
When it is determined that the execution of the request has been completed, a contract is set so that an authentication 2 key used for transmission of the token is generated based on the predetermined information stored by the DB, and the first smart contract compares the authentication 2 key transmitting the authentication 2 key generated from the DB to the second smart contract; and
The method further comprising: if information is received that the authentication 2 key is the same as the result of comparison of the second smart contract, storing the authentication 2 key in the DB and providing a token to the user;
The token is used for the purpose of proving that the execution of the user's request has been completed,
How to prove self-assurance.
10. The method of claim 9,
The predetermined information held by the OP account and the predetermined information stored in the DB are, respectively,
The user's public key, identification information of the token, and the user's authentication 1 key, and time information when the predetermined information is input by an authentication 2 key generation function,
The authentication 2 key is,
The predetermined information is generated by being encrypted with the secret key of the OP account,
How to prove self-assurance.
According to claim 1,
After the step of creating investor information to be recorded in the on-chain,
OP, which is a blockchain account with permission to access the DB, creates a transaction that allows token issuance to prove the status of borrowers and investors according to the investment contract to a smart contract that manages the execution of the request through the OPM account (operator) creating an account;
Transmits the investor's authentication 1 key obtained by decrypting the investor's Key Value uploaded to the on-chain through the OPM account to the OP account, and the OP account receives the investor's authentication 1 transmitted from the OPM account a first forgery determination step of comparing the key and the authentication 1 key extracted from the investor's TxID stored in the DB;
The borrower's authentication 1 key obtained by decrypting the borrower's Key Value uploaded to the on-chain through the OPM account is transmitted to the OP account, and the OP account receives the borrower's authentication 1 from the OPM account a second forgery determination step of comparing the key and the authentication 1 key extracted from the borrower's TxID stored in the DB; and
Further comprising the step of determining the transaction creation based on the first and second forgery determination,
How to prove self-assurance.
12. The method of claim 11,
After determining to create the transaction,
The OPM account receives the investor's authentication 1 key from the OP account again, and compares the re-transmitted investor's authentication 1 key with the investor's regenerated authentication 1 key to authenticate the investor held by the OP account 1 determining the validity of the key;
if the investor's authentication 1 key is valid, sending, by the OPM account, a token issuance transaction of a predetermined amount to the smart contract so that a first token is paid to the OP account;
determining, by the OPM account, whether the number of first tokens received by the OP account matches the predetermined quantity, and recording the fact that the first token issuance by the OP account in a block;
The OPM account receives the borrower's authentication 1 key from the OP account again, compares the re-transmitted borrower's authentication 1 key with the borrower's regenerated authentication 1 key, determining the validity of the authentication 1 key;
if the borrower's authentication 1 key is valid, sending, by the OPM account, a token issuance transaction of a predetermined amount to the smart contract so that a second token is paid to the OP account; and
When the OPM account determines whether the number of second tokens received by the OP account matches the predetermined quantity, the OP account further comprises the step of recording the fact about the issuance of the second token in a block ,
How to prove self-assurance.
13. The method of claim 12,
After recording the facts about the first and second token issuance in a block, for each of the investor and the borrower,
generating an authentication 2 key used for transmission of the first and second tokens based on predetermined information held by the OP account and transmitting it to a first smart contract;
When it is determined that the execution of the request is completed, an authentication 2 key used for transmission of the first and second tokens is generated based on the predetermined information stored by the DB, and the first smart contract generates the authentication 2 key transmitting the authentication 2 key generated from the DB to a second smart contract with a set protocol for comparison; and
If information is received that the authentication 2 key is the same as a result of the comparison of the second smart contract, storing the authentication 2 key in the DB, and providing the first and second tokens to the investor and borrower, respectively including,
The first token is used to prove the investor's right to receive principal and interest, and the second token is used to prove the borrower's loan debt,
How to prove self-assurance.
In the blockchain-based service device,
one or more memories storing instructions for performing predetermined operations; and one or more processors operatively coupled with the one or more memories and configured to execute the instructions;
The one or more processors,
Create a blockchain account for users including investors and borrowers who use the P2P loan service, create an authentication 1 key that encrypts the user's unique information, and generate a TxID that encrypts information including the authentication 1 key, Storing in off-chain DB;
an operation of encrypting the data including the TxID with an asymmetric key of an operator master (OPM), which is a block chain account managed by the device, in the DB and uploading it to the DB and on-chain; and
When receiving a request for a predetermined operation from the user, including the borrower's loan request and the investor's investment execution request for the loan, the authentication 1 key is regenerated after the request time, and the on-chain Based on the forgery determination of retrieving the Key Value stored in the DB based on the uploaded Key Value, and comparing the authentication 1 key obtained by decrypting the retrieved Key Value with the corresponding key of the asymmetric key with the regenerated authentication 1 key. perform an action that determines the execution of the request;
The operation to determine the performance is,
when receiving the loan request from the borrower, regenerating the authentication 1 key of the borrower after the time of the loan request based on a predetermined loan examination for the borrower, and generating loan information for the borrower;
When receiving the investor's investment request for the loan request, the investor's authentication 1 key is regenerated after the investment request time, and stored in the DB based on the investor's Key Value uploaded to the on-chain The investor's authentication 1 key obtained by searching the investor's Key Value and decrypting it with the asymmetric key of the OPM is compared with the regenerated investor's authentication 1 key to determine forgery and forgery to determine whether the investor's investment contract for the loan information action to do; and
When the investment contract according to the loan request is established, the borrower's Key Value stored in the off-chain DB is retrieved based on the borrower's Key Value uploaded to the on-chain, and the obtained by decrypting the OPM's asymmetric key The borrower's authentication 1 key is compared with the regenerated borrower's authentication 1 key to determine forgery, and the borrower information to be recorded on-chain in relation to the loan request and the investor to record on-chain in relation to the investment request comprising the operation of generating information;
Blockchain-based service device.
Claims 1 to 4 and claim 6 to claim 13, any one of the method of any one of claims, a computer program comprising instructions for causing a processor to perform a computer program is recorded on a computer-readable recording medium.

Images