Secure Token Wallet Version Switching for Safer Token Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing secure token wallets face challenges in maintaining security and efficiency during updates, with existing methods often requiring simultaneous updates of wallet codes and tokens, which can disrupt system security and performance.

Innovation Solution

A secure token wallet system that allows independent updates of wallet codes and tokens, automatically switching to a new token version upon detection during transactions, supporting both versions until the switch is complete, and utilizing a token exchange management unit for seamless transitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If simultaneous updates of wallet codes and tokens are performed, then system security is maintained through coordinated updates, but system disruption increases and update complexity worsens

Engineering Contradiction:
Improvesystem securityVSAvoidupdate complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the update process into two independent components: wallet code updates and token updates. The wallet code can be updated separately from the token, and vice versa. This segmentation allows each component to be updated independently without requiring coordinated simultaneous updates, reducing overall system complexity while maintaining security through independent update cycles.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If wallet code and token are updated independently, then update flexibility improves, but the coexistence period of multiple versions increases security risks

Engineering Contradiction:
Improveupdate flexibilityVSAvoidsystem security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements preliminary version checking before transactions. The wallet checks the version of the counterparty's wallet code or token before executing a transaction. If version incompatibility is detected, the transaction is rejected or upgraded appropriately. This preliminary action prevents security vulnerabilities from arising during the coexistence period of multiple versions, allowing independent updates while maintaining security.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If remote updates are used for hardware token wallets, then ease of update improves, but security during the update transition period may be compromised

Engineering Contradiction:
Improveease of updateVSAvoidsecurity during update
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent enables the wallet to automatically detect version mismatches and self-correct by refusing to process transactions with incompatible versions or by automatically initiating version synchronization. This self-service mechanism reduces reliance on remote updates while maintaining security, as the wallet autonomously manages version compatibility without requiring external intervention during critical update transitions.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP4517629B1Secure token wallet and electronic transaction system
Publication Date: 2025.12.31 GIESECKEDEVRIENT ADVANCE52 GMBH
  • EP4517629B1 patent drawingFigure 1
  • EP4517629B1 patent drawingFigure 2~3
  • EP4517629B1 patent drawingFigure 4~5

AI summary

A secure token wallet (11-14) of a transaction system, comprising: a token (21) of the transaction system, wherein a token version of the token (21) is an initial token version; and a token exchange management unit (29) for exchanging tokens in transactions. A token version for the secure token wallet (11-14) can be changed from the initial token version to a new token version. The secure token wallet (11-14) is configured to change (47) the token version for the secure token wallet (11-14), if the new token version is detected (46) in a transaction (45).