Custom Mempool Filtering for Compliant Blockchain Block Creation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain systems face challenges in identifying and preventing transactions associated with criminal activities, as existing technologies lack effective mechanisms to vet and exclude suspicious or criminal addresses, allowing them to be included in block creation, which complicates regulatory compliance and facilitates illicit activities.
Innovation Solution
Implementing a custom mempool protocol that utilizes AddressScores to evaluate and exclude cryptographic identifiers with criminal propensity from block creation, leveraging a filtering node to apply a custom protocol that is compatible with public blockchain protocols, and using a filtering node to exclude transactions with high AddressScores from being included in blocks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a custom mempool protocol with AddressScore filtering is implemented, then the ability to identify and prevent criminal transactions is improved, but the device complexity and protocol implementation difficulty increase
Solution Approach 1:
The patent introduces a filtering node as an intermediary component between the mempool and block creation. This filtering node evaluates cryptographic identifiers using AddressScores and selectively filters transactions before they reach the block creation process, thereby improving transaction security without requiring changes to the core blockchain protocol
Solution Approach 2:
The patent segments the blockchain network into different functional components: a custom mempool protocol layer, a filtering node layer, and the core blockchain protocol layer. This segmentation allows the filtering mechanism to operate independently at the mempool level while maintaining compatibility with the underlying blockchain protocol
2Reliability
If AddressScore filtering is applied to exclude criminal addresses, then regulatory compliance is improved, but the processing time and transaction throughput may be reduced
Solution Approach 1:
The patent performs AddressScore evaluation and filtering of cryptographic identifiers in advance, during the mempool phase, before transactions are selected for block creation. This preliminary action ensures that only compliant transactions proceed to block creation, maintaining regulatory compliance while minimizing impact on overall processing time
3Reliability
If a custom protocol is implemented for filtering nodes, then the ability to vet cryptographic identifiers is improved, but the ease of operation and network compatibility may deteriorate
Solution Approach 1:
The filtering node acts as an intermediary that implements the custom AddressScore evaluation protocol while maintaining compatibility with the public blockchain protocol. It translates the custom filtering requirements into standard protocol operations, ensuring that the enhanced vetting capability does not compromise network compatibility
Solution Approach 2:
The filtering node is designed to perform multiple functions: it evaluates AddressScores, filters cryptographic identifiers, and interfaces with both the custom mempool protocol and the public blockchain protocol. This multi-functionality allows a single component to handle both the enhanced vetting requirements and maintain protocol compatibility
Data Source
AI summary
Systems and methods for processing events transmitted by an application to hashing processors executing a custom mempool protocol that is independent of the public blockchain protocol. Events transmitted by the application are hashed only into blocks with other events transmitted by the application or events with parameters satisfying a screening criterion and are not propagated to mempools of nodes that are not executing the custom mempool protocol. The blocks are appended to the blockchain according to the public blockchain protocol. Thus, application users exercise intentionality over which hashing processors process their events and which other events will be hashed into a block with the users' events.