Function-Level Permissions Control for Scalable Blockchain
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current permissioned blockchain architectures face scalability issues and are prone to single-point failures when implementing permissioned views across geography, limiting their ability to support a large number of views effectively.
Innovation Solution
The implementation of function-level permissions control on a blockchain using a kernel execution framework with function boundary detection, where function calls are checked against a set of permissions control rules to determine permitted or prohibited actions, allowing for dynamic and granular permission management without editing or redeploying smart contracts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If permissioned views are implemented using enterprise message bus solutions like KAFKA in a blockchain framework, then permissioned views can be established with topic-based partitioning, but scalability across geography is limited and single-point failures occur
Solution Approach 1:
The system segments the blockchain network into multiple independent permissioned view networks, each operating autonomously with its own consensus mechanism. This segmentation eliminates the single-point failure issue by distributing authority across multiple independent networks while maintaining scalability through modular architecture that can add new view networks without impacting existing ones.
Solution Approach 2:
The patent introduces a view manager as an intermediary component that coordinates between different permissioned view networks and the underlying blockchain. This mediator handles cross-network communication, permission verification, and data synchronization, enabling scalable geographic deployment while maintaining system reliability through centralized coordination of distributed components.
2Adaptability or versatility
If function-level permissions control is implemented by editing or redeploying smart contracts, then granular permission management is achieved, but system complexity and deployment overhead increase
Solution Approach 1:
The system performs preliminary action by pre-defining permission templates and function-level access control policies during smart contract deployment. These pre-configured permission structures are stored as immutable code in the contract, enabling granular permission management without requiring subsequent edits or redeployments. The permission logic is prepared in advance and automatically applied during execution.
Solution Approach 2:
The patent implements dynamic permission management through a configuration system that allows permission rules to be modified and updated without changing the underlying smart contract code. The contract contains flexible permission checking logic that can adapt to different permission configurations stored in external storage or configuration tables, enabling granular control while maintaining deployment simplicity.
Data Source
AI summary
Technologies are shown for function level permissions control for smart contract execution to implement permissions policy on a blockchain. Permissions control rules control function calls at a system level utilizing function boundary detection instrumentation in a kernel that executes smart contracts. The detection instrumentation generates a call stack that represents a chain of function calls in the kernel for a smart contract. The permissions control rules are applied to the call stack to implement permissions control policy. Permissions control rules can use dynamic state data in the function call chain. If the dynamic state data observed in function call chains does not meet the requirements defined in the permissions control rules, then the function call can be blocked from executing or completing execution. The permissions control rules can be generated for a variety of different entities, such as a domain, user or resource.