JP2021530010A - Systems and methods to verify transactions embedded in electronic blockchain - Google Patents

Abstract

A system has been disclosed that partially uses automated protocol-based methods to verify the integrity of blockchain transactions before they are added to the electronic blockchain. By using such a system, it is possible to avoid the current costly consensus mechanism for verifying transactions before including them in the underlying electronic blockchain. In a preferred embodiment, the disclosed system can be implemented in a blockchain environment where the parties "trust" each other, where the trading parties prove their trust in various ways. In such an example, the system can provide automated protocol-based verification of transactions approved by the trading parties and add a record of the verified transactions to the blockchain. [Selection diagram] Fig. 2

Description

The present invention is generally related to the field of blockchain verification. This process, often referred to as the consensus process, verifies the integrity of new transactions, the integrity of electronic blocks that may be integrated before new transactions are added to the blockchain, and the resulting updated blocks. Further verify the integrity of the chain. More specifically, the present invention relates to a system implemented in a blockchain environment in which the parties to a transaction "trust" each other, where trust is (a) the knowledge of the other parties, (b). ) One or more of confidence in the remedies available if the transaction is not completed as intended, or (c) the ability to verify the accuracy and integrity of the transaction prior to verifying the transaction. What you get is that transaction validation based on automated protocols works to validate new transactions before they are added to the electronic blockchain.

The purpose of cryptocurrency protocols such as Bitcoin is to maintain a real-time trading ledger that can protect against double-spending attacks from malicious Byzantine generals by actors who may try to deviate from accepted protocols. It is to be. See Lamport, L .; Shostak, R .; Pease, M. (1982), "The Byzantine Generals Problem", "ACM Transactions on Programming Languages and Systems". To support the anonymity of trading parties (more precisely, pseudonyms) while avoiding the hegemony of having a "owner" of the ledger, Bitcoin employs a decentralized verification process, Bitcoin. The consensus of the transaction ledger is secured by a network of miners. These miners are incentived to participate in the consensus process through a reward schedule to provide consensus confirmation related to the blocks added to the blockchain.

Minor work, or mining, costs one miner-or an attacker-to create multiple accounts or divert blockchain to gain control of the blockchain. Includes proof-of-work calculations that are designed to be extremely difficult and resource-complicated. By the way, in the current Bitcoin price and reward schedule, miners get about $ 1.5 million daily to secure the blockchain, a significant portion of which does the processing required for proof calculations. It has been pointed out that it is spent only on electricity for the purpose. Depending on the history and scale of the Bitcoin blockchain, the proof-of-work-based consensus protocol is time consuming, given the complexity of the calculations required to establish a consensus. It takes up to an hour to reasonably confirm payments to prevent heavy spending. See Jae Kwon, "Tendermint: Consensus Without Mining" Draft V0.6, http://tendermint.com/docs/tendermint.pdf.

End-user and consumer marketplaces that use blockchain technology (eg, many cryptocurrencies) are decentralized so that they are not unduly affected by a single user, business, or government agency. Decentralized or decentralized markets provide incentives for many customers. In fact, many of these markets are deliberately designed to support anonymous and untrusted participants.

The combination of decentralized and anonymous (more precisely, pseudonym) actor support is a verification system without the permission of such markets and actors, as there is no central authority to exercise hegemony over the system by design. In other words, it results in the support of a verification system that allows anyone to compete for rewards without the need for anyone's permission. A transaction is authenticated by both parties approving the transaction, usually by each party applying a digital signature, thereby establishing their respective approval and consent to the transaction. In a blockchain system, such consented transactions are bundled into blocks and later added to the blockchain, which may be the "parent" blockchain.

Such systems rely on anonymous validators (such as Bitcoin miners) to add these blocks to the blockchain using a consensus approach such as Proof of Work calculations, which is a consensus approach. It is intended to validate new anonymously self-selected blocks.

Unauthorized miners are used in Bitcoin and are the original approach envisioned to ensure the integrity of transaction blocks added to blockchain logs or ledgers. Such a permissionless consensus system typically follows the Bitcoin paper written by Satoshi Nakamoto. See S. Nakamoto, “Bitcoin: A peer-to-peer electronic cash system,” 2008.

The downside of this consensus approach is that you have to provide rewards to attract people to miners. In addition, Bitcoin and other marketplaces have conducted proof-of-work tests for miners to limit the ability of any miner or minor group to hijack the system and add contaminated blocks to the blockchain. It is being carried out. The cost of passing the Proof of Work test is exorbitant to overwhelm the consensus of the system and create the validator multiplicity needed to verify improper transactions, for example by brute force calculations. It is expensive or difficult enough to be costly. At the same time, these marketplaces must provide miners with rewards that are well worth the investment in passing the proof of work test, resulting in a consensus approach. Will be costly.

This approach also allows you to roll back specific blocks. By "undoing" a particular block of the blockchain, it guarantees the integrity of the entire blockchain in case a collusion is found in the verified block, but it further delays the final verification of the transaction. ..

Other cryptocurrencies seek to reduce verification costs by implementing different consensus technologies. The Ethereum platform seeks to implement proof-of-stake procedures that do not create computing challenges like proof-of-stake and do not require costly electricity expenditures to solve difficult problems. do. Ethereum's rewards are smaller than those offered by Bitcoin, but so are the entry fees.

Compared to open currencies and decentralized markets such as Bitcoin, corporate marketplaces (such as financial market clearing systems) are generally centralized and are identified as anonymous participants. Offering both untrusted participants. Because it is centralized, it is possible to provide services with a more cost-effective permit ledger system. In a licensed system, the central authority reviews and assigns system validators, but the validation process remains decentralized among the validators as the validators must reach consensus to approve the transaction block. Rather than paying large sums, these identified and screened validators can pay a simple salary. In addition, central authorities have greater confidence in authorized agents, which can speed up the verification process and reduce rollback opportunities and needs. Due to its low operating costs, many new authorization applications are being developed using this alternative consensus approach. In such a system, transactions by anonymous parties are validated by identified validators, and a centralized scrutiny process and regular audits can further increase collusion resistance. A description of such a permitted solution was written by Jae Kwon in a paper entitled "Tendermint: Consensus Without Mining".

Other applications seeking the benefits of blockchain technology include transactions by parties who have known and credible reasons for each other (eg, existing binding contracts or other applications that offer relatively predictable recourses). Because of the legal infrastructure), there is an opportunity to completely avoid the consensus process, thereby further reducing operating costs. In addition, for transactions that include highly confidential content, it is also an advantage to be able to prevent the transaction information from being disclosed to the validator. Opportunities for such systems are ripe, as no such approach has been proposed at this time, and subject disclosure addresses this issue and opportunity.

In a preferred embodiment, the described systems and methods provide an application in which transactions are made between participants who are known and trusted by each other (or, if there is not a sufficient level of trust, the participants Have sufficient means to correct misrepresentation or misconduct by one or more parties). The disclosed systems and methods do not require the intervention of multiple agents to reach consensus, and are efficient and efficient in assembling blocks that are added to the blockchain according to computer-readable protocols to verify transactions. Create an automated protocol-based system.

A wide range of consensus models have been developed to address block verification issues. For the purposes of the present invention, these various consensus models meet two criteria: permissionless and with permission. As can be seen from Table 1 below, both systems can support anonymous (pseudonym) users and known users, but neither model requires users to trust each other. And both provide incentives (such as rewards and salaries) to parties wishing to participate in the creation of a consensus to validate the block of transactions added to the blockchain.

The incentives offered to consensus participants vary between models, and permissionless offers high rewards to justify the cost of competing for rewards. Authorized systems, on the other hand, pay a fixed salary to generally known reviewed agents, and examples of such systems are designed and disclosed. One such method and system is disclosed in US Pat. No. 9,569,771 Method and System For Storage and Retrieval of Blockchain Block Using Galois Fields issued to Lesavich et al. ("771 Patent" or "Lesavich et al."). .. The '771 patent discloses a method and system for securely storing and retrieving one or more blocks for a blockchain using a modified Galois field over a cloud or peer-to-peer communication network. In particular, the '771 patent appears to focus on using Galois Field to enhance security for the storage and retrieval of electronic data on cloud communication networks. The '771 patent discloses or suggests a method for performing automated protocol-based verification of transaction integrity before adding transaction records to the block or directly to the parent blockchain. It doesn't look like it does.

Another example of a related system is described in US Patent Application Serial Number 15 / 086,801, Systems and Methods of Blockchain Transaction Recordation, filed by Fay et al. ("'801 application" or "Fay et al."). The '801 application teaches a computer system that communicates with a distributed blockchain computing system that includes multiple computing nodes. The apparent core elements and steps of the '801 application are to form an exchange of transactions in which two separate transactions are recorded (eg, one transaction from A to B and another from B to A). In addition, there is a transaction monitoring process and generation that relies on determining when it will be validated. If one of the parties fails to submit a transaction, or if the submitted transaction fails, the computer system may generate a new blockchain transaction that cancels one of the two related transactions.

The '801 application appears to rely appropriately on matching separate transaction records, which raises some issues. First, each complete transaction requires at least two component transactions. Not only does this cause the blockchain to grow larger and at a faster pace, but it also requires additional processing time. Second, if the first transaction needs to be invalidated, the completed transaction will require processing of at least four component transactions, further depleting both performance and scalability. Finally, Fay et al.'S process does not provide a method or system for automatically validating completed transactions based on the protocol. For example, in the example of Fay et al., If the initial trading component needs to be flipped or undone, the process will automatically process because it is impossible for the protocol-based process to predict all potential revisions. Not processed.

The automated protocol-based system of the present invention expects and relies on the condition that all trading parties verify the belief that a candidate transaction has or will be made. Therefore, if these conditions are met, there is no need for a consensus incentive to verify the transaction. The precondition of confirmation by the parties to the transaction and the consent of the parties to the specified transaction terms is sufficient verification of the underlying transaction.

The present invention overcomes the shortcomings of the prior art and meets the above needs by providing a system and method for verifying the integrity of a transaction before recording the verified transaction on the electronic blockchain.

A preferred embodiment of the present invention is a protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to an electronic block within the electronic blockchain. The protocol (a) obtains first confirmation that at least one of the first parties agrees to at least one provision of the transaction in order to transfer the asset as part of the transaction. That, (b) a second confirmation that at least one of the second parties has confirmed their respective agreements with at least one clause of the transaction in order to receive the assets as part of the transaction. Obtaining, (c) creating a valid electronic record of the transaction based on the receipts of the first and second confirmations, (d) adding a valid electronic record of the block of electronic transactions, (e) It consists of adding blocks for electronic transactions to the blockchain.

A more preferred embodiment is a method of verifying the integrity of electronic records within a block using a protocol-based instruction set before the block is added to the electronic blockchain, (a) all contained within the block. Verify that the electronic record of the is confirmed by at least one transferor and recipient for at least one underlying transaction if it relates to at least one condition of at least one underlying transaction. And (b) by adding the verified block to the electronic blockchain.

And a more preferred embodiment is a computerized system for verifying the integrity of the electronic records of a transaction before the records are added to the electronic blocks in the electronic blockchain, the system being (a) at least. It consists of one computer server, (b) multiple terminals are associated with each of the first and second parties involved in the transaction, and (c) machines stored on at least one computer server. A computer system characterized in that when a readable instruction is executed, it manages the blockchain data structure associated with the transaction and causes at least one computer server to perform the following steps:
i. Receive transaction specifications from at least one of the first parties involved in the transaction.
ii. Obtain confirmation from at least one of the second parties that the transaction specifications have been verified.
iii. The electronic data transmission request regarding the verification confirmation of the acquired transaction specifications is transmitted to each of the remaining terminals.
iv. Receive verification confirmations of transaction specifications from each of the remaining terminals associated with multiple parties.
v. Create a valid electronic record of the transaction based on the receipt of verification confirmations of multiple parties.
vi. Add validated electronic records to the blocks of transactions that are added to the blockchain data structure.
vii. Add a block of transactions to the blockchain data structure.

For purposes of illustrating the present invention, the accompanying figures show specific aspects and embodiments that are currently preferred. However, the invention is not limited to the exact methods, process steps, or system elements shown in the accompanying figures, but is further disclosed and claimed in accordance with the appended claims. Should be understood.
FIG. 1 is a schematic system diagram showing key participants and elements related to exemplary embodiments of the system of the invention for verifying transactions maintained on an electronic blockchain.
FIG. 2 is another system block diagram of the first system element in the system of the present invention and an exemplary embodiment of the communication flow.
FIG. 3 is an explanatory diagram of a system flowchart of an exemplary embodiment of a particular step in the method of the invention that provides an exemplary overview of the process flow.
FIG. 4 is another system flow chart illustrating an exemplary embodiment of a particular step in the method of the invention, including the registration of assignees and recipients.

Innovative systems, processes, and methods for verifying the accuracy of transactions are disclosed and described through some preferred embodiments and exemplary applications below. The disclosed systems and the methods implemented in those systems, whether tangible or intangible assets, are used to validate transactions involving electronic distributed ledger transactions such as tracking the sale or transfer of assets. Can be applied. Table 1 above outlines the various elements and components involved in validating transactions between two or more parties.

Specific terms are used interchangeably herein to describe certain preferred embodiments of the systems, processes, and methods of the invention. The use of these terms to refer to a particular embodiment or figure should not be construed as limiting the scope of the methodology or system of the invention. At its core, an embodiment of the methodology and system of the invention is shown in FIG. 1, where the assignor (or seller) 70 and the recipient (or recipient or buyer) 90 related participants are computers, respectively. Shown with terminals or computer I / O devices, each device communicating with blockchain server 30 (maintained in cloud 110). For participants, as usual, the term "seller" or "transferor" may include an entity that exchanges an asset for cash or some other form of reward, simply of the asset (such as legal evidence). The storage location may be transferred to another entity. Similarly, the terms "buyer" or "recipient" or "recipient" may include an entity that purchases an asset for cash or some other form of reward, as well as a shipper or courier. They may also receive temporary or final custody of assets (such as legal evidence) from other entities, including intermediaries such as stools.

In addition, the term "asset" refers to any product, material, including data, electronic files, intangible assets (such as domain names, various intellectual property, trademarks, or copyrights), and even virtual assets such as cryptocurrencies. It is intended to cover a wide range of device components, packages, and physical or electronic documents or files. In addition, the term "blockchain" is used here to refer to any technique that makes it possible to create tamper-resistant and undeniable transaction records or ledgers.

The core or key element of the innovative system is to use a protocol-implemented method to validate (or confirm) aspects of the transaction between the transferor and the recipient. More specifically, its core methodology is that (a) the transferor of the asset verifies the terms related to the transaction, (b) the recipient of the asset verifies the terms validated by the transferor, ( c) Includes verifying completed transactions based on the verification of the parties prior to adding the transaction record to the blockchain. The disclosed process and underlying technology will help create an irreversible and verifiable electronic log of the transaction. Electronic logs are verified using secure identifiers that are provided and maintained for each system user. As an example, multiple asset custodians use secure identifiers when creating, transferring, or receiving assets. Such secure identifiers are also used by other parties who may prove the transaction.

A preferred embodiment of this transaction verification technique is particularly applicable and useful for electronic blockchain verification. As a background of the outline, the blockchain is an electronic ledger of transactions. Blockchains and ledgers "grow" when "completed" blocks are added to the blockchain for new transactions (eg, change of storage location or owner). New transactions are grouped into blocks, and each new block goes through a validation process before being added to the blockchain. As mentioned above, in current cryptocurrency blockchain systems, validation of new blocks requires multiple agents, usually unrelated to transactions, to reach consensus on transaction and block accuracy before being added to the block. It is done by a consensus process. As disclosed herein, in various embodiments, the block verification process is based on an automated protocol, which significantly reduces the operational costs of the distributed ledger and improves system performance. (That is, the number of transactions that can be processed in a given amount of time can be significantly increased, and the time required for a transaction to be validated can be significantly reduced).

FIG. 2 is a diagram showing the basic functional components of an exemplary embodiment of System 100 in an asset sales transaction. A seller (eg, a manufacturer) wants to sell a portion of a product to a buyer (eg, one of the authorized distributors). Since the buyer is an authorized distributor of the manufacturer, each business partner is known to other business partners, and there is a relationship of trust between the two. In particular, the parties have a historic relationship that provides both parties that the seller is willing to ship the goods to the buyer and that the buyer trusts to accurately confirm receipt of the shipped goods. There is.

In the embodiment shown in the figure, the transferor uses the terminal 10 to authenticate the person through the authentication service 15 trusted by the recipient. The terminal 10 can be, for example, a desktop computer, a tablet computer, a mobile phone, or other similar type of computer input / output device. The authentication service 15 may be part of the service provided by the blockchain provider or may simply be an independent service accepted by both the recipient and the blockchain provider. Then, the authentication service 15 provides authentication to the blockchain server 30. This allows the transferor access to the blockchain server 30.

Similarly, the recipient authenticates himself / herself through the authentication service 25 using his / her own terminal 20. The recipient authentication service 25 may be the same service as the transferor, or may be another service accepted by the transferor and the blockchain provider. The recipient authentication service 25 provides the authentication to the blockchain server 30 so that the recipient can access the blockchain server 30.

Then, when the transferor ships a particular asset, the transferor uploads the digitally signed transaction 18 (eg, invoice or bill of lading) to the blockchain server 30, where the blockchain server 30 digitally signs the transaction. Upload 18 to blockchain server 30. Digital Transaction 18 includes a list of products included in the transaction, the data of which at least includes the name of the recipient (s) or recipient of the goods on the invoice. Then, the blockchain server 30 notifies the recipient that the transaction is awaiting verification. The digital transaction 18 is not necessarily sent to the recipient, but when the recipient logs in to the blockchain server 30 and views the same digital transaction 18, a record of the transaction accessible to the recipient is notified. .. In some embodiments, as shown in FIG. 2, the blockchain server 30 is (1) to manage the transaction before adding it to the block, (2) to verify the transaction, and (3) to be validated. Separate servers 30a, 30b, to add transactions to the block, (4) to validate the block before adding it to the blockchain, or (5) to add the validated block to the blockchain, It may be composed of 30c.

The recipient then validates the identified and notified transaction on the blockchain server 30. If the goods received by the recipient match the goods included in the digital transaction 18 specified by the transferor, the recipient digitally uploads or signs the digital transaction 28 on the blockchain server 30. The transaction is verified when the recipient uploads or signs the digital transaction. More specifically, the recipient and the transferor are known to each other and have a sufficient relationship of trust, so that the shipped product is received, as evidenced by the transferor and recipient's digital signature. Once confirmed and recorded to be the same as the product, there is no need for further independent verification or confirmation of the transaction. Therefore, this transaction may be added to the block added to the blockchain 35 or may be added directly to the blockchain 35.

In addition, as shown in FIG. 2, the blockchain server 30 and the blockchain 35 are duplicated, and the transactions of the copy 30a, 30b, 30c of the blockchain server 30 and the copy 35a, 35b, 35c of the blockchain 35 are performed in parallel. It may be possible to process it. Such a redundant system architecture eliminates the problem of any component (blockchain server 30 or blockchain 35) becoming a single point of failure, and an automated protocol-based consensus algorithm for each blockchain server 30. Implemented in. Compare and discard the calculation results, or vote out blockchain servers 30 that are different from the majority of the remaining blockchain servers 30. As is known within redundant computer systems, the comparison and voting process is automated, protocol-based, and does not require the intervention of a separate or independent agent.

Alternatively, in a further embodiment of the system of the invention, a plurality of independent blockchain servers may be implemented to handle different asset transactions, such as a blockchain for wine and a blockchain for handbags.

FIG. 3 is a diagram illustrating an exemplary embodiment of the process flow disclosed above in connection with FIG. More specifically, the transferor 115 authenticates his identity to the system via the authentication server 15. The transferor then defines the content of transaction 116, digitally signs transaction document 18 and uploads it to blockchain server 118, and the product or service for which transaction document 18 (eg, invoice) is provided to the recipient. Is accurately reflected. The recipient authenticates the identity from the system 125 to the blockchain server 30 through a separate authentication service 25 or through the same authentication service 25 used by the transferor. Further, in another embodiment of the system process shown in FIG. 4, if there are multiple transferors of the asset element to be transferred, each transferor registers 135 in the system. Similarly, the recipient registers 145 in the system. Registrations 135, 145 occur by using a separate registration service 12 or by using a single agreed registration service 12, as shown in FIG.

The blockchain server 30 then notifies the transaction awaiting recipient approval 132. The recipient reviews and validates details 227 of transaction 18 on the blockchain server 30 (eg, compares the received item with the billed item). If all is well, the recipient adds his digital signature 228 to transaction 28 on blockchain server 30. After obtaining the consent of both parties that the transaction has been approved as specified, the blockchain server 30 may add the transaction to block 332 and a new block 335 to blockchain 35.

What is not depicted in the above example is a situation in which the recipient disagrees with the accuracy of Invoice 18. In such cases, the recipient identifies a discrepancy with the transaction on the blockchain server 30. The blockchain server 30 notifies the transferor that the identified discrepancy requires at least verification by the transferor.

At this stage, the transferor has several options. First, the transferor can modify the previous transaction 18 and sign a new transaction 18a to address the inconsistency pointed out by the recipient and notified by the blockchain server 30. In such cases, the original transaction 18 proposed by the transferor but not approved by the recipient may be recorded in the data structure (which may be within or part of the target blockchain). It does not need to be recorded.

Alternatively, the transferor can negotiate a discrepancy with the recipient. If there is negotiation between the transferor and the recipient and the recipient accepts the original transaction 18, the recipient simply digitally signs the transaction 28. However, if the original transaction 18 is modified in any way, the transferor signs the modified transaction 18a and obtains the recipient's signature before the recorded transaction 18a can be added to the new block. There must be. As mentioned above, in different embodiments, the blockchain server 30 tracks the history of negotiated or modified transactions before being added to the block. This may or may not be recorded. For certain uses, it may be necessary to keep and record records or all negotiated or modified transaction information within the blockchain. However, for other uses, such detailed history, negotiations, and modified transaction information are rarely used or important during final transaction verification. In different embodiments, any of these aspects can be readily implemented and achieved by the disclosed methods and systems. For example, to simplify and reduce the complexity and data retention requirements of the core blockchain, another ledger or record may be created and maintained for negotiation or transaction revision logs.

Preferred embodiments of the systems, processes, and methodologies of the present invention are described and disclosed, but in particular for blockchain transactions prior to being added to the electronic blockchain using specific diagrams and automated protocol-based methodologies. Illustrative representations by reference to exemplary embodiments for verifying consistency are not construed as limiting the scope of the methodology or system of the invention. As an example, the transactional integrity verification system described herein can be easily applied to other non-sale environments. The system of the present invention is equally applied to the transfer of assets even when the transfer of fees, remunerations, expenses, etc. is not required, for example, the transfer of intangible assets such as evidence. An example of such evidence or transfer of intangible assets is the recording of a will at a will registration office. Another exemplary application of the system of the invention relates to use in contracts or transactions where the obligations, responsibilities, and actions of the parties may be automatically monitored and recorded, such as "smart contracts". ing.

It is recognized by those skilled in the art that other modifications, substitutions, or applicable methods are within the true scope and spirit of the invention. Similarly, the appended claims are intended to cover all such modifications, replacements, or applications.

Claims (24)

A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block of the electronic blockchain, the protocol involves the following steps:
a. Obtain first confirmation from at least one first party that each first party has agreed to at least one clause of the transaction in order to transfer the asset as part of the transaction.
b. Obtain a second confirmation from at least one second party that they have confirmed their respective agreements on at least one clause of the transaction in order to receive the asset as part of the transaction.
c. Create a valid electronic record of the transaction based on the receipts of the first and second confirmations.
d. Add verified electronic records to the block of electronic transactions.
e. Add a block of e-commerce to the blockchain. A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, the first of at least one person to transfer assets as part of the transaction. The method of claim 1, comprising the step of registering a party and the step of registering at least one second party who receives the asset as part of a transaction. A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, the first of at least one person to transfer assets as part of the transaction. The method of claim 2, comprising authenticating a party and authenticating at least one second party who receives the asset as part of a transaction. A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, at least one of the first and second confirmations of the transaction. The method of claim 1, which is a digitally signed specification. A protocol-based method for verifying the integrity of electronic records of transactions before records are added to electronic blocks within the electronic blockchain, where assets are stored between at least two parties. The method of claim 1, wherein the transfer takes place in at least one phase of the transaction. Claim 1 is a protocol-based method for verifying the integrity of an electronic record of a transaction and the transfer of assets between the parties to the transaction before the record is added to the electronic block in the electronic blockchain. The method described. Claim 1 is a protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, the sale of assets between the parties to the transaction. The method described. A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, step (a) is at least a portion of the asset as part of the transaction. The method of claim 1, wherein each of the first and second parties agrees to at least one of the terms and conditions of the transaction, with first confirmation from at least one first party to transfer. A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block within the electronic blockchain, and the verified electronic record is added directly to the blockchain, billing. The method described in Item 1. A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, recording the amendment for at least one period of the transaction and related to the amendment. The method of claim 1, wherein the records of the data are recorded separately. A protocol-based method of verifying the integrity of an electronic record of a transaction before the record is added to the electronic block of the electronic blockchain, including the following steps.
a. That all electronic records contained in the block have been confirmed by at least one transferor and receiver for at least one underlying transaction if they are related to at least one condition of at least one underlying transaction. Verify.
b. Add verified blocks to the electronic blockchain. A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, with at least one transferor and recipient for at least one underlying transaction. 11. The method of claim 11, further comprising the step of registering each of the above. A method of verifying the integrity of electronic records within a block using a protocol-based instruction set before the block is added to the electronic blockchain, with at least one transferor and receiver for at least one underlying transaction. 11. The method of claim 11, further comprising the step of authenticating each person. A claim that is a protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, and the verification becomes the specification of the digitally signed transaction. The method described in 11. A protocol-based method for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block in the electronic blockchain, where the confirmation of the electronic record is performed by all parties to the underlying transaction. The method of claim 11. A protocol-based method for verifying the integrity of electronic records of transactions before records are added to electronic blocks within the electronic blockchain, based on the transfer of asset storage between the parties. , The method of claim 11. It is a computerized system for verifying the integrity of electronic records of transactions before records are added to the electronic blocks of the electronic blockchain, and consists of:
a. At least one computer server.
b. A plurality of first transferors and second recipients associated with a transaction are associated with each of the plurality of terminals.
c. A machine-readable instruction stored on at least one computer server that, when executed, manages the blockchain data structures associated with the transaction and causes at least one computer server to perform the following steps:
i. Receive transaction specifications from at least one of the first transferors involved in the transaction.
ii. Obtain confirmation that the transaction specifications have been verified by at least one of the multiple second recipients.
iii. The electronic data transmission request related to the verification confirmation of the acquired transaction specifications is transmitted to each of the remaining terminals.
iv. Receive confirmation of transaction specifications from each of the remaining terminals associated with multiple first and second parties.
v. Create a verified electronic record of the transaction based on the receipt of verification confirmations from multiple first and second parties.
vi. Add validated electronic records to the blocks of transactions that are added to the blockchain data structure.
vii. Add a block of transactions to the blockchain data structure. A computerized system for verifying the integrity of electronic records of a transaction before the records are added to the electronic block of the electronic blockchain, further including the step of registering each authenticated party associated with the transaction. The method of claim 17. A computerized system for verifying the integrity of electronic records of a transaction before the records are added to the electronic block of the electronic blockchain, including further steps to authenticate each authenticated party associated with the transaction. The method of claim 17. A computerized system for verifying the integrity of electronic records of transactions before the records are added to the electronic blocks of the electronic blockchain, and the verified electronic records are digitally signed specifications related to the transaction. A method according to claim 17. A computerized system for verifying the integrity of electronic records of transactions before they are added to the electronic blocks of the electronic blockchain, where transaction specifications are transferred between multiple parties on receipts of assets. A method according to claim 17. Claim, a computerized system for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block of the electronic blockchain, a transfer of assets in which the transaction takes place between multiple parties. The method described in 17. Claim, a computerized system for verifying the integrity of an electronic record of a transaction before the record is added to the electronic block of the electronic blockchain, the sale of an asset in which the transaction takes place between multiple parties. The method described in 17. A computerized system for verifying the integrity of electronic records of transactions before records are added to the electronic block of the electronic blockchain, and the verified electronic records are added directly to the electronic block of the electronic blockchain. , The method of claim 17.

Images