Home › Features › Backup & Recovery

Features · the auditable exit

The exit door is open-source

MPC wallet recovery your auditors can read on GitHub

Every key share backs up wrapped to an RSA key only you hold. Recovery runs in a public, MIT-licensed, offline desktop tool that reconstructs your keys without Vaultody's involvement or permission. Audit the exit before you move in.

Share the Trust, Guard the Keys

Create accountLive on testnet in an afternoon

Compare PlansIncluded in a plan, not an add-on

MIT-licensedrecovery tool, public on GitHub

offlineruns air-gapped, no network

3-of-5thresholds reachable by reshare

0on-chain moves in a reshare

The problem

Ask a custody vendor to show you the exit before you move in

Every vendor has a recovery story. Almost none of them let you read it. Vaultody's recovery path is a public, MIT-licensed desktop tool that runs offline: it takes your backup and your RSA private key and reconstructs your keys with the company entirely out of the loop. Your security team can review it before you onboard.

Wrapped to a key only you holdEach party's share is encrypted to an RSA public key you generate on your own machine. Vaultody stores the public half and never sees the private one.
Both curve families, every backupOne encrypted file per curve — ECDSA and EdDSA — so recovery restores everything, not just the popular chains.
Auditable, not describedThe tool is public and offline. Reading the code is the diligence step, not a call with our engineers.

How it works

Back up once, verifiably

Each party's share is encrypted to your RSA public key and delivered as a package with a step-by-step guide — covering both curve families (ECDSA and EdDSA) in every backup, so recovery restores everything, not just the popular chains.

✓Your RSA private key is the only recovery secret — store it cold
✓Backups from the mobile app go to storage you control
✓No third-party escrow, no recovery-as-a-service dependency

recovery — offline, open-source

$ vaultody-recovery \ --backup shares.zip \ --rsa-key ./recovery-key.pem ✓ shares decrypted (3/3) ✓ key reconstructed — ECDSA + EdDSA ✓ ran fully offline # MIT-licensed · inspect it on GitHub

Reshare: recovery without drama

A reshare ceremony rotates all shares while preserving the public key — and therefore every address. It is the lost-phone path, the employee-departure path, and the threshold-change path, with zero on-chain footprint.

✓Addresses never change — nothing moves on-chain
✓Add or remove client-side parties, adjust thresholds up to 3-of-5
✓Runs as a governed, approval-gated ceremony

reshare — lost phone

Old share

device lost

revoked

New share

new device enrolled

active

Addresses

unchanged — zero on-chain moves

preserved

How it works

The backup ceremony, end to end

Five steps, and the last one matters more than it looks.

01Generate your RSA key pair

Inside the recovery tool, on a machine you control. The private key is password-encrypted and never leaves that machine.

02Submit the public key

The vault records the public half and the backup moves to awaiting approval.

03Approve the request

Backup is an approval-gated action like any other sensitive operation.

04Download the package

A ZIP with a human-readable recovery guide and one encrypted JSON per curve. It is downloadable only while the backup sits in the approved state — capture it then.

05Finalize with the verification code

The code is printed in the guide inside the ZIP. Submitting it completes the backup — and until it completes, the vault cannot add further accounts.

Specification

Recovery specification

Including the parts a competitor would leave out.

ToolPublic, MIT-licensed, offline desktop application. Runs air-gapped; no network access required at any point.

InputsYour backup package and your RSA private key. There is no passphrase held by Vaultody and no escrow to petition.

Share combinationShares recombine by the scheme recorded in the backup — additive, multiplicative or Shamir with commitment verification.

OutputThe master private key for both curves, from which every address you ever derived can be reconstructed.

ReshareThe lighter path for a lost device or a departing employee: rotate all shares, keep the public key, keep every address, zero on-chain footprint.

Party changesThresholds extend to 3-of-4 and 3-of-5 on your side. Removing a party from a full n-of-n committee takes two ceremonies — lower, then remove.

InstallersDesktop builds are currently unsigned, so macOS and Windows warn on first launch. Verify the download against the published checksum.

Known gapsThere is no verify-only dry run that proves a backup is recoverable without assembling the key, and no fingerprint of your RSA public key to compare. Both are on the roadmap; neither is pretended away.

Frequently asked questions

Get answers to commonly asked questions.

What does recovery NOT depend on?

Vaultody. With your backups and your RSA key, the open-source tool derives your keys with the company entirely out of the loop — that is the design goal.

Is the recovery tool really public?

Yes — MIT-licensed, runs offline on an air-gapped machine. Your security team can review it before you onboard.

When do we reshare vs restore?

Lost device with the vault still operational → reshare (lighter). Catastrophic loss of a party → restore from backups. Both are documented procedures.