Skip to content

Recovery

In the VaultKeepR apps, fragmented recovery defaults to 3 of 5 fragments. The current SDK has the same default, defined by FRAGMENTED_DEFAULT_THRESHOLD, FRAGMENTED_DEFAULT_TOTAL and DEFAULT_FRAGMENTED_CONFIG.

Recovering your own vault and digital legacy are separate flows, in the open-source @vaultkeepr/recovery and @vaultkeepr/legacy packages.

The flow uses Shamir secret sharing. createFragmentedVault generates a random master key with generateMasterKey, encrypts the vault with that key, then splits it into five fragments with a threshold of three. encryptFragmentsForStorage encrypts storage fragments using the recovery identifier. The SDK threshold is configurable; for an existing vault, use the value recorded in its manifest.

The configuration names five channels: device, IPFS, contact, smart contract and API. This does not certify that all are available: check the channels you actually configured and whether you can retrieve the fragments.

Keep the required material separately:

  • The secret recovery identifier (generateRecoveryId), used to decrypt stored fragments. computeLookupIdHash computes the reference used to locate the manifest.
  • The manifest, with the encrypted vault CID, threshold and fragment locations, and access to the encrypted vault itself. Fragments do not replace vault data.
  • At least three valid, distinct fragments for the default configuration. The recovery ID alone cannot reconstruct the key.

combineFragmentsAndDecrypt reconstructs the key from the quorum of decrypted fragments, then decrypts the vault. This is not a new password-plus-wallet-signature key derivation. The client then persists the restored vault using the password requested by its recovery form.

The recovery README linked below still contains an older 2-of-3 example. It is not the current SDK or app default; refer to the constants and recovery code linked below.

We cannot reset your master password or decrypt your vault for you. Recovery needs the identifier, accessible encrypted vault data and the quorum of valid fragments. If these are lost or unavailable, recovery can fail; support does not hold a replacement key.

Before relying on fragmented recovery for a production vault, run a full dry run with a test vault: distribute the fragments, confirm the threshold restores access, and verify you can locate the recovery ID. Do not delete or overwrite the main vault until the flow has worked end to end.

@vaultkeepr/legacy implements time-locked inheritance backed by the VaultKeeperLegacy contract on Base L2. The owner registers a beneficiary list, a delay, and a grace period in days. The master key travels only inside ECIES envelopes encrypted to each beneficiary’s public key; the chain stores pointers, the beneficiary list, and timing, never keys.

A heartbeat mechanism (proof of life) pushes the deadline forward while the owner stays active. After the deadline passes without a heartbeat, a beneficiary can call claimLegacy and receive the master key and vault CID from the IPFS envelope bundle. The owner can revoke the setup at any time with revokeLegacy.