Zero-Knowledge Proof P2P Transaction System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing secure transactional systems in P2P networks require specialized hardware for executing Wallet Programs, limiting their execution to specific hardware nodes and restricting their flexibility and scalability.

Innovation Solution

A secure P2P transactional system that enables Wallet Programs to be executed on conventional data processing equipment using Zero-Knowledge Proof (ZKP) mechanisms, allowing non-secure processors to generate and verify proofs, and incorporating a Crypto Memory Management Unit (CMMU) for secure handling of units of account, enabling execution on conventional processors and ensuring the integrity and authenticity of transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If specialized hardware is used for executing Wallet Programs, then security and integrity of transactions are ensured, but flexibility and scalability are limited

Engineering Contradiction:
Improvesecurity and integrity of transactionsVSAvoidflexibility and scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent uses zero-knowledge proofs to create a cryptographic copy or representation of the secure execution state. Instead of requiring actual specialized hardware execution, the system verifies execution through mathematical proofs that replicate the security guarantees of hardware execution on conventional processors, enabling flexibility while maintaining security

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces the mechanical hardware-based execution model (specialized WN hardware) with a software-based zero-knowledge proof verification model. This substitution allows conventional processors to achieve the same security properties as specialized hardware through cryptographic verification rather than physical constraints

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If Wallet Programs are executed on conventional processors, then flexibility and scalability are enhanced, but security and integrity may be compromised

Engineering Contradiction:
Improveflexibility and scalabilityVSAvoidsecurity and integrity of transactions
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces zero-knowledge proofs as an intermediary mechanism between conventional processors and the security requirements of transaction execution. The ZKPs act as a mediator that allows untrusted conventional processors to produce verifiable proofs of correct execution, bridging the gap between flexible software execution and security requirements

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback through verification of zero-knowledge proofs. The executing node generates a proof and sends it to other nodes, which verify the proof to confirm correct execution. This feedback loop ensures that even though execution occurs on untrusted conventional processors, the security and integrity are maintained through cryptographic verification

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3803745B1Secure transactional system in a p2p architecture
Publication Date: 2022.11.16 MAIM ENRICO
  • EP3803745B1 patent drawingFigure 1
  • EP3803745B1 patent drawingFigure 2
  • EP3803745B1 patent drawingFigure 3

AI summary

The invention relates to a secure P2P transactional system comprising a set of nodes (WN) communicating by messages (WM), each message comprising data to be processed by a program (WP) and the hash of the program to be used at the destination node on the input data contained in this message, wherein, upon receiving a message and by using the hash contained in this message, each node is capable of causing the execution of the program to be used on the input data contained in said received message, said program generating an output message containing output data generated by the program and the hash of the program. The system is characterized in that at least certain programs are capable of being executed in a zero-knowledge proof mode (ZKP) and of including in output messages a zero-knowledge proof information for verification by the destination node.