Account Key Derivation with Compute and View Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain transactions are publicly viewable, compromising user privacy and security by revealing account activities and token amounts.
Innovation Solution
Implement a system that generates and manages cryptographic keys for blockchain accounts, including an account private key and derivative keys such as compute, view, and graph keys, which are used to perform specific functions without revealing the private key, allowing trusted third parties to perform tasks while maintaining privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If blockchain transactions are made publicly viewable for transparency, then transaction verification and auditability are improved, but user privacy and security are compromised
Solution Approach 1:
The patent segments the account private key into multiple derivative keys (compute key, view key, graph key), each with specific functions. The compute key verifies transactions, the view key decrypts transaction data, and the graph key identifies account relationships. This segmentation allows different functions to be performed by different keys, enabling privacy preservation while maintaining transaction verification capability.
Solution Approach 2:
The patent introduces trusted third parties as intermediaries who hold derivative keys and perform specific tasks on behalf of account holders. These intermediaries can verify transactions, decrypt data, or analyze account graphs without having access to the full private key, thus acting as mediators between public transparency requirements and private key security.
2Ease of operation
If the account private key is shared with third parties for transaction management, then operational capability is improved, but security risk increases
Solution Approach 1:
The patent divides the private key functionality into separate derivative keys that can be independently shared with different third parties for specific tasks. For example, a compute key can be shared with a transaction processor, while a view key can be shared with an auditor. This allows operational capabilities to be distributed without compromising overall account security.
Solution Approach 2:
Different derivative keys have different functional qualities and security requirements. The compute key is optimized for transaction verification, the view key for data decryption, and the graph key for relationship analysis. By assigning specific qualities to each key, the system enables tailored sharing arrangements where each third party receives only the specific key capability needed for their function.
Data Source
AI summary
Key derivation for account management is disclosed, including: generating an account private key associated with a new account; generating a compute key associated with the new account based at least in part on the account private key, wherein the compute key is usable to verify a new transaction to be confirmed on a blockchain, and wherein the new transaction is initiated by the new account; and generating a view key associated with the new account based at least in part on the account private key, wherein the view key is usable to decrypt a portion of a confirmed transaction on the blockchain that belongs to the new account.