On-Chain Push MFA for Blockchain Authentication Status Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 2FA mechanisms cannot be directly adopted in Web3 due to the need for secret information to be publicly accessible in the blockchain, and existing solutions like U.S. Ser. No. 11/025,431B2 expose both authentication keys to potential hacking, lacking security in decentralized environments.

Innovation Solution

An on-chain push-mode multi-factor authentication system where the multi-factor authentication status is stored directly in the blockchain, using a multi-factor provider smart contract to manage and update authentication statuses across multiple blockchains, ensuring secure and efficient MFA without off-chain interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current 2FA mechanisms are adopted in Web3, then authentication security is improved, but the system complexity increases due to the need for off-chain interactions and oracle networks

Engineering Contradiction:
Improveauthentication securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the MFA status management functionality from off-chain oracle networks and relocates it directly to the blockchain smart contract. The multi-factor provider smart contract stores and manages authentication statuses on-chain, eliminating the need for complex off-chain communication infrastructure while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a push-mode authentication server as an intermediary between the user's wallet and the smart contract. This server handles the authentication logic and communicates with the blockchain, simplifying the overall system architecture by centralizing the mediation function rather than requiring direct complex interactions between multiple components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multi-factor authentication status is stored off-chain using oracle networks, then authentication flexibility is improved, but gas costs and transaction time increase

Engineering Contradiction:
Improveauthentication flexibilityVSAvoidgas costs
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent merges the MFA status storage function directly into the blockchain smart contract, combining what were previously separate off-chain oracle operations with the on-chain authentication process. This integration eliminates the need for additional gas payments to oracle networks while maintaining full authentication flexibility through the smart contract's built-in status management capabilities.

Inventive Principle:
Principle #5Merging (Combining)

3Stability of the object's composition

If authentication data is stored publicly in the blockchain, then transparency and immutability are improved, but user privacy and security are worsened

Engineering Contradiction:
Improvedata immutabilityVSAvoiduser privacy exposure
Core Design Contradiction:
Stability of the object's compositionVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by storing only the authentication status (a simple boolean or enumerated value) on the blockchain rather than sensitive user data. The actual user credentials and personal information remain private in the wallet or authentication server, while only the necessary authentication state is made publicly visible on-chain, thus maintaining transparency without exposing sensitive information.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12585740B2On-chain push-mode multi-factor authentication method and system for blockchain services
Publication Date: 2026.03.24 TELEFÓNICA INNOVACIÓN DIGITAL SL
  • US12585740B2 patent drawing
  • US12585740B2 patent drawing
  • US12585740B2 patent drawing

AI summary

A method and a system for multi-factor authentication for blockchain services are proposed. The method comprises holding, by a server, an account of an end-user, the account being identifiable via an accountID; associating the accountID with a clientAddr by executing a pairing process; establishing, by the end-user, using a software application, an approval status for a multi-factor service in the server; in response to said established approval status, calling, by the server, a changeStatus function of a multi-factor provider smart contract operating in at least one blockchain, the changeStatus function including the established multi-factor approval status, the clientAddr, and a certificate termed ownerAddr; modifying, by the provider, the established approval status in the blockchain; delivering, by the provider, a notification to the end-user via the server when the established approval status is modified in the blockchain; and retrieving, by a smart contract developer the established approval status from the provider.