Continued Anastasis protocol development
Work continues on the recovery protocol specification, with a focus on clarifying provider-side state handling and tightening the description of policy evaluation during recovery.
Privacy-preserving key recovery
Anastasis provides privacy-preserving recovery for cryptographic keys and digital credentials — without giving any single provider custody of your secret.
The problem
Strong cryptography protects users precisely because nobody else possesses their key. That same property is what makes loss final: if the key is gone, the asset, credential or encrypted data may be permanently inaccessible.
No backup
Risk of permanent loss
A lost device or forgotten passphrase can make the asset, credential or encrypted data unrecoverable.
Centralised backup
Custody and security risk
Someone or something must hold a recoverable copy — and becomes a target, a dependency and a liability.
Both options concentrate risk in one place. Anastasis provides a third option.
The Anastasis approach
Anastasis encrypts recovery information and distributes it across independent providers. Recovery can require several authentication methods and several providers, according to a policy chosen by the user or the organisation. No single provider is meant to hold enough information to recover the original secret.
The design assumption is deliberately conservative: providers are treated as independent parties that may fail, be compromised, or attempt to learn more than they should. The recovery policy — not a custodian's goodwill — decides what it takes to get a secret back.
The secret is encrypted on the user's own device and prepared for distributed recovery under a policy they choose.
Recovery information is stored across independent providers, none of which is meant to hold enough to reconstruct anything alone.
The legitimate user authenticates according to the chosen recovery policy, and the secret is reconstructed on their device.
Why Anastasis
No single provider needs to hold enough information to reconstruct the protected secret. Trust is spread across independent parties chosen by the user or the organisation.
The protocol is designed to minimise what recovery providers learn — about the secret, about the person recovering it, and about the other providers involved.
Combinations of providers and authentication methods can be configured to match an organisation's risk model, regulatory context and operational reality.
Anastasis is built on documented protocols, Free Software and interoperable components, so integrations can be reviewed and audited rather than taken on faith.
Recovery does not require handing the original secret to a single trusted custodian, so the recovery path does not become the weakest link.
Use cases
The same distributed recovery model applies wherever the loss of a key would be operationally, financially or legally serious.
Recover access to wallet keys without introducing centralised key custody.
Protect access to cryptographic assets while preserving strong self-custody properties.
Recover identity credentials and cryptographic identity keys.
Recover keys protecting critical files, infrastructure and applications.
Enable resilient recovery of keys used in payment infrastructure and digital money systems.
Recover cryptographic credentials used by connected devices and autonomous systems.
Security architecture
The architecture separates who authenticates a user from who can reconstruct a secret, and keeps the protected secret out of any central store.
| Scenario | Anastasis design goal |
|---|---|
| User device lost or destroyed | Recovery remains possible through the configured policy, without the original device. |
| A single provider is compromised | The protected secret should remain protected; one provider's material is designed to be insufficient on its own. |
| A provider database is leaked | Stored material should not reveal the original secret to whoever obtains the dump. |
| A provider becomes unavailable or ceases operation | Alternative recovery policies may remain usable, provided the policy was configured with redundancy. |
| The user forgets a password | Recovery need not depend solely on a memorised secret; other authentication methods can be part of the policy. |
| A provider tries to profile its users | The protocol is designed to limit what a provider learns about the user and about the wider recovery policy. |
Transparency
Anastasis is built around open protocols and Free Software. Security-sensitive infrastructure should be inspectable, auditable and interoperable — not accepted on trust.
Enterprise integration
Organisations evaluate Anastasis for recovery in wallets, digital asset platforms, payment systems, identity systems, cybersecurity products, encrypted storage and regulated digital infrastructure.
Latest development
Work continues on the recovery protocol specification, with a focus on clarifying provider-side state handling and tightening the description of policy evaluation during recovery.
The GTK reference client received usability work on the policy-configuration flow, making it clearer which combinations of providers and authentication methods a user is actually committing to.
Discussions are ongoing with wallet and payment teams evaluating Anastasis for recovery in self-custodial products. Pilot participants get direct access to the engineering team.
Ecosystem
GNU Anastasis is the open-source protocol and reference implementation. Anastasis SARL supports development, integration, deployment and research collaboration — and is who an enterprise talks to.
Tell us what you are protecting and how recovery has to work in practice. We will tell you plainly whether Anastasis fits today, or what would need to be true first.