IP Library › Granted Patent US 11,611,438

Granted Patent B2

US 11,611,438 · App. 17/706,438 · Granted Mar 21, 2023

Computer network systems for cryptographically-secured, token-based operations and methods of use thereof

Inventors: Horacio Barakat (New York, NY); Harsha Kolagani (Hyderabad, IN); Kishore Seshagiri (Hyderabad, IN); Ashfaq Shaik (Hyderabad, IN); John Garahan (Annandale, NJ); Vijay Mayadas (New York, NY); Michael McMahon (Jersey City, NJ)

Assignee: Broadridge Financial Solutions, Inc.

H04L9/3213 G06F16/162 H04L9/3236 H04L9/38 H04L9/50

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 11,611,438
App. No.: 17/706,438
Granted: Mar 21, 2023
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

Systems and methods of the present disclosure enable reversible blockchain operations. An operation-reverse operation pair specifies an operation for exchange of a first token for a second token, and a reverse operation for return of the second token for the first token upon at least one condition being satisfied. A self-executing software container (SESC) executes the operation-reverse operation pair according to the condition by detecting a transfer of the first token into a first segregated data structure, and a transfer of the second token from a second token storage to a first token storage. The SESC initiates a transfer of the first token from the first segregated data structure to a second segregated data structure in response to the transfer of the second token. Upon detecting a reverse operation matching the condition, the SESC initiates a transfer of the first token back to the first segregated data structure.

Claims (115)

1. A method comprising:

receiving, by at least one processor, an activity initiation request from a first client device associated with a first user;

wherein the activity initiation request comprises:

at least one operation for exchange of a first token type for a second token type, and

at least one reverse operation for exchange of the second token type for the first token type upon at least one condition being satisfied;

wherein the first token type comprises a first cryptographic hash on a blockchain;

wherein the second token type comprises a second cryptographic hash on the blockchain;

wherein the first client device is a node on the blockchain;

receiving, by the at least one processor, an activity initiation response from a second client device associated with a second user;

wherein the activity initiation response indicates an acceptance of the activity initiation request, the acceptance corresponding to the at least one operation and the at least one reverse operation within the activity initiation request;

wherein the second client device is a node on a blockchain;

generating, by the at least one processor, at least one self-executing software container (SESC) on the blockchain;

wherein the at least one SESC comprises a plurality of instructions for execution of the at least one operation and the at least one reverse operation based at least in part on the at least one condition;

wherein the plurality of instructions of the at least one SESC causes the at least one processor to:

detect a transfer of the first token type into a first segregated token storage;

wherein the first segregated data structure is associated with a first segregated data structure of a third-party entity;

wherein the first client device has permissions to access the first segregated token storage;

wherein the first segregated data structure comprises a schema configured to store the first token type;

detect a transfer of the second token type from a second token storage associated with the second client device to a first token storage associated with the first client device;

automatically initiate a transfer of the first token type from the first segregated data structure to a second segregated token storage in response to the transfer of the second token type;

wherein the second segregated token storage is associated with a second segregated data structure of the third-party entity;

wherein the second client device has condition-dependent permissions to access the second segregated token storage;

wherein the first segregated data structure comprises a schema configured to store the first token type;

detect the at least one reverse operation matching the at least one condition; and

initiate a transfer via the detected at least one reverse operation of the first token type from the second segregated token storage back to the first segregated token storage.

2. The method of claim 1 , wherein the activity initiation request comprises activity parameters comprising at least one of:

a first token transfer amount associated with the first token type,

a second token transfer amount associated with the second token type,

at least one condition identifier identifying the at least one condition,

a time identifier identifying a time limit to satisfy the at least one condition,

a first client device identifier identifying the first client device, and

a second client device identifier identifying the second client device.

3. The method of claim 2 , further comprising:

generating, by the at least one processor, at least one instruction of the plurality of instructions based at least in part on each activity parameter of the activity parameters; and

generating, by the at least one processor, the at least one SESC based at least in part on the plurality of instructions.

4. The method of claim 2 , further comprising:

determining, by the at least one processor, a first token stored amount of the first token type in a first token storage associated with the first client device;

generating, by the at least one processor, a segregated first token type having the first token transfer amount;

generating, by the at least one processor, a stored first token type having an updated first token stored amount of the first token stored amount less the first token transfer amount;

deleting, by the at least one processor, the first token stored amount of the first token type from the first token storage;

adding, by the at least one processor, the updated first token stored amount to the first token storage; and

transferring, by the at least one processor, the first token transfer amount of the first token type into a first segregated token storage.

5. The method of claim 1 , further comprising:

receiving, by the at least one processor, an asset-linked data segregation message comprising an indication of a movement of a first asset-linked data into the first segregated data structure; and

generating, by the at least one processor, the first token type in the first segregated token storage to represent the first asset-linked data in the first segregated data structure.

6. The method of claim 1 , further comprising:

receiving, by the at least one processor, an asset-linked data provision message comprising an indication of a provision of a second asset-linked data in a second client data structure;

wherein the second client data structure comprises a schema configured to store the second asset-linked data; and

generating, by the at least one processor, the second token type in a second client token storage to represent the second asset-linked data in the second client data structure.

7. The method of claim 1 , wherein the first client device, the second client device and the third-party entity are associated with a particular entity; and

wherein the first segregated data structure and the second segregated data structure are the same segregated data structure.

8. The method of claim 1 , further comprising instructing, by the at least one processor, at least one display associated with the first client device to render a second token type receipt notification indicating receipt of the second token type in the first token storage.

9. The method of claim 8 , further comprising:

receiving, by the at least one processor, at least one first token type return request from the first client device;

wherein the first token type return request comprises a return of the second token type according to the at least one condition; and

initiating, by the at least one processor, the at least one reverse operation.

10. The method of claim 1 , further comprising instructing, by the at least one processor, at least one display associated with the first client device to render a first token type return notification indicating receipt of the first token type in the first segregated token storage.

11. A system comprising:

at least one processor configured to execute software instructions, wherein the software instructions, upon execution, cause the at least one processor to perform steps to:

receive activity initiation request from a first client device associated with a first user;