# Multisig for a small team: the setup that does not lock you out

URL: https://www.caijing188.com/multisig-small-team/
Published: 2026-10-25T18:09:39+08:00 | Updated: 2026-10-27T22:09:49+08:00
Verified: 2026-10-27

## Quick answer
A 2-of-3 multisig survives one lost key and one compromise, which is why it fits a small team, while 3-of-5 suits a treasury and needs five maintained signers. Staked ETH showed the availability side as of October 2026, with an exit queue of 850,000 ETH, about 14.8 days. Test a recovery before funding.

## Summary
A threshold trades theft risk against availability risk, and most teams raise the count without pricing the second one. 2-of-3 is the small-team default because it tolerates one lost key and one compromise; 3-of-5 belongs to a treasury with a payment process behind it. Where the signers live matters more than how many there are, and a recovery drill before the first deposit is what proves the setup.

## Key takeaways
- Every extra signature buys theft resistance and spends availability
- Three keys in one flat on three devices from one vendor is a 1-of-1 in practice
- Most real losses come from procedure: a trusted initiator and an unchecked destination
- Staked ETH's exit queue held 850,000 ETH, about 14.8 days, in October 2026, which is the kind of clock a lockout compounds

## FAQ
Q: Is 2-of-3 enough for a company treasury?
A: It depends on the process behind it. 2-of-3 tolerates one lost key and one compromised key, which is adequate when three people genuinely control three devices in different places. If one person holds two signers, the effective threshold is 1 and the count on paper is misleading.
Q: What happens if a signer leaves the company?
A: The wallet keeps working until that signer's key is needed, and then it may not. Replace the signer before the departure, not after, and run a recovery drill with the new set. Turnover is the most common route from a working multisig to an unusable one.
Q: Should I use different wallet vendors for each signer?
A: Different vendors reduce the chance that one firmware flaw removes several signers at once. Different people, cities and devices matter at least as much. The test is whether a single event, a fire, a seizure or a bad update, can take two signers together.