Blockchain Access Control via Intermediary Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing blockchain systems lack effective mechanisms to control access and protect against security vulnerabilities, particularly in private blockchain networks where unauthorized access and malicious transactions can occur.

Innovation Solution

The implementation of a system comprising a security agent, a controller, an authenticator, a rules engine, and a policy engine, which works together to authenticate users, enforce access policies, and scan for malicious content before allowing transactions to proceed on the blockchain.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a public blockchain is used where anyone can become a miner and access the distributed ledger, then accessibility and decentralization are improved, but security vulnerabilities and unauthorized access risks increase

Engineering Contradiction:
ImproveaccessibilityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system segments the blockchain network into private and public portions, allowing selective access control. The private blockchain portion restricts mining and transaction initiation to authorized entities only, while the public portion maintains openness for verification and transparency, thus resolving the contradiction between accessibility and security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary access control layer between external users and the blockchain network. This intermediary validates identities and permissions before allowing access to private blockchain resources, enabling public accessibility while preventing unauthorized access and security vulnerabilities through controlled mediation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If permission is required to read information and conduct transactions on a private blockchain, then security is improved, but ease of operation and accessibility deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidaccessibility
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The system implements a universal authentication mechanism that handles multiple functions: identity verification, permission validation, and access control across different blockchain operations. This multi-functional approach maintains security through permission requirements while simplifying user interaction through a unified access interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If traditional blockchain consensus mechanisms are used, then decentralization is improved, but control over malicious transactions and unauthorized access deteriorates

Engineering Contradiction:
ImprovedecentralizationVSAvoidmalicious transactions
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies different quality characteristics to different parts of the blockchain system. The private portion implements centralized control with strict access permissions to prevent malicious transactions, while the public portion maintains decentralized consensus for verification. This local differentiation resolves the contradiction between decentralization and control over harmful activities.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12250218B2Systems and methods for controlling access to a blockchain
Publication Date: 2025.03.11 BLOCKSAFE TECHNOLOGIES INC
  • US12250218B2 patent drawing
  • US12250218B2 patent drawing
  • US12250218B2 patent drawing

AI summary

Systems and methods for controlling access to a blockchain are disclosed. The systems and methods are comprised of a security agent, a controller, an authenticator, a rules engine, and a policy engine. In certain embodiments, the security agent receives a message from an application, parses the message, and transmits the message to the controller if the message comprises one or more predetermined applicable rules or policies. The controller receives the message with its rules and policies, queries the rules engine and the policy engine to apply the rules and policies, and transmits an authentication request to the authenticator. The authenticator then requests an authentication signal from a user and transmits the results to the controller. The controller applies the results and forwards them to the security agent, which may or may not release the message to the blockchain depending the results.