| CPC H04L 9/34 (2013.01) [G06F 21/54 (2013.01); G06F 21/57 (2013.01); G06F 21/602 (2013.01); G06F 21/6272 (2013.01); G06Q 40/04 (2013.01); H04L 9/0618 (2013.01); H04L 9/3247 (2013.01); H04L 63/0823 (2013.01); G06F 2221/2115 (2013.01); H04L 9/50 (2022.05); H04L 2209/56 (2013.01)] | 20 Claims |
|
1. A distributed computer system comprising:
non-transitory storage configured to store data for a plurality of accounts including an intermediary account, wherein each of the plurality of accounts is associated with a respective private key;
at least one computing node of a distributed ledger computer system that includes a plurality of computing nodes, with each of the plurality of computing nodes configured to store a copy, or a portion thereof, of a distributed ledger data structure;
a computer system that includes at least one hardware processer configured to execute computer executable instructions that perform operations comprising:
processing match data for each of a plurality of matches between different data transaction requests that are each associated with a respective one of the plurality of accounts, wherein the processing of the match data for each corresponding one of the plurality of matches includes:
generating a first new distributed ledger identifier based on the respective private key that is associated with the account of the plurality of accounts that is also associated one of the data transactions requests of the respective match,
generating a second new distributed ledger identifier based on the respective private key that is associated with the account of the plurality of accounts that is associated with another one of the data transactions requests of the respective match, wherein new distributed ledger identifier(s) are generated for each match data that is processed,
generating a first transaction that is from the first new distributed ledger identifier to an intermediary identifier that is associated with the intermediary account, wherein the first transaction includes at least one value that is included in the match data of the corresponding one of the plurality of matches,
generating a second transaction that is from the intermediary identifier to the second new distributed ledger identifier, wherein the second transaction includes the at least one value that is included in the match data of the corresponding one of the plurality of matches, and
submitting the first and second transactions to the distributed ledger computer system to incorporate the first and second transactions into the distributed ledger data structure; and
the at least one computing node of a distributed ledger computer system configured to perform second operations comprising:
receiving the first and second transactions and generating, in connection with incorporation of the first and second transactions into the distributed ledger data structure, a cryptographic proof that is used to validate the first and second transactions;
receiving event data;
validating the event data as coming from an authentic source; and
based on reception of the event data, automatically triggering a further programmatic action or event that is automatically executed, wherein the further programmatic action or event is based on the at least one value included in the first or second transaction for the match data for one of the plurality of matches that has been processed.
|