Proof of cache using Argon2d cryptographic hashing in payment processing
Aspects of the disclosure relate to methods, systems, and apparatuses for improving speed of transaction processing in payment systems using a proof of cache system. The proof of cache system may be used to validate transactions using cached keys stored on Directed Acyclic Graph (DAG) nodes that are available. The cached keys may be encrypted using Argon2d cryptographic hashing.
1. A method of validating payment transactions in a payment processing system, the method comprising:
receiving, by the payment processing system comprising one or more processors, a payment transaction and an associated identifier from a user device, wherein the associated identifier corresponds to a unique account identifier;
determining, by the payment processing system, whether the associated identifier is stored in a cache memory of the payment processing system;
in response to determining that the associated identifier is not stored in the cache memory, generating, by the payment processing system, a unique key for the associated identifier, the unique key being encrypted using cryptographic hashing;
transmitting, by the payment processing system, the payment transaction and the unique key to at least one directed acyclic graph (DAG) node of a plurality of DAG nodes in the payment processing system, the at least one DAG node being configured to store the unique key in a cache memory of the at least one DAG node and facilitate transaction validation;
determining, by the payment processing system, one or more DAG nodes from the plurality of DAG nodes, wherein each DAG node of the one or more DAG nodes has at least two-thirds of a total number of keys stored in its respective cache memory;
determining, by the payment processing system, whether a consensus percentage for the payment transaction between the master node and the one or more DAG nodes meets or exceeds a predetermined validation threshold;
validating, by the payment processing system, the payment transaction in response to the consensus percentage meeting or exceeding the predetermined validation threshold, wherein the validation includes updating a blockchain ledger to record a processing status of the payment transaction;
in response to receiving a subsequent payment transaction associated with the associated identifier, determining, by the payment processing system, whether the associated identifier corresponds to a unique key already stored in a cache memory of at least one DAG node of the plurality of DAG nodes;
in response to determining that the associated identifier corresponds to the unique key already stored in the cache memory of the least one DAG node, bypassing the generation of a new key and transmitting, by the payment processing system, the subsequent payment transaction and the unique key to the at least one DAG node for validation;
determining, by the payment processing system, whether a consensus percentage for the subsequent payment meets or exceeds the predetermined validation threshold; and
validating, by the payment processing system, the subsequent payment transaction in response to the consensus percentage meeting or exceeding the predetermined validation threshold, wherein the validation includes updating the blockchain ledger to record a processing status of the subsequent payment transaction.