A treasury wallet your finance team can actually run
Company crypto tends to end up in one of two bad places: an exchange account in someone's name, or a multisig contract only the engineer who deployed it understands. Vault mode is the middle that is missing; multisig approvals, per-chain guardians and plain-English automation, in an interface built for people who close books.
Multisig without Solidity
Require a second approver before funds move, configured in the app rather than deployed as a contract.
Guardians per chain
Recovery is configured on-chain per network, so losing a device does not mean losing the treasury.
Rules in plain English
The AI Treasury Copilot takes instructions like convert anything above 50,000 USDT to fiat on Fridays.
Three security profiles, one wallet
ZenWallet ships three profiles and you switch between them as the situation requires. Everyday covers routine transactions with a lower daily ceiling. Trading raises the ceiling for active management. Vault requires multisig approval before anything moves.
A finance team typically runs operating funds in Everyday or Trading and holds reserves in Vault, so a single compromised device cannot reach the reserve.
| Profile | Daily limit | Approval required |
|---|---|---|
| Everyday | $5,000 | Single approval |
| Trading | $50,000 | Single approval |
| Vault | Set by policy | Multisig |
Why not just use a multisig contract
Contract-based multisig is the right answer for protocol treasuries and DAOs, and it is genuinely well-built. It is also developer-shaped: deployment, signer management, chain-by-chain setup and gas administration all assume someone technical owns it.
Most companies holding crypto do not have that person, or have exactly one and cannot afford them to be the single point of failure for treasury access. Vault mode gives the same approval discipline with configuration instead of deployment.
Recovery when someone leaves
Staff turnover is the quiet risk in company crypto. If access lives in one person's phone and one person's seed phrase, their resignation is a treasury incident.
ZenWallet has no seed phrase to hand over. Access rests on MPC key shares plus recovery factors: on-chain guardians configured per chain, email one-time passwords, WebAuthn biometrics and an optional TOTP authenticator. Reconfiguring who holds what does not require anyone to trust a piece of paper.
Common questions
Can I require two approvals before company crypto moves?
Yes. Vault mode requires multisig approval, so a single signer cannot move funds on their own.
Do we need a developer to set up a treasury vault?
No. Vault mode is configured in the app rather than deployed as a smart contract, which is the main practical difference from contract-based multisig tools.
What happens if the person holding access leaves the company?
There is no seed phrase to recover from an ex-employee. Access rests on MPC key shares and recovery factors including on-chain guardians, WebAuthn and TOTP, all of which can be reconfigured.
Which chains does Vault mode cover?
The same seven networks as the rest of the wallet: Ethereum, Bitcoin, Solana, Polygon, TRON, BNB Chain and TON. Guardians are configured per chain.