Core design principles

The DeRec standard is guided by a set of architectural and security principles that shape the protocol, message formats, and reference implementations. These principles ensure that decentralized recovery remains interoperable, secure, and implementation-neutral.

Standard-First, Not Product-First

DeRec is an open protocol specification. It is not a proprietary platform or managed service. The goal is to enable independent implementations that can interoperate through a shared protocol definition. The specification defines protocol flows, message schemas, and cryptographic responsibilities. Implementations may vary internally, but conformance to the protocol ensures interoperability.

Cryptographic Separation of Responsibilities

DeRec separates the Owner's possession of the Secret from the recovery material distributed to Helpers. The Owner splits the Secret into cryptographic shares using a threshold scheme; each Helper stores only one share, which on its own carries no information about the Secret. This separation reduces systemic risk and ensures that compromise of a single Helper does not expose sensitive data.

Threshold-Based Security

Security derives from a configurable threshold model. If n is the total number of Helpers and t is the recovery threshold, any set of at least t shares can reconstruct the Secret. Any set of fewer than t shares provides no information about the Secret. This model provides strong cryptographic guarantees while allowing applications to tune availability and resistance to collusion.

Explicit Protocol Coordination

All interactions between Owner and Helpers occur through defined protocol flows. Share storage, verification, and recovery are structured exchanges governed by message schemas and validation rules. This ensures deterministic behavior across independent implementations.

Interoperability through Structured Messages

DeRec uses structured message definitions (for example protobuf schemas) to define wire-level interoperability. Message structure, field semantics, and versioning rules are part of the specification. This enables language-agnostic implementations and forward-compatible protocol evolution.

Decentralization Without Central Coordination

DeRec achieves decentralization through independent Helpers and threshold reconstruction. It does not require blockchain infrastructure, global consensus, or a central coordinator. Decentralization is achieved at the recovery layer through the distribution of key shares across independent parties.

Explicit Trust Boundaries

The protocol makes trust assumptions explicit. The Owner environment is assumed to be trusted during protection and recovery. When an Owner identity spans multiple devices via the replica feature, every replica device shares the same trust boundary as the Owner — the protocol does not separate them cryptographically. Helpers are assumed to operate independently. Security holds as long as fewer than the threshold number of Helpers collude.

Implementation Neutrality

The standard does not mandate storage backends, authentication systems, user interfaces, or deployment models. These are implementation decisions. The protocol defines the requirements for protection and recovery while allowing implementations to choose their operational architecture.

Extensibility and Evolution

The protocol is designed to evolve without breaking interoperability. Message schemas support versioning, and cryptographic primitives can be upgraded over time. This enables the standard to adapt to new security requirements while maintaining compatibility between implementations.

Security Over Convenience

DeRec prioritizes explicit cryptographic guarantees over operational shortcuts. Recovery requires threshold participation and shares must be validated according to protocol rules. Failure cases and validation requirements are defined explicitly to preserve security invariants across implementations.