Threshold signature scheme for treasury wallets. Key shares, DKG ceremonies, emergency reshare, and multi-chain signing without ever reconstructing the private key.
The marketplace treasury uses a Multi-Party Computation (MPC) threshold signature scheme. The private key is split across all participating nodes and is never reconstructed at any point, not even during signing.
Each node holds a key share derived from a Distributed Key Generation (DKG) ceremony. To produce a valid signature:
No single node, and no subset below the threshold, can sign independently.
The threshold is set at 2/3 BFT standard (6667 basis points), with a minimum of 2 signers. For a 9-node network, the threshold is 6. This matches the Byzantine Fault Tolerance bound: the network can tolerate up to 1/3 faulty or malicious nodes.
| Wallet | Threshold | Purpose |
|---|---|---|
| Treasury | 67%+ of nodes | Primary marketplace funds, listing escrow |
| Rewards | 67%+ of nodes | Automated reward claim payouts |
Both wallets use the standard BFT threshold (67%) to ensure consistent security guarantees across all MPC operations. This prevents a compromised rewards wallet from being exploited at a lower threshold than the treasury.
Generates a shared public key and individual key shares without any trusted dealer.
Phase flow:
PREPARE -> COMMITMENT -> SHARE_EXCHANGE -> VERIFICATION -> FINALIZEDRedistributes key shares to a new participant set while preserving the same public key. Old shares are cryptographically invalidated.
Phase flow:
PREPARE -> COMMITMENT -> SHARE_EXCHANGE -> VERIFICATION -> FINALIZEDSame phase structure as DKG, but the old share holders act as dealers for the new set. After reshare completes, the previous shares cannot produce valid partial signatures.
Produces a threshold signature over a transaction digest.
Phase flow:
PREPARE -> NONCE_COMMIT -> NONCE_REVEAL -> PARTIAL -> FINALIZEDKey shares are encrypted at rest using AES-256-GCM. Each share file includes:
Shares are never written to disk in plaintext. The encryption key is derived from node-specific secrets.
An emergency reshare triggers automatically when more than 15% of nodes go offline. The protocol:
This prevents a slow leak of offline nodes from eventually dropping below the signing threshold.
| Chain | Curve | Signature Scheme |
|---|---|---|
| Bitcoin | secp256k1 | ECDSA |
| Ethereum | secp256k1 | ECDSA |
| Solana | Ed25519 | EdDSA |
Each chain has its own MPC wallet instance with independent key shares. A single DKG ceremony produces shares for one curve. Multi-chain support requires separate ceremonies per curve.