Circuit: Key Backup

Trustless Encryption and Storage for the Secrets You Cannot Lose

Q: What is Circuit Key Backup?

It is trustless encrypted storage for critical secrets. Your organization generates the keypair and holds the decryption key; Circuit stores only ciphertext it cannot decrypt. Retrieval requires your quorum's approval and is fully logged.

Q: Does Circuit hold my private keys?

Circuit holds only an encrypted copy of whatever you store, and it cannot decrypt or use it. You generate and hold the decryption key, which is split M-of-N across your team. Circuit cannot access, use, or reconstruct your keys.

Q: What can I store in Key Backup?

Seed phrases, private keys, wallet recovery kits, validator withdrawal keys, HSM and quorum material, Root CA and code-signing keys, PGP and SSH keys, exchange API secrets, or any text file you need secured.

Q: How is Key Backup different from Recovery and Response?

Recovery moves the assets out and Response stops an attack in flight, both without touching your keys. Key Backup is the backstop: it holds the key material you fall back on when the wallet stack itself has failed and you need the key back.

Q: What happens if Circuit is breached or subpoenaed?

Your secret stays encrypted. Circuit only ever holds ciphertext, and the decryption key is held by your team, split M-of-N, never by Circuit.

Encrypted storage for the secrets you cannot lose and cannot leave sitting in a safe. You hold the key. Circuit holds ciphertext that cannot be decrypted without it.

See it in Action ↗

The Problem

Every institution holds secrets it cannot afford to lose and cannot leave lying around.

Seed phrases, root keys, recovery kits, HSM and signing material. Keep them in-house and one fire, theft, or departure can be catasphropic. Hand them to a custodian and you have swapped one single point of failure for another, one that can be breached, subpoenaed, or go dark, taking your secrets with it.

Own The Encryption with
Circuit: Key Backup

Key Backup is durable, encrypted storage for your most critical material, where the decryption key is held only by your team. Each secret is encrypted by you, before it leaves your hands. Circuit stores the envelope and can never open it.

See it in Action ↗

Two Layers of Control

Org-Owned Decryption

The backup is encrypted to a keypair your organization generates and owns. Circuit never sees the private key and cannot request it. The key is split M-of-N across your trusted team, so no single person is a point of failure.

Policy Control

Retrieval takes approval from your quorum. Circuit enforces the policy you set and logs every request, approval, and download.

What you can store

Any secret, on any stack, including ones Circuit has never seen:

Seed phrases and private keys

Wallet recovery kits and validator withdrawal keys

HSM admin and quorum material

Root CA and code-signing keys

PGP and SSH keys

Exchange API secrets

Any text file you need secured

How It Works

01

Generate your keypair

Your organization creates and holds the decryption keypair, split M-of-N across your team.

02

Encrypt, then upload

Each secret is encrypted before it leaves your hands, so Circuit receives only ciphertext.

03

Verified at upload

Every secret is checked when you store it, not when you need it.

04

Retrieve under policy

When you need a secret back, your quorum approves and only your team can decrypt it. Every request, approval, and download is logged.