Computer-implemented system and method for managing a large distributed memory pool in a blockchain network
A computer-implemented method implemented in a blockchain network is described. Validation nodes receive data regarding a newly mined block comprising a plurality of transactions and send a delete request to a distributed memory pool to delete the plurality of transactions from the distributed memory pool. Nodes storing the distributed memory pool store a plurality of transactions, the plurality of transactions forming at least part of a distributed memory pool of transactions waiting to be mined into a block of a blockchain. The computer-implemented method further comprises receiving a delete request from a validation node of the blockchain network, the delete request identifying one or more transactions which have been included in a newly mined block, the delete request indicating that the one or more transactions should be deleted from the distributed memory pool.
1. A computer-implemented method for a node of a blockchain network, the computer-implemented method comprising:
storing, in a distributed hash table (DHT), a plurality of transactions, the plurality of transactions forming at least part of a distributed memory pool of unconfirmed transactions waiting to be mined into a block of a blockchain and confirmed mined transactions; and
receiving a delete request from a validation node of the blockchain network, the delete request identifying one or more confirmed transactions in the distributed memory pool of transactions waiting to be mined which have been included in a newly mined block, the delete request indicating that one or more transactions should be deleted from the distributed memory pool, the method further comprising;
verifying the delete request by authenticating that the validation node is authorized to validate transactions by verifying a digital signature of the validation node and confirming the validation node validated the one or more confirmed transactions identified in the delete request;
marking a transaction as removed from the distributed memory pool when a first threshold number of delete requests is received for the transaction, the method further comprising;
deleting the transaction data from the DHT of the distributed memory pool when a second threshold number of delete requests is received for the transaction, wherein the first and second threshold numbers of delete requests are required to come from a threshold number of different validation nodes in the blockchain network, wherein requiring the threshold numbers of delete requests from different validation nodes implements a consensus mechanism that maintains data consistency in the distributed memory pool.
2. The computer-implemented method according to claim 1 , wherein the second threshold number is larger than the first threshold number.
3. The computer-implemented method according to claim 1 , wherein a transaction is physically removed from the distributed memory pool only after a threshold time has passed since receiving a delete request, during which time no further data requests for the transaction are received.
4. The computer-implemented method according to claim 3 , wherein the threshold time corresponds to one or more blocks being incorporated into the blockchain after the transaction was incorporated into the blockchain for which deletion from the distributed memory pool is requested.
5. The computer-implemented method according to claim 1 , wherein transactions are physically removed from the distributed memory pool in descending order of time passed since receiving a delete request during which time no further data requests for the transaction are received.
6. The computer-implemented method according to claim 1 , further comprising marking the transaction as removed from the distributed memory pool when the transaction depends on a previously removed transaction.
7. The computer-implemented method according to claim 1 , wherein delete requests are stored in a database.
8. The computer-implemented method according to claim 1 , wherein delete requests received from validators which didn't validate the transactions are discarded.
9. The computer-implemented method according to claim 8 , wherein said transactions are discarded only if a check validator option is enabled.
10. The computer-implemented method according to claim 1 , further comprising monitoring a number of data requests for transactions already marked as removed from the distributed memory pool.
11. The computer-implemented method according to claim 1 , further comprising marking a transaction as a candidate for reversion back into the distributed memory pool after a threshold number of data requests is received for a transaction which is marked for removal from the distributed memory pool.
12. The computer-implemented method according to claim 1 , further comprising unmarking a transaction as removed from the distributed memory pool when a revert request is received for the transaction.
13. The computer-implemented method according to claim 1 , further comprising unmarking a transaction as removed from the distributed memory pool when a threshold number of revert requests is received for the transaction.
14. The computer-implemented method according to claim 13 , wherein the threshold number of revert requests is required to come from a threshold number of different validation nodes in the blockchain network.
15. The computer-implemented method according to claim 1 , further comprising sending a message indicating that a transaction has been removed from the distributed memory pool in response to a query for a transaction which has been removed from the distributed memory pool.
16. The computer-implemented method according to claim 15 , wherein said message indicating that a transaction has been removed from the distributed memory pool also indicates a number of delete messages received for the removed transaction.
17. The computer-implemented method according to claim 1 , wherein a transaction comprises three states with respect to the distributed memory pool:
available;
removed; and
physically removed.
18. The computer-implemented method according to claim 1 , wherein delete requests are activated by one or more of:
reception of a mined block;
blockchain reorganization; and
double spending or other form of transaction conflict.
19. The computer-implemented method according to claim 1 , wherein pruning of transactions from the distributed memory pool is activated by one or more of:
manual pruning;
transaction expiration; and
a memory limit being reached for transaction in the distributed memory pool.
20. A node of a blockchain network, the node configured to perform the method of claim 1 .
21. An electronic device comprising:
an interface device;
one or more processor(s) coupled to the interface device; and
a memory coupled to the one or more processor(s), the memory having stored thereon computer executable instructions which, when executed, configure the one or more processor(s) to perform the method of claim 1 .
22. An electronic device comprising:
an interface device;
one or more processor(s) coupled to the interface device; and
a memory coupled to the one or more processor(s), the memory having stored thereon computer executable instructions which, when executed, configure the one or more processor(s) to:
store, in a distributed hash table (DHT), a plurality of transactions, the plurality of transactions forming at least part of a distributed memory pool of unconfirmed transactions waiting to be mined into a block of a blockchain and confirmed mined transactions; and
receive a delete request from a validation node of a blockchain network, the delete request identifying one or more confirmed transactions in the distributed memory pool of transactions waiting to be mined which have been included in a newly mined block, the delete request indicating that one or more transactions should be deleted from the distributed memory pool;
verify the delete request by authenticating that the validation node is authorized to validate transactions by verifying a digital signature of the validation node and confirming the validation node validated the one or more confirmed transactions identified in the delete request;
mark a transaction as removed from the distributed memory pool when a first threshold number of delete requests is received for the transaction; and
delete transaction data from the DHT of the distributed memory pool when a second threshold number of delete requests is received for the transaction, wherein the first and second threshold numbers of delete requests are required to come from a threshold number of different validation nodes in the blockchain network, wherein requiring the threshold numbers of delete requests from different validation nodes implements a consensus mechanism that maintains data consistency in the distributed memory pool.