Wallet operations
MPC wallets
BroSettlement wallets use multi-party computation (MPC) so the normal signing path does not depend on one complete private key held in one place.
The target model is DKG-generated, 2-of-3 MPC:
- Client key share belongs to the client and is used by the client-run Co-Signer.
- BroSettlement key share is operated by BroSettlement for coordinated signing.
- Backup or recovery key share is stored separately for recovery workflows.
Why MPC
MPC lets your platform sign transactions without reconstructing a complete private key in one place. Each participant contributes a key share to produce a valid signature.
This keeps the wallet noncustodial by design while still supporting programmable API workflows for deposits, withdrawals, transfers, events, and reconciliation.
Wallet lifecycle
- Create wallet request
Your backend requests a wallet for an organization, chain, and use case.
- Generate key shares
DKG creates distributed key shares without reconstructing a full private key in one location.
- Activate address
BroSettlement returns the wallet address and marks the wallet ready for deposits.
- Sign transactions
Withdrawal signing requires the threshold signing flow and the client-run Co-Signer.
Signing policy
Use policy controls around withdrawals and signing approvals. Common controls include:
- Amount limits
- Destination allowlists
- Organization role checks
- Time-based restrictions
- Manual approval requirements