Chameleon Hash Access Control for Decentralized Data Ownership
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing decentralized ledger systems face challenges in efficiently managing data ownership, access, and transfer due to limitations in consensus protocols like Proof-of-Work and Proof-of-Stake, leading to inefficiencies in verifying transactions and maintaining data integrity.
Innovation Solution
Implementing chameleon hash functions to enable secure decentralized data ownership and access management, allowing WTRUs to register, provide access, revoke, and transfer data ownership using chameleon hash collision public parameters, and interacting with access control entities for verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Proof-of-Work or Proof-of-Stake consensus protocols are used for verification, then data integrity is maintained, but transaction verification efficiency deteriorates
Solution Approach 1:
The patent introduces an access control entity as an intermediary between data owners and data consumers. This entity manages access control lists and verification requests, reducing the computational burden on the distributed ledger system while maintaining security. The intermediary handles routine access control operations, allowing the consensus protocol to focus only on critical verification tasks.
Solution Approach 2:
The verification process is segmented into multiple components: data registration, access control list management, and transaction verification. By dividing the verification workload into discrete manageable tasks handled by different entities (data owners, access control entities, and consensus nodes), the system improves overall verification efficiency without compromising data integrity.
2Reliability
If decentralized ledger systems are used for data ownership management, then data security is improved, but system complexity increases
Solution Approach 1:
The access control entity serves multiple functions: it manages access control lists, processes verification requests, and coordinates with the distributed ledger system. This multi-functional approach reduces the number of separate components needed in the system, thereby reducing overall complexity while maintaining decentralized security.
Solution Approach 2:
Data owners can independently register their data and manage their own access control lists without requiring complex centralized management. The system enables self-service operations where participants can autonomously perform common tasks, reducing the complexity of system administration and coordination.
3Reliability
If chameleon hash functions are used for ownership verification, then data access security is enhanced, but computational overhead increases
Solution Approach 1:
Chameleon hash values and access control lists are pre-computed and stored during data registration. This preliminary action allows verification operations to use these pre-computed values rather than performing full cryptographic computations during each access request, significantly reducing computational overhead while maintaining security.
Solution Approach 2:
The system uses lightweight verification tokens and pre-computed hash values that can be quickly generated and discarded for each verification operation. These disposable verification objects require minimal computational resources compared to full cryptographic proofs, reducing the energy cost of frequent access verifications.
Data Source
AI summary
Procedures, methods, architectures, apparatuses, systems, devices, and computer program products for decentralized data control and access management. For example, a data owner may perform a subscription procedure to obtain verification credentials and an index (e.g., address, identifier) to public data control and access information. The data owner may perform a registration procedure to register ownership of data using the public data control and access information. The public data control and access information may include a public key. The public key is paired with a private trapdoor key to form a key pair. The data owner and a data consumer may perform an access procedure to grant access to registered data. For example, the registration procedure may verify collisions between a token hash, a data hash, and a data owner hash based on use of the key pair.


