Trusted Execution Environment for CBDC Node Privacy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed networks, such as those used for Central Bank Digital Currencies (CBDCs), face challenges in securely processing confidential data as nodes in the network have access to all computation data, violating user privacy and introducing security vulnerabilities, especially when using Zero Knowledge cryptography is complex and risky.

Innovation Solution

Implementing a Trusted Execution Environment (TEE) within nodes to perform computations securely, ensuring that untrusted components cannot access sensitive data, thereby maintaining privacy and security without increasing network complexity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If nodes in the distributed network perform computations transparently with full data access, then network simplicity and ease of operation are maintained, but user privacy and security are compromised as all nodes can access confidential transaction data

Engineering Contradiction:
Improveease of operationVSAvoidunauthorized access to confidential data
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent segments the node into two distinct execution environments: a trusted execution environment (TEE) for secure computation and a standard execution environment for network operations. This segmentation isolates confidential data within the TEE, preventing unauthorized access while maintaining overall network functionality and simplicity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The TEE acts as an intermediary between the node and the network. It receives data from the network, performs secure computations in isolation, and returns results without exposing confidential information to either the node operator or other network participants, thus mediating between security requirements and operational simplicity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If Zero Knowledge cryptography is used to protect confidential data, then user privacy is improved, but system complexity and development difficulty increase significantly

Engineering Contradiction:
Improveunauthorized access to confidential dataVSAvoidsystem complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent replaces complex cryptographic mechanisms (Zero Knowledge proofs) with a hardware-based trusted execution environment. This substitution achieves similar privacy protection goals through hardware isolation and memory protection mechanisms rather than through complex mathematical cryptography, thereby reducing software complexity.

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

Solution Approach 2:

Rather than implementing complex, long-term cryptographic solutions that require extensive developer knowledge and maintenance, the patent uses a simpler TEE approach that leverages existing hardware capabilities. The TEE provides a disposable security boundary that can be instantiated without requiring deep cryptographic expertise.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Productivity

If all nodes access and process all transaction data, then network efficiency and consensus are improved, but security vulnerabilities increase as nodes can access sensitive information

Engineering Contradiction:
Improvenetwork efficiencyVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments data access rights by creating isolated execution environments. Each node can participate in network consensus efficiently while the TEE ensures that sensitive transaction data remains isolated and inaccessible to node operators, thus maintaining both network efficiency and security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by providing different access characteristics to different parts of the system. Within the TEE, data is accessible to the computation logic but isolated from the node operator. Outside the TEE, data remains encrypted and inaccessible. This creates localized security zones that maintain overall network productivity while protecting sensitive information.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP4145322A1Systems and methods for implementing privacy layer in CBDC networks
Publication Date: 2023.03.08 FLUENCY GRP LTD
  • EP4145322A1 patent drawingFigure 1
  • EP4145322A1 patent drawingFigure 2
  • EP4145322A1 patent drawingFigure 3

AI summary

The invention provides a computer-implemented method for configuring a node to join a distributed network such as a CBDC network that enables secure computations to be performed. The invention also provides a computer-implemented method for securely operating on data in a distributed network such as securely performing transactions in a CBDC network. The invention enables this by requiring nodes to perform network-related computations in a trusted execution environment (TEE) within the node processing capabilities. As the TEE is a separate execution environment from the main unsecure computational resources of the node, it is not possible for the unsecure node components to gain access to data relating to the computations. In this manner, secure operation on data is enabled without the significant increase in complexity associated with Zero Knowledge cryptography.