Threshold wallet where the private key is split across ALL nodes. Three ceremony types, two wallet tiers, multi-chain support, emergency reshare, and epoch batching.
The MPC (Multi-Party Computation) Treasury is a threshold wallet where the private key is split across ALL network nodes. No single node -- not even the foundation -- can spend treasury funds alone. There is no hot wallet to hack.
The private key is NEVER reconstructed. Not during key generation. Not during reshare. Not during signing. Each node holds a key share and produces a partial signature. Partial signatures are combined to create a valid on-chain signature without ever assembling the complete key. The full private key literally never exists in one place.
Runs once per asset to bootstrap a new key pair.
| Stage | What Happens |
|---|---|
| PREPARE | Coordinator broadcasts ceremony parameters, participants acknowledge |
| COMMITMENT | Each node generates a random polynomial and broadcasts commitments |
| SHARE_EXCHANGE | Nodes exchange encrypted key shares via pairwise channels |
| VERIFICATION | Each node verifies received shares against commitments |
| FINALIZED | Public key derived, key shares stored locally, wallet address usable |
All nodes participate simultaneously. Each receives a unique key share. The public key (wallet address) is immediately usable for receiving funds. The private key exists only as distributed shares that never leave their respective nodes.
Runs automatically when node membership changes (join or leave events).
| Stage | What Happens |
|---|---|
| PREPARE | Coordinator identifies old and new participant sets |
| COMMITMENT | Old shareholders commit to re-sharing their existing shares |
| SHARE_EXCHANGE | Old shares are redistributed to include new nodes |
| VERIFICATION | New shareholders verify they received valid shares |
| FINALIZED | New share set active, old shares from departed nodes invalidated |
The public key stays the same, so no fund migration is needed. This is triggered automatically when autoReshareOnMembershipChange is enabled (default: true).
Runs for each treasury transaction requiring an on-chain signature.
| Stage | What Happens |
|---|---|
| PREPARE | Coordinator broadcasts the transaction to sign |
| NONCE_COMMIT | Each signer commits to a random nonce |
| NONCE_REVEAL | Nonces are revealed and aggregated |
| PARTIAL_SIGN | Each signer produces a partial signature using their key share |
| FINALIZED | Partial signatures combined into a valid ECDSA or Ed25519 signature |
The resulting signature is indistinguishable from a normal single-key signature. No one can tell it was produced by an MPC ceremony.
Treasury Wallet (67%+ threshold):
Rewards Wallet (67%+ threshold):
Both wallets require the same 67%+ BFT threshold, ensuring a uniform security model across all MPC operations.
The MPC system maintains separate key pairs per chain:
| Chain | Algorithm | Usage |
|---|---|---|
| SOL | Ed25519 | SPL token operations, reward distributions |
| ETH | secp256k1 | ERC-20 distributions, staking contract |
| BTC | secp256k1 | Bitcoin treasury holdings |
| BTC_ORDINALS | secp256k1 | Ordinal-specific operations |
Each chain gets its own DKG ceremony and independent key shares. A compromise of one chain's shares does not affect other chains.
When network health degrades, the system triggers an immediate reshare without waiting for the standard grace period:
emergencyReshareHealthBps = 8500, meaning health drops below 85%)reshareGracePeriodMinutes); emergency reshare fires immediatelyheartbeatStalenessSecs)maxStaleShareSetHoursThe emergency reshare action type is EMERGENCY_RESHARE_INITIATED, broadcast as a protocol event.
Payouts are batched into epochs to minimize ceremony overhead:
OPEN --> CLOSING --> FUNDING --> SIGNING --> BROADCASTING --> CONFIRMED
--> FAILED| Stage | What Happens |
|---|---|
| OPEN | Claims accumulate as PENDING entitlements |
| CLOSING | Epoch cutoff reached, no new claims accepted |
| FUNDING | Verify treasury has sufficient balance for all claims |
| SIGNING | MPC SIGN ceremony produces batch transaction signature |
| BROADCASTING | Signed transaction submitted to the blockchain |
| CONFIRMED | On-chain confirmation received, claims marked SIGNED |
| FAILED | Transaction failed, claims returned to next epoch |
Default epoch frequency: 168 hours (weekly), governance-configurable. Each ceremony stage has a 30-second timeout (ceremonyStageTimeoutMs).
Any staked node can propose a treasury spend:
ceil(N * thresholdBps / 10000) where N is total staked nodesGovernance-approved spends are flagged in the foundation audit system so they do not trigger withdrawal warnings.
In production, the foundation master node (Node-1) manually activates the initial MPC DKG ceremony:
mpcTreasury.enabled flag starts as true but autoInitiateCeremony is falseinstrumentation.ts