Modular Smart Contracts for Dynamic Blockchain Validation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing blockchain systems lack flexibility in design, requiring recoding and redeployment of smart contracts on all nodes for updates, and fail to efficiently manage attribute updates and privacy in transactions.

Innovation Solution

Implement modular smart contracts that allow for the addition of new attributes without overwriting old ones, preserving privacy by controlling access to attributes and enabling real-time tracking of data object states using world state databases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional smart contracts are used in blockchain systems, then transaction validation and execution are achieved, but updates require recoding and redeployment on all nodes, increasing complexity and time loss

Engineering Contradiction:

Improveflexibility in updating transaction validation criteriaVSAvoidtime required for recoding and redeployment

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The smart contract is divided into a static core logic component and a dynamic configuration component. The configuration component is stored as data objects in the blockchain that can be updated independently of the core logic, allowing validation criteria to be modified without recoding the contract itself.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system transitions from static smart contracts with fixed validation logic to dynamic contracts where validation criteria can be changed in real-time by updating configuration data objects on the blockchain, enabling adaptive transaction validation without redeployment.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If traditional smart contracts are used, then transaction processing is achieved, but adding new attributes requires overwriting old ones, losing historical data

Engineering Contradiction:

Improveability to add new attributes to data objectsVSAvoidloss of historical attribute data

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The data object structure uses versioning where each version contains all attributes from previous versions plus any new attributes. This nested structure allows new attributes to be added at any version level without deleting or overwriting historical attribute data, preserving the complete attribute history across all versions.

Inventive Principle:

Principle #7Nested doll (Nesting)

3Loss of information

If all attributes are made accessible in blockchain transactions, then transparency is improved, but privacy and security of confidential information deteriorate

Engineering Contradiction:

Improvetransparency of transaction dataVSAvoidexposure of confidential information

Core Design Contradiction:

Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The system implements different access qualities for different attributes within the same data object. Attributes are tagged with access control metadata that specifies which parties can read or write them, allowing confidential attributes to remain private while shared attributes remain transparent, all within the same blockchain transaction structure.

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS12423693B2Modular, configurable smart contracts for blockchain transaction processing

Publication Date: 2025.09.23 KPMG LLP

AI summary

The invention relates to systems and methods for providing modular and configurable smart contracts for blockchain applications. The smart contracts may be utilized to retain all transaction attribute values in a world state database of the blockchain-implemented ledger. The systems and methods can further provide for dynamically configurable metadata and rules for transaction attributes recorded on a blockchain transaction log. The metadata and rules corresponding to the transaction attributes may be dynamically updated and applied to the transaction attributes.