SoloBox is a non-custodial, zero-knowledge vault designed to preserve and transfer access to digital assets and secrets over long time horizons — in other words, a vault that "outlives you." The project provides a privacy-preserving recovery and inheritance solution for private keys, credentials, and other sensitive data using cryptographic primitives and user-configured recovery mechanisms. ^[1]

Overview

SoloBox is a non-custodial digital information platform designed for encrypted data storage, digital inheritance, and scheduled information delivery. According to project documentation, the platform combines client-side encryption, distributed storage infrastructure, and zero-knowledge security principles to enable users to retain control of digital information without relying on custodial access models. ^[1] The platform utilizes end-to-end encryption, IPFS-based storage, and cryptographic key management systems that operate on user-controlled devices. SoloBox also incorporates inheritance and time-triggered delivery protocols intended to facilitate the transfer or release of information under predefined conditions. ^[1]

Products

SoloBox provides a collection of services focused on encrypted information storage, digital inheritance, and scheduled information delivery. These services operate within the platform's non-custodial architecture and are integrated with its cryptographic infrastructure. ^{[1] [2]}

SoloBox Vault

The SoloBox Vault serves as the platform's primary encrypted storage environment. According to project documentation, files are encrypted locally on user-controlled devices before being stored through an IPFS-based distributed storage network. ^[2] The platform's architecture is designed so that storage infrastructure processes encrypted data while cryptographic keys remain under user control. This approach aims to separate storage functions from decryption capabilities. ^[2]

Sentinel Protocol

The Sentinel Protocol is a digital inheritance mechanism designed to transfer access rights to designated beneficiaries following prolonged user inactivity. ^[2] The protocol incorporates heartbeat monitoring, configurable inactivity thresholds, grace periods, beneficiary verification procedures, and key-shard distribution mechanisms. The protocol aims to provide a structured process for information transfer when predefined inactivity conditions are met. ^[2]

Time-Capsule Protocol

The Time-Capsule Protocol is a time-triggered delivery mechanism that enables encrypted information to be released at a predefined future date. ^[2] The protocol utilizes cryptographic time-lock systems and automated release procedures intended to facilitate delayed delivery of digital information. According to project documentation, the protocol aims to support future information delivery while maintaining encrypted storage prior to release. ^[2]

Architecture & Technology

The SoloBox technology stack combines cryptographic security standards, distributed storage infrastructure, and client-side processing systems. According to project documentation, security-sensitive operations are designed to occur on user-controlled devices rather than on platform servers. ^{[1] [2]}

Zero-Knowledge Architecture

SoloBox utilizes a zero-knowledge architecture in which servers do not process, access, or store plaintext user information. According to the project, encryption and decryption operations occur exclusively on user devices, while platform infrastructure is limited to processing encrypted ciphertext and operational metadata. ^[1] This architecture aims to reduce reliance on service providers for information confidentiality by limiting access to cryptographic key material. ^[2]

System Architecture

SoloBox utilizes a three-layer distributed architecture designed to separate cryptographic operations, protocol execution, and data storage into distinct trust domains. According to the whitepaper, the architecture establishes separate operational boundaries intended to prevent platform infrastructure from accessing plaintext user information. ^[1]

Client Layer (Trust Anchor)

The Client Layer serves as the primary trust boundary of the SoloBox system. According to project documentation, encryption, decryption, key derivation, and cryptographic key management occur exclusively on user-controlled devices. The layer utilizes technologies including React Native, WebAssembly (WASM), Secure Enclave, Argon2id, and AES-256-GCM. According to the whitepaper, secret material is intended to remain within the client environment during normal operation. ^[2]

Logic Control Layer (Sentinel)

The Logic Control Layer is responsible for protocol execution and application services. According to the project, this layer hosts the Sentinel service, scheduled task execution systems, authentication processes, and API relay functions. The layer processes operational information required for protocol execution while remaining separate from cryptographic key material and plaintext user content. ^[2]

Distributed Storage Layer (Vault)

The Distributed Storage Layer is responsible for storing encrypted information through IPFS-based infrastructure. According to project documentation, encrypted files are stored as ciphertext and distributed across decentralized storage networks. ^[2] The layer stores encrypted data and does not perform decryption operations. This separation aims to isolate storage functions from cryptographic key management processes.

Cryptographic Standards

SoloBox utilizes a collection of cryptographic standards and security technologies intended to support encryption, authentication, and key management functions. According to the whitepaper, these technologies are implemented across both mobile and browser environments. ^{[1] [2]} The platform utilizes Argon2id for password-based key derivation, AES-256-GCM for authenticated encryption, Secure Enclave technology for device-level key protection, WebAssembly (WASM) environments for browser-based cryptographic operations, and libsodium cryptographic libraries for implementation support. ^{[1] [2]} These technologies are incorporated into the platform's broader security architecture and aim to support confidentiality, authentication, and key-management functions. ^[2]

Security Architecture

Security within SoloBox is based on client-side encryption, cryptographic key isolation, and separation between encrypted content and operational services. According to project documentation, the platform utilizes a security model intended to reduce exposure of plaintext information to platform infrastructure. ^[2]

Data Sovereignty

According to the poject, SoloBox is designed so that cryptographic keys remain under user control. Encryption and decryption operations occur on user devices, while stored information remains encrypted throughout storage and transmission processes. ^[2] This architecture aims to provide users with direct control over access to encrypted information. ^[2]

Threat Model and Defense Mechanisms

SoloBox describes a threat model that considers unauthorized access, infrastructure compromise, device loss, and network interception as potential risks. To address these risks, the platform incorporates client-side encryption, cryptographic authentication mechanisms, secure hardware integration, rate-limiting controls, and separation between encrypted data and operational services. These measures aim to reduce the impact of unauthorized access to infrastructure components. ^[2]

Ecosystem

The SoloBox ecosystem consists of users, distributed storage infrastructure, cryptographic systems, and protocol services responsible for inheritance and scheduled information delivery operations. Supporting infrastructure includes IPFS storage services, cryptographic libraries, browser-based cryptographic environments, mobile application frameworks, and device-level security technologies. ^[1]

According to project documentation, these components work together to support encrypted storage, information preservation, and protocol execution while maintaining separation between cryptographic operations and storage infrastructure. ^[1]

Use Cases

SoloBox is designed to support a variety of information-preservation and access-management scenarios. According to project documentation, potential use cases include:

• Personal document preservation
• Digital asset recovery planning
• Cryptocurrency seed phrase storage
• Digital inheritance management
• Family archive preservation
• Legal document retention
• Scheduled information delivery
• Business continuity planning
• Long-term encrypted data storage
• Estate management
• Cross-generational information transfer ^{[1] [2]}