{"id":"solobox","title":"SoloBox","content":"**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\\]](#cite-id-KKFzY3QeMO3dae0H) \n\n## Overview\n\n**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\\]](#cite-id-KKFzY3QeMO3dae0H) \r\nThe platform utilizes end-to-end encryption,[ IPFS](https://iq.wiki/wiki/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\\]](#cite-id-KKFzY3QeMO3dae0H) \n\n## Products\n\n**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\\]](#cite-id-KKFzY3QeMO3dae0H)  [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n#### SoloBox Vault\n\nThe **SoloBox Vaul**t 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](https://iq.wiki/wiki/ipfs)-based distributed storage network. [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \r\nThe 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\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n#### 
Sentinel Protocol\n\nThe **Sentinel Protocol** is a digital inheritance mechanism designed to transfer access rights to designated beneficiaries following prolonged user inactivity. [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \r\nThe 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\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n#### Time-Capsule Protocol\n\nThe **Time-Capsule Protocol** is a time-triggered delivery mechanism that enables encrypted information to be released at a predefined future date. [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \r\nThe 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\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n## Architecture & Technology\n\nThe 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\\]](#cite-id-KKFzY3QeMO3dae0H)  [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n### Zero-Knowledge Architecture\n\n**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\\]](#cite-id-KKFzY3QeMO3dae0H) \r\nThis architecture aims to reduce reliance on service providers for information confidentiality by limiting access to cryptographic key material. [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n### System Architecture
\n\n**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\\]](#cite-id-KKFzY3QeMO3dae0H) \n\n#### Client Layer (Trust Anchor)
\n\nThe 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.\r\nThe 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\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n#### Logic Control Layer (Sentinel)
\n\nThe **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.\r\nThe layer processes operational information required for protocol execution while remaining separate from cryptographic key material and plaintext user content. [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n#### Distributed Storage Layer (Vault)
\n\nThe **Distributed Storage Laye**r 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\\]](#cite-id-WYhjhai8IPJuF5kI) \r\nThe layer stores encrypted data and does not perform decryption operations. This separation aims to isolate storage functions from cryptographic key management processes.\n\n### Cryptographic Standards
\n\n**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\\]](#cite-id-KKFzY3QeMO3dae0H)  [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \r\nThe 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 l**ibsodium cryptographic libraries** for implementation support. [\\[1\\]](#cite-id-KKFzY3QeMO3dae0H)  [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \r\nThese technologies are incorporated into the platform's broader security architecture and aim to support confidentiality, authentication, and key-management functions. [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n### Security Architecture
\n\nSecurity 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\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n#### Data Sovereignty
\n\nAccording 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\\]](#cite-id-WYhjhai8IPJuF5kI) \r\nThis architecture aims to provide users with direct control over access to encrypted information. [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n#### Threat Model and Defense Mechanisms\n\nSoloBox 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\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n## Operational Protocol\n\n**Operational Protocols**\r\nSoloBox incorporates operational protocols that manage inheritance, scheduled delivery, device migration, and beneficiary verification processes. These protocols are integrated into the platform's broader security and information-preservation framework.\n\n**Sentinel Protocol**\r\nThe Sentinel Protocol utilizes periodic heartbeat verification to determine user activity status. According to the whitepaper, inactivity is measured against predefined thresholds and grace periods configured by the user.\r\nIf inactivity conditions remain unresolved, the protocol may initiate inheritance procedures that transfer designated access rights to approved beneficiaries according to predefined configurations.\n\n**Time-Capsule Protocol**\r\nThe Time-Capsule Protocol implements time-based release conditions for encrypted information. According to project documentation, information may be configured for delivery at a predefined future date.\r\nThe protocol utilizes cryptographic time-lock mechanisms and automated execution procedures that aim to facilitate delayed information delivery while maintaining encrypted storage before release conditions are met.\n\n**Cross-Device Migration**\r\nSoloBox supports migration between devices without transmitting plaintext cryptographic keys across a network. According to the whitepaper, key reconstruction occurs locally through password-derived cryptographic processes.\r\nCloud infrastructure functions only as a carrier for encrypted supporting data, while cryptographic operations remain on user-controlled devices.\n\n**Beneficiary Verification**\r\nThe platform incorporates beneficiary-verification procedures intended to reduce unauthorized access during inheritance events. According to project documentation, verification procedures include credential validation, rate-limiting mechanisms, and temporary restrictions following repeated unsuccessful verification attempts.\r\nThese procedures aim to support controlled access during inheritance-related operations.\n\n## Ecosystem\n\nThe **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](https://iq.wiki/wiki/ipfs) storage services, cryptographic libraries, browser-based cryptographic environments, mobile application frameworks, and device-level security technologies. [\\[1\\]](#cite-id-KKFzY3QeMO3dae0H) \n\nAccording 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\\]](#cite-id-KKFzY3QeMO3dae0H) \n\n## Use Cases\n\n**SoloBox** is designed to support a variety of information-preservation and access-management scenarios. According to project documentation, potential use cases include:\n\n* Personal document preservation\n* Digital asset recovery planning\n* Cryptocurrency seed phrase storage\n* Digital inheritance management\n* Family archive preservation\n* Legal document retention\n* Scheduled information delivery\n* Business continuity planning\n* Long-term encrypted data storage\n* Estate management\n* Cross-generational information transfer [\\[1\\]](#cite-id-KKFzY3QeMO3dae0H)  [\\[2\\]](#cite-id-WYhjhai8IPJuF5kI) \n\n##\n\n##\n\n​","summary":"SoloBox is a non-custodial zero-knowledge vault for long-term recovery and inheritance of digital assets and secrets, using client-side encryption, threshold sh...","images":[{"id":"QmX29qD5c4ML9Hi9xMMnHRqRCA1qBk7uGA15HiWdJWMKZc","type":"image/jpeg, image/png"}],"categories":[{"id":"projects-and-protocols","title":"Projects & Protocols"}],"tags":[{"id":"Identity"},{"id":"Infrastructure"},{"id":"Privacy"}],"media":[{"id":"QmSmKfGavNqCA5QJA6YouNEMRwdfX16oWSeYbMeKi5M6Ek","size":null,"name":null,"type":"GALLERY","source":"IPFS_IMG"},{"id":"QmbpXmVh8YwPJyCMJzpXsE3tt4NmUwQCYX9JaKRS5W8Lbu","size":null,"name":null,"type":"GALLERY","source":"IPFS_IMG"},{"id":"QmYv8aV7XF4EzHwd35w6C2UZ2VmJVbG1rSDfMHrd4fz8Ct","size":null,"name":null,"type":"GALLERY","source":"IPFS_IMG"}],"metadata":[{"id":"website","value":"https://soloboxapp.com"},{"id":"twitter_profile","value":"https://x.com/SoloboxApp"},{"id":"telegram_profile","value":"https://t.me/soloboxcommunity"},{"id":"youtube_profile","value":"https://youtube.com/@SoloboxApp"},{"id":"facebook_profile","value":"https://facebook.com/SoloBoxApp"},{"id":"references","value":"[{\"id\":\"KKFzY3QeMO3dae0H\",\"url\":\"https://www.soloboxapp.com\",\"description\":\"SoloBox site\",\"timestamp\":1780801608423},{\"id\":\"WYhjhai8IPJuF5kI\",\"url\":\"https://www.soloboxapp.com/whitepaper\",\"description\":\"SoloBox whitepaper\",\"timestamp\":1780801608423}]"},{"id":"previous_cid","value":"\"https://ipfs.everipedia.org/ipfs/QmaQSDJQut7JMX3sxe1fANDmJWCVAgTmS4y1DmZNXbxqnx\""},{"id":"commit-message","value":"\"Removed SoloBox detailed description and overview\""},{"id":"previous_cid","value":"QmaQSDJQut7JMX3sxe1fANDmJWCVAgTmS4y1DmZNXbxqnx"}],"events":[],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x8AF7a19a26d8FBC48dEfB35AEfb15Ec8c407f889"},"operator":{"id":"0x2D403Be9b67bE06FFEEb7C2681e19FB4D0eeA48b"},"language":"en","version":1,"linkedWikis":{"blockchains":["ethereum"],"founders":[],"speakers":[]},"recentActivity":"{\"items\":[{\"id\":\"525b1299-9b6c-4067-ab95-a500b86ec056\",\"title\":\"SoloBox\",\"description\":\"SoloBox is a non-custodial zero-knowledge vault for long-term recovery and inheritance of digital assets and secrets, using client-side encryption, threshold sharing, and verifiable recovery triggers.\",\"timestamp\":\"2026-06-07T17:35:47.854Z\",\"category\":\"projects-and-protocols\",\"status\":{\"icon\":\"RiGlobalLine\",\"label\":\"Wiki Updated\",\"iconClassName\":\"text-green-500\"},\"user\":{\"name\":\"0x8AF7a19a26d8FBC48dEfB35AEfb15Ec8c407f889\",\"address\":\"0x44864d85CAe284ca28D010f741bb26A336756E94\"},\"button\":{\"label\":\"View Summary\",\"icon\":\"RiFileTextLine\"},\"summarySections\":[{\"title\":\"Categories\",\"subtitle\":\"Category/tag entries were changed\",\"variant\":\"modified\",\"changeCount\":2,\"changes\":[\"Removed category id 'organizations'\",\"Added category id 'projects-and-protocols'\"]},{\"title\":\"Content\",\"subtitle\":\"Main article content was replaced — the previous product/company profile was removed and a technical project description was added\",\"variant\":\"modified\",\"changeCount\":22,\"changes\":[\"Removed opening description and product-focused profile about SoloBox as a maker of pannier racks and motorcycle accessories (product overview, features, ecosystem, use cases, architecture, tokenomics, confirmed partnerships, references)\",\"Removed section: Overview\",\"Removed section: Products\",\"Removed section: Features\",\"Removed section: Ecosystem\",\"Removed section: Use Cases\",\"Removed section: Architecture\",\"Removed section: Tokenomics\",\"Removed section: Confirmed Partnerships\",\"Removed section: References\",\"Added section: Overview [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added section: Products [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added subsection: SoloBox Vault [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added subsection: Sentinel Protocol [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added subsection: Time-Capsule Protocol [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added section: Architecture & Technology [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added subsection: Zero-Knowledge Architecture [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added section: System Architecture and its layers (Client Layer / Logic Control Layer / Distributed Storage Layer) [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added section: Cryptographic Standards [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added section: Security Architecture (including Data Sovereignty and Threat Model) [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added section: Ecosystem (updated to describe distributed storage, cryptographic systems and supporting infrastructure) [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\",\"Added section: Use Cases (digital inheritance, seed phrase storage, legal document retention, scheduled delivery, etc.) [[1]](#cite-id-KKFzY3QeMO3dae0H) [[2]](#cite-id-WYhjhai8IPJuF5kI)\"]},{\"title\":\"Events\",\"subtitle\":\"Event/item identifiers were replaced and multi-date fields were added (null)\",\"variant\":\"modified\",\"changeCount\":3,\"changes\":[\"Removed event id '35617c5f-b5d3-4787-ab52-67857868aff7' and added event id 'b3b84284-1d12-4ca3-a6cc-f4151fd7364d'\",\"Removed event id '9c18a607-8ca7-4947-a5db-c80af5538f1c' and added event id '77558e51-7a41-46ea-85a3-c964fa78253b'\",\"Added fields 'multiDateStart': null and 'multiDateEnd': null to event item(s)\"]},{\"title\":\"Blockchains\",\"subtitle\":\"Blockchain support list was updated\",\"variant\":\"modified\",\"changeCount\":2,\"changes\":[\"Removed empty blockchains array\",\"Added blockchain 'ethereum'\"]},{\"title\":\"Speakers\",\"subtitle\":\"Speaker list structure changed from an empty array to multiple speaker objects with null values\",\"variant\":\"modified\",\"changeCount\":4,\"changes\":[\"Removed speakers: []\",\"Added speaker object with fields name: null, size: null\",\"Added speaker object with fields name: null, size: null\",\"Added speaker object with fields name: null, size: null\"]},{\"title\":\"References\",\"subtitle\":\"Reference entries were replaced with a new reference list\",\"variant\":\"modified\",\"changeCount\":3,\"changes\":[\"Removed reference id 'GE4XRAsPHE0IvwbU' (https://www.stromtrooper.com/threads/solobox-customer-service-review.439753)\",\"Added reference id 'KKFzY3QeMO3dae0H' (https://www.soloboxapp.com)\",\"Added reference id 'WYhjhai8IPJuF5kI' (https://www.soloboxapp.com/whitepaper)\"]},{\"title\":\"Metadata\",\"subtitle\":\"New metadata field added\",\"variant\":\"added\",\"changeCount\":1,\"changes\":[\"Added 'wiki_score' with value '58'\"]},{\"title\":\"Summary\",\"subtitle\":\"Top-level summary text was updated to reflect a different project focus\",\"variant\":\"modified\",\"changeCount\":2,\"changes\":[\"Updated summary from: \\\"SoloBox is a versatile storage and utility solution, designed to offer durable and adaptable space management options. Known for its customer-focused service, it serves a range of applications from personal to industrial use.\\\"\",\"To: \\\"SoloBox is a non-custodial zero-knowledge vault for long-term recovery and inheritance of digital assets and secrets, using client-side encryption, threshold sharing, and verifiable recovery triggers.\\\"\"]},{\"title\":\"Tags\",\"subtitle\":\"Tag/topic identifiers were added and removed\",\"variant\":\"modified\",\"changeCount\":5,\"changes\":[\"Removed tag id 'DataPlatform'\",\"Added tag id 'Infrastructure'\",\"Removed tag id 'Infrastructure'\",\"Added tag id 'Privacy'\",\"Added tag id 'Identity'\"]}]}]}"}