Extensible Blockchain Object Model for Smart Contract Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current distributed ledger technologies (DLTs) lack a first-class object model, which restricts code reuse, requires manual coding conventions, and limits the ability to dynamically add functionality to smart contracts, leading to inefficiencies in managing and executing smart contracts across different ledger accounts.
Innovation Solution
Implementing a systemic extensible blockchain object model (XBOM) that includes a class manager infrastructure for creating and managing object instances within ledger account states, enabling late dynamic binding, object-oriented inheritance, and dynamic loading of method implementations, using ledger object identifiers (LOIDs), method identifiers (MIDs), and field identifiers (FIDs) to facilitate message passing and method execution across different ledger accounts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a first-class object model is implemented in DLT, then code reuse and dynamic functionality are improved, but system complexity increases
Solution Approach 1:
The patent implements a nested object model where class objects contain method implementations, which in turn contain object instances. This nesting structure allows code reuse through inheritance while maintaining a manageable hierarchical organization that reduces overall system complexity.
Solution Approach 2:
The class manager library serves multiple functions: it manages instantiation of all object instances, handles references to object instances, enables message passing, and supports inheritance. This multi-functionality reduces the need for separate components, thereby reducing system complexity while improving adaptability.
2Ease of manufacture
If manual coding conventions are used for smart contracts, then implementation simplicity is maintained, but development efficiency decreases
Solution Approach 1:
The system enables self-service through automatic method resolution and dynamic binding. When a message is sent to an object, the class manager library automatically resolves the appropriate method implementation based on the object's class and inheritance hierarchy, eliminating the need for manual coding conventions and significantly improving development efficiency.
Solution Approach 2:
The patent introduces dynamic method resolution where the binding between messages and method implementations is resolved at runtime rather than compile time. This dynamic behavior allows for greater flexibility and development efficiency while maintaining implementation simplicity through the automated nature of the resolution process.
3Reliability
If separate smart contract ledger accounts are used, then functional isolation is improved, but system resource utilization decreases
Solution Approach 1:
The patent merges the smart contract functionality directly into the ledger account state through object instances. Instead of having separate smart contract ledger accounts, the class manager library manages object instances within the existing account state, combining functional isolation with efficient resource utilization.
Solution Approach 2:
The ledger account state serves multiple functions by containing both the account balance and the object instances that represent smart contract functionality. This multi-functionality eliminates the need for separate smart contract ledger accounts, improving resource utilization while maintaining functional isolation through the object-oriented structure.
Data Source
AI summary
A method for processing one or more message passing transactions sent from one or more client computers to one or more distributed ledger accounts, of one or more distributed ledgers, executed on one or more distributed ledger nodes, the message passing transactions processed by one or more class manager infrastructure intrinsics.