Granted Patent B2

US 12,505,430 · App. 18/140,778 · Granted Dec 23, 2025

Inventor: Shishir Singh (New York, NY)

Assignee: CITIBANK, N.A.

G06Q20/3827G06Q20/3674H04L9/0637H04L9/0643H04L9/50H04L2209/56

Abstract

Claims (72)

1. A system comprising:

a first set of nodes each corresponding to a computing device having a processor and memory to store data, the first set of nodes configured to maintain a first blockchain, wherein one or more computing devices of the first set of nodes are configured to:

receive, from a second set of nodes maintaining a second blockchain, a first plurality of event requests each corresponding to a pending event between a first computing device and a second computing device, each of the first plurality of event requests comprising a different first set of event attributes from a different block instance of the second blockchain and corresponding to the pending event, wherein the pending event corresponds to a transfer of a digital asset from the second blockchain to a third blockchain;

append a first block instance to the first blockchain for each of the first plurality of event requests from the second set of nodes, each first block instance comprising a different first set of event attributes of the first plurality of event requests from a different block instance of the second blockchain;

receive, from a third set of nodes maintaining the third blockchain, a second plurality of event requests each corresponding to the pending event between the first computing device and the second computing device, each of the second plurality of event requests comprising a different second set of event attributes from a different block instance of the third blockchain and corresponding to the pending event corresponding to the transfer of the digital asset from the second blockchain to the third blockchain;

append a second block instance to the first blockchain for each of the second plurality of event requests from the third set of nodes, each second block instance comprising a different second set of event attributes of the second plurality of event requests from a different block instance of the third blockchain;

execute an electronic protocol stored in a block instance of the first blockchain to:

identify first block instances for the first plurality of event requests and second block instances for the second plurality of event requests appended to the first blockchain;

retrieve a first sets of event attributes from the first block instances and a second sets of event attributes from the second block instances; and

compare the first sets of event attributes retrieved from the first block instances with the second sets of event attributes retrieved from the second block instances respectively corresponding to the first block instances;

responsive to determining, based on the comparison, that a first set of event attributes retrieved from a first block instance of the first block instances does not match a second set of event attributes retrieved from a second block instance of the second block instances corresponding to the first block instance, transmit a message to the first computing device or the second computing device identifying a difference between the first set of event attributes and the second set of event attributes;

receive an updated first set of event attributes or an updated second set of event attributes from the first computing device or the second computing device, the updated first set of event attributes or the updated second set of event attributes updated based on the difference; and

responsive to determining that each of the first sets of event attributes matches a corresponding second set of event attributes based at least on the updated first set of event attributes or the updated second set of event attributes:

append a match block instance identifying the digital asset and corresponding to the pending event to the first blockchain; and

communicate with the second set of nodes to complete the pending event through the second blockchain and with the third set of nodes to complete the pending event through the third blockchain.

2. The system of claim 1 , wherein the one or more computing devices of the first set of nodes are further configured to:

determine the first block instance corresponds to the second block instance based on an identification of the pending event in the first block instance and the second block instance and responsive to the first block instance comprising event attributes of a same type as the second block instance;

retrieve the first set of event attributes from the first block instance and the second set of event attributes from the second block instance; and

compare the retrieved first set of event attributes with the retrieved second set of event attributes.

3. The system of claim 2 , wherein the one or more computing devices are configured to compare the first set of event attributes with the second set of event attributes by executing the electronic protocol stored on the first blockchain.

4. The system of claim 1 , wherein the one or more computing devices of the first set of nodes are further configured to:

determine a third block instance corresponds to a fourth block instance;

retrieve data from the third block instance and the fourth block instance; and

append a fifth block instance corresponding to the pending event to the first blockchain responsive to the retrieved data from the third block instance matching the retrieved data from the fourth block instance.

5. The system of claim 4 , wherein the first block instance and the second block instance each correspond to a set of event attributes of a first type, and the third block instance and the fourth block instance each correspond to a set of event attributes of a second type.

6. The system of claim 1 , wherein the pending event corresponds to an account associated with the first computing device transferring the digital asset to an account associated with the second computing device.

7. The system of claim 1 , wherein the first set of event attributes of the first block instance is generated at a first computer corresponding to the first computing device and the second set of event attributes of the second block instance is generated at a second computer corresponding to the second computing device.

8. The system of claim 7 , wherein the one or more computing devices of the first set of nodes are configured to:

append a second match block instance corresponding to the pending event to the first blockchain responsive to a third set of event attributes from a third block instance matching a fourth set of event attributes from a fourth block instance,

wherein the third set of event attributes of the third block instance is generated at a third computer corresponding to the first computing device and the fourth set of event attributes of the fourth block instance is generated at a fourth computer corresponding to the second computing device.

9. The system of claim 1 , wherein the pending event is initiated by the first computing device in communication with one or more servers, and

wherein the one or more servers transmit a message to the second set of nodes maintaining the second blockchain responsive to determining an asset being exchanged in the pending event is stored in the second blockchain.

10. The system of claim 1 , further comprising:

the second set of nodes and the third set of nodes,

wherein the second set of nodes transmit the first plurality of event requests to the first set of nodes by, for each of the first plurality of event requests:

appending a first sub-event block instance to the second blockchain comprising a first set of event attributes of the event request of the first plurality of event requests; and

executing a first electronic protocol stored on the second blockchain to transmit the event request comprising the first set of event attributes from the first sub-event block instance to the first set of nodes, and

wherein the third set of nodes transmit the second plurality of event requests to the first set of nodes by, for each of the second plurality of event requests:

appending a second sub-event block instance to the third blockchain comprising a second set of event attributes of the event request of the second plurality of event requests; and

executing a second electronic protocol stored on the third blockchain to transmit the event request comprising the second set of event attributes from the second sub-event block instance to the first set of nodes.

11. A method comprising:

receiving, by one or more computing devices of a first set nodes configured to maintain a first blockchain and from a second set of nodes maintaining a second blockchain, a first plurality of event requests each corresponding to a pending event between a first computing device and a second computing device, each of the first plurality of event requests comprising a different first set of event attributes from a different block instance of the second blockchain and corresponding to the pending event, wherein the pending event corresponds to a transfer of a digital asset from the second blockchain to a third blockchain;

appending, by the one or more computing devices, a first block instance to the first blockchain for each of the first plurality of event requests from the second set of nodes, each first block instance comprising a different first set of event attributes of the first plurality of event requests from a different block instance of the second blockchain;

receiving, by the one or more computing devices and from a third set of nodes maintaining a fourth blockchain associated with the third blockchain, a second plurality of event requests each corresponding to the pending event between the first computing device and the second computing device, each of the second plurality of event requests comprising a different second set of event attributes from a different block instance of the third blockchain and corresponding to the pending event corresponding to the transfer of the digital asset from the second blockchain to the third blockchain;

appending, by the one or more computing devices, a second block instance to the first blockchain for each of the second plurality of event requests from the third set of nodes, each second block instance comprising a different second set of event attributes of the second plurality of event requests from a different block instance of the third blockchain;

executing, by the one or more computing devices, an electronic protocol stored in a block instance of the first blockchain to:

identify first block instances for the first plurality of event requests and second block instances for the second plurality of event requests appended to the first blockchain;

retrieve a first sets of event attributes from the first block instances and a second sets of event attributes from the second block instances; and

compare the first sets of event attributes retrieved from the first block instances with the second sets of event attributes retrieved from the second block instances respectively corresponding to the first block instances;

responsive to determining, based on the comparison, that a first set of event attributes retrieved from a first block instance of the first block instances does not match a second set of event attributes retrieved from a second block instance of the second block instances corresponding to the first block instance, transmitting, by the one or more computing devices, a message to the first computing device or the second computing device identifying a difference between the first set of event attributes and the second set of event attributes;

receiving, by the one or more computing devices, an updated first set of event attributes or an updated second set of event attributes from the first computing device or the second computing device, the updated first set of event attributes or the updated second set of event attributes revised based on the difference; and

responsive to determining that each of the first sets of event attributes matches a corresponding second set of event attributes based at least on the updated first set of event attributes or the updated second set of event attributes:

appending, by the one or more computing devices, a match block instance identifying the digital asset and corresponding to the pending event to the first blockchain; and

communicating, by the one or more computing devices, with the second set of nodes to complete the pending event through the second blockchain and with the third set of nodes to complete the pending event through the third blockchain.

12. The method of claim 11 , further comprising:

determining, by the one or more computing devices, the first block instance corresponds to the second block instance based on an identification of the pending event in the first block instance and the second block instance and responsive to the first block instance comprising event attributes of a same type as the second block instance;

retrieving, by the one or more computing devices, the first set of event attributes from the first block instance and the second set of event attributes from the second block instance; and

comparing, by the one or more computing devices, the retrieved first set of event attributes with the retrieved second set of event attributes.

13. The method of claim 12 , wherein comparing the first set of event attributes with the second set of event attributes comprises executing, by the one or more computing devices, the electronic protocol stored on the first blockchain.

14. The method of claim 11 , further comprising:

determining, by the one or more computing devices, a third block instance corresponds to a fourth block instance;

retrieving, by the one or more computing devices, data from the third block instance and the fourth block instance; and

appending, by the one or more computing devices, a fifth block instance corresponding to the pending event to the first blockchain responsive to the retrieved data from the third block instance matching the retrieved data from the fourth block instance.

15. The method of claim 14 , wherein the first block instance and the second block instance each correspond to a set of event attributes of a first type, and the third block instance and the fourth block instance each correspond to a set of event attributes of a second type.

16. The method of claim 11 , wherein the pending event corresponds to an account associated with the first computing device transferring the digital asset to an account associated with the second computing device.

17. The method of claim 11 , wherein the first set of event attributes of the first block instance is generated at a first computer corresponding to the first computing device and the second set of event attributes of the second block instance is generated at a second computer corresponding to the second computing device.

18. The method of claim 17 , further comprising:

appending, by the one or more computing devices, a second match block instance corresponding to the pending event to the first blockchain responsive to a third set of event attributes from a third block instance matching a fourth set of event attributes from a fourth block instance,

wherein the third set of event attributes of the third block instance is generated at a third computer corresponding to the first computing device and the fourth set of event attributes of the fourth block instance is generated at a fourth computer corresponding to the second computing device.

19. The method of claim 11 , wherein the pending event is initiated by the first computing device in communication with one or more servers, and

wherein the one or more servers transmit a message to the second set of nodes maintaining the second blockchain responsive to determining an asset being exchanged in the pending event is stored in the second blockchain.

20. The method of claim 19 , wherein the one or more servers select the second set of nodes from a plurality of sets of nodes each maintaining a different blockchain responsive to the second set of nodes maintaining the second blockchain that stores the asset being exchanged in the pending event.

Assignments (1)

Continuity (4)

References Cited (53)