Hybrid blockchain network for dynamic cross-account transfer operations
View Patent ↗This document describes techniques for performing dynamic transfer operations based on a blockchain ledger without needing to perform computationally expensive cryptographic hash reversal operations. In some cases, an example system stores a hashed identifier on a blockchain ledger, along with one or more ledger values like an account balance value and/or a payout amount value. The example system may store un-hashed sensitive backend data on a private backend database. When the example system receives an event notification, the system extracts an identifier from the notification, hashes the identifier, and uses the hashed identifier to retrieve the blockchain ledger. The system then determines whether the ledger value(s) satisfy a condition. If so, the system uses the hashed identifier stored on the blockchain ledger to query the backend database for an account identifier, maps the account identifier to a blockchain wallet, and executes a blockchain transfer operation to the blockchain wallet.
1 . A method comprising:
receiving, by a processor, a first event notification; and
based on receiving the first event notification, executing, by the processor, an automated routine characterized by a first condition and a first transfer operation, wherein the automated routine is configured to:
retrieve an identifier represented by the first event notification,
apply a one-way hash function to the identifier to determine a hashed identifier,
determine, based on the hashed identifier, a retrieval key,
retrieve, based on the retrieval key, a distributed record comprising the retrieval key and a first value,
determine, based on the first condition and the first value, to execute the first transfer operation,
based on determining to execute the first transfer operation, query a backend system, using the retrieval key, to retrieve first data, wherein the first data maps the retrieval key to a first account identifier,
map, based on the first data, the retrieval key to the first account identifier;
based on mapping the retrieval key to the first account identifier, execute the first transfer operation in relation to the first account identifier and based on the first value,
based on executing the first transfer operation, determine an execution outcome, and
update the first value stored on the distributed record based on the execution outcome.
2 . The method of claim 1 , wherein the first condition represents a first threshold for the first value.
3 . The method of claim 1 , wherein executing the first transfer operation comprises:
determining, based on the automated routine, a transfer ratio;
determining a second value by applying the transfer ratio to the first value; and
executing the first transfer operation by performing a transfer of the second value to the first account identifier.
4 . The method of claim 1 , further comprising:
receiving, by the processor, a registration request representing the identifier, the first value, and the first account identifier;
based on receiving the registration request, determining, by the processor, the retrieval key based on the identifier; and
based on determining the retrieval key:
creating, by the processor, the distributed record based on the retrieval key and the first value, and
storing, by the processor, the retrieval key and the first account identifier on the backend system.
5 . The method of claim 1 , wherein receiving the first event notification comprises:
receiving the first event notification from a trigger system, wherein the trigger system is configured to:
query a database to determine an event record,
map the event record to the identifier,
based on mapping the event record to the identifier, determine the first event notification based on the event record, and
provide the first event notification to the processor.
6 . The method of claim 1 , further comprising:
based on updating the first value, receiving, by the processor, a second event notification representing the identifier; and
based on receiving the first event notification, executing, by the processor, the automated routine, wherein the automated routine is configured to:
apply the first condition to the first value to refrain from executing the first transfer operation.
7 . The method of claim 1 , wherein the backend system stores the identifier, and wherein executing the first transfer operation comprises:
retrieving the identifier; and
executing the first transfer operation based on the identifier and the first account identifier.
8 . The method of claim 1 , wherein;
retrieving the distributed record comprises querying a first database associated with a blockchain network,
querying the backend system comprises querying a second database associated with the backend system,
the first database is a publicly accessible distributed database that is configured to store non-sensitive data comprising the hashed identifier, and
the second database is a private database.
9 . A computing system, comprising:
a processor; and
memory storing computer-executable instructions that, when executed by the processor, cause the computing system to perform operations comprising:
receiving a first event notification; and
based on receiving the first event notification, executing an automated routine characterized by a first condition and a first transfer operation, wherein the automated routine is configured to:
retrieve an identifier represented by the first event notification,
apply a one-way hash function to the identifier to determine a hashed identifier,
determine, based on the hashed identifier, a retrieval key,
retrieve, based on the retrieval key, a distributed record comprising the retrieval key and a first value,
determine, based on the first condition and the first value, to execute the first transfer operation,
based on determining to execute the first transfer operation, query a backend system, using the retrieval key, to retrieve first data, wherein the first data maps the retrieval key to a first account identifier,
map, based on the first data, the retrieval key to the first account identifier;
based on mapping the retrieval key to the first account identifier, execute the first transfer operation in relation to the first account identifier and based on the first value,
based on executing the first transfer operation, determine an execution outcome, and
update the first value stored on the distributed record based on the execution outcome.
10 . The computing system of claim 9 , wherein the first condition represents a first threshold for the first value.
11 . The computing system of claim 9 , wherein executing the first transfer operation comprises:
determining, based on the automated routine, a transfer ratio;
determining a second value by applying the transfer ratio to the first value; and
executing the first transfer operation by performing a transfer of the second value to the first account identifier.
12 . The computing system of claim 9 , the operations further comprising:
receiving, by the processor, a registration request representing the identifier, the first value, and the first account identifier;
based on receiving the registration request, determining, by the processor, the retrieval key based on the identifier; and
based on determining the retrieval key:
creating, by the processor, the distributed record based on the retrieval key and the first value, and
storing, by the processor, the retrieval key and the first account identifier on the backend system.
13 . The computing system of claim 9 , wherein receiving the first event notification comprises:
receiving the first event notification from a trigger system, wherein the trigger system is configured to:
query a database to determine an event record,
map the event record to the identifier,
based on mapping the event record to the identifier, determine the first event notification based on the event record, and
provide the first event notification to the processor.
14 . The computing system of claim 9 , the operations further comprising:
based on updating the first value, receiving, by the processor, a second event notification representing the identifier; and
based on receiving the first event notification, executing, by the processor, the automated routine, wherein the automated routine is configured to:
apply the first condition to the first value to refrain from executing the first transfer operation.
15 . The computing system of claim 9 , wherein the backend system stores the identifier, and wherein executing the first transfer operation comprises:
retrieving the identifier; and
executing the first transfer operation based on the identifier and the first account identifier.
16 . One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by a processor, cause the processor to perform operations, comprising:
receiving a first event notification; and
based on receiving the first event notification, executing an automated routine characterized by a first condition and a first transfer operation, wherein the automated routine is configured to:
retrieve an identifier represented by the first event notification,
apply a one-way hash function to the identifier to determine a hashed identifier,
determine, based on the hashed identifier, a retrieval key,
retrieve, based on the retrieval key, a distributed record comprising the retrieval key and a first value,
determine, based on the first condition and the first value, to execute the first transfer operation,
based on determining to execute the first transfer operation, query a backend system, using the retrieval key, to retrieve first data, wherein the first data maps the retrieval key to a first account identifier,
map, based on the first data, the retrieval key to the first account identifier;
based on mapping the retrieval key to the first account identifier, execute the first transfer operation in relation to the first account identifier and based on the first value,
based on executing the first transfer operation, determine an execution outcome, and
update the first value stored on the distributed record based on the execution outcome.
17 . The one or more non-transitory computer-readable media of claim 16 , wherein the first condition represents a first threshold for the first value.
18 . The one or more non-transitory computer-readable media of claim 16 , wherein executing the first transfer operation comprises:
determining, based on the automated routine, a transfer ratio;
determining a second value by applying the transfer ratio to the first value; and
executing the first transfer operation by performing a transfer of the second value to the first account identifier.
19 . The one or more non-transitory computer-readable media of claim 16 , the operations further comprising:
receiving, by the processor, a registration request representing the identifier, the first value, and the first account identifier;
based on receiving the registration request, determining, by the processor, the retrieval key based on the identifier; and
based on determining the retrieval key:
creating, by the processor, the distributed record based on the retrieval key and the first value, and
storing, by the processor, the retrieval key and the first account identifier on the backend system.
20 . The one or more non-transitory computer-readable media of claim 16 , wherein receiving the first event notification comprises:
receiving the first event notification from a trigger system, wherein the trigger system is configured to:
query a database to determine an event record,
map the event record to the identifier,
based on mapping the event record to the identifier, determine the first event notification based on the event record, and
provide the first event notification to the processor.