Open-source · 2-of-2 MPC signer

A signature no one can forge, steal, or sign alone.

SOVRA splits your private key across two independent machines with threshold cryptography. Neither an AI agent running on your laptop, nor a single compromised server, can ever move your funds — every transaction needs both halves to consent.

Read the source ↗ See how it works
Threshold ECDSA · DKLs23 · Ethereum
01 — The concept

The key that was never whole.

A one-time Distributed Key Generation ceremony creates two independent shards on two machines. The complete private key is never assembled — not on disk, not in memory, not for an instant.

To sign, the two machines run a multi-party computation between them. The key exists only as mathematics distributed across both parties. Compromise one, and you hold exactly half of nothing.

02 — The threat model

One half is never enough.

Machine one
Raspberry Pi · your desk
SHARD ½
held locally · never leaves
Both
required
Machine two
Cloud cosigner
SHARD ½
separate trust domain
A1
An AI agent goes rogue on your laptop
It can reach one shard. It cannot produce a signature without the second party's cooperation.
Funds safe
A2
One machine is fully compromised
The attacker extracts a single shard — mathematically useless on its own.
Funds safe
A3
The cloud cosigner is breached
Same outcome. A valid signature requires both parties to independently consent to the exact transaction.
Funds safe
03 — How it works

Three moves to a verified transaction.

Step 01 · DKG
Generate

A one-time ceremony derives two shards over the DKLs23 protocol. Each machine keeps its own; the derived address is verified independently.

Step 02 · Sign
Cosign

Both cosigners run the threshold rounds peer-to-peer over one unsigned transaction, returning a single valid ECDSA signature.

Step 03 · Broadcast
Settle

The assembled signature is verified and broadcast to the network — publicly auditable on-chain, indistinguishable from any other signature.