Identity-Based Blockchain Accounts for Scalable Multi-Signature Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing blockchain platforms face challenges with spatial limitations on data capacity, high transaction costs, slow processing speeds, limited scalability, and inadequate data access control, especially in handling computationally intensive smart contracts and enterprise data applications.

Innovation Solution

A blockchain system organized around digital identities using Stateful Merkle Trees (SMTs) and continuous growth, allowing flexible block synchronization frequencies and parallel processing, with integrated key management and synthetic transactions for inter-chain communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If traditional blockchain blocks with fixed data capacity are used, then security and immutability are maintained, but data storage efficiency and scalability are limited

Engineering Contradiction:
Improvedata storage capacityVSAvoidtransaction processing speed
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent segments the blockchain data structure by introducing multiple types of blocks (commit blocks, update blocks, delta blocks) that serve different functions. Commit blocks maintain security and immutability, while update and delta blocks enable efficient data storage and retrieval. This segmentation allows the system to scale data capacity without compromising the security of the core blockchain.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds temporal and hierarchical dimensions to the traditional linear blockchain structure. By organizing data into multiple block types with different retention policies and access patterns, the system creates a multi-dimensional data architecture that increases storage capacity while maintaining fast access paths for critical transactions.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Quantity of substance

If more data is stored in each block, then data capacity increases, but block validation time and transaction costs increase

Engineering Contradiction:
Improvedata capacityVSAvoidblock processing time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent extracts frequently accessed data and metadata from the main blockchain blocks into separate update blocks and delta blocks. This extraction allows the core commit blocks to remain small and fast to validate, while bulk data storage occurs in the extracted structures that can be processed in parallel and do not require full node validation for each transaction.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements partial validation strategies where not all blocks require full cryptographic verification. Delta blocks and update blocks use simplified validation mechanisms compared to commit blocks, allowing the system to process large volumes of data with appropriate levels of verification rather than exhaustive checking for every block.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If blockchain processing is sequential, then security and consistency are maintained, but processing speed and throughput are limited

Engineering Contradiction:
Improvetransaction throughputVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces dynamic processing modes that adapt to different block types and network conditions. Certain block types can be processed in parallel when consistency requirements allow, while critical security-related blocks maintain sequential processing. This dynamic approach optimizes throughput without sacrificing reliability for essential operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces intermediary structures (such as state roots, Merkle proofs, and validation layers) that mediate between parallel processing operations and the final consistent state. These intermediaries enable concurrent validation of multiple blocks while ensuring that the ultimate blockchain state maintains consistency through cryptographic verification of intermediate results.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If complex access control mechanisms are implemented, then data security and authorization are improved, but system complexity and processing overhead increase

Engineering Contradiction:
Improvedata access controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements local quality by applying different access control mechanisms to different parts of the data structure. Critical security-sensitive data in commit blocks uses strong cryptographic access control, while less sensitive data in update and delta blocks uses simpler authorization mechanisms. This localized approach provides appropriate security for each data type without uniformly increasing system complexity.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12580782B2Systems and methods for processing blockchain transactions
Publication Date: 2026.03.17 INVENIAM CAPITAL PARTNERS INC
  • US12580782B2 patent drawing
  • US12580782B2 patent drawing
  • US12580782B2 patent drawing

AI summary

A blockchain system has an identity-based blockchain account including a primary chain, a secondary chain, and at least one key book applying to the account, the at least one key book having a key page. The system includes: a hardware processor; and a memory device storing instructions. When the instructions are executed by the processor, they cause the processor to: record a multi-signature transaction originating from the account in the secondary chain; associate the transaction with the key page of the at least one key book, the key page including (i) a signature-authorization rule, and (ii) a plurality of keys corresponding to a plurality of transaction authorizers; record, in the secondary chain, an authorization of the transaction from a transaction authorizer of the plurality of transaction authorizers; and once a number of authorizations recorded on the secondary chain satisfies the signature-authorization rule, record the transaction on the primary chain for execution.