Vault-Specific Policy Maps for Cryptoasset Custody
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain systems lack secure access control mechanisms for managing private keys, particularly in cryptoasset custodial systems, which can lead to risks of key loss or theft, especially when multiple users need access to cryptocurrencies, necessitating a trusted custodial system that ensures secure storage and retrieval of private keys while enabling participation in online protocols like staking and governance.
Innovation Solution
The implementation of Hardware Security Modules (HSMs) with custom firmware to securely manage and authenticate private keys, using air-gap switching to ensure availability for staking and governance protocols, and employing policy maps with cryptographic key management to enforce access control rules, allowing multiple users to approve actions through endorsement messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If private keys are stored securely in air-gapped hardware wallets, then security against theft is improved, but access control for multiple users and participation in online protocols deteriorates
Solution Approach 1:
The system segments private key management by creating separate vaults for different cryptoassets, each with its own policy map. The HSM is divided into logical components: secure key storage, policy authentication, and action checking. This segmentation allows different access controls for different assets while maintaining overall security.
Solution Approach 2:
The HSM acts as an intermediary between the air-gapped secure storage and online protocols. It mediates by authenticating policy maps, checking actions against policies, and enabling staking/governance operations without exposing private keys. The relay computer serves as another intermediary layer between online servers and the HSM.
2Reliability
If private keys are kept in air-gapped environment, then protection against breaches is improved, but availability for staking and governance protocols deteriorates
Solution Approach 1:
The system performs preliminary actions by pre-authenticating policy maps and pre-configuring vaults with their access control rules. The HSM is pre-loaded with cryptographic keys and policy authentication mechanisms, enabling it to quickly process staking and governance requests without compromising security.
Solution Approach 2:
The HSM maintains continuous availability for staking and governance protocols by keeping the air gap dynamically managed. The system allows frequent, controlled interactions for time-sensitive operations while maintaining the protective air gap, ensuring both security and protocol participation continuity.
3Reliability
If hardware security modules with custom firmware are implemented, then cryptographic key management security is improved, but device complexity increases
Solution Approach 1:
The HSM is designed as a universal device that performs multiple functions: secure key storage, policy map authentication, action checking, and support for multiple staking/governance protocols. This multi-functionality reduces the need for separate specialized devices while maintaining security.
Solution Approach 2:
The system manages complexity by making the HSM configurable through parameter changes. Custom firmware allows the HSM to adapt to different cryptoassets and protocols by changing operational parameters rather than requiring hardware modifications, simplifying deployment and maintenance.
4Measurement precision
If policy maps with vault-specific rules are enforced, then access control precision is improved, but system complexity increases
Solution Approach 1:
The system applies local quality by implementing vault-specific policy maps that define access control rules tailored to each individual vault. Each vault can have its own unique authentication requirements and permitted actions, allowing precise control without requiring complex global rules.
Data Source
AI summary
Methods, and systems for secure storage and retrieval of information, such as private keys, useable to control access to a blockchain, include: receiving a request to take an action with respect to a vault of multiple different vaults in a cryptoasset custodial system, and each of the multiple different vaults has an associated policy map that defines vault control rules; authenticating, by a hardware security module, a policy map for the vault on which the action is requested based on a cryptographic key controlled by the hardware security module; checking the action against the policy map for the vault when the policy map for the vault is authenticated based on the cryptographic key controlled by the hardware security module; and effecting the action when the action is confirmed to be in accordance with the policy map for the vault.