Abstract: System and method to validate Blockchain transactions in a distributed ledger network is disclosed. The method includes adding, by a computing node in the distributed ledger network, a transaction validation information in a header of a block, wherein the transaction validation information is encrypted. The method further includes transmitting, by the computing node, the block comprising the transaction validation information in the header to a validator computing node in the distributed ledger network. The method includes receiving, by a validator computing node, a transaction validation information in a header of a block from a computing node in the distributed ledger network, wherein the transaction validation information is encrypted and is associated with a Blockchain transaction. The method further includes decrypting and validating the Blockchain transaction, by the validator computing node, based on the transaction validation information in the header of the block in response to the decryption. FIG. 2
Claims:
WE CLAIM
1. A method for enabling validation of Blockchain transactions in a distributed ledger network, the method comprising:
adding, by a computing node in the distributed ledger network, a transaction validation information in a header of a block, wherein the transaction validation information is encrypted; and
transmitting, by the computing node, the block comprising the transaction validation information in the header to a validator computing node in the distributed ledger network, wherein the block is shared with an approver computing node post validation by the validator computing node.
2. The method of claim 1 further comprising receiving the block by an intermediate computing node in the distributed ledger network, wherein the intermediate computing node lies between the computing node and the validator computing node in the distributed ledger network.
3. The method of claim 2 further comprising:
creating, by the intermediate computing node, a modified transaction validation information from the transaction validation information included in the header of the block, wherein the modified transaction validation information is modified based on requirement of an entity associated with a computing node succeeding the intermediate computing node in the distributed ledger network; and
adding, by the intermediate computing node, the modified transaction validation information in a header of an intermediate block associated with the intermediate computing node.
4. The method of claim 3 further comprising:
retaining, by the intermediate computing node, the transaction validation information of the block in the header of the intermediate block; and
creating, by the intermediate computing node, a transaction validation tree comprising traversal relation between the transaction validation information and the modified transaction validation information.
5. The method of claim 4, wherein the transaction validation information forms a root node of the transaction validation tree, when the computing node is an issuer computing node initiating a transaction.
6. The method of claim 1, wherein the transaction validation information comprises account information attributes, customer information attributes, and a block Identifier (ID) associated with the computing node.
7. The method of claim 6, wherein the account information attributes comprise at least one of an account identifier, an account type, an account model, an account classification, an account security, mode of operation, execution type, operative model, primary owner, secondary owner, nominee attributes, last operated account, account active status, approval status, negative balance attributes, or bank remarks.
8. The method of claim 6, wherein the customer information attributes comprise at least one of a customer name, country of origin, allowed country of operations, customer type, customer category, operation type, execution type, customer address, linked accounts, secondary operator, bank remarks, or credit score.
9. The method of claim 6, wherein the validator computing node decrypts the transaction validation information and performs validation based on the account information attributes and customer information attributes in the transaction validation information.
10. A method for validating Blockchain transactions in a distributed ledger network, the method comprising:
receiving, by a validator computing node, a transaction validation information in a header of a block from a computing node in the distributed ledger network, wherein the transaction validation information is encrypted and is associated with a Blockchain transaction;
decrypting, by the validator computing node, the transaction validation information; and
validating the Blockchain transaction, by the validator computing node, based on the transaction validation information in the header of the block in response to the decrypting.
11. The method of claim 10 further comprising creating a validated block, by the validator computing node, wherein a header of the validated block comprises the validated transaction validation information and a transaction validation tree.
12. The method of claim 11, wherein the transaction validation tree comprises:
information associated with the validator computing node and a plurality of computing nodes traversed to reach the validator computing node; and
traversal relation between each of the plurality of computing nodes and the validator computing node, wherein a root node in the transaction validation tree is an issuer computing node that initiated the Blockchain transaction.
13. The method of claim 11 further comprising transmitting the validated block to a receiver computing node for processing the validated block to approve or reject the Blockchain transaction, wherein the Blockchain transaction culminates at the receiver computing node.
14. A computing node in a distributed ledger network for enabling validation of Blockchain transactions in a distributed ledger network, the computing node comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor and having processor instructions stored thereon, causing the processor, on execution to:
add a transaction validation information in a header of a block, wherein the transaction validation information is encrypted; and
transmit the block comprising the transaction validation information in the header to a validator computing node in the distributed ledger network, wherein the block is shared with an approver computing node post validation by the validator computing node.
15. The computing node of claim 14, wherein the processor instructions further cause an intermediate computing node in the distributed ledger network to receive the block, wherein the intermediate computing node lies between the computing node and the validator computing node in the distributed ledger network.
16. The computing node of claim 15, wherein the processor instructions further cause the intermediate computing node to:
create a modified transaction validation information from the transaction validation information included in the header of the block, wherein the modified transaction validation information is modified based on requirement of an entity associated with a computing node succeeding the intermediate computing node in the distributed ledger network; and
add the modified transaction validation information in a header of an intermediate block associated with the intermediate computing node.
17. The computing node of claim 16, wherein the processor instructions further cause the intermediate computing node to
retain the transaction validation information of the block in the header of the intermediate block; and
create a transaction validation tree comprising traversal relation between the transaction validation information and the modified transaction validation information.
18. A validator computing node for validating Blockchain transactions in a distributed ledger network, the computing node comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor and having processor instructions stored thereon, causing the processor, on execution to:
receive a transaction validation information in a header of a block from a computing node in the distributed ledger network, wherein the transaction validation information is encrypted and is associated with a Blockchain transaction;
decrypt the transaction validation information; and
validate the Blockchain transaction based on the transaction validation information in the header of the block in response to decrypting the transaction validation information.
19. The computing node of claim 18, wherein the processor instructions further cause the at least one processor to create a validated block, wherein a header of the validated block comprises the validated transaction validation information and a transaction validation tree.
20. The computing node of claim 19, wherein the processor instructions further cause the processor to transmit the validated block to a receiver computing node for processing the validated block to approve or reject the Blockchain transaction, wherein the Blockchain transaction culminates at the receiver computing node.
Dated this 21st day of November, 2017
R Ramya Rao
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
This disclosure relates generally to distributed ledger networks and more particularly to system and method to validate Blockchain transactions in a distributed ledger network.
| # | Name | Date |
|---|---|---|
| 1 | 201741041664-STATEMENT OF UNDERTAKING (FORM 3) [21-11-2017(online)].pdf | 2017-11-21 |
| 2 | 201741041664-REQUEST FOR EXAMINATION (FORM-18) [21-11-2017(online)].pdf | 2017-11-21 |
| 3 | 201741041664-POWER OF AUTHORITY [21-11-2017(online)].pdf | 2017-11-21 |
| 4 | 201741041664-FORM 18 [21-11-2017(online)].pdf | 2017-11-21 |
| 5 | 201741041664-FORM 1 [21-11-2017(online)].pdf | 2017-11-21 |
| 6 | 201741041664-DRAWINGS [21-11-2017(online)].pdf | 2017-11-21 |
| 7 | 201741041664-DECLARATION OF INVENTORSHIP (FORM 5) [21-11-2017(online)].pdf | 2017-11-21 |
| 8 | 201741041664-COMPLETE SPECIFICATION [21-11-2017(online)].pdf | 2017-11-21 |
| 9 | abstract 201741041664 .jpg | 2017-11-22 |
| 10 | 201741041664-REQUEST FOR CERTIFIED COPY [27-11-2017(online)].pdf | 2017-11-27 |
| 11 | 201741041664-REQUEST FOR CERTIFIED COPY [20-12-2017(online)].pdf | 2017-12-20 |
| 12 | 201741041664-REQUEST FOR CERTIFIED COPY [06-02-2018(online)].pdf | 2018-02-06 |
| 13 | 201741041664-Proof of Right (MANDATORY) [07-02-2018(online)].pdf | 2018-02-07 |
| 14 | Correspondence by Agent_Form1_09-02-2018.pdf | 2018-02-09 |
| 15 | 201741041664-FER_SER_REPLY [11-05-2021(online)].pdf | 2021-05-11 |
| 16 | 201741041664-FER.pdf | 2021-10-17 |
| 17 | 201741041664-US(14)-HearingNotice-(HearingDate-19-02-2024).pdf | 2024-01-18 |
| 18 | 201741041664-POA [23-01-2024(online)].pdf | 2024-01-23 |
| 19 | 201741041664-FORM 13 [23-01-2024(online)].pdf | 2024-01-23 |
| 20 | 201741041664-Correspondence to notify the Controller [23-01-2024(online)].pdf | 2024-01-23 |
| 21 | 201741041664-AMENDED DOCUMENTS [23-01-2024(online)].pdf | 2024-01-23 |
| 22 | 201741041664-Written submissions and relevant documents [05-03-2024(online)].pdf | 2024-03-05 |
| 23 | 201741041664-FORM-26 [05-03-2024(online)].pdf | 2024-03-05 |
| 24 | 201741041664-FORM 3 [05-03-2024(online)].pdf | 2024-03-05 |
| 25 | 201741041664-PETITION UNDER RULE 137 [07-03-2024(online)].pdf | 2024-03-07 |
| 26 | 201741041664-PatentCertificate24-05-2024.pdf | 2024-05-24 |
| 27 | 201741041664-IntimationOfGrant24-05-2024.pdf | 2024-05-24 |
| 1 | SearchStrategy_201741041664E_13-08-2020.pdf |
| 2 | 2020-11-2310-46-51E_23-11-2020.pdf |