Overview
DeRec Alliance is a non-profit that maintains a free, open standard for getting back things you cannot afford to lose: the key to a crypto wallet, a password, a passkey, a photo, a legal document. Rather than writing a recovery phrase on paper, you split the secret into scrambled fragments and give one to each of several helpers you pick yourself, such as friends, family, or a company offering the service. No single helper can read your secret, but enough of them together can hand it back1.
The standard is called Decentralized Recovery, or DeRec, and it runs without any blockchain1. The alliance that maintains it is a US non-profit whose founding members are drawn from several blockchain ecosystems, including Cardano developer Input Output Group2.
Key Features
- Nothing to write down and lose. DeRec replaces the paper backup with people. An owner pairs with at least three helpers, and the alliance recommends at least five, which leaves room and time to replace one or two before recovery is at risk3.
- Helpers see nothing. Each helper stores a scrambled fragment rather than the secret, and helpers never speak to each other or learn who else holds a piece4.
- Protection that repairs itself. The owner's device checks in with each helper on a schedule to prove the fragment is still intact. When a helper drops out for good, the secret is re-split among the rest, as long as at least three are still reachable3.
- Anything worth keeping, not only crypto. Blockchain keys, wallet recovery phrases, passwords, two-factor recovery codes, identity credentials, notes, and photos all fit, and the developer interface stores secrets in a generic container it calls a lockbox, which is how password managers integrate it3.
- Free to build on. The protocol is a royalty-free open standard from a US non-profit1, and its code carries the Apache-2.0 license, which allows commercial products5.
What to Expect
DeRec is not an app you download. The alliance is direct about this: look for wallets, password managers, and other software that build DeRec support into their own products, then pair with helpers from inside those apps3. Pairing can be done in person, with one person's app showing a QR code that carries a one-time value and the other scanning it, which is what stops a stranger from slipping into the middle of the exchange4.
On a new phone you install a DeRec-supporting app, choose to recover rather than start fresh, and pair again with enough of your helpers. Each helper has to satisfy itself that you are the same person who paired before, and the protocol leaves how that is done to the app, so that identity check is where the security actually sits4. If the bundle you protected included your list of helpers, you get all of them back at once instead of pairing again one by one4.
Developers and organizations come in a different door. The reference implementation is written in Rust and also targets the web6, and the documentation site walks through the architecture, the message flows, and integration paths for TypeScript, React Native, Go, and .NET7. Companies that join the alliance can run a helper service as a business line, vote on where the specification goes, and display a "Protected by DeRec" mark5.
