JP2023015223A - Systems and methods to validate transactions for inclusion in electronic blockchains - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system and a method that validate transactions for inclusion in electronic blockchains capable of avoiding costly consensus mechanisms for validating transactions prior to inclusion onto an underlying electronic blockchain.

SOLUTION: A system which partially utilizes an automated protocol-based method, and which validates consistency of a blockchain transaction prior to inclusion onto an electronic blockchain is implemented within blockchain environments where transacting parties "trust" each other, where the trust is validated by various ways for the transaction parties, executes an automated protocol-based validation of the transaction acknowledged by the transaction parties, and adds a record of the validated transaction to the blockchain.

SELECTED DRAWING: Figure 3

COPYRIGHT: (C)2023,JPO&INPIT

Description

The present invention relates generally to the field of blockchain validation. This process, often referred to as the consensus process, validates the integrity of new transactions, the integrity of electronic blocks that may be integrated before new transactions are added to the blockchain, and updates as a result. to further validate the integrity of the blockchain that was created. More particularly, the present invention relates to systems implemented within a blockchain environment in which parties to a transaction "trust" each other, where trust means (a) knowledge of the other party; a) reliance on available remedies if the transaction is not completed as intended; or (c) one or more of the ability to verify the accuracy and completeness of the transaction prior to validating it. , where automated protocol-based transaction validation operates 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 ledger of transactions that can defend against double-spend attacks from malicious Byzantine generals by actors who may seek to deviate from the accepted protocol. 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 (more precisely, pseudonymity) of transaction parties while avoiding the hegemony of having a ledger "owner", Bitcoin has implemented a decentralized validation (or validation) process. The Bitcoin transaction ledger consensus is secured by a network of miners. These miners are incentivized to participate in the consensus process through a reward schedule for providing consensus confirmation related to blocks being added to the blockchain.

The work of miners, or mining, involves the cost of creating multiple accounts or misappropriating a blockchain for a single miner -- or an attacker -- to try to gain control of the blockchain. This includes proof-of-work computations that are designed to be very difficult and resource complex as they take. By the way, with the current Bitcoin price and reward schedule, miners get about $1.5 million in rewards each day for securing the blockchain, a significant portion of which goes to the processing required to compute proofs. It has been pointed out that only electricity for Given the increasing complexity of the computations required to establish consensus, depending on the history and size of the Bitcoin blockchain, proof-of-work-based consensus protocols can be time-consuming and two-way. We require up to 1 hour to reasonably confirm payment 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 (e.g., many cryptocurrencies) are decentralized to prevent undue influence from any single user, business, or government agency. A decentralized or decentralized marketplace is an incentive for many customers. In fact, many such marketplaces are purposely designed to support anonymous and untrusted participants.

The combination of decentralization and the support of anonymous (or more precisely pseudonymous) actors, by design, means that there is no central authority exercising hegemony over the system, so that such markets and actors are subject to permissionless validation. It results in favoring a system, ie a validation system in which anyone can compete for rewards without requiring anyone's permission. A transaction is authenticated by both parties approving the transaction, typically accomplished by each party applying a digital signature thereby establishing their respective authorization and consent to the transaction. In a blockchain system, transactions with such consent are bundled into blocks that are later added to a potential “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 computation, which is a To verify the validity of new anonymously self-selected blocks.

Permissionless miners are used in Bitcoin and are the original approach envisioned for ensuring the integrity of transaction blocks added to the blockchain log or ledger. Such permissionless consensus systems typically follow the Bitcoin paper by Satoshi Nakamoto. See S. Nakamoto, “Bitcoin: A peer-to-peer electronic cash system,” 2008.

The downside of this consensus approach is that in order to attract people to miners, you have to provide rewards. Additionally, to limit the ability of arbitrary miners or groups of miners to hijack the system and add tainted blocks to the blockchain, Bitcoin and other marketplaces have proof-of-work tests for miners. are being implemented. The cost of passing a proof-of-work test is to create the multiplicity of validators needed to overwhelm the consensus of the system and validate improper transactions, e.g., by brute-force calculations. expensive or difficult enough to make it prohibitively costly. At the same time, these marketplaces must offer miners rewards of sufficient value to induce them to make the necessary investments in passing the proof-of-work test, resulting in a consensus approach. will be costly.

Also, this approach allows you to roll back specific blocks. “Undoing” a particular block of the blockchain ensures the integrity of the entire blockchain in case collusion is discovered in a validated block, but it is not the final validity of the transaction. Further delay in verification.

Other cryptocurrencies attempt to reduce validation costs by implementing different consensus techniques. The Ethereum platform seeks to implement proof-of-stake procedures that do not create computing challenges like proof-of-stake and do not require the costly expenditure of electricity to solve hard problems. do. Ethereum rewards are smaller than what Bitcoin offers, but so is the entry fee.

Compared to open currency, decentralized markets like Bitcoin, corporate marketplaces (such as clearing systems in financial markets) are typically centralized, with anonymous participants, although identified Offers both untrusted participants. Because it is centralized, services can be provided in a more cost-effective permit ledger system. In a sanctioned system, a central authority reviews and assigns system validators, but the validation process remains decentralized among validators, as validators must reach consensus to approve transaction blocks. Rather than paying large sums of money, these identified and vetted validators can be paid a simple salary. Also, because the central authority has greater confidence in authorized agents, the validation process can be shortened, reducing the chances and need for rollbacks. Many new permission applications are being developed using this alternative consensus approach due to its low operating costs. In such systems, transactions by anonymous parties are validated by identified validators, and a scrutiny process and regular audits by a central administrator can further enhance collusion resistance. A description of such a permissive solution is provided by Jae Kwon in his paper "Tendermint: Consensus Without Mining".

Other applications seeking the benefits of blockchain technology involve transactions by parties who have a reason to know and trust each other (e.g. existing binding contracts or other applications that offer relatively predictable recourse). legal infrastructure), there is an opportunity to avoid the consensus process altogether, thereby further reducing operational costs. Another benefit is the ability to hide transaction information from validators for transactions that contain sensitive content. Since no such approach has been proposed at this time, the opportunity is ripe for such a system, and the Covered Disclosure addresses this issue and opportunity.

In preferred embodiments, the systems and methods described provide applications in which transactions are conducted between participants who are known and trusted to each other (or, in the absence of a sufficient level of trust, the participants have sufficient means to remedy any misrepresentation or fraud by one or more parties); The disclosed system and method does not require the intervention of a large number of agents to reach consensus, and assembles blocks added to the blockchain according to a computer-readable protocol to validate transactions. Create an efficient and automated protocol-based system.

A wide range of consensus models have been developed that attempt to address the problem of block validation. For the purposes of the present invention, these various consensus models fall into two criteria: permissionless and permissioned. As can be seen from Table 1 below, both systems can support anonymous (pseudonymous) and known users, but neither model requires users to trust each other. And both offer incentives (such as rewards or salaries) to parties who want to participate in building consensus to validate blocks of transactions added to the blockchain.

The incentives offered to consensus participants differ between models, with permissionless offering higher rewards to justify the cost of competing to earn rewards. Licensed systems, on the other hand, generally pay fixed salaries to known vetted agents, and examples of such systems are designed and disclosed. One such method and system is disclosed in U.S. 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 fields to enhance security for electronic data storage and retrieval on cloud communication networks. The '771 patent discloses or suggests methods for automated, protocol-based validation of the integrity of transactions before adding records of transactions to blocks or directly to the parent blockchain. does not appear to

Another example of a related system is described in US Patent Application Serial No. 15/086,801, Systems and Methods of Blockchain Transaction Recording, filed by Fay et al. ("the '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 (e.g., one transaction from A to B and another transaction from B to A). Second, the monitoring process and generation of transactions that depend on determining when they are validated. If one of the parties fails to submit the 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 several problems. First, each complete transaction requires at least two component transactions. Not only does this cause blockchains to grow larger and at a faster pace, it also requires additional processing time. Second, if the first transaction needs to be invalidated, the completed transaction requires processing at least four component transactions, further draining both performance and scalability. Finally, the Fay et al. 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., when an early transaction component needs to be reversed or undone, the process automatically Not processed.

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

The present invention overcomes the shortcomings of the prior art by providing a system and method for validating the integrity of a transaction prior to recording the validated transaction on an electronic blockchain, meet the needs mentioned above.

A preferred embodiment of the present invention is a protocol-based method for validating the integrity of electronic records of transactions before the records are added to electronic blocks within an electronic blockchain. The protocol provides that (a) to transfer assets as part of a transaction, at least one of the first parties obtains first confirmation that each first party has agreed to at least one term of the transaction; and (b) to receive assets as part of the transaction, at least one of the second parties has provided a second confirmation that the first party's respective agreement to at least one provision of the transaction has been confirmed. (c) creating a validated electronic record of the transaction based on the receipt of the primary and secondary confirmations; (d) blocking the electronic transaction with a validated electronic (e) by adding a block of electronic transactions to a blockchain;

A further preferred embodiment is a method of validating the integrity of electronic records within a block using a protocol-based set of instructions before the block is added to an electronic blockchain, comprising: (a) that all electronic records contained therein have been confirmed by at least one transferor and recipient for at least one underlying transaction, provided that they relate to at least one condition of at least one underlying transaction; (b) adding the validated block to an electronic blockchain;

And a further preferred embodiment is a computerized system for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, the system comprising ( a) consists of at least one computer server, (b) a plurality of terminals are respectively associated with the first and second plurality of parties involved in the transaction, and (c) is stored on the at least one computer server; A computer system that manages a blockchain data structure associated with a transaction when executed machine-readable instructions and causes at least one computer server to perform the following steps:
i. A transaction specification is received from at least one of a plurality of first parties associated with the transaction.
ii. Obtain confirmation from at least one of the plurality of second parties that the transaction specification has been verified.
iii. An electronic data transmission request regarding verification confirmation of the acquired transaction specification is transmitted to each of the remaining terminals.
iv. Receive confirmation of transaction specification verification from each of the remaining terminals associated with the multiple parties.
v. Create a validated electronic record of a transaction based on receipt of verification confirmations from multiple parties.
vi. Add a validated electronic record to a block of transactions that are added to the blockchain data structure.
vii. Add blocks of transactions to the blockchain data structure.

For the purpose of illustrating the invention, the accompanying figures show certain presently preferred aspects and embodiments. However, the present invention is not limited to the precise method, process steps, or system elements as illustrated in the accompanying figures, which are further disclosed and claimed in accordance with the appended claims. should be understood.
FIG. 1 is a schematic system diagram showing the main participants and elements involved in an exemplary embodiment of the present invention system for validating transactions maintained on an electronic blockchain.
FIG. 2 is another system block diagram of an exemplary embodiment of the first system elements and communication flow within the system of the present invention.
FIG. 3 is a system flowchart illustration of an exemplary embodiment of certain steps in the method of the present invention providing an exemplary overview of the process flow.
FIG. 4 is another system flow diagram illustrating an exemplary embodiment of certain steps of the method of the present invention involving registration of transferors and recipients.

Innovative systems, processes, and methods for validating the accuracy of transactions are disclosed and illustrated through several preferred embodiments and exemplary applications below. The disclosed systems and methods implemented in those systems validate transactions, including electronic distributed ledger transactions, such as tracking the sale or transfer of assets, whether they are tangible or intangible assets. An application for confirmation is possible. Table 1 above outlines the various elements and components involved in validating a transaction between two or more parties.

Certain terms are used interchangeably herein to describe certain preferred embodiments of the systems, processes, and methods of the present invention. Use of these terms to refer to particular embodiments or figures 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 present invention is illustrated in FIG. It is shown having a terminal or computer input/output device, each device communicatively connected to a blockchain server 30 (maintained within cloud 110). With respect to participants, by way of example, the terms "seller" or "transferor" may include an entity that exchanges property for cash or some other form of compensation, and is merely a transfer of property (such as legal evidence). Storage may be transferred to another entity. Similarly, the terms “buyer” or “recipient” or “recipient” may include an entity that purchases property for cash or some other form of compensation, or may include a shipper or courier. It may also have temporary or final custody of assets (such as legal evidence) from other entities, including intermediaries such as flights.

Further, the term “property” shall mean any product, material, It is intended to broadly cover device components, packaging, and physical or electronic documents or files. Further, the term "blockchain" is used herein to refer to any technology that allows the creation of a tamper-resistant, non-repudiation record or ledger of transactions.

A core or primary element of the innovative system is the use of protocol-implemented methods to verify (or confirm) aspects of transactions between transferors and recipients. More specifically, the core methodology is that (a) the transferor of the asset verifies the terms associated with the transaction; (b) the transferor verifies the terms verified by the asset receiver; c) including verifying the validity of completed transactions based on verification by the parties prior to adding the transaction record to the blockchain; The disclosed process and underlying technology help create an irreversible and verifiable electronic log of transactions. Electronic logs are verified using a secure identifier provided and maintained for each system user. As an example, multiple asset custodians each use a secure identifier when creating, transferring or receiving assets. Such secure identifiers are also used by other parties who may prove transactions.

This preferred embodiment of the validation technique is particularly applicable and useful for validating electronic blockchains. As background, a blockchain is an electronic ledger of transactions. Blockchains and ledgers “grow” as “completed” blocks corresponding to new transactions (e.g. changes in custody or ownership) are added to the blockchain. New transactions are grouped into blocks, and each new block goes through a validation process before being added to the blockchain for the first time. As mentioned above, in current cryptocurrency blockchain systems, validation of a new block involves multiple agents, usually unrelated to the transaction, reaching a consensus about the accuracy of the transaction and the block before it is added to the block. It is done by a consensus process that needs to be reached. As disclosed herein, in various embodiments, the block validation process is automated and protocol-based, thereby significantly reducing distributed ledger operating costs and improving system performance. Improve (i.e., the number of transactions that can be processed in a given amount of time can be significantly increased, and the time required for transactions to be validated can be significantly reduced).

FIG. 2 is a diagram illustrating the basic functional components of an exemplary embodiment of system 100 in asset sales transactions. A seller (e.g. manufacturer) seeks to sell part of a product to a buyer (e.g. one of its authorized distributors). Since the buyer is an authorized agent of the manufacturer, each business partner is known to other business partners, and there is a relationship of trust between them. In particular, the parties have a historical relationship that provides both parties that the Seller intends to ship the goods to the Buyer and that they trust the Buyer to accurately confirm receipt of the shipped goods. there is

In the illustrated embodiment, the transferor uses the terminal 10 to authenticate himself via an authentication service 15 trusted by the recipient. Terminal 10 may be, for example, a desktop computer, tablet computer, mobile phone, or other similar type of computer input/output device. The authentication service 15 may be part of the services offered by the blockchain provider, or may simply be an independent service accepted by both the recipient and the blockchain provider. Authentication service 15 then provides authentication to blockchain server 30 . Thereby, the transferor permits access to the blockchain server 30.

Similarly, the recipient uses his terminal 20 to authenticate himself via the authentication service 25 . Note that the authentication service 25 of the recipient may be the same service as that of the transferor, or may be a different service accepted by the transferor and the blockchain provider. Recipient authentication service 25 enables recipient access to blockchain server 30 by providing its authentication to blockchain server 30 .

Then, when the transferor ships certain assets, the transferor uploads the electronically signed transaction 18 (e.g., invoice or bill of lading) to the blockchain server 30, and the blockchain server 30 receives the electronically signed transaction. Upload 18 to blockchain server 30. The digital transaction 18 includes a list of products involved in the transaction, the data also including at least the recipient(s) or name of the recipient of the invoiced goods. The blockchain server 30 then notifies the recipient that the transaction is pending validation. The digital transaction 18 is not necessarily sent to the recipient, but the recipient is informed of the record of the transaction accessible by logging into the blockchain server 30 and viewing the same digital transaction 18. . In some embodiments, as shown in FIG. 2, blockchain server 30 (1) manages transactions before adding them to blocks, (2) validates transactions, and (3 ) to add a validated transaction to a block, (4) to validate a block before adding it to the blockchain, or (5) to add a validated block to the blockchain. , may consist of separate servers 30a, 30b, 30c.

The recipient then verifies the identified and notified transaction on the blockchain server 30 . If the goods received by the recipient match the goods included in the transferor-specified digital transaction 18, the recipient digitally uploads or signs the digital transaction 28 on the blockchain server 30. When a recipient uploads or signs a digital transaction, the transaction is validated. More specifically, the recipient and transferor are known to each other and have sufficient trust to ensure that the shipped product has been received, as evidenced by the digital signatures of the transferor and recipient. Once confirmed and recorded to be the same as the product purchased, no further independent validation or confirmation of the transaction is required. Therefore, the transaction may be added to a block that is added to blockchain 35 or added directly to blockchain 35 .

Also, as shown in Fig. 2, the blockchain server 30 and the blockchain 35 are replicated, and each transaction of the copies 30a, 30b, 30c of the blockchain server 30 and the copies 35a, 35b, 35c of the blockchain 35 is executed in parallel. You may enable it to process. Such a redundant system architecture eliminates the problem of any one component (blockchain server 30 or blockchain 35) becoming a single point of failure, with automated protocol-based consensus algorithms running on each blockchain server 30 implemented within. Comparing and discarding calculation results, or voting out blockchain servers 30 that differ from the majority of remaining blockchain servers 30. As is known in redundant computer systems, the comparison and voting process is automated, protocol-based, and does not require the intervention of separate or independent agents.

Alternatively, in further embodiments of the system of the present invention, multiple independent blockchain servers may be implemented to process 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 with respect to FIG. More specifically, transferor 115 authenticates his identity to the system via authentication server 15 . The transferor then defines the content of the transaction 116, digitally signs the transaction document 18 and uploads it to the blockchain server 118, and the transaction document 18 (e.g., invoice) identifies the product or service being offered to the recipient. indicates that it accurately reflects The recipient authenticates its identity from the system 125 to the blockchain server 30 via a separate authentication service 25 or via the same authentication service 25 used by the transferor. Additionally, in another embodiment of the system process shown in FIG. 4, if there are multiple assignees of the asset element to be transferred, each assignor registers 135 with the system. Similarly, the recipient registers 145 with the system. Registrations 135, 145 may occur using separate registration services 12, as shown in FIG. 1, or by using a single agreed-upon registration service 12.

Blockchain server 30 then notifies the transaction awaiting recipient approval 132 . Recipient confirms and verifies transaction 18 details 227 on blockchain server 30 (eg, compares items received and items claimed). If all goes well, the recipient adds his digital signature 228 to the transaction 28 on the blockchain server 30. After obtaining consent from both parties that the transaction has been approved as specified, blockchain server 30 can add the transaction to block 332 and add a new block 335 to blockchain 35 .

Not depicted in the above example is the situation where the recipient disputes 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 discrepancy identified requires at least verification by the transferor.

At this stage, the transferor has several options. First, the transferor can amend the previous transaction 18 and sign a new transaction 18a to address discrepancies noted 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 a data structure (which may be in or part of the subject blockchain), does not need to be recorded.

Alternatively, the transferor may negotiate any discrepancies with the recipient. If there is a 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 altered in any way, the transferor signs the amended transaction 18a and obtains the recipient's signature before the recorded transaction 18a can be added to the new block. There must be. As noted above, in different embodiments, blockchain server 30 tracks the history of negotiated or modified transactions before they are added to blocks. This may or may not be recorded. For certain applications, it may be necessary to keep and record records or all negotiated or amended transaction information within the blockchain. However, in other applications, such detailed history, negotiation, and revised transaction information is of little or no importance during final transaction validation. In different embodiments, any of these aspects can be readily implemented and accomplished by the disclosed methods and systems. For example, separate ledgers or records may be created and maintained for revision logs of negotiations or transactions to simplify and reduce the complexity and data storage requirements of the core blockchain.

While preferred embodiments of the systems, processes, and methodologies of the present invention have been described and disclosed, in particular, blockchain transactions before being added to an electronic blockchain using specific diagrams and automated protocol-based methodologies. Exemplary language by referring to exemplary embodiments to validate consistency is not to be construed as limiting the scope of the methodology or system of the present invention. As an example, the transaction integrity validation system described herein can be readily applied to other non-sale environments. The system of the present invention is equally applicable to the transfer of assets, for example, the transfer of intangible assets such as evidence, even if the transfer of fees, rewards, expenses, etc. is not required. An example of such a transfer of evidence or intangible property is the recording of a will, for example, in the registry office. Another exemplary application of the system of the present invention relates to use in contracts or transactions, e.g. "smart contracts", where the obligations, responsibilities and actions of the parties may be automatically monitored and recorded. ing.

It will be appreciated by those skilled in the art that other modifications, substitutions, or adaptations are possible within the true scope and spirit of the invention. Likewise, the appended claims are intended to cover any such modifications, substitutions or adaptations.
The following is the invention described at the time of filing of this application.
<Claim 1>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block of an electronic blockchain, the protocol includes the following steps:
a. Obtain first confirmation from at least one first party that each first party has agreed to at least one term of the transaction to transfer assets as part of the transaction.
b. Obtain second confirmation from at least one second party that they have confirmed the first party's respective agreement to at least one term of the transaction to receive assets as part of the transaction.
c. Create a validated electronic record of the transaction based on the receipt of the primary and secondary confirmations.
d. Add validated electronic records to blocks of electronic transactions.
e. Add electronic trading blocks to the blockchain.
<Claim 2>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, at least one person transferring assets as part of the transaction and registering at least one second party to receive assets as part of the transaction.
<Claim 3>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, at least one person transferring assets as part of the transaction and authenticating at least one second party to receive assets as part of the transaction.
<Claim 4>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, and at least one of a primary confirmation and a secondary confirmation. 2. The method of claim 1, wherein one is a digitally signed specification of the transaction.
<Claim 5>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, and which takes place between at least two parties. 2. The method of claim 1, wherein the transfer of custody occurs in at least one period of the transaction.
<Claim 6>
Billing, a protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, is the transfer of assets between parties to the transaction. The method of paragraph 1.
<Claim 7>
A claim, which is a protocol-based method for validating the integrity of electronic records of transactions before the records are added to electronic blocks within an electronic blockchain, is the sale of assets between parties to the transaction. The method of paragraph 1.
<Claim 8>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, wherein step (a) 2. The method of claim 1, wherein obtaining first confirmation from at least one first party to transfer at least a portion, each of the first and second parties agreeing to at least one term of the transaction. .
<Claim 9>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain; 2. The method of claim 1, added directly.
<Claim 10>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain; 2. The method of claim 1, wherein records of data relating to are recorded separately.
<Claim 11>
A protocol-based method for validating the integrity of electronic records of transactions before the records are added to electronic blocks of an electronic blockchain, including the following steps:
a. that all electronic records contained in the block have been confirmed by at least one forwarder and receiver for at least one underlying transaction, provided that they relate to at least one condition of at least one underlying transaction; Validate.
b. Add a validated block to an electronic blockchain.
<Claim 12>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, with at least one forwarder for at least one underlying transaction. and a recipient respectively.
<Claim 13>
A method of validating the integrity of electronic records in a block using a protocol-based set of instructions before the block is added to an electronic blockchain, and is transferred to at least one underlying transaction. 12. The method of claim 11, further comprising authenticating each party and recipient.
<Claim 14>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, where the validation is a digitally signed transaction specification. 12. The method of claim 11, wherein:
<Claim 15>
A protocol-based method for validating the integrity of an electronic record of a transaction before the record is added to an electronic block within an electronic blockchain, where confirmation of the electronic record is performed by all parties to the underlying transaction. 12. The method of claim 11, performed.
<Claim 16>
A protocol-based method for validating the integrity of electronic records of transactions before the records are added to electronic blocks within an electronic blockchain, based on the transfer of custody of assets between parties. 12. The method of claim 11, as a transaction.
<Claim 17>
A computerized system for validating the integrity of electronic records of transactions before they are added to the electronic blocks of an electronic blockchain, consisting of:
a. At least one computer server.
b. A plurality of first transferors and second recipients associated with the transaction are associated with each of the plurality of terminals.
c. Machine-readable instructions stored on at least one computer server that, when executed, manage blockchain data structures associated with transactions and cause at least one computer server to perform the following steps:
i. A transaction specification is received from at least one of a plurality of first transferors associated with the transaction.
ii. Obtaining confirmation from at least one of the plurality of secondary recipients that the transaction specification has been verified.
iii. An electronic data transmission request associated with verification confirmation of the acquired transaction specification is transmitted to each of the remaining terminals.
iv. A confirmation of the transaction specification is received from each of the remaining terminals associated with the plurality of first and second parties.
v. Create a validated electronic record of the transaction based on receipt of multiple first and second party verification confirmations.
vi. Add a validated electronic record to a block of transactions that are added to the blockchain data structure.
vii. Add blocks of transactions to the blockchain data structure.
<Claim 18>
A computerized system for validating the integrity of an electronic record of a transaction before the record is added to the electronic blocks of an electronic blockchain, with the steps of registering each authenticated party involved in the transaction. 18. The method of claim 17, further comprising:
<Claim 19>
A computerized system for validating the integrity of an electronic record of a transaction before the record is added to the electronic blocks of an electronic blockchain, which includes the step of authenticating each authenticated party involved in the transaction. 18. The method of claim 17, further comprising:
<Claim 20>
A computerized system for validating the integrity of an electronic record of a transaction before the record is added to the electronic block of an electronic blockchain such that the validated electronic record is digitally linked to the transaction. 18. The method of claim 17, which is a signed specification.
<Claim 21>
A computerized system for validating the integrity of an electronic record of a transaction before the record is added to the electronic block of an electronic blockchain, used for assets whose transaction specifications are transferred between multiple parties. 18. The method of claim 17, which is a receipt.
<Claim 22>
A computerized system for validating the integrity of an electronic record of a transaction before the record is added to the electronic blocks of an electronic blockchain, a transfer of assets in which the transaction takes place between multiple parties. 18. The method of claim 17.
<Claim 23>
A computerized system for validating the integrity of electronic records of transactions before the records are added to the electronic block of an electronic blockchain, where the transaction is a sale of assets between multiple parties. 18. The method of claim 17.
<Claim 24>
A computerized system for validating the integrity of an electronic record of a transaction before the record is added to the electronic block of an electronic blockchain, where the validated electronic record is added to the electronic block of the electronic blockchain. 18. The method of claim 17, added directly to the block.

Claims (12)

A computer-implemented protocol-based method for improving the efficiency and integrity of a blockchain through protocol-based block validation without input from parties unrelated to transactions to be added to the blockchain. , the protocol includes the following steps:
1. Uploading authentication rules to at least one authenticating blockchain node for authenticating a trading entity associated with at least one transaction intended to be added to said blockchain.
2. Uploading validation rules to at least one validating blockchain node for validating the integrity of at least one transaction intended to be added to said blockchain.
3. uploading validation rules to at least one validation blockchain node for creating and validating blocks to be added to the blockchain;
4. Authenticating the credentials of the at least one first trading entity according to the authentication rules by at least one authenticating blockchain node.
5. Authenticating credentials of at least one second trading entity according to the authentication rules by the at least one authenticating blockchain node.
6. receiving a transaction description created by the at least one first transaction entity from at least one computer interface by the at least one validating blockchain node, wherein the transaction description is appendable to the blockchain; Specify the parameters in at least one intended transaction.
7. sending a request for confirmation of the transaction description from the at least one second trading entity to the at least one computer interface by the at least one validating blockchain node, wherein the request is the at least one containing said specified parameters of one transaction;
8. Receive confirmation of transactions made by at least one second transaction entity from at least one computer interface by the at least one validating blockchain node.
9. verifying the at least one transaction by the at least one verifying blockchain node upon receiving confirmation of the transaction description from the at least one second trading entity, wherein the verifying step; is a. verifying the authenticated credentials of the first and second trading entities applicable to the transaction description;
b.
i. the transaction description and confirmation of the transaction description are compared for consistency and determined to be consistent according to the validation rules, or ii. automatically verifying the at least one transaction, wherein confirmation of the transaction description approves the transaction description;
c. creating at least one verified transaction by the at least one verifying blockchain node when automatic verification according to step 9(b) occurs;
including.
10. Sending the at least one verified transaction by the at least one verification blockchain node to the at least one validation blockchain node.
11. verifying the integrity validity of the at least one verified transaction by verifying the origin, content and format of the at least one verified transaction according to the validation rules by the at least one validation blockchain node; confirm.
12. including said at least one validated transaction to be added to said blockchain according to said rules by said at least one validating blockchain node without further input or consent from additional parties. Automatically create blocks where transactions are validated.
13. Automatically adding a validated block of the transaction to the blockchain by the at least one validating blockchain node. 2. The computer-implemented protocol-based method of claim 1, wherein at least one of said transaction description and said confirmation of said transaction description is a digitally signed specification of said at least one transaction. 3. The computer-implemented method of claim 1, wherein the at least one transaction is the creation, purchase, sale, transfer, alteration, transfer of ownership, or transfer of custody of at least a portion of a tangible or intangible asset. protocol-based method. 3. The computer-implemented protocol-based method of claim 1, wherein the at least one transaction creates, moves, adds, modifies, transfers, or sells at least a portion of an asset. 2. The computer of claim 1, wherein a record of modifications to at least one clause of said at least one transaction, or a record of any data associated with said modifications, is recorded as a transaction separate from said at least one transaction. Implemented protocol-based method. 2. The computer-implemented protocol-based method of claim 1, wherein the at least one transaction creates, adds, deletes or modifies at least a portion of information, data or documents. A blockchain that incorporates machine-readable code to improve the operational efficiency and integrity of the blockchain through protocol-based block validation without input from parties unrelated to transactions to be added to the blockchain. wherein the blockchain is
a. a first set of machine-readable instructions stored on at least one blockchain node for managing the blockchain when executed;
b. at least one authenticated blockchain node operatively connected with said;
c. at least one validating blockchain node operatively connected to the blockchain;
d. at least one validation blockchain node operatively connected to the blockchain;
e. at least one computer interface operably coupled to at least one blockchain node;
with
The at least one authentication blockchain node, the at least one verification blockchain node, the at least one validation blockchain node and the at least one computer interface for the blockchain by the following steps: A blockchain that runs authentication, verification and validation protocols.
1. Uploading authentication rules to the at least one authenticating blockchain node for authenticating trading entities associated with at least one transaction intended to be added to the blockchain.
2. Uploading validation rules to the at least one validating blockchain node for validating the integrity of at least one transaction intended to be added to the blockchain.
3. Uploading validation rules to the at least one validation blockchain node for creating and validating blocks to be added to the blockchain.
4. Authenticating authentication information of at least one first trading entity according to the authentication rules by the at least one authenticating blockchain node.
5. Authenticating credentials of at least one second trading entity according to the authentication rules by the at least one authenticating blockchain node.
6. receiving, by the at least one validating blockchain node, a transaction description created by the at least one first transaction entity from at least one computer interface, wherein the transaction description is added to the blockchain; specifies the parameters in at least one transaction for which is intended.
7. sending a request for confirmation of the transaction description from the at least one second trading entity to the at least one computer interface by the at least one validating blockchain node, wherein the request is the at least one containing said specified parameters of one transaction;
8. Confirmation of a transaction made by at least one second trading entity is received by the at least one validating blockchain node from the at least one computer interface.
9. verifying the at least one transaction by the at least one verifying blockchain node upon receiving confirmation of the transaction description from the at least one second trading entity, wherein the verifying step; is a. verifying the authenticated credentials of the first and second trading entities applicable to the transaction description;
b.
i. the transaction description and confirmation of the transaction description are compared for consistency and determined to be consistent according to the validation rules, or ii. automatically verifying the at least one transaction, wherein confirmation of the transaction description approves the transaction description;
c. creating at least one verified transaction by the at least one verifying blockchain node when automatic verification according to step 9(b) occurs;
including.
10. Sending the at least one verified transaction by the at least one verification blockchain node to the at least one validation blockchain node.
11. verifying the integrity validity of the at least one verified transaction by verifying the origin, content and format of the at least one verified transaction according to the validation rules by the at least one validation blockchain node; confirm.
12. including said at least one validated transaction to be added to said blockchain according to said rules by said at least one validating blockchain node without further input or consent from additional parties. Automatically create blocks where transactions are validated.
13. Automatically adding a validated block of the transaction to the blockchain by the at least one validating blockchain node. 8. The blockchain of claim 7, wherein the at least one transaction description and the confirmation of the transaction description comprise digitally signed specifications associated with the at least one transaction. 9. The digitally signed specification of claim 8, wherein the digitally signed specification is associated with at least a portion of assets transferred between the at least one first trading entity and the at least one second trading entity. blockchain. wherein the at least one transaction creates, buys, sells, transfers at least a portion of a tangible or intangible asset between the at least one first trading entity and the at least one second trading entity; The blockchain according to claim 7, which is change, transfer of ownership, or transfer of storage destination. 8. The blockchain of claim 7, wherein said at least one transaction is a sale of at least a portion of an asset between said at least one first trading entity and said at least one second trading entity. of said at least one blockchain node, said at least one verification blockchain node, said at least one authentication blockchain node, said at least one validation blockchain node and said at least one computer interface 8. The computing device of claim 7, wherein at least two are single blockchain nodes.

Images